Install stuck on "SATA link down"

[fS31w6YeqMdrL715yZoV]

Hi there,

I'm currently trying to install proxmox on a new server, and for some reason the install doesn't seem to go very far and stops after about 2 seconds with an error message "SATA link down".

Here is the full log from the install.


I have already tried:
- "nomodeset" parameter
- installing a previous PVE version (7.4)
- plugging in a random HDD in one of the SATA ports, just to check. It is recognized, but the install still doesn't proceed.

Hardware:
Intel N150
no graphics card
no HDD plugged in
one SSD (future PVE OS drive) in PCIe

Any idea how I could proceed? I'm not sure what the problem is here.

Thanks!

 

[cheiss]

The "SATA link down" message isn't an error, just informal, FWIW. The kernel prints something about each SATA port it detects.

Have you tried the Install Proxmox VE (Console) install option?
You can try booting in Debug mode (under the Advanced Options menu) and see how far you get there and/or if you get a shell.

Otherwise, you can also try installing plain Debian 12 and see if that works - and then Proxmox VE on top: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_install_proxmox_ve_on_debian
That is also supported, but requires some extra setup.

 

[fS31w6YeqMdrL715yZoV]

Thank you for the quick reply!

The "Install Proxmox VE (Terminal UI, Serial Console)" and "Install Proxmox VE (Serial Console Debug Mode)" both lead to a black screen without anything showing after "loading initial ramdisk".

The debian install also leads to a dead end, stopping right after the SATA ports check:


Is there something I should pay attention to in the BIOS maybe?

 

[cheiss]

The "Install Proxmox VE (Terminal UI, Serial Console)" and "Install Proxmox VE (Serial Console Debug Mode)" both lead to a black screen without anything showing after "loading initial ramdisk".

Did you try with the nomodeset parameter too?

The debian install also leads to a dead end, stopping right after the SATA ports check:

So basically the same problem, so at least not something specific to our kernel.

Is there something I should pay attention to in the BIOS maybe?

I'd first suggest updating the BIOS, if available. Maybe that fixes something. You can also search for anything related to AHCI, maybe. Virtualization settings (such as e.g. VT-d) shouldn't affect booting, but you can try messing with them too.

In any case, seems like a firmware issue, especially these cheap boards often have very shoddy firmware.