Grub error after Update to v3

[FabianRn]

Hello everybody..

I urgently need your help. Today, I upgraded our Proxmox Backup Server from version 2.x to 3. Since then, it no longer boots, and I get the error message

'error: disk xx.x.x. not found.'

The recovery guide for Proxmox doesn't seem to help me here.

Does anyone have any ideas? The backup server runs in a VM on a Proxmox server

Thank you very much!!"

 

[fabian]

which parts of the recovery guide did you try? it's very likely you are running into exactly that issue: https://pve.proxmox.com/wiki/Recove...disk_not_found.22_error_when_booting_from_LVM

 

[FabianRn]

which parts of the recovery guide did you try? it's very likely you are running into exactly that issue: https://pve.proxmox.com/wiki/Recove...disk_not_found.22_error_when_booting_from_LVM

Hello Fabian, I've taken exactly those steps.

1. Boot from a live USB/CD/DVD with LVM support (grml).
2. Run vgscan.

Vgscan doesn't output anything.
When I execute "lvcreate -L 4M pve -n grubtemp," I get the error "Volume group 'pve' not found. Cannot process volume group 'pve'."
If I use "psb-root" instead of "pve," I get the same error message.

What am I doing wrong?

 

[fabian]

what about "pvscan" ?

 

[FabianRn]

what about "pvscan" ?

Not matching physical volumes found

 

[fabian]

could you run "blkid" as well? I assume /dev/sda3 would be your PV, and /dev/sdb and /dev/sdc are set up as zpools?

 

[FabianRn]

could you run "blkid" as well? I assume /dev/sda3 would be your PV, and /dev/sdb and /dev/sdc are set up as zpools?

blkid:

I assume /dev/sda3 would be your PV, and /dev/sdb and /dev/sdc are set up as zpools?

Yes!

 

[fabian]

okay, this might be a different issue then, if grml isn't able to detect the disk as LVM whatsoever.. are the disks regular volumes on some storage, or passed through somehow?

two more things you could try:
- "pvck /dev/sda3"
- "lvmdiskscan"

based on the size I assume LVM "only" contained your / file system, and not your datastores?

 

[FabianRn]

okay, this might be a different issue then, if grml isn't able to detect the disk as LVM whatsoever.. are the disks regular volumes on some storage, or passed through somehow?

two more things you could try:
- "pvck /dev/sda3"
- "lvmdiskscan"

based on the size I assume LVM "only" contained your / file system, and not your datastores?

Yes, those are the disks from Proxmox on which the VM is running. Yes, SDB is very important. Our backups run on it every night, just like tonight. Can I alternatively create a new PBS VM and migrate the SDB1 'BackupStorage' to it?

 

[fabian]

yes, that should work (you will have to manually create the datastore.cfg entry (or create a new datastore with a different path and then edit it to point at the existing one and reboot) and re-create any job configuration you had before), the datastore is completely self-contained other than the job configs.