The failing fsck problem on root FS has disappeared now, either with new 
initscripts or last kernel 19mdk.

I have to check for raid linear on my other machine now

thanks
Pascal

Le Mercredi 13 F�vrier 2002 19:16, pascal a �crit :
> Le Wednesday 13 February 2002 17:42, vous avez �crit :
> maybe try simulating a bad shutdown  by  touching  /.autofsck and then
> reboot.
>
> > pascal <[EMAIL PROTECTED]> writes:
> > > Other problems with last kernel and boot scripts:
> > >
> > > 1. It seems that your initrd is corrupted but in a subtle manner.
> > > Sometimes uncompressing the initrd after boot gives error, sometimes
> > > not.
> > >
> > > I suspect that when the uncompressor does not detect the error, we have
> > > various module loading problems ( i got lots of usb-uhci modules not
> > > found errors etc...).
> > >
> > > What i did is rebuilding the initrd while in maintenance mode, and all
> > > when well after that, except for one thing :
> > >
> > > 2. Is the root FS mounted RW at the beginning ? because
> > > /etc/rc.d/rc.sysinit now complains that it cannot fsck / which is
> > > mounted !  I checked the rc.sysinit and discover the fastboot option
> > > which was the only way for me to skip this step at boot now (except
> > > forcing rc=0 after call to Fsck() ). Is there a place where all this is
> > > logged in a file ?
> > > With this false fsck error we are dropped to the maintenance mode and
> > > cannot ever go to our live normal system !
> >
> > I'm sorry but i really can't reproduce that problem.

Reply via email to