Re: Cobalt Mips chkrroot.sh

[Peter Horton <pdh@colonel-panic.org>]

On Thu, Mar 17, 2005 at 02:43:54AM -0500, Gerald Waugh wrote:
> 
> Has the chkroot.sh on every reboot ever been resolved.
> I searched for an answer, but never found one.
> We are using 350GB drives on file servers, and it takes a long time!
> Granted reboots aren't often, but... Sh**t happens!
> 

Try enabling 'sulogin', logging in before the root is remounted r/w,
loading the time from the RTC (hwclock --hctosys --utc) and then
checking the affected volume (e2fsck -f /dev/hda???). IIRC it'll then
check on the next boot but should be okay after that ...

P.

PS - rather that enabling 'sulogin' you could always pass
'init=/bin/bash' to the kernel instead.