Probleme mit LVM-Volume nach RAID-Controller-Ausfall

Dec 18, 2019
2
0
1
27
Hallo zusammen,

Ich habe seit heute morgen Probleme mit einem Proxmox-Host:

Ausgangslage:
Raid-Controller: HPE Smart Array E208i-p SR Gen10
Disks: 3 * Intel 545s 512GB SSDs (RAID 5)
Dateisystem: Eine LVM-Volume-Group "pve" mit volumes für pve und die einzelnen VMs (Zwei VMs sind auf dem Host)

Der RAID-Controller hatte wohl Probleme mit seinem BIOS - ganz haben wir das Thema noch nicht ergründet.

Was wir aktuell versuchen, ist an die Disks einer VM zu kommen.
--- Physical volume ---
PV Name /dev/sda3
VG Name pve
PV Size <953.32 GiB / not usable <3.32 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 244048
Free PE 1960
Allocated PE 242088
PV UUID FpFQgz-9orn-ktVi-NC8h-DeGd-B3gG-r8NPdd
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 39
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 7
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 953.31 GiB
PE Size 4.00 MiB
Total PE 244048
Alloc PE / Size 242088 / <945.66 GiB
Free PE / Size 1960 / <7.66 GiB
VG UUID 9rvjH3-hNKg-OeH4-ErIV-nFjY-dN4r-FgLbBF
~# lvdisplay

--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID c0OUlC-kyvm-McuE-CvV3-k9jy-aKiE-Dp87R0
LV Write Access read/write
LV Creation host, time proxmox, 2020-01-23 15:14:26 +0100
LV Status available
# open 2
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID L5HbHd-tZqI-qkTA-XDuC-xj1M-9y6g-S478kP
LV Write Access read/write
LV Creation host, time proxmox, 2020-01-23 15:14:26 +0100
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name data
VG Name pve
LV UUID 0VPb8r-mfkl-B2ce-WoBl-rF4v-hQBf-AtfzH0
LV Write Access read/write
LV Creation host, time proxmox, 2020-01-23 15:14:26 +0100
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 1
LV Size <816.65 GiB
Allocated pool data 0.00%
Allocated metadata 0.23%
Current LE 209062
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

--- Logical volume ---
LV Path /dev/pve/vm-120-disk-0
LV Name vm-120-disk-0
VG Name pve
LV UUID z7Ug4O-4rfd-qZIp-e6Au-7Ykz-gynU-4qF2nF
LV Write Access read/write
LV Creation host, time vk-sv-prx-01, 2020-01-23 15:12:23 +0100
LV Pool name data
LV Status NOT available
LV Size 75.00 GiB
Current LE 19200
Segments 1
Allocation inherit
Read ahead sectors auto

--- Logical volume ---
LV Path /dev/pve/vm-120-disk-1
LV Name vm-120-disk-1
VG Name pve
LV UUID KV30A4-qbdy-aqhl-TbIO-t4UL-0eF1-GIMIrY
LV Write Access read/write
LV Creation host, time vk-sv-prx-01, 2020-01-23 15:13:05 +0100
LV Pool name data
LV Status NOT available
LV Size 100.00 GiB
Current LE 25600
Segments 1
Allocation inherit
Read ahead sectors auto

--- Logical volume ---
LV Path /dev/pve/vm-104-disk-2
LV Name vm-104-disk-2
VG Name pve
LV UUID T4lJLR-54Bp-1uSc-cKd9-EAWc-5BG1-SfWKUB
LV Write Access read/write
LV Creation host, time vk-sv-prx-01, 2020-01-28 12:05:59 +0100
LV Pool name data
LV Status NOT available
LV Size 625.00 GiB
Current LE 160000
Segments 1
Allocation inherit
Read ahead sectors auto

--- Logical volume ---
LV Path /dev/pve/data_meta0
LV Name data_meta0
VG Name pve
LV UUID kZiS0E-7aY5-EQFk-tzJ3-gIoK-AYBo-nDVqc7
LV Write Access read/write
LV Creation host, time proxmox, 2020-01-23 15:14:26 +0100
LV Status available
# open 0
LV Size <8.34 GiB
Current LE 2134
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6

--- Logical volume ---
LV Path /dev/pve/data_meta1
LV Name data_meta1
VG Name pve
LV UUID pyb9zf-BXiq-NKle-2Mie-BqyX-3Grf-tXpwms
LV Write Access read/write
LV Creation host, time proxmox, 2020-01-23 15:14:26 +0100
LV Status available
# open 0
LV Size <8.34 GiB
Current LE 2134
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:7

Es geht uns um das LV "vm-104-disk-2".
Nach einem Ausflug ins initramfs bootet der Server mittlerweile wieder (daher kommen auch die beiden data_metas) und root, swap und data sind wieder available. Die VM-Disks allerdings nicht, dort steht "NOT available".

Ein Aktivierungsversuch mittels "lvchange -ay /dev/pve/vm-104-disk-2" gibt zurück:
Code:
  device-mapper: reload ioctl on  (253:8) failed: No data available
In /dev/pve befinden sich laut lsauch bloß data_meta_0, data_meta_1, root und swap

~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 953.8G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi
└─sda3 8:3 0 953.3G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:2 0 8.3G 0 lvm
│ └─pve-data-tpool 253:4 0 824.3G 0 lvm
│ └─pve-data 253:5 0 824.3G 0 lvm
├─pve-data_tdata 253:3 0 824.3G 0 lvm
│ └─pve-data-tpool 253:4 0 824.3G 0 lvm
│ └─pve-data 253:5 0 824.3G 0 lvm
├─pve-data_meta0 253:6 0 8.3G 0 lvm
└─pve-data_meta1 253:7 0 8.3G 0 lvm
sdj 8:144 0 223.6G 0 disk
└─sdj1 8:145 0 223.6G 0 part /extern
sr0 11:0 1 1024M 0 rom
sr1 11:1 1 1024M 0 rom
sr2 11:2 1 1024M 0 rom
sr3 11:3 1 1024M 0 rom

Hat irgendjemand eine Idee, wie wir die vm-Disk mounten können, sodass wir an die Daten darin kommen?
 
Hallo,

So wie das aussieht sind deine ThinMetaLV vom ThinPoolLV weg oder besser gesagt nicht gemapt.
Du hast anscheinend einen Zweiten meta ThinMetaLV erstellt und der ist halt leer.
das heißt die ThinLV wissen nicht wo Ihre Blöke liegen.
Ob der andere ThinMetaLV noch brauchbare Daten hat kann ich nicht sagen.

Was hast du genau gemacht?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!