Multiple pct commands, including start: Failed to parse thin params: Error

[kyeotic]

I'm not sure how related this is, but I recently had a a ZFS pool fail and require recreation. I still haven't been able to get everything else working because some containers won't start. Several pct commands show the error "Failed to parse thin params: Error" 3 times before showing anything else, even if the command ultimately succeeds, and even on containers that do start. I don't know how to troubleshoot this.


This command succeeded

root@homelab:~# pct start 105
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.

This is the log anytime I try to start one of the other containers, 106

()
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
run_buffer: 571 Script exited with status 32
lxc_init: 845 Failed to run lxc.hook.pre-start for container "106"
__lxc_start: 2034 Failed to initialize container "106"
TASK ERROR: startup for container '106' failed

Here is that containers config

root@homelab:~# pct config 106
arch: amd64
cores: 2
features: nesting=1
hostname: kye-nas
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.1,hwaddr=BC:24:11:8D:D2:DA,ip=192.168.0.11/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-106-disk-0,size=8G
swap: 512
unprivileged: 1

EDIT

I tried resizing the disk of 106 and got some weird errors that seem to indicate the disk is corrupt. This is the same local-lvm storage volume the working containers are using.

root@homelab:~# pct resize 106 rootfs 10G
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Failed to parse thin params: Error.
  Size of logical volume pve/vm-106-disk-0 changed from 8.00 GiB (2048 extents) to 10.00 GiB (2560 extents).
  Logical volume pve/vm-106-disk-0 successfully resized.
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Input/output error while trying to open /dev/pve/vm-106-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>

Failed to update the container's filesystem: command 'e2fsck -f -y /dev/pve/vm-106-disk-0' failed: exit code 8