The Proxmox server rebooted then LV fail, so I installed new Proxmox and old proxmox renamed to pve2.
Here are what I have tried:
# lsblk
# lvscan
# lvs
The /dev/pve2/data2 now Activated then:
Any change to fix this error? Or change to copy /dev/pve2/vm-108-disk-0 to a new disk/file ?
Here are what I have tried:
# lsblk
Code:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 1G 0 part
└─sda3 8:3 0 1.8T 0 part
├─pve2-data2_tmeta 253:2 0 15.8G 0 lvm
│ └─pve2-data2-tpool 253:5 0 1.7T 0 lvm
│ └─pve2-data2 253:7 0 1.7T 1 lvm
└─pve2-data2_tdata 253:3 0 1.7T 0 lvm
└─pve2-data2-tpool 253:5 0 1.7T 0 lvm
└─pve2-data2 253:7 0 1.7T 1 lvm
sdb 8:16 0 931G 0 disk
├─sdb1 8:17 0 1007K 0 part
├─sdb2 8:18 0 1G 0 part
└─sdb3 8:19 0 930G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:4 0 8.1G 0 lvm
│ └─pve-data 253:9 0 793.8G 0 lvm
└─pve-data_tdata 253:6 0 793.8G 0 lvm
└─pve-data 253:9 0 793.8G 0 lvm
sdc 8:32 1 14.4G 0 disk
├─sdc1 8:33 1 224K 0 part
├─sdc2 8:34 1 2.8M 0 part
├─sdc3 8:35 1 1G 0 part
└─sdc4 8:36 1 300K 0 part
sr0 11:0 1 1024M 0 rom
root@prox:~## lvscan
Code:
root@prox:~# lvscan
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [96.00 GiB] inherit
ACTIVE '/dev/pve/data' [793.79 GiB] inherit
ACTIVE '/dev/pve2/data2' [<1.67 TiB] inherit
inactive '/dev/pve2/vm-108-disk-0' [100.00 GiB] inherit
inactive '/dev/pve2/vm-109-disk-0' [300.00 GiB] inherit
inactive '/dev/pve2/vm-118-disk-0' [40.00 GiB] inherit
inactive '/dev/pve2/vm-119-disk-0' [50.00 GiB] inherit
inactive '/dev/pve2/vm-120-disk-0' [4.00 MiB] inherit
inactive '/dev/pve2/vm-120-disk-1' [250.00 GiB] inherit
inactive '/dev/pve2/vm-120-disk-2' [4.00 MiB] inherit
inactive '/dev/pve2/vm-102-disk-0' [100.00 GiB] inherit
inactive '/dev/pve2/vm-105-disk-0' [100.00 GiB] inherit
inactive '/dev/pve2/vm-100-disk-0' [4.00 MiB] inherit
inactive '/dev/pve2/vm-100-disk-1' [250.00 GiB] inherit
inactive '/dev/pve2/vm-100-disk-2' [4.00 MiB] inherit
inactive '/dev/pve2/vm-106-disk-0' [100.00 GiB] inherit
root@prox:~#
Code:
root@prox:~# lvchange -ay /dev/pve2/data2
root@prox:~## lvs
Code:
root@prox:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-a-tz-- 793.79g 0.00 0.24
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g
data2 pve2 twi-aotz-- <1.67t 0.00 0.15
vm-100-disk-0 pve2 Vwi---tz-- 4.00m data2
vm-100-disk-1 pve2 Vwi---tz-- 250.00g data2
vm-100-disk-2 pve2 Vwi---tz-- 4.00m data2
vm-102-disk-0 pve2 Vwi---tz-- 100.00g data2
vm-105-disk-0 pve2 Vwi---tz-- 100.00g data2
vm-106-disk-0 pve2 Vwi---tz-- 100.00g data2
vm-108-disk-0 pve2 Vwi---tz-- 100.00g data2
vm-109-disk-0 pve2 Vwi---tz-- 300.00g data2
vm-118-disk-0 pve2 Vwi---tz-- 40.00g data2
vm-119-disk-0 pve2 Vwi---tz-- 50.00g data2
vm-120-disk-0 pve2 Vwi---tz-- 4.00m data2
vm-120-disk-1 pve2 Vwi---tz-- 250.00g data2
vm-120-disk-2 pve2 Vwi---tz-- 4.00m data2
root@prox:~#The /dev/pve2/data2 now Activated then:
Code:
root@prox:~# lvchange -ay /dev/pve2/vm-108-disk-0
device-mapper: reload ioctl on (253:8) failed: No data available
root@prox:~#Any change to fix this error? Or change to copy /dev/pve2/vm-108-disk-0 to a new disk/file ?
Last edited: