Error: disk 'lvmid/***' not found, grub rescue.

[acaniza]

Update, problem seems to be solved.

I've booted proxmox debug from a usb and executed this command:

lvextend -L +1G /dev/pve/root

I rebooted the node without usb, and magically my proxmox node reboots normal & working without the grub rescue screen.

I undid the above command with

lvreduce -L -1G /dev/pve/root

rebooted, and proxmox still starts normal & working.

I like to pretend i know what i'm doing, but i'm unsure what caused this issue & how above commands was able to fix it.

Maybe someone could explain?

I've made a backup once manually from my node several weeks ago.
Since, hours of work went in which i didn't backup.

Atleast lesson learned now, next thing i will do now is set up automatic backups every week or so...

Gracias. Me funcionó y salvó la vida, que haríamos sin estos post... como haces los backups?

 

[acaniza]

Gracias. Me funcionó y salvó la vida, que haríamos sin estos post... como haces los backups?

Update, problem seems to be solved.

I've booted proxmox debug from a usb and executed this command:

lvextend -L +1G /dev/pve/root

I rebooted the node without usb, and magically my proxmox node reboots normal & working without the grub rescue screen.

I undid the above command with

lvreduce -L -1G /dev/pve/root

rebooted, and proxmox still starts normal & working.

I like to pretend i know what i'm doing, but i'm unsure what caused this issue & how above commands was able to fix it.

Maybe someone could explain?

I've made a backup once manually from my node several weeks ago.
Since, hours of work went in which i didn't backup.

Atleast lesson learned now, next thing i will do now is set up automatic backups every week or so...

Thank you. It worked for me and saved my life, what would we do without these posts... how do you make backups?

 

[HiroPro]

Update, problem seems to be solved.

I've booted proxmox debug from a usb and executed this command:

lvextend -L +1G /dev/pve/root

I rebooted the node without usb, and magically my proxmox node reboots normal & working without the grub rescue screen.

I undid the above command with

lvreduce -L -1G /dev/pve/root

rebooted, and proxmox still starts normal & working.

I like to pretend i know what i'm doing, but i'm unsure what caused this issue & how above commands was able to fix it.

Maybe someone could explain?

I've made a backup once manually from my node several weeks ago.
Since, hours of work went in which i didn't backup.

Atleast lesson learned now, next thing i will do now is set up automatic backups every week or so...

I'm in a similar situation. Do you have any suggestions? Wish i was more experienced with linux.

root@proxmox:/# Ivextend -L +16 /dev/pve/root
[5136.148236] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER OK cmd_age=0s
[5136.148647] sd 4:0:0:0: [sdc] tag#0 Sense Key: Medium Error [current]
[5136.149048] sd 4:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[5136.149477] sd 4:0:0:0: [sdc] tag#0 CDB: Read (10) 28 00 00 00 08 00 00 01 00 00
[5136.149887] blk_update_request: critical medium error, dev sdc, sector 2048 op 0x0: (READ) flags 0x0 phys_seg 2 prio class 0
[5136.790830] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID OK driverbyte=DRIVER OK cmd_age=0s
[5136.791290] sd 4:0:0:0: [sdc] tag#0 Sense Key: Medium Error [current]
[5136.791745] sd 4:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[5136.792208] sd 4:0:0:0: [sdc] tag#0 CDB: Read (10) 28 00 00 10 08 00 00 01 00 00
[5136.792724] blk_update_request: critical medium error, dev sdc, sector 1050624 op 0x0: (READ) flags 0x0 phys_seg 25 prio class 0
Volume group "pve" not found
Cannot process volume group pve

 

[fiona]

Hi,

I'm in a similar situation. Do you have any suggestions? Wish i was more experienced with linux.

root@proxmox:/# Ivextend -L +16 /dev/pve/root
[5136.148236] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER OK cmd_age=0s
[5136.148647] sd 4:0:0:0: [sdc] tag#0 Sense Key: Medium Error [current]
[5136.149048] sd 4:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[5136.149477] sd 4:0:0:0: [sdc] tag#0 CDB: Read (10) 28 00 00 00 08 00 00 01 00 00
[5136.149887] blk_update_request: critical medium error, dev sdc, sector 2048 op 0x0: (READ) flags 0x0 phys_seg 2 prio class 0
[5136.790830] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID OK driverbyte=DRIVER OK cmd_age=0s
[5136.791290] sd 4:0:0:0: [sdc] tag#0 Sense Key: Medium Error [current]
[5136.791745] sd 4:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[5136.792208] sd 4:0:0:0: [sdc] tag#0 CDB: Read (10) 28 00 00 10 08 00 00 01 00 00
[5136.792724] blk_update_request: critical medium error, dev sdc, sector 1050624 op 0x0: (READ) flags 0x0 phys_seg 25 prio class 0
Volume group "pve" not found
Cannot process volume group pve

sounds like the sdc disk is breaking down. Please check the cable (the issue could also be there) and check the output of smartctl -a /dev/sdc. To salvage recoverable data, you might want to try something like ddrescue.

 

[mow]

I'm in a similar situation. Do you have any suggestions? Wish i was more experienced with linux.

That's not similar, that's a hardware failure. Is that a disk or an SSD? If disk, does it make weird noises? Does it work after letting it cool down? Do you have a recent backup?

 

[HiroPro]

Hi,

sounds like the sdc disk is breaking down. Please check the cable (the issue could also be there) and check the output of smartctl -a /dev/sdc. To salvage recoverable data, you might want to try something like ddrescue.

I'll look into that thank you. Do you know of any options on how to backup the boot drive so this doesn't happen again? I also want to test out PVE 8

That's not similar, that's a hardware failure. Is that a disk or an SSD? If disk, does it make weird noises? Does it work after letting it cool down? Do you have a recent backup?

The boot drive was a SanDisk USB connected to the mainboard... Luckly I finished building my ProxMox Backup Server the day before. Talk about timing haha.

 

[fiona]

Do you know of any options on how to backup the boot drive so this doesn't happen again?

There's nothing integrated in Proxmox VE for that, but there are a lot of applications for both, backing up the whole drive as an image or taking a backup on the filesystem level.

 

[newhinton]

I have encountered the original issue aswell. After a hardware change (in this case swapping either the physical sata-port, or adding a new harddrive) the system only boots into "grub rescue".

However, i am not using the proxmox iso. I am installing debian (with luks fde) manually, and then following the proxmox guide. The only change i made, besides setting up ssh and proxmox itself, is adding dropbear to the initramfs.

This issue persists even after a reinstall, and the provided fix does not seem to work. Any suggestions on how to get this stable? What info can i provide?

Thanks!