Ubuntu Container disk resized now wont start.

[proxmoxertj]

I have a Ubuntu container, I needed more space and went to resources and selected root disk then resize and entered more GBs and clicked resize disk. Ever since that point it wont start.

I get this in the task log on Start command:
run_buffer: 321 Script exited with status 255
lxc_init: 846 Failed to run lxc.hook.pre-start for container "101"
__lxc_start: 2002 Failed to initialize container "101"
TASK ERROR: startup for container '101' failed

This is the output of the resize:
Image resized.
e2fsck 1.46.2 (28-Feb-2021)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/var/lib/vz/images/101/vm-101-disk-0.raw: 74119/786432 files (0.3% non-contiguous), 1750406/3145728 blocks
resize2fs 1.46.2 (28-Feb-2021)
resize2fs: MMP: invalid magic number while trying to resize /var/lib/vz/images/101/vm-101-disk-0.raw
Please run 'e2fsck -fy /var/lib/vz/images/101/vm-101-disk-0.raw' to fix the filesystem
after the aborted resize operation.
Resizing the filesystem on /var/lib/vz/images/101/vm-101-disk-0.raw to 2624585728 (4k) blocks.
Failed to update the container's filesystem: command 'resize2fs /var/lib/vz/images/101/vm-101-disk-0.raw' failed: exit code 1

TASK OK

 

[proxmoxertj]

Ok, I cloned it (broke) and then started the cloned copy and it works. What???
On the cloned this is what I have which is not typical SDA devices I have Loop

root@Utility01:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 8G 0 loop loop1 7:1 0 8G 0 loop loop2 7:2 0 9.8T 0 loop / sda 8:0 0 931.5G 0 disk |-sda1 8:1 0 1007K 0 part |-sda2 8:2 0 512M 0 part `-sda3 8:3 0 931G 0 part root@Utility01:~# fdisk -l root@Utility01:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/loop2 9.7T 4.9G 9.3T 1% / none 492K 4.0K 488K 1% /dev udev 7.8G 0 7.8G 0% /dev/tty tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 1.6G 88K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock root@Utility01:~#

 

[oguz]

hi,

Ok, I cloned it (broke) and then started the cloned copy and it works. What???

that's interesting but glad that it works now.

On the cloned this is what I have which is not typical SDA devices I have Loop

that is normal with containers.

I have a Ubuntu container, I needed more space and went to resources and selected root disk then resize and entered more GBs and clicked resize disk.

which PVE version are you using? pveversion -v

could you also post the container configuration? pct config 101

also, what was the previous size and how many GBs did you add on top?