Hi Sven, > Did you consider the "nofail" Option for your /etc/fstab entries which might > fail/shouldn't fail?
no, not yet. Maybe it will work. But the question is: Are there more side effects than this one? Probably it won't help here. The rw-remount of / is too late: Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory /var/cache: Read-only file system Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory /var/cache/man: No such file or directory Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory /var/run/screen: Read-only file system Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory /var/run/sshd: Read-only file system Jun 18 17:25:48 train1 systemd-tmpfiles[163]: Failed to create directory /var/lib: Read-only file system and right after: Jun 18 17:25:48 train1 systemd-fsck[157]: /dev/sda1: clean, 8403/65536 files, 84857/262144 blocks and Jun 18 17:25:50 train1 kernel: EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro /dev/sda1 is the root partition... So it tries two seconds before / is mounted rw to create the needed directories. Ok, one could mount per se root as rw instead of ro during boot up... But my concerns are: How much headaches will I get with systemd? Is it worse the effort? An remote system where ssh may be failing on boot up is nothing which makes me in any way happy. This was one day of headache: Will there be much more? Best regards Dirk -- +----------------------------------------------------------------------+ | Dr. Dirk Geschke / Plankensteinweg 61 / 85435 Erding | | Telefon: 08122-559448 / Mobil: 0176-96906350 / Fax: 08122-9818106 | | d...@geschke-online.de / d...@lug-erding.de / kont...@lug-erding.de | +----------------------------------------------------------------------+
