LVM bzw. LVM-thin reparieren nach versuchter Diskerweiterung

S

stkw

Member
Proxmox Subscriber
Oct 25, 2020
35
3
13
44
Ich habe heute versucht mein LVM Laufwerk zu erweitern mit zwei noch verfügbaren Laufwerken.
Dazu habe ich die Anleitung unter folgendem Link verwendet: https://serverfault.com/questions/423544/how-would-i-add-a-second-physical-hard-drive-to-proxmox

Leider ist nun das passiert was bei einem der Kommentare auch dabei steht: Bad magic number in super-block while trying to open /dev/mapper/pve-data

Die Frage ist nun wie kann ich mein Laufwerk wieder reparieren?


Code: 
root@pve2:~# lvs
  LV            VG  Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data          pve twi-aotz-- <613.11g             7.03   2.48                           
  root          pve -wi-ao----   58.00g                                                   
  swap          pve -wi-ao----    8.00g                                                   
  vm-100-disk-0 pve Vwi-a-tz--   32.00g data        10.35                                 
  vm-101-disk-0 pve Vwi-aotz--   16.00g data        18.69                                 
  vm-102-disk-0 pve Vwi-aotz--    8.00g data        46.75                                 
  vm-103-disk-0 pve Vwi-aotz--    8.00g data        49.36                                 
  vm-104-disk-0 pve Vwi-aotz--   25.00g data        93.89                                 
  vm-105-disk-0 pve Vwi-aotz--   12.00g data        46.93

Code: 
  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                Do9WEm-jExL-q5Wz-DLax-rn4v-H36Y-2t09CE
  LV Write Access        read/write (activated read only)
  LV Creation host, time proxmox, 2021-11-15 10:30:04 +0100
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 0
  LV Size                <613.11 GiB
  Allocated pool data    7.03%
  Allocated metadata     2.48%
  Current LE             156956
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:5

Code: 
root@pve2:~# vgdisplay
  --- Volume group ---
  VG Name               pve
  System ID             
  Format                lvm2
  Metadata Areas        3
  Metadata Sequence No  647
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                9
  Open LV               7
  Max PV                0
  Cur PV                3
  Act PV                3
  VG Size               <698.12 GiB
  PE Size               4.00 MiB
  Total PE              178718
  Alloc PE / Size       174622 / <682.12 GiB
  Free  PE / Size       4096 / 16.00 GiB
  VG UUID               Td1Zkt-i0O2-9kOn-akR5-H8Sf-VWe0-gLpu3C

Code: 
root@pve2:~# fsck -nv /dev/mapper/pve-data
fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mapper/pve-data

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>
 
You must log in or register to reply here.
Top Bottom
Back