After installing Proxmox (7.1) to a 64gb USB, on a Dell R620 w/H710 mini and no drives installed, I ran into an issue that after quite of bit of researching. I was able to piece together what happened and how I managed to fix it and just figured I would post for anyone else who runs into this.
Using fohdeesha method of flashing the H710 mini to an IT firmware. I went ahead and installed proxmox 7.1 (yea, I need to update it) to a 64gb usb I installed in the R620. After doing this it booted up with no issues and after configuring proxmox and waiting a day, I got my drives in and put them all in the server and fired it up. This time I ran into a "cannot process volume group pve" and kept getting dropped the busybox cli. After some read and testing, found that everytime I added a new drive it was re-ordering the drives at boot then handing it off to grub and would fail. Needless to say I found quite a few threads on here that cover the problem, but don't really get to the bottom of the issue. But I did want to say this is what fixed it for me.
Pulled the drives, got the server to do a good boot to my fresh install. SSH into the box and edited the '/etc/default/grub' file and added...
after saving the file, I ran...
shut the server down, re-added all the drives and powered it back up. This time it booted up with no issues.
I don't know if it's just not good on a basic system to have these extra commands in grub, but with as many times as this has been an issue for people. I'd hope it would finally get fixed in proxmox.
Which, I did finally make a new proxmox 7.3-4 boot disc and tried this all over and had the same issue.
Using fohdeesha method of flashing the H710 mini to an IT firmware. I went ahead and installed proxmox 7.1 (yea, I need to update it) to a 64gb usb I installed in the R620. After doing this it booted up with no issues and after configuring proxmox and waiting a day, I got my drives in and put them all in the server and fired it up. This time I ran into a "cannot process volume group pve" and kept getting dropped the busybox cli. After some read and testing, found that everytime I added a new drive it was re-ordering the drives at boot then handing it off to grub and would fail. Needless to say I found quite a few threads on here that cover the problem, but don't really get to the bottom of the issue. But I did want to say this is what fixed it for me.
Pulled the drives, got the server to do a good boot to my fresh install. SSH into the box and edited the '/etc/default/grub' file and added...
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=10"
GRUB_CMDLINE_LINUX="scsi_mod.scan=sync"
GRUB_PRELOAD_MODULES="lvm"after saving the file, I ran...
Code:
update-grubshut the server down, re-added all the drives and powered it back up. This time it booted up with no issues.
I don't know if it's just not good on a basic system to have these extra commands in grub, but with as many times as this has been an issue for people. I'd hope it would finally get fixed in proxmox.
Which, I did finally make a new proxmox 7.3-4 boot disc and tried this all over and had the same issue.
