Debian LXC container won't start after update due to fastboot.tmp

rampage

New Member
Oct 17, 2016
22
2
3
40
Debian LXC container won't start after update due to fastboot.tmp

the error is

root@pve:~# lxc-start -n 113 -F --logfile /var/113.log
unable to open file '/fastboot.tmp.11018' - Read-only file system
error in setup task PVE::LXC::Setup::pre_start_hook
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "113".
lxc-start: start.c: __lxc_start: 1313 Failed to initialize container "113".
lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained by setting the --logfile and --logpriority options.
root@pve:~# cat /var/113.log
lxc-start 20161214092255.168 ERROR lxc_conf - conf.c:run_buffer:347 - Script exited with status 1
lxc-start 20161214092255.168 ERROR lxc_start - start.c:lxc_init:450 - Failed to run lxc.hook.pre-start for container "113".
lxc-start 20161214092255.168 ERROR lxc_start - start.c:__lxc_start:1313 - Failed to initialize container "113".
lxc-start 20161214092255.168 ERROR lxc_start_ui - tools/lxc_start.c:main:365 - The container failed to start.
lxc-start 20161214092255.168 ERROR lxc_start_ui - tools/lxc_start.c:main:369 - Additional information can be obtained by setting the --logfile and --logpriority options.
 
It's is becouse zfs sub-vol stays in readonly mode.(for me it happens from time to time while i reboot container)

lxc-start -n 108
lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 367 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained by setting the --logfile and --logpriority options.


lxc-start -n 108 --foreground
unable to open file '/fastboot.tmp.19662' - Read-only file system
error in setup task PVE::LXC::Setup::pre_start_hook
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "108".
lxc-start: start.c: __lxc_start: 1313 Failed to initialize container "108".
lxc-start: tools/lxc_start.c: main: 365 The container failed to start.
lxc-start: tools/lxc_start.c: main: 369 Additional information can be obtained by setting the --logfile and --logpriority options.


#check subvol properties. (
zfs get all |grep 108
....
rpool/data/subvol-108-disk-1 readonly on temporary
....

zfs set readonly=off rpool/data/subvol-108-disk-1
...

#verify result.
zfs get all |grep 108


#And finally start container
lxc-start -n 108
 

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!