On Fri, Mar 07, 2008 at 08:38:07PM -0500, John Fleming wrote: > On 3/7/08, Douglas A. Tutty <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > 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 [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
