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

[Shern, Benjamin J]

This here is the culprit - 
According to the fstab(5) manpage the last digit for root should be 1 and
all others should be 2.  Lunar install defaults to 0 which means don't
check....
Ben


  > -----Original Message-----
  > From: Shern, Benjamin J 
  > Sent: February 12, 2003 10:59 AM
  > To: 'lunar at lunar-linux.org'
  > Subject: Root disk not getting fsck
  > 
  > 
  > Yikes!!!
  > 
  > My root partition was not getting fsck'ed after an unclean dismount.
  > I believe I see why:
  > 
  > Just a heads-up for those of you who have a /boot partition 
  > on ext2 and /
  > partition on some other fs type.....
  > 
  > Check your /etc/fstab and make sure the last digit is 
  > non-zero on any
  > partitions you care about!
  > Ben
  > 
  > 
  > 
  > lunar.install from the .iso :
  > 
  > determine_fstab_settings()  {
  > 
  >   LAST="0 0"
  >   case  $FSYS  in
  >         swap)  OPTIONS="defaults"                        ;;
  >     reiserfs)  OPTIONS="defaults,notail,noatime"         ;;
  >         ext3)  OPTIONS="defaults,noatime"                ;;
  >          xfs)  OPTIONS="defaults,noatime"
  > ;;
  >         ext2)  OPTIONS="defaults,noatime"
  >                case  $POINT  in
  >                  /)  LAST="0 1"                          ;;
  >                  *)  LAST="0 2"                          ;;
  >                esac
  >                ;;
  >   esac
  > }

  > -----Original Message-----
  > From: Shern, Benjamin J [mailto:ShernBJ at louisville.stortek.com] 
  > Sent: April 23, 2003 9:46 AM
  > To: 'Lunar Linux Mailing List! (all are welcome)'
  > Subject: RE: e2fsck doesn't run after "maximal mount count 
  > reached" during boot?
  > 
  > 
  > 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
  >   > 
  > _______________________________________________
  > Lunar mailing list
  > Lunar at lunar-linux.org
  > http://lunar-linux.org/mailman/listinfo/lunar
  >