[systemd-devel] No maintenance shell on local fs failure (/bin/sh: no such file or directory)

[Reindl Harald]

Am 15.01.2016 um 11:40 schrieb Frank Steiner:
> This didn't mean that /bin/echo was not found, but the CHDIR failed!
> That was caused by /root being a symbolic link to /local/home/root
> (we strictly separate any user data including root from the system, so
> that we can reformat / on reinstalling or upgrading the system).
> But /usr/lib/systemd/system/emergency.service contains:

that is a BIG MISTAKE and there is a good reason that by default the 
homedir auf root is *not* below /home just because /home is typically a 
own partition

the reason is to avoid the problems you had and make sure that roots 
environment is available even when all disks but the rootfs are failing

> [Service]
> Environment=HOME=/root
> WorkingDirectory=/root
> ...
>
> and because /root was a link pointing to nowhere (/local is not mounted
> when starting the emergency service, only /) the chdir failed.
>
> I solved this buy changing the lines to
> Environment=HOME=/
> WorkingDirectory=/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20160115/878256e1/attachment.sig>