fsck problem on updating to F10 -- SOLVED

Tom London selinux at gmail.com
Tue Nov 11 00:10:29 UTC 2008


On Mon, Nov 10, 2008 at 3:57 PM, Patrick O'Callaghan
<pocallaghan at gmail.com> wrote:
> On Mon, 2008-11-10 at 15:44 -0800, Tom London wrote:
>> On Mon, Nov 10, 2008 at 3:34 PM, Patrick O'Callaghan
>> <pocallaghan at gmail.com> wrote:
>> > On Mon, 2008-11-10 at 16:42 -0500, Bill Nottingham wrote:
>> >> Patrick O'Callaghan (pocallaghan at gmail.com) said:
>> >> > > I'm doing a yum update right now to see if it goes away, but any hints
>> >> > > would be welcome.
>> >> >
>> >> > I figured it out. The problem is with an external USB drive, which takes
>> >> > a few seconds to come online. The boot process thinks it's failing, but
>> >> > once I get to the root shell and run fsck, it's fine.
>> >>
>> >> So, the udevsettle in rc.sysinit isn't actually working for you. Lovely.
>> >
>> > I took a look, and rc.sysinit has no reference to udevsettle. This is
>> > from initscripts-8.85-1.x86_64.
>> >
>> > poc
>> >
>> udevsettle is "called' from /sbin/start_udev.
>
> So I see. The question is then, how does it decide on a timeout value?
> There's a udevtimeout variable but I'm not sure how it's set. Some
> sleuthing required.
>
> poc
>
Believe you can set it on the boot line with udevtimeout=NNN

tom
Tom London




More information about the fedora-test-list mailing list