Proxmox Takes 15 Minutes to Boot: "Reading all physical volumes. This may take awhile..."

[noahajac]

I've been trying to wrap my head around this issue for awhile now. I have Proxmox hosted on a Dell R720 with various drives put together into virtual drives using Dell's RAID card. Everything works well except for an about 15 minute delay during booting. The console shows:

Reading all physical volumes. This may take awhile...

and then seemingly hangs (see first picture) for about 15 minutes until it shows all my logical volumes "activated" (see second photo). I tried running `systemd-analyze blame` but it shows nothing useful, indicating this is an issue before systemd starts.

Also attached is dmesg, which shows an obvious jump from

[7.868970] random: 7 urandom warning(s) missed due to ratelimiting

and

[815.865931] device-mapper: thin: Data device (dm-3) discard unsupported: Disabling discard passdown.

I don't really see what the urandom warning has to do with my LVMs though. I also attached my GRUB config.

I understand boot will take a few minutes but ≈15min seems excessive. I've seen other forum posts with this issue although they don't seem to be relevant to my situation other than one which suggested removing "quiet" from my kernel command line. This still resulted in the hang but the console shows the urandom warning from earlier.

Hopefully someone can help me out. Thanks!

 

[udo]

Hi,
only an guess - do you have any volumes connected with the idrac (or remote console)?
Do you have disabled Sata* and Iscsi in the bios?
* I assume you don't use the internal sata-port due an Perc?!

Is your bios up to date?


Udo

 

[noahajac]

Hi,
only an guess - do you have any volumes connected with the idrac (or remote console)?
Do you have disabled Sata* and Iscsi in the bios?
* I assume you don't use the internal sata-port due an Perc?!

Is your bios up to date?


Udo

BIOS is up to date. Internal SATA is used for the Proxmox boot drive (has srv01gr_pve which is active before the hang), I believe I left it at the default AHCI mode. No remote volumes attached. Thank you for the response!

 

[furmansk]

I ran into this after trying to enable IOMMU on my HP machine. I set it in the systemd-boot cmdline script. I was editing the grub config and IOMMU would never show up as being enabled after following instructions. Then I looked to see if I was using grub or systemd-boot and turns out it was using the latter. Setup the boot config stuff for it and now I am having this same thing where it scans for drives. Does it do it every time?

 

[noahajac]

I ran into this after trying to enable IOMMU on my HP machine. I set it in the systemd-boot cmdline script. I was editing the grub config and IOMMU would never show up as being enabled after following instructions. Then I looked to see if I was using grub or systemd-boot and turns out it was using the latter. Setup the boot config stuff for it and now I am having this same thing where it scans for drives. Does it do it every time?

Yes, it is done every time and as far as I'm aware GRUB is used.

 

[furmansk]

Yes, it is done every time and as far as I'm aware GRUB is used.

So mine never booted. I had to go into a ubuntu live image and reset my /etc/kernel/cmdline file back to default. I can't figure out why it is booting with systemd-boot but uses the grub config file in /etc/default/grub. I guess I will need to make a post about this and stop hijacking yours haha.