Bug#774412: Re: Bug#774412: systemd unable to boot with fixed mount points

[Michael Biebl]

Am 03.01.2015 um 15:59 schrieb Andrei POPESCU:
> Control: severity -1 minor
> Control: retitle -1 systemd-fsck tries to check unavailable filesystems even if 0 in fstab passno field
> 
> On Sb, 03 ian 15, 13:42:34, HJ wrote:
>>> Does systemd still try to fsck the non-available filesystem?
>>
>> no ;)
> 
> Ok, since systemd is failing the boot by design if a filesystem not 
> marked 'nofail' or 'noauto' is missing I'll re-purpose this bug to be 
> about the additional delay due to systemd-fsck trying to check a 
> filesystem which is not available, despite it being marked to not be 
> checked in fstab.
> 
> However, since fsck will be skipped in the normal case I'll downgrade to 
> 'minor'.

Are you sure, that systemd does actually run fsck for the device?

Looking back at HJs first message, he mentioned:

> at first fsck trieds to check this drive even if it does not exist and is
> disabled, this already takes ~1:30 minutes and I'm unable to stop it(A start
> job is running...)

We would need the full log message here, but to me, that rather looks
like systemd waits for the /dev/sdc1 device to appear and enters rescue
mode after the (internal) 90s timeout.

HJ, if you boot again with the faulty fstab, which drops you into the
emergency shell, can you check if you have active
systemd@<device-name>.service unit for /dev/sdc1 (it's most likely named
systemd at dev-sdc1.service).






-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150103/605e65e4/attachment-0002.sig>