On Tue, 2006-09-26 at 15:08 +0000, Daniel Werner wrote:
> Could you please include the error messages you mentioned, even the
> "minor" ones?
>
I've tried again checking /dev/hda5 from the live CD, and it passes
clean. here is the log:
[EMAIL PROTECTED]:~# e2fsck /dev/hda5 -d -f
e2fsck 1.38 (30-Jun-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda5: 125124/1224000 files (0.7% non-contiguous), 732289/2443880
blocks
This is the partition table (again done from the live CD):
[EMAIL PROTECTED]:/# fdisk /dev/hda
The number of cylinders for this disk is set to 9729.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1825 14659281 7 HPFS/NTFS
/dev/hda2 1826 3770 15623212+ 5 Extended
/dev/hda3 3771 8869 40957717+ 83 Linux
/dev/hda4 8870 9729 6907950 83 Linux
/dev/hda5 1826 3042 9775521 83 Linux
/dev/hda6 3043 3165 987966 82 Linux swap /
Solaris
/dev/hda7 3166 3770 4859631 83 Linux
Command (m for help): q
When I boot up, the same thing is still happening - i.e. it passes the
root filesystem check, then when it gets to 'checking all filesystems',
it drops into a root shell with the following error message (maybe not
quite exact as I had to type it in by hand):
/local: clean, 157063/5118176 files, 6784838/10239429 blocks
/ contains a filesystem with errors, check forced.
/: Root inode is not a directory.
/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
/ :clean, 204348/864960 files, 1565691/1726987 blocks
/dev/hda7: clean ....
The weird thing is that / (/dev/hda5) shouldn't be being checked at all
at this point, I think, as it has already been checked in the 'checking
root filesystem' bit, and by now it's mounted read/write.
My fstab looks like this:
[EMAIL PROTECTED]:/home/andy/Desktop# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda5 / ext3 defaults,errors=remount-ro 0
1
/dev/hda3 /local ext3 defaults 0 2
/dev/hda1 /media/hda1 ext3 defaults 0 2
/dev/hda4 /media/hda4 ext3 defaults 0 2
/dev/hda7 /var ext3 defaults 0 2
/dev/hda6 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
I'm switching to another computer (a laptop) for most of my work (mainly
just because the laptop is quieter), so this bug isn't urgent for me at
the moment, but it is still a problem and I'm quite happy to send any
more information you need to work out what's going on.
andy baxter.
--
filesystem check fails on boot, but filesystem isn't bad
https://launchpad.net/bugs/48563
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
