Thanks. I haven't been using that machine for some time (I bought a 
laptop), so as far as I am concerned this bug is not a problem at the 
moment. If I go back to using the other machine, I'll try installing the 
latest ubuntu on it and then see if it's still a problem.

cheers,

andy baxter

Theodore Ts'o wrote:
> Hi Andy,
>
> I have a sneaking suspicion that what's confusing you is that there is
> some other filesystem which is NOT your root filesystem that has a label
> of "/".   E2fsck will use the label assuming it is more "human friendly"
> than the raw device name.   However, if some other device (say,
> /dev/hda1) has a label of "/", but which is NOT your real root
> filesystem, this would result in very confusing behavior.   When you ran
> e2fsck /dev/hda5 from a rescue CD, it printed the following:
>
> [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
>
> If /dev/hda5 had a label of '/', it would have printed:
>
> /: 125124/1224000 files (0.7% non-contiguous), 732289/2443880 blocks
>
> But, it didn't.    However, the filesystem that reported the warning
> with the bad root directory caused e2fsck to report:
>
> /: Root inode is not a directory.
>
> So what I would suggest is that you use the command "e2label /dev/hdXX"
> where /dev/hdXX gets replaced with each of the ext2/3 filesystems
> mentioned in your /etc/fstab.  I suspect that some other filesystem
> other than your root filesystem, /dev/hda5, has a label of '/', and this
> is confusing you.
>
> Regards,
>
>

-- 
filesystem check fails on boot, but filesystem isn't bad
https://bugs.launchpad.net/bugs/48563
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to