[SOLVED] Can't start CT: "JBD2: Invalid checksum recovering block 1 in log"

Feb 3, 2018
6
1
6
34
I'm lost and I'm not seeing anything on the google that fits what I'm getting.

Any Ideas?

Code:
 Unit pve-container@104.service has begun starting up.
Feb 04 19:49:20 moxprox0 kernel: JBD2: Invalid checksum recovering block 1 in log
Feb 04 19:49:21 moxprox0 kernel: JBD2: recovery failed
Feb 04 19:49:21 moxprox0 kernel: EXT4-fs (loop2): error loading journal
Feb 04 19:49:21 moxprox0 lxc-start[26180]: lxc-start: 104: lxccontainer.c: wait_on_daemonized_start: 751 No such file or d
Feb 04 19:49:21 moxprox0 lxc-start[26180]: lxc-start: 104: tools/lxc_start.c: main: 371 The container failed to start.
Feb 04 19:49:21 moxprox0 lxc-start[26180]: lxc-start: 104: tools/lxc_start.c: main: 373 To get more details, run the conta
Feb 04 19:49:21 moxprox0 lxc-start[26180]: lxc-start: 104: tools/lxc_start.c: main: 375 Additional information can be obta
Feb 04 19:49:21 moxprox0 systemd[1]: pve-container@104.service: Control process exited, code=exited status=1
Feb 04 19:49:21 moxprox0 systemd[1]: Failed to start PVE LXC Container: 104.
-- Subject: Unit pve-container@104.service has failed
-- Defined-By: systemd
--
-- Unit pve-container@104.service has failed.
--
-- The result is failed.
Feb 04 19:49:21 moxprox0 pvedaemon[4024]: unable to get PID for CT 104 (not running?)
Feb 04 19:49:21 moxprox0 systemd[1]: pve-container@104.service: Unit entered failed state.
Feb 04 19:49:21 moxprox0 systemd[1]: pve-container@104.service: Failed with result 'exit-code'.
Feb 04 19:49:21 moxprox0 pvedaemon[26178]: command 'systemctl start pve-container@104' failed: exit code 1
Feb 04 19:49:21 moxprox0 pvedaemon[4022]: <root@pam> end task UPID:moxprox0:00006642:00041AD3:5A77B81F:vzstart:104:root@pa
lines 2957-2992/2992 (END)
 
Code:
pct fsck <vmid>
Do a filesystem check of your container, seems your containers EXT4 has issues.
 
Output:

Code:
root@moxprox1:~# pct fsck 104
fsck from util-linux 2.29.2
/mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw: recovering journal
JBD2: Invalid checksum recovering block 1 in log
Journal checksum error found in /mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw
/mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw: Clearing orphaned inode 13 (uid=0, gid=0, mode=0100600, size=0)
/mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw was not cleanly unmounted, check forced.
/mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw: 27269/7864320 files (0.1% non-contiguous), 882873/31457280 blocks
command 'fsck -a -l /mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw' failed: exit code 1

I moved the VM to another node and got:

Code:
root@moxprox0:~# pct fsck 104
fsck from util-linux 2.29.2
/mnt/pve/xochitl-vm/images/104/vm-104-disk-2.raw: clean, 27270/7864320 files, 882873/31457280 blocks

I had to change some networking setting to get it to boot but- it is now booted.

Thank you Alwin!