Proxmox LXC was not able to boot after disk increase (when the storage is full)

hzhoanglee

New Member
Dec 4, 2023
1
0
1
Today, my friend tried to increase the size of the disk of 1 LXC and unfortunately, he didn't check that the "local-lvm" was 100% full.
Now the LXC is completely dead and cannot be booted.
When I try to start, it said:
Code:
DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: cannot mount; probably corrupted filesystem on /dev/mapper/pve-vm--103--disk--0.

and when I try to run fsck
Code:
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Superblock checksum does not match superblock
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Superblock checksum does not match superblock while trying to open /dev/pve/vm-103-disk-0

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>

Is there any chance that I can repair the disk and get the data inside the LXC? Thank you so much :(
 

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!