On Thu, Feb 5, 2009 at 6:27 AM, Mark Knecht <[email protected]> wrote: > On Thu, Feb 5, 2009 at 6:15 AM, Mark Knecht <[email protected]> wrote: >> On Thu, Feb 5, 2009 at 2:11 AM, Duncan <[email protected]> wrote: >> <SNIP> >>> >>> How all that applies to this thread is just this, here's the default >>> order: >>> >>> CRITICAL_SERVICES="checkroot modules checkfs localmount clock bootmisc" >>> >>> See the problem? The clock service isn't started until AFTER checkroot >>> and checkfs, and due to the above, changing the dependencies as one might >>> normally do won't change that, so the system won't be adjusted for local >>> time until after they have run. That's what's causing the issue. >>> >>> To fix it, try this: >>> >>> In /etc/runlevels/${BOOTLEVEL}/ (where $BOOTLEVEL is simply "boot", if >>> you don't do anything fancy like setting it on the kernel command line), >>> as root, create the (hidden) file .critical with the following contents, >>> using the following command (with the path changed if appropriate for >>> your setup, it's wrapped here, but it's all one command): >>> >>> echo CRITICAL_SERVICES="clock checkroot modules checkfs localmount >>> bootmisc" > /etc/runlevels/boot/.critical >>> >>> What that does is simply reorder those services, so clock is started >>> first, before checkroot, instead of after everything is already fscked >>> and mounted. >>> >>> Of course, everything necessary to run the clock service must be on your >>> root filesystem, and it won't be able to write anything to it since at >>> that point, the filesystem is still read-only. However, as Gentoo is >>> normally setup, that shouldn't be an issue, or at least it wasn't for me, >>> way back when I was dealing with it, which is why I knew about it, tho I >>> did have to refresh my memory as that was well over a year ago, IIRC. >>> >>> I believe that'll fix your problem! =:^) >> >> Well, unfortunately, it didn't and now the machine doesn't boot. It >> stops at boot time with the message: >> >> * Failed to source /etc/init.d/CRITICAL_SERVICES/clock: No such file >> or directory >> >> I'll have to find a Live CD and see if I can remove the .critical file >> for the time being. >> >> I guess this implies to those that come after me that they should >> check their file system for clock, checkroot, modules, etc., first? >> >> - Mark >> > > As a follow up I'm in the Live CD environment. Looking in > /mnt/gentoo/etc/runlevels/boot there is at least one new link created > and marked red: > > CRITICAL_SERVICES=clock -> /etc/init.d/CRITICAL_SERVICES=clock > > To me that's a pretty strange name for both the link and the target, > but that's just me... > > Removing the file, the new link, and rebooting worked. > > Thanks, > Mark >
Now, revisiting the file it seems that the echo command has dropped the quotes so the line in the file looks like CRITICAL_SERVICES=checkroot modules checkfs localmount clock bootmisc I'll wait for a little instruction about this. Why did they get dropped and should I add them in by hand? thanks, Mark
