e2fsck doesn't run after "maximal mount count reached" during boot?

[Shern, Benjamin J]

The root partition should be mounted read-only - at which point it can
be fsck'ed.  After it comes back clean, it should be mounted read-write.
Ben

  > -----Original Message-----
  > From: Terry Chan [mailto:tpchan at attbi.com] 
  > Sent: April 23, 2003 9:41 AM
  > To: lunar at lunar-linux.org
  > Subject: Re: e2fsck doesn't run after "maximal mount count 
  > reached" during boot?
  > 
  > 
  > Ralph,
  > 
  > No it can't really happen automatically.  Slight chicken 
  > and egg problem.
  > 
  > You can't run e2fsck on a partition that is mounted already 
  > -- it must be run
  > against a partition that is NOT mounted.  Egg part is that 
  > the e2fsck binary is
  > only located on the partition that you are trying to fsck.  
  > That's why you
  > need to boot from another source like the ISO to run e2fsck.  See ?
  > 
  > Terry Chan
  > ----------------------------------------------------------------
  > On Wed, Apr 23, 2003 at 08:51:48AM -0400, Ralph Crongeyer wrote:
  > > Terry, Thanks for the response. I just did that and it 
  > worked with no 
  > > problems! Thanks!
  > > 
  > > But shouldn't this be happining automatically when the 
  > maximal mount count is 
  > > reached?
  > > 
  > > Ralph
  > > 
  > > > Ralph,
  > > >
  > > > Boot your Lunar box with any version of the Lunar 
  > Install/Rescue ISO. 
  > > > e2fsck is of course included on the ISO.
  > > >
  > > > After the ISO is booted, get to the point in the 
  > install process before
  > > > you have to mount partitions and just use the menu 
  > option to drop to
  > > > a shell prompt.  From there you can run "e2fsck /dev/dha2".
  > > >
  > > > Terry Chan
  > _______________________________________________
  > Lunar mailing list
  > Lunar at lunar-linux.org
  > http://lunar-linux.org/mailman/listinfo/lunar
  >