[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem: Slow boot -- Mounts fail.



On 5/14/19, Dennis Wicks <wix@mgssub.com> wrote:
> Greetings;
>
> During the boot process there are several mount "jobs"
> started, and they all finish/fail with two messages;
>
> 	Dependency failed for ...
> 	Timeout waiting for ...
>
> that is except for root.
>
> I removed all the mounts for user partitions from fstab and
> just left the mounts for root, boot, home and home2 but got
> the same results for the four that were left. Incidentally,
> when I run the user mounts after the system is "up" it takes
> just a few seconds to mount 14 partitions.
>
> After the mounts "fail" the boot process stops in Emergency
> Mode, and I have the choice of logging on to root to fix the
> problem, or entering ctl-d to continue on. If I log on to
> root I find that all four of the volumes are mounted and
> nothing is wrong. If I choose ctl-d the boot process will
> continue with no problems.
>
> How do I prevent the mounts from failing and make the system
> continue on with the boot process?


Hi.. As usual, I probably won't be a whole lot of help, BUT.. that
never stops my keyboard. :)

#1 Is this something new, or has it been doing this all along? What
I'm thinking is.. What about the (logical step-by-step) mount order in
fstab? That might be one thing that would explain why it doesn't work
at bootup but then does work after one or two primary mount points are
successful...

#2 I experience something similar related to hardware failure of the
kind where it's after a power outage. The hard drive dock will need to
be turned back on via the hardware on/off button. That's obviously not
this case because you didn't mention that. I am mentioning it so that
maybe someone else can check it off their list. :)

For my instances, the message will just keep unsuccessfully cycling
through all the various mount points that reference partitions on that
dock. If I'm distracted and don't see those advisements occurring,
mine will eventually end up at that same point of it kicking to the
prompt along with offering that CTRL+D as an option. Click the
hardware on/off button and then CTRL+D, and mine then completes yet
another successful boot operation. *yay, TEAM!*

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *


Reply to: