alert! /dev/mapper/pve-root does not exist

K

kamrang

New Member
Feb 16, 2024
10
1
3
Hello, Please help because I don't know what to do anymore, I'm very frustrated and have tried various things but can't do it.

I have 3 proxmox servers with HA and cehp systems, 2 of the servers are dead and can't boot as in the picture below:

Actions that I could do via the Ubuntu livecd but to no avail:
- Set rootdelay=15
- install grub (grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
) and Update group
- update-initramfs -u

I also ask for your advice on how to back up my VM in the case above and take it so I can restore the backup to the new Proxmox, because I haven't had time to do a backup and the server has a problem.

1717097914818.jpeg
1717097945879.jpeg
 
from the livecd shell:

vgchange -ay pve
fsck /dev/mapper/pve-root
mount /dev/mapper/pve-root /mnt (or another temporary location)

inspect the mounted filesystem. if it look normal (/etc is present, etc) reboot. it should work now. if NOT... post any relevent output from above.
 
Thank you for your response, I just tried it, but after booting into Proxmox the error that appeared was still the same

1717103590797.png
1717103606615.jpeg
1717103674833.jpeg
 
The fsck didn't run because the filesystem was already mounted in the live-system (which may mean that it's still working).
Unmount the device first and the use the commands above again:

umount /dev/mapper/pve-root

Another idea. In some cases it's needed that you add "rootdelay=10" into your grub-config.
Or try to boot into an older 6.5-Kernel.
 
Last edited:
I have tried again but the problem is still the same.

I've tried rootdelay=10 but it's the same
and how to boot into the older 6.5 kernel, does this mean reinstalling to an older version?

1717107938634.jpeg
 
Proxmox always stores the older kernels in the system. I never had to use it, but you should be able to select the older 6.5 kernel while interupting (esc? cursor?) grub menu before booting.
 
do you mean in I can boot into version 6.5 this part:

FYI I have never updated the version on Proxmox, from the beginning until now I am still using version 8
 

Attachments

  • IMG-20240531-WA0011.jpg
    IMG-20240531-WA0011.jpg
    53.6 KB · Views: 24
Last edited:
Sorry, FYI I have never updated the version on Proxmox, from the past until now I am still using version 8, so where do I choose version 6.5 as you mean?
 
I have done the mount as you have shared, but the installation stage of proxmox-karnel-6.5 failed because there was no package as below:
1717123892970.jpeg
 
First: It's proxmox-kernel-6.5
Second: Are you really in your /dev/mapper/pve-root chroot?
Third: Use the command apt update to update the packages
 
devaux said:
First: It's proxmox-kernel-6.5
Second: Are you really in your /dev/mapper/pve-root chroot?
Third: Use the command apt update to update the packages
Click to expand...

I have solved the problem, I have found what you mean, there was a problem with kernel-pve 6.8 and I tried booting using kernel 6.5 and the error was resolved.

I'm currently thinking about how to boot using Karne 6.5 automatically.

Terima kasih atas bantuan Anda dan senang bertemu dengan Anda.

1717147684038.jpeg
1717147701986.jpeg
 
  • Like
Reactions: mverdugocarvajal
Great! I think you want to use the proxmox-boot-tool
For pinning kernel 5.15.13-5-pve the command would be:
proxmox-boot-tool kernel pin 5.15.13-5-pve

Since you have a running system now, you could also try to update your Proxmox-Server to the latest 6.8.4-3 kernel. Maybe this will solve your problem without pinning. If not, you now know how to boot the older kernel and pin it.
 
You must log in or register to reply here.
Top Bottom