pct fsck failed

[kotakomputer]

I try to resize a container, TASK OK but with error:

Image resized.
e2fsck 1.43.4 (31-Jan-2017)
MMP interval is 10 seconds and total wait time is 42 seconds. Please wait...

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>

e2fsck: MMP: device currently active while trying to open /mnt/data/images/3256/vm-3256-disk-1.raw
Failed to update the container's filesystem: command 'e2fsck -f -y /mnt/data/images/3256/vm-3256-disk-1.raw' failed: exit code 8

TASK OK

So I try to fix but still fail:

# pct stop 3256
# pct fsck 3256
fsck from util-linux 2.29.2
MMP interval is 10 seconds and total wait time is 42 seconds. Please wait...
fsck.ext4: MMP: device currently active while trying to open /mnt/data/images/3256/vm-3256-disk-1.raw
/mnt/data/images/3256/vm-3256-disk-1.raw:
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>

command 'fsck -a -l /mnt/data/images/3256/vm-3256-disk-1.raw' failed: exit code 8
root@sds-999:~#

 

[kotakomputer]

# mke2fs -n /mnt/data/images/3256/vm-3256-disk-1.raw
mke2fs 1.43.4 (31-Jan-2017)
/mnt/data/images/3256/vm-3256-disk-1.raw contains a ext4 file system
        created on Thu Jun 14 09:34:18 2018
Proceed anyway? (y,N) y
Creating filesystem with 39845888 4k blocks and 9961472 inodes
Filesystem UUID: 157ab929-2cdc-4db9-87a3-9fed6e178b21
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872

#

# e2fsck -b 32768 /mnt/data/images/3256/vm-3256-disk-1.raw
e2fsck 1.43.4 (31-Jan-2017)
MMP interval is 10 seconds and total wait time is 42 seconds. Please wait...
e2fsck: Bad magic number in super-block while trying to open /mnt/data/images/3256/vm-3256-disk-1.raw

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>

/mnt/data/images/3256/vm-3256-disk-1.raw contains a ext4 file system
        created on Thu Jun 14 09:34:18 2018
#

Any suggestion?

 

[kotakomputer]

When I try to backup ... I found

INFO: tar: ./home/mail/new/1538852941.M550773P24916,S=1532,W=1561: Cannot stat: Bad message

Try to delete this file but error ... Cannot stat: Bad message.

Event I manually mount the file of this Container, I still can not delete this Corrupted File. How to delete this "Corrupted File"?

 

[oguz]

hi.

what error do you get when trying to delete after mounting the container rootfs?

 

[kotakomputer]

# pct stop 3256
# mount /mnt/data/images/3256/vm-3256-disk-1.raw /mnt/test/

Change to that folder then:

# rm 1538852941.M550773P24916\,S\=1532\,W\=1561
rm: cannot remove '1538852941.M550773P24916,S=1532,W=1561': Bad message
#

 

[oguz]

hi.

e2fsck: Bad magic number in super-block while trying to open /mnt/data/images/3256/vm-3256-disk-1.raw

according to this, it looks like your filesystem is a bit weird.

# mount /mnt/data/images/3256/vm-3256-disk-1.raw /mnt/test/

do you get any error output after the mount command?

 

[kotakomputer]

do you get any error output after the mount command?

No error on mount.

Since this VPS used for hosting then my last change is backup all files then move to new VPS, but I must prepare a long time because data size was nearly 80GB.

Is there a way Proxmox Backup ignore invalid files?

 

[psionic]

Just trying to find out if this is an error that needs to be fixed?
pct fsck 104
fsck from util-linux 2.33.1
fsck.ext2: Unable to resolve 'rbd:test/vm-104-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/test.keyring'
command 'fsck -a -l 'rbd:test/vm-104-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/test.keyring'' failed: exit code 8

Package Versions:
proxmox-ve: 6.0-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.0-12 (running version: 6.0-12/0a603350)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.4-pve1
ceph-fuse: 14.2.4-pve1
corosync: 3.0.2-pve4 criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-7
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-3
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

 

[bialy7]

What problem have you found a solution for? What was the solution?