Re: systemd woes continue

Hi!

On 9/1/19 9:12 PM, Aurelien Jarno wrote:
>> 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.

Indeed. I have observed this as well on my XP-1000. I think I have sometimes seen that on sh4
but so far it's not clear to me what the problem is. I will have a look at the system issue
tracker and if it's not already reported, open a new issue upstream.

systemd upstream is usually very responsive when it comes to fixing such issues, so I'm confident
we can get this sorted out.

Adrian