LVM is pointing to wrong path

Chiranjeevi

New Member
May 6, 2017
23
0
1
41
I Restarted the Proxmox server

After that the VM s are not stating so when i start searching i saw this thread https://www.linuxquestions.org/ques...-lv-status-not-available-after-reboot-771192/

So i run the

Code:
lvconvert --repair pve/data

lvchange -a y pve/data

i have 12 VM shown on web UI but lvs shows 13

so 2 MVs got corrupted

How can i recover these, other VMs are running fine


when i run fdisk -l

Code:
Disk /dev/mapper/pve-vm--108--disk--1: 260 GiB, 279172874240 bytes, 545259520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 2097152 bytes
Disklabel type: dos
Disk identifier: 0x0471863d

Device                                 Boot   Start       End   Sectors   Size Id Type
/dev/mapper/pve-vm--108--disk--1-part1 *       2048    999423    997376   487M 83 Linux
/dev/mapper/pve-vm--108--disk--1-part2      1001470 524285951 523284482 249.5G  5 Extended
/dev/mapper/pve-vm--108--disk--1-part5      1001472 524285951 523284480 249.5G 8e Linux LVM

Partition 2 does not start on physical sector boundary.

Disk /dev/mapper/pve-vm--106--disk--1: 900 GiB, 966367641600 bytes, 1887436800 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 262144 bytes / 2097152 bytes

Disklabel type: dos

Disk identifier: 0xff9e0456


Device                                 Boot   Start        End    Sectors   Size Id Type

/dev/mapper/pve-vm--106--disk--1-part1 *       2048     999423     997376   487M 83 Linux

/dev/mapper/pve-vm--106--disk--1-part2      1001470 1887434751 1886433282 899.5G  5 Extended

/dev/mapper/pve-vm--106--disk--1-part5      1001472 1887434751 1886433280 899.5G 8e Linux LVM


Partition 2 does not start on physical sector boundary.

Only for those 2 VMs it shows this error
 
Last edited: