Re: systemd woes continue
Aurelien Jarno <[email protected]>
| Newsgroups | gmane.linux.debian.ports.alpha |
|---|---|
| Message-ID | <[email protected]> |
On 2019-09-01 21:12, Aurelien Jarno wrote: > On 2019-07-17 20:36, Michael Cree wrote: > > On Wed, Jul 10, 2019 at 09:54:40PM -0500, Bob Tracy wrote: > > > First, "systemd" still cannot handle systems with persistent filesystems > > > other than "/" and "/usr". As far as I know, the bug report I filed > > > against "systemd" is still open, and no progress has been made on that > > > front. > > > > The bug I see on my XP1000 with systemd is that it fails to mount > > the filesystems in /etc/fstab and so stops in emergency mode; one > > can enter the root password, issue "mount -a" and "swapon -a" and > > exit and the boot resumes fines. > > This issue is reproducible in qemu-system-alpha. I have never seen that > on other architectures. > > In my case there are a few infos about the issue in the boot log (I > don't remember seeing that before, so they might have appeared with > recent systemd versions): > > [ 15.010734] systemd[1]: Set hostname to <alpha>. > [ 15.052726] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument > [ 16.959952] systemd[1]: Condition check resulted in udev Kernel Socket being skipped. > [ 16.962881] systemd[1]: Starting of /dev/disk/by-uuid/4b9cdcc1-bb8b-4905-97cc-0a9be7a44bcc not supported. > [UNSUPP] Starting of /dev/disk/by-u…cc-0a9be7a44bcc not supported. > [ 16.970694] systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/4b9cdcc1-bb8b-4905-97cc-0a9be7a44bcc. > [DEPEND] Dependency failed for File…1-bb8b-4905-97cc-0a9be7a44bcc. > [ 16.974600] systemd[1]: Dependency failed for /boot. > [DEPEND] Dependency failed for /boot. > [ 16.977530] systemd[1]: Dependency failed for Local File Systems. > [DEPEND] Dependency failed for Local File Systems. > [ 16.980460] systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. > [ OK ] Started Emergency Shell. > [ OK ] Reached target Emergency Mode. > > ... > > You are in emergency mode. After logging in, type "journalctl -xb" to view > system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" > to boot into default mode. > Give root password for maintenance > (or press Control-D to continue): In my case, upgrading glibc to 2.29 (now available in unstable) fixed the issue. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net