Hi guys,
I ran into a small issue with my Proxmox Installation. As of late we had a couple of power outtages and the latest seems to have killed /dev/mapper/pve-root, at least I get that error upon bootup: unexpected inconsistency run fsck manually.
After reading and googling and trying for 4-5 hours I ran out of ideas and booted from a Ubuntu Live-CD because I thought at least I can try and pull some data off of it.
What I tried before starting the LiveCD: I did try to run fsck of course (without success) and also tried to restore the superblocks (got the list of Backup blocks via "mke2fs -n /dev/mapper/pve-root") via the backup superblocks (e2fsck -b block_number /dev/mapper/pve-root) but that also never worked (unable to set superblock flags). I tried with all the backup blocks available.
So I fired up a Ubuntu live CD on a USB stick on the same machine and I am trying to mount the "partition"(?) with my data in it...
It's just a small setup with 1 SSD and 3 VM's setup (2x Win10, 1x Ubuntu). So nothing special/fancy.
I am a complete linux noob, so bare with me, I tried a couple of things, maybe anyone spots anything!?
sudo mount /dev/mapper/pve-vm--102--disk--0 /media/recover
Same result with "sudo mount -t ntfs" and "sudo mount -t ntfs-3g"
sudo lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINT
sudo lvdisplay
sudo lvscan
sudo ls -l /dev/mapper/
sudo fuseext2 -o ro -o allow_other /dev/pve/pve-vm-102-disk-0 /mnt/recover
sudo dmesg
Does anyone have a clue how I could get to the data? Or what would be the best approach here?
I ran into a small issue with my Proxmox Installation. As of late we had a couple of power outtages and the latest seems to have killed /dev/mapper/pve-root, at least I get that error upon bootup: unexpected inconsistency run fsck manually.
After reading and googling and trying for 4-5 hours I ran out of ideas and booted from a Ubuntu Live-CD because I thought at least I can try and pull some data off of it.
What I tried before starting the LiveCD: I did try to run fsck of course (without success) and also tried to restore the superblocks (got the list of Backup blocks via "mke2fs -n /dev/mapper/pve-root") via the backup superblocks (e2fsck -b block_number /dev/mapper/pve-root) but that also never worked (unable to set superblock flags). I tried with all the backup blocks available.
So I fired up a Ubuntu live CD on a USB stick on the same machine and I am trying to mount the "partition"(?) with my data in it...
It's just a small setup with 1 SSD and 3 VM's setup (2x Win10, 1x Ubuntu). So nothing special/fancy.
I am a complete linux noob, so bare with me, I tried a couple of things, maybe anyone spots anything!?
sudo mount /dev/mapper/pve-vm--102--disk--0 /media/recover
Code:
mount: /media/recover: Falscher Dateisystemtyp, ungültige Optionen, der Superblock von /dev/mapper/pve-vm--102--disk--0 ist beschädigt, fehlende Kodierungsseite oder ein anderer Fehler.Same result with "sudo mount -t ntfs" and "sudo mount -t ntfs-3g"
sudo lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINT
Code:
NAME FSTYPE LABEL SIZE MOUNTPOINT
loop0 squashfs 2,3G /rofs
loop1 squashfs 4K /snap/bare/5
loop2 squashfs 150,4M /snap/firefox/631
loop3 squashfs 65,2M /snap/gtk-common-themes/1519
loop4 squashfs 61,8M /snap/core20/1169
loop5 squashfs 54,2M /snap/snap-store/557
loop6 squashfs 99,3M /snap/core/11743
loop7 squashfs 242,3M /snap/gnome-3-38-2004/76
sda 29,3G
└─sda1 vfat UBUNTU 21_1 29,3G /cdrom
nvme0n1 931,5G
├─nvme0n1p1 1007K
├─nvme0n1p2 vfat 512M
└─nvme0n1p3 LVM2_member 931G
├─pve-swap swap 8G
├─pve-root 96G
├─pve-data_tmeta 8,1G
│ └─pve-data-tpool 794,8G
│ ├─pve-data 794,8G
│ ├─pve-vm--100--disk--0 92G
│ ├─pve-vm--101--disk--0 64G
│ └─pve-vm--102--disk--0 500G
└─pve-data_tdata 794,8G
└─pve-data-tpool 794,8G
├─pve-data 794,8G
├─pve-vm--100--disk--0 92G
├─pve-vm--101--disk--0 64G
└─pve-vm--102--disk--0 500Gsudo lvdisplay
Code:
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID TELIXQ-MmmY-pc87-uvaP-4CKp-sXpK-8CISbr
LV Write Access read/write
LV Creation host, time proxmox, 2021-10-18 18:45:18 +0000
LV Status available
# open 0
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 G75BW0-Q1jQ-m4L0-Lxiu-RaTd-SJ00-mR6Q7B
LV Write Access read/write
LV Creation host, time proxmox, 2021-10-18 18:45:18 +0000
LV Status available
# open 0
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 CDcbG1-BDQK-JdK8-mIdr-ntO3-eoAQ-UQzAXR
LV Write Access read/write (activated read only)
LV Creation host, time proxmox, 2021-10-18 18:45:21 +0000
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 0
LV Size <794,79 GiB
Allocated pool data 50,31%
Allocated metadata 2,58%
Current LE 203466
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5
--- Logical volume ---
LV Path /dev/pve/vm-100-disk-0
LV Name vm-100-disk-0
VG Name pve
LV UUID Fm2ChF-fwcj-ue2e-WkSx-sAJn-hQ3j-EAfw5u
LV Write Access read/write
LV Creation host, time pve, 2021-10-18 19:02:55 +0000
LV Pool name data
LV Status available
# open 0
LV Size 92,00 GiB
Mapped size 66,76%
Current LE 23552
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6
--- Logical volume ---
LV Path /dev/pve/vm-101-disk-0
LV Name vm-101-disk-0
VG Name pve
LV UUID tLCHas-bZFP-HSeB-UwP2-lbLS-24NH-f5XQpo
LV Write Access read/write
LV Creation host, time pve, 2021-10-19 13:01:07 +0000
LV Pool name data
LV Status available
# open 0
LV Size 64,00 GiB
Mapped size 16,83%
Current LE 16384
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:7
--- Logical volume ---
LV Path /dev/pve/vm-102-disk-0
LV Name vm-102-disk-0
VG Name pve
LV UUID N1jvSq-rpne-vtvL-oQ0B-buGl-CWwU-B9nUDa
LV Write Access read/write
LV Creation host, time pve, 2021-10-19 14:59:51 +0000
LV Pool name data
LV Status available
# open 0
LV Size 500,00 GiB
Mapped size 65,53%
Current LE 128000
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8sudo lvscan
Code:
ACTIVE '/dev/pve/swap' [8,00 GiB] inherit
ACTIVE '/dev/pve/root' [96,00 GiB] inherit
ACTIVE '/dev/pve/data' [<794,79 GiB] inherit
ACTIVE '/dev/pve/vm-100-disk-0' [92,00 GiB] inherit
ACTIVE '/dev/pve/vm-101-disk-0' [64,00 GiB] inherit
ACTIVE '/dev/pve/vm-102-disk-0' [500,00 GiB] inheritsudo ls -l /dev/mapper/
Code:
crw------- 1 root root 10, 236 Apr 29 19:45 control
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-data -> ../dm-5
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-data_tdata -> ../dm-3
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-data_tmeta -> ../dm-2
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-data-tpool -> ../dm-4
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-root -> ../dm-1
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-swap -> ../dm-0
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-vm--100--disk--0 -> ../dm-6
lrwxrwxrwx 1 root root 7 Apr 29 19:46 pve-vm--101--disk--0 -> ../dm-7
lrwxrwxrwx 1 root root 7 Apr 29 21:30 pve-vm--102--disk--0 -> ../dm-8sudo fuseext2 -o ro -o allow_other /dev/pve/pve-vm-102-disk-0 /mnt/recover
Code:
fuse-umfuse-ext2: version:'0.4', fuse_version:'29' [main (fuse-ext2.c:331)]
fuse-umfuse-ext2: Failed to access '/dev/pve/pve-vm-102-disk-0' [main (fuse-ext2.c:341)]sudo dmesg
Code:
[ 6275.641857] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[ 7311.164666] exFAT-fs (dm-8): invalid fs_name
[ 7311.164672] exFAT-fs (dm-8): failed to read boot sector
[ 7311.164673] exFAT-fs (dm-8): failed to recognize exfat type
[ 7598.860819] exFAT-fs (dm-8): invalid fs_name
[ 7598.860824] exFAT-fs (dm-8): failed to read boot sector
[ 7598.860826] exFAT-fs (dm-8): failed to recognize exfat typeDoes anyone have a clue how I could get to the data? Or what would be the best approach here?
Last edited: