Re: systemd : Timed out waiting for defice dev-disk-by…

[Philip Seeger <p0h0i0l0i0p@gmail.com>]

On 07/27/2015 07:20 AM, Duncan wrote:
> Philip Seeger posted on Sun, 26 Jul 2015 22:39:04 +0200 as excerpted:
>
>> Hi,
>>
>>> 50% of the time when booting, the system go in safe mode because my 12x
>>> 4TB RAID10 btrfs is taking too long to mount from fstab.
>>
>> This won't help, but I've seen this exact behavior too (some time ago).
>> Except that it wasn't 50% that it didn't work, more like almost
>> everytime.
>> Commenting out the fstab entry "fixed" it, mounting using a cronjob
>> (@reboot) worked without a problem.
>>
>> (As far as I remember, options like x-systemd.device-timeout didn't
>> change anything.)
>>
>> If someone has the answer, I'd be interested too.
>
> You mean something like a custom systemd *.service unit file?  That's
> what I'd do here. =:^)
> [...]

Thanks for the tip and the detailed explanation. I believe I have tried 
something similar back then (involving a custom systemd service), but 
it's too long ago, I can't tell for sure. What I do remember clearly is 
that the timeout error came within seconds after invoking the mount 
command, maybe 5 or 10 seconds - certainly not even close to 30 seconds. 
Just wanted to throw that out there.

Other than that, I believe using the noauto option together with a 
custom systemd service sounds like it should do the trick (and sounds 
like a clean solution if you indeed want that filesystem mounted on 
demand only), but then again, mounting a filesystem without that option 
should work too. In any case, I've saved your email, maybe I'll hit that 
issue again someday - I'll try your suggestion then.


Philip