Re: fsck'd

On Fri, Mar 07, 2008 at 08:38:07PM -0500, John Fleming wrote:
On 3/7/08, Douglas A. Tutty <dtutty@xxxxxxxxxxxxx> wrote:
On Fri, Mar 07, 2008 at 08:29:08AM -0500, John Fleming wrote:
Backgroud - I had a well-established LAMP server that was giving some
filesystem errors on boot, with the "hit control-D to continue or give root
password to fix manually" message. It would go ahead and work normally if I
hit Control-D.

Doug, thanks for the good ideas - I learned some things from your
considered response. I ended up finally reinstalling etch again.
I've now captured the pertinent part of the boot messages and will
copy below. Why does the filesystem check clean once and then come up
with errors the 2nd time? You mentioned that I should fix it manually
- Well, if I enter the root password at the prompt and try to run fsck
manually, it warns me about the damage I might due to the MOUNTED
filesystem. I mentioned in my earlier post that if I boot into
Knoppix and run fsck, it comes back CLEAN. So I can't seem to repair
it with Knoppix fsck, yet I get the error when I boot from my
/dev/hda1 - the second time in the fsck sequence. Can you shed any
light on this?

Here is the pertinent boot sequence:

Checking root filesystem...fsck 1.40-WIP (14-Nov-2006)
/dev/hda1: clean, 126072/19218432 files, 1420493/38409399 blocks
done.

Setting up system clock..
Cleaning up ifupdown....
Loading kernel modules...loop: loaded (max 8 devices)
done.

Loading device-mapper supportdevice-mapper: ioctl: 4.7.0-ioctl
(2006-06-24) initialized: dm-devel@xxxxxxxxxx

Checking file systems...fsck 1.40-WIP (14-Nov-2006)
/ contains a file system with errors, check forced.
/:
Inodes that were part of a corrupted orphan linked list found.
/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
fsck died with exit status 4

What fsck command do you enter then in single-user? The filesystem
should only be mounted ro.

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: fsckd - FIXED
    ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
    (Debian-User)
  • Re: fsckd
    ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
    (Debian-User)
  • Re: Disk Druid - Fedora flame #1
    ... >Gene Heskett wrote: ... > be part of a minimal boot environment. ... >And the root filesystem should be as small as reasonably possible, ... as long as root is trusted. ...
    (Fedora)
  • Re: Disk Druid - Fedora flame #1
    ... What I do as root, ... Root's home directory should contain very little: ... part of a minimal boot environment. ... And the root filesystem should be as small as reasonably possible, ...
    (Fedora)
  • Re: [SLE] Need HELP with fsck on root partition
    ... is I can't boot all ... > can't seem to fsck on the command line. ... exception is the root partition, and it should be mounted read-only. ... Reiserfs will not perform other than minor repairs on a mounted ...
    (SuSE)