fsck forced on every system crash

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

Subject: fsck forced on every system crash
From: chased@rogers.com (David Chase)
Date: Thu, 23 May 2002 20:17:09 -0400
In-reply-to: <3CEC9F7D.5090406@free.fr>
References: <008301c1ffb0$82d81210$8e1c7018@cr464463b> <20020520060557.GH26598@turbolinux.com> <3CE91B8E.2000109@rogers.com> <20020520182630.GB7784@turbolinux.com> <000e01c2011e$df936260$8e1c7018@cr464463b> <20020522095611.A2082@redhat.com> <20020523020357.CMVP8996.fep04-mail.bloor.is.net.cable.rogers.com@cr464463-a><3CEC9F7D.5090406@free.fr>

QL> You are missing
QL> initrd=/boot/initrd-2.4.7-10smp.img
QL> in lilo.conf.

Yay, fixed!  Thanks to all for the patience.  Oddly enough "man lilo.conf" on my system makes no mention of the initrd directive, so I wasn't *totally* out to lunch...

References:
- fsck forced on every system crash
  - From: David Chase
- fsck forced on every system crash
  - From: Andreas Dilger
- fsck forced on every system crash
  - From: David Chase
- fsck forced on every system crash
  - From: Andreas Dilger
- fsck forced on every system crash
  - From: David Chase
- fsck forced on every system crash
  - From: Stephen C. Tweedie
- fsck forced on every system crash
  - From: David Chase
- fsck forced on every system crash
  - From: Qing Liu

Prev by Date: Bad directories appearing in ext3 after upgrade 2.4.16 -> 2.4.18+cvs
Next by Date: Bad directories appearing in ext3 after upgrade 2.4.16 -> 2.4.18+cvs
Previous by thread: fsck forced on every system crash
Next by thread: fsck forced on every system crash
Index(es):
- Date
- Thread

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

Powered by Linux