I actually do think that systemd handles this correctly. How is it
supposed to know if the mount points listed in /etc/fstab aren't vital
for the system to function properly unless you tell it so?
Thinking about it, I actually agree. Let us close this bug.
If you want one you can add a line
retitle 743265 systemd drops into emergency mode if devices from /etc/fstat are
missing
thanks
Hi,
Am 02.04.2014 05:59, schrieb Norbert Preining:
On Tue, 01 Apr 2014, Michael Biebl wrote:
Apr 01 15:49:04 wienerschnitzel systemd[1]: Failed to start Load Kernel
Modules.
I confirm that
Package: systemd
Version: 204-8
Severity: important
Hi,
I just tried to boot with init=/bin/systemd, and that didn't
work out well:
* first some error message
Failed to start Load Kernel Modules.
(I think!)
* after that it tried to fsck.vfat my Win8.1 partition
* after that dropped me into
Am 01.04.2014 09:21, schrieb Norbert Preining:
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-sda3.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
dev-sda5.device...
Apr 01 15:49:04 wienerschnitzel systemd[1]: Expecting device
Hi Michael,
On Tue, 01 Apr 2014, Michael Biebl wrote:
Could you post your /etc/fstab? Are the devices/partitions you specified
in there all available during boot?
No, some of those are not available, and not marked with noauto.
I will try after adding noauto keywords.
instructions at [0]
On Tue, 01 Apr 2014, Michael Biebl wrote:
Apr 01 15:49:04 wienerschnitzel systemd[1]: Failed to start Load Kernel
Modules.
I confirm that adding the noauto option to the strange devices
allows booting with init=/bin/systemd.
The above message interestingly remains, but that might have
6 matches
Mail list logo
