Bug#901289: breaks boot in containers

Adam Borowski kilobyte at angband.pl
Sun Dec 23 21:58:34 GMT 2018

Uh oh...  looks like the logsave issue suddenly became RCish: it prevents
lxc containers from booting unattended:

mordor:[~]# lxc-start -F -n durthang
INIT: version  booting

   OpenRC 0.39 is starting up Linux 4.18.0-0.bpo.3-amd64 (x86_64) [LXC]

 * /proc is already mounted
 * Mounting /run ... * /run/openrc: creating directory
 * /run/lock: creating directory
 * /run/lock: correcting owner
 * Caching service dependencies ... [ ok ]
Setting the system clock.
hwclock: Cannot access the Hardware Clock via any known method.
hwclock: Use the --verbose option to see the details of our search for an access method.
Unable to set System Clock to: Sun Dec 23 21:54:59 UTC 2018 ... (warning).
Activating swap...done.
Checking file systems.../etc/init.d/checkfs.sh: 94: /etc/init.d/checkfs.sh: logsave: not found
failed (code 127).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning).
Give root password for maintenance
(or press Control-D to continue): 

Host: stretch, guest: unstable.
So we need to fix this one way or another...

⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄⠀⠀⠀⠀ to the city of his birth to die.

More information about the Debian-init-diversity mailing list