fsck forced on every system crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, May 22, 2002 at 10:03:58PM -0400, David Chase wrote:

> Ok, there's obviously something really dumb that I'm missing and I'll probably feel like an ass when someone points it out.

Yes, I'm afraid so.  :-)

> Oh well, here goes.  I executed the following:
> $ mkinitrd -v -f initrd-2.4.7-10smp.img 2.4.7-10smp
> 
> It executes without a hitch and reports that ext3 has been loaded.  Then I run lilo and it too executes without a hitch.  Here is my lilo.conf:
> 
> image=/boot/vmlinuz-2.4.7-10smp
> 	label=Linux
> 	read-only
> 	root=/dev/hda1
> 	append="hdd=ide-scsi"

You made an initrd, but didn't tell lilo to load it, so the ext3
module in the initrd is naturally being totally ignored!  You need to
add an "initrd=" line to the lilo entry for this image.

Cheers,
 Stephen





[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux