On Monday 28 May 2001 16:27, Eugenio Diaz wrote:
> Eugenio Diaz wrote:
> > After upgrading to kernel-2.4.4-6mdk, the boot process halts to single
> > user just after the "Checking file systems" message. It complains about
> > filesystem being mounted; which I traced back to fsck ... Anyway, after
> > a few minutes of troubleshooting I determined that the kernel is first
> > mounting the root filesystem as read-write instead of read-only as it
> > should be; and as expected, fsck complains, dropping into single user
> > mode.
> >
> > I don't know why this is happening, or where to properly fix it. Is this
> > hard coded when the kernel is compiled, or is this configurable by lilo?
> >
> > I fixed it temporarily by adding the following line to rc.sysinit just
> > before fsck is called:
> >
> > mount -n -o remount,ro /
>
> I just remembered that the "read-only" directive in the lilo.conf is what
> controls this.
>
> Well, then there most be something wrong with either lilo, or the kernel,
> since: a) I haven't changed my lilo.conf, and b) it contains the
> "read-only" directive.
>
> I suspect the kernel is at fault.
>
I'm using kernel-2.4.4-6mdk in cooker and don't have this problem - but I
couldn't use cooker's lilo - I chrooted /cooker from 8.0 and ran lilo from
there.
I have a Promise UDMA100 controller, and cooker's installer sees my three
drives as hd{e,f,g} but the installed kernel sees them as hd{a,b,c}, so lilo
doesn't work for me at install time. Prior to cooker upgrade I have to alter
fstab to hd{e,f,g}, then do the hd upgrade, skip lilo, boot into 8.0, chroot
/cooker, change fstab back, run lilo - then I can boot cooker sucessfully.
I haven't yet tried rerunning lilo from cooker, but I suspect your problem is
caused by cooker's lilo rather than the kernel.
--
Linux Mandrake release 8.0 (Traktopel) for i586
Linux 2.4.3-20mdk-p, KDE: 2.1.2, Qt: 2.3.0
Uptime 5 hours 11 minutes
