Proxmox don't boot anymore, unable to find /dev/mapper/pve-root

[Verrnum]

Hello,

I really need your help, I'm trying desespartly to migrate Proxmox disk to larger new one.

First, I have created IMG file of the old disk, and I restore it on new larger disk (500 Gb to 1 TB) with "Disk", then proxmox startup fines but the extra 500 GB are not yet allocated.

Then I follow this tutorial to extend the remaining free space to the /dev/pve/data (with an Ubuntu OS running on VM workstation ) :

https://www.thegeekdiary.com/centos...-in-lvm-by-extending-the-disk-partition-used/

remark : I apply this tutorial to the third partition, where the data (sdc3 and not sdc1..)

I have the feeling that everything is fine (see command below).

But I when I put back my disk on my PowerEdge R410, I can't boot anymore, its fails to find /dev/mapper/pve-root, shell initramfs is started dropped.
In deed, when I list the /dev/mapper folder , There is only data-data and control devices.

I'm looking for your help !

Thanks you




sudo vgdisplay --- Volume group --- VG Name pve System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 124 VG Access read/write VG Status resizable MAX LV 0 Cur LV 6 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size <931,01 GiB PE Size 4,00 MiB Total PE 238338 Alloc PE / Size 238338 / <931,01 GiB Free PE / Size 0 / 0 VG UUID RCZ5Qd-EVQP-3wF8-qhl9-d2QA-RZSU-jgC3Oc

verrnum@verrnum-virtual-machine:/mnt$ sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-aotz-- 820,48g 2,56 0,88 root pve -wi-a----- 96,00g swap pve -wi-a----- 8,00g vm-100-disk-0 pve Vwi-a-tz-- 18,00g data 99,83 vm-101-disk-0 pve Vwi-a-tz-- 8,00g data 19,59 vm-102-disk-0 pve Vwi-a-tz-- 8,00g data 17,99

crw------- 1 root root 10, 236 oct. 15 11:28 control lrwxrwxrwx 1 root root 7 oct. 15 13:20 pve-data -> ../dm-5 lrwxrwxrwx 1 root root 7 oct. 15 13:20 pve-data_tdata -> ../dm-3 lrwxrwxrwx 1 root root 7 oct. 15 13:20 pve-data_tmeta -> ../dm-2 lrwxrwxrwx 1 root root 7 oct. 15 13:20 pve-data-tpool -> ../dm-4 lrwxrwxrwx 1 root root 7 oct. 15 14:40 pve-root -> ../dm-1 lrwxrwxrwx 1 root root 7 oct. 15 13:16 pve-swap -> ../dm-0 lrwxrwxrwx 1 root root 7 oct. 15 13:16 pve-vm--100--disk--0 -> ../dm-6 lrwxrwxrwx 1 root root 7 oct. 15 13:16 pve-vm--101--disk--0 -> ../dm-7 lrwxrwxrwx 1 root root 7 oct. 15 13:16 pve-vm--102--disk--0 -> ../dm-8

Remark :

The logical volume data doesn't path :

--- Logical volume --- LV Name data VG Name pve LV UUID cl7JGG-d7VM-EiUz-kiiU-gI07-Njut-bmVSl7 LV Write Access read/write (activated read only) LV Creation host, time proxmox, 2020-12-15 14:37:09 +0100 LV Pool metadata data_tmeta LV Pool data data_tdata LV Status available # open 0 LV Size 820,48 GiB Allocated pool data 2,56% Allocated metadata 0,88% Current LE 210044 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 131064 Block device 253:5

 

[shanreich]

After resizing, can you post the output of lsblk -fi, fdisk -l /dev/sdc and the content of your /etc/fstab ? (on the machine where you put the disk back in)

Can you also try running vgchange -ay and check if it detects your root LV after this?

 

[Verrnum]

Hello,

thank you for your reply.
finally, it's fixed.
it was not the good strategy to reduce existing partition.
I have just updated pv,vg and create an new lvm partition directly from proxmox host