Am 30.08.20 um 18:45 Uhr schrieb Viktor Sævarsson:
Hi all!
I have a tumbleweed transactional server that is unable to boot after automatically updating to snapshot 20200824. The error seems to occur during volume mounting.
Related logs:
etc.mount: Directory /etc to mount over is not empty, mounting anyway overlayfs: failed to resolve '/sysroot/var/lib/overlay/395/etc': -2 ignored apparmor.service errors etc.mount: Mount process exited, code=exited, status=32/n/a etc.mount: Failed with result 'exit-code'. Failed to mount /etc. bunch of dependency errors and related mounting errors
Oh dear, that's not good: I assume /var/lib/overlay is empty? If so then I've seen that once before, but wasn't able to find out what caused it. A recent health-checker update (in case you are using it) should prevent such a broken system from booting and switch to emergency mode instead to prevent any other jobs doing any more harm like in this case. What you can do now: If you haven't changed anything in /etc lately, then you can try to recreate the directories listed in /etc/fstab in the hopes that there haven't been any new configuration files from package updates. I'll add more consistency checks into transactional-update to prevent such a case in the future, and also change the overlay mechanism to make this more robust, i.e. always sync the /etc status of the currently running system to make a rollback in case of a loss of the overlays easier. Ignaz
This warning occurs towards the start of the boot but I'm not sure that it is related: "sysroot-var.mount: Directory /sysroot/var to mount over is not empty, mounting anyway."
Regards
-- Ignaz Forster <iforster@suse.com> Research Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org