Hi
I am posting this for people experiencing this as i have read the accepted solutions and none address this.
Condition:
New Install version proxmox-ve_8.1-2, installed via ventoy usb. Install completes normally however system fails to boot past "loading initramfs" and hangs the system.
Attempting to boot recovery option results in system hanging around this error "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
Solution/Condition confirmation:
-boot proxmox from install medium (ventoy flash) using the "rescue boot" option
-login to root using the password you created at your origional installation
-create a mount point: mkdir /mnt/pve
-mount root mapper partition: mount /dev/mapper/pve-root /mnt/pve
-open grub.conf: vi /mnt/pve/boot/grub/grub.cfg
-search for lines that look like this:
echo 'Loading Linux 6.8.4-2-pve ...'
linux /boot/vmlinuz-6.8.4-2-pve root=/dev/mapper/pve-root ro rdinit=/vtoy/vtoy quiet
-comment out or delete the "rdinit=/vtoy/vtoy quiet" part
-mine had 3 seperate entries i commented out
- write and reboot
It should boot up now.
I am posting this for people experiencing this as i have read the accepted solutions and none address this.
Condition:
New Install version proxmox-ve_8.1-2, installed via ventoy usb. Install completes normally however system fails to boot past "loading initramfs" and hangs the system.
Attempting to boot recovery option results in system hanging around this error "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
Solution/Condition confirmation:
-boot proxmox from install medium (ventoy flash) using the "rescue boot" option
-login to root using the password you created at your origional installation
-create a mount point: mkdir /mnt/pve
-mount root mapper partition: mount /dev/mapper/pve-root /mnt/pve
-open grub.conf: vi /mnt/pve/boot/grub/grub.cfg
-search for lines that look like this:
echo 'Loading Linux 6.8.4-2-pve ...'
linux /boot/vmlinuz-6.8.4-2-pve root=/dev/mapper/pve-root ro rdinit=/vtoy/vtoy quiet
-comment out or delete the "rdinit=/vtoy/vtoy quiet" part
-mine had 3 seperate entries i commented out
- write and reboot
It should boot up now.