Fail at boot on a clear Proxmox 5.1.3 installation

[jaime.fuentes]

Hi,

I tried to install the latest 5.1 Proxmox ISO many times, but has some issues with boot. On the installer, I chose ZFS (RAID 1) option. On first boot, it stopped on the initram without any zfs volume mounted. I had to mount manually with 'zpool import -N rpool' after 'exit'.

At this moment, the boot process continues bat stop with 'A start job is running for Activation of LVM2 logical volumes ...'. I uploaded a screenshot to show.

I tried to look for this problem everywhere, but can't find any help. Could you help me please?

Regards,

 

[Rob Loan]

I know it sounds funny, but turn on both legacy and uEFI boot options in your BIOS. Proxmox will boot via the legacy partition, but the devices will be enumerated correctly. (the copy of /etc/zfs/zpool.cache in /boot/initrd.img* isn't using /dev/disk/by-id/* so it can't find the pool as the devices have been renamed from the cdrom boot instance where the pool was made)

 

[jaime.fuentes]

I had UEFI enabled in the BIOS during the installation, but I can't understand this.

I had solve the problem with the zfs volume at boot with this: https://forum.proxmox.com/threads/failed-to-import-pool-rpool.29942/

But the problem with "A start job is running for Activation of LVM2 logical volumes ..." persists. The system can't start, because LVM2 volumes activation never ends. Is there any way to disable LVM2 at boot?

 

[jaime.fuentes]

Could the problem comes from udev???

Failed start udev ....

 

[fabian]

try installing using the 5.0 iso and then upgrade to the most recent package versions. there was a kernel bug in most of 4.13 which affected certain SCSI controllers..

 

[jaime.fuentes]

Thanks a lot fabian! You solved my problem in a couple of servers.

it's enough with the no-suscription to update the most recent packages?

Best regards,

 

[fabian]

Thanks a lot fabian! You solved my problem in a couple of servers.

it's enough with the no-suscription to update the most recent packages?

Best regards,

yes

 

[levifig]

Same thing happened to me on a Supermicro X9DR7-LN4F, just FYI. 5.0 ISO worked fine, though updating didn’t update versino number (not sure if that’s expected thought).

Cheers.

 

[fabian]

Same thing happened to me on a Supermicro X9DR7-LN4F, just FYI. 5.0 ISO worked fine, though updating didn’t update versino number (not sure if that’s expected thought).

Cheers.

you might want to check your package repositories and the apt output.