Error when starting an ubuntu container

[CopperCable]

A few hours ago the service installed in the container with Ubuntu 22.04 was no longer reachable, I restart the container and these errors appear

run_buffer: 571 Script exited with status 255
lxc_init: 845 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2034 Failed to initialize container "102"
TASK ERROR: startup for container '102' failed

I tried to follow some posts on Reddit but I couldn't solve it, I also just updated proxmox to 8.2.4 from 8.2.2, how can I solve it?

 

[leesteken]

Maybe you can get some logs following the Wiki instructions: https://pve.proxmox.com/wiki/Linux_Container#_obtaining_debugging_logs ?

 

[CopperCable]

Maybe you can get some logs following the Wiki instructions: https://pve.proxmox.com/wiki/Linux_Container#_obtaining_debugging_logs ?

sure, here it is

run_buffer: 571 Script exited with status 255
lxc_init: 845 Failed to run lxc.hook.pre-start for container "102"
__lxc_start: 2034 Failed to initialize container "102"
0 hostid 100000 range 65536
INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/loop1.
dmesg(1) may have more information after failed mount system call.

DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: command 'mount /dev/loop1 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32

ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255
ERROR    start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "102"
ERROR    start - ../src/lxc/start.c:__lxc_start:2034 - Failed to initialize container "102"
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "102", config section "lxc"
startup for container '102' failed

 

[CopperCable]

I think I know the cause of the problem: the SSD was 99.99% full, I freed up space but it still gives me that error, can I repair it or do I have to recreate the container?

 

[leesteken]

I think I know the cause of the problem: the SSD was 99.99% full, I freed up space but it still gives me that error, can I repair it or do I have to recreate the container?

I don't know. Maybe restore it from backup to make sure you don't have any silent corruption due to write failing because of lack of space.

 

[CopperCable]

I don't know. Maybe restore it from backup to make sure you don't have any silent corruption due to write failing because of lack of space.

but I have never made a backup... how can I do it? and above all, how do I restore it from that backup if it happens again?

 

[leesteken]

but I have never made a backup...

Then the data is not important and you might as well recreate the container, after you free up space on your storage.

how can I do it? and above all, how do I restore it from that backup if it happens again?

Read the manual? Search this forum? Search the Wiki? have a look at the Backup section of the container using the Proxmox web GUI?

 

[CopperCable]

Then the data is not important and you might as well recreate the container, after you free up space on your storage.

Read the manual? Search this forum? Search the Wiki? have a look at the Backup section of the container using the Proxmox web GUI?

Thanks for your HUGE availability, if you don't feel like helping/teaching someone who knows less than you don't respond to requests for help. instead of making others feel stupid and lazy
If I had known how to fix the problem, how to make a backup and how to reload it I wouldn't have asked for help

 

[leesteken]

Thanks for your HUGE availability, if you don't feel like helping/teaching someone who knows less than you don't respond to requests for help. instead of making others feel stupid and lazy
If I had known how to fix the problem, how to make a backup and how to reload it I wouldn't have asked for help

To do a backup: Go the container in the Proxmox web GUI, go to the Backup section, press the Backup now button. You'll need to configure a storage that allows to store backups first.
To restore; Go the container in the Proxmox web GUI, go to the Backup section, select a backup and press the Restore button. Or go the backup storage in the Proxmox web GUI, go to the Backups section, select a previou backup and press the Restore button.

EDIT: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_vzdump

 

[CopperCable]

thanks, easier than I thought, I'll recreate the container and make backups this time