@felices this is the method you should try:
- download and decompress generic-x86-64 balenaOS for your application via balenaCloud
- unwrap the payload image from the flasher image using using GitHub - balena-os/balena-image-flasher-unwrap: Tool for unwrapping balena-image from a balena-image-flasher into
output/ - copy the image to your server rescue system
- from the rescue boot, run
dd if=output/balena.img of=/dev/{{disk}} bs=4M - reboot
Your server should appear in your balenaCloud app/dashboard shortly.
If it doesn’t, try doing to same with the development variant on balenaOS so you can SSH in and see what’s going on. If you can see the OS booting but are unable to get network connectivity (ping), it would suggest the NIC in the proliant isn’t part of the NICs supported by the packaged kernel modules, in which case you’ll need to build one manually and create a custom version of the OS. Some examples here.