Not really sure why my CT stopped booting

jcazes

New Member
Jun 11, 2024
4
0
1
I have a standalone proxmox machine with 2 vm's and 1 CT. I'm not sure if its because I shutdown the machine using the power button or because I updated to the latest 8.2.2. but now I can't seem to start the CT. I get the following error and have no idea where to look.

lxc-start 102 20240611024534.161 DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/sh
are/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: closing file '/etc/network/interfa
ces.tmp.5286' failed - No space left on device

Any help greatly appreciated.
 
Last edited:
No space left on device
Hi,
seems like your container filesystem ran out of space. Can you mount the filesystem via pct mount <VMID>? If so, you might navigate to the path returned as result to that command and inspect the filesystem and if possible clean up some unneeded files to create space. Once done, you can unmount the filesystem again via pct unmount <VMID> and start the container via pct start <VMID>.

Edit: Fixed typo.
 
  • Like
Reactions: Kingneutron
Yup...that was it.

When the error line inclued interfaces.tmp, I thought it had something to do with the network.

My next question is how can I increase the filesystem?
 
My next question is how can I increase the filesystem?
You can increase the root disk of the container via e.g. the WebUI by navigating to <CT> > Resouces > <select root disk> > Volume Action > Resize and add the desired storage amount. This will already increase your available storage for the root filesystem of the container. The same action can be used to increase a disk mounted as mount point.
 
Again...thank you very much Chris. You were extremely helpful.

I was able to resize my rootfs and we're all good. Too bad promox doesn't give a warning when approaching the limit OR purposely leave enough room to mount the fs. Like a reserve reservoir.

Anyways much appreciate the help.
 
Too bad promox doesn't give a warning when approaching the limit OR purposely leave enough room to mount the fs. Like a reserve reservoir.
You might want to add some monitoring inside the container or set up filesystem quotas if that is of concern, nothing Proxmox VE should be concerned with.

Anyways much appreciate the help.
Glad to help
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!