Booting Problem After Power Loss (fsck)?

From: Rishi Chopra (rchopra_at_cal.berkeley.edu)
Date: 02/09/04

  • Next message: Gary: "RE: QMail? - additional thoughts" 
    Date: Sun, 08 Feb 2004 21:12:51 -0800
To: questions@freebsd.org

    Here's a summary of my problem so far:

    Server was idle (e.g. absolutely no processes running aside from
    csh, ttyv0 and ps) when power was cut; server reports a problem mounting
    /usr partition upon reboot.

    I have since tried the following:

    (1) Booted into single-user mode and ran 'fsck' - the latest output to
    the terminal says:

    **** FILE SYSTEM MARKED CLEAN ****
         /dev/da0s1e
         Last Mounted on /usr
         Phase 1 - check blocks and sizes

    After letting the system 'do its thing' for 5+ days, the output did not
    change.

    (2) I tried an 'fsck -p' and got the following message:

    /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771
    blocks, 0.1% fragmentations)

    The display has been stuck with that same output for countless hours now.

    Questions I have:

    (1) Have I suffered a total loss or is this still some way to revover my
    filesystem? After suffering a similar loss with a hardware raid-0
    failure under win2k, I was assuming the FreeBSD setup would be more
    durable. I would hate to walk away thinking that a simple power loss
    could wipe out a freebsd server under nothing more than one terminal login.

    (2) Why would a simple fsck of the filesystem not work in my case?

    Thanks,
    Rishi

    Ion-Mihai Tetcu wrote:

    > On Tue, 03 Feb 2004 01:09:22 -0800
    > Rishi Chopra <rchopra@cal.berkeley.edu> wrote:
    >
    >
    >>I booted into single-user mode and ran 'fsck' - the latest output to the
    >>terminal says:
    >>
    >>**** FILE SYSTEM MARKED CLEAN ****
    >> /dev/da0s1e
    >> Last Mounted on /usr
    >> Phase 1 - check blocks and sizes
    >>
    >>**** FILE SYSTEM STILL DIRTY ****
    >
    >
    > Can't be only this. It should have outputted something else between
    > Phase 1 and FILE SYSTEM STILL DIRTY.
    >
    >
    >>Will fsck continue attempting to fix the filesystem? Have I suffered a
    >>total loss or is fsck still doing its thing?
    >
    >
    > Read man fsck and its see also section.
    >
    >
    > 

    -- 
Rishi Chopra
http://www.ocf.berkeley.edu/~rchopra
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Gary: "RE: QMail? - additional thoughts"

    Relevant Pages

    • RE: Problem with fsck : continued
      ... Problem is not with FreeBSD or fsck, it's your electrical power ... There is FreeBSD port system software that works with different UPS ... My server faces unscheduled power cuts and consequent improper ...
      (freebsd-questions)
    • SOLVED! : Please help - URGENT - disk/fsck problems!
      ... > server down before the outage occurred), ... > disk problems and suggested I run fsck. ... No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another ... presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, ...
      (freebsd-questions)
    • Re: Please help - URGENT - disk/fsck problems!--SOLVED!
      ... > server down before the outage occurred), ... > disk problems and suggested I run fsck. ... No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another ... presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, ...
      (freebsd-questions)
    • Re: error ouput of fsck
      ... Also the other server had this sudden diffrent output ... RECONNECT? ... UNREF FILE I=659457 OWNER=admin MODE=140755 ... I tried to do fsck.. ...
      (freebsd-questions)
    • Re: Freebsd filesystem ( hard reboot )
      ... It is important to differentiate between expected fsck activity and ... If you machine shutdown softly as a result of the UPS communicating that power ... you "should" not have to fsck (barring other issues in the ... you are relying on luck for recovery if you're on ufs/reiserfs/xfs/etc. ...
      (freebsd-questions)