Re: couldn't mount because of unsupported optional features (4000400)

On 04/20/2007 08:50 PM, Anthony J Placilla wrote:
--
Sjoerd Mullender
Sjoerd Mullender wrote:
On 04/20/2007 07:33 PM, Anthony J Placilla wrote:
Sjoerd Mullender wrote:
Does anybody know what this means:
EXT3-fs: hdc1: couldn't mount because of unsupported optional features
(4000400).

I googled but only found questions.

I can read the disk (both fdisk and dd are happy enough), but I don't
want to overwrite anything if I don't have to.

# uname -r
2.6.20-1.2944.fc6

Well the first question that comes to mind is what type of media is it?

Detailed info please

Oops. Harddisk. The system is a Dell Inspiron 8200 laptop with two
internal drives. The second drive (hdc) is the original one and so used
to work fine. There is a single partition with a file system that until
recently (I don't know when I actually tried last) worked well.


have you run fsck at the disk?

what does fdisk -l /dev/hdc say?

what does e2label /dev/hdc1 say?

and how is it being mounted? from fstab? What are the relevant lines?

# fsck /dev/hdc1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
fsck.ext3: Filesystem revision too high while trying to open /dev/hdc1
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

# e2fsck -b 8193 /dev/hdc1
e2fsck 1.39 (29-May-2006)
fsck.ext3: Bad magic number in super-block while trying to open /dev/hdc1

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

# fdisk -l /dev/hdc

Disk /dev/hdc: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 4864 39070048+ 83 Linux
# e2label /dev/hdc1
e2label: Filesystem revision too high while trying to open /dev/hdc1
Couldn't find valid filesystem superblock.
# grep hdc1 /etc/fstab
# grep hdc /etc/auto.misc
virtual -fstype=ext3 :/dev/hdc1
#

It's normally mounted through the automounter. This has worked.

--
Sjoerd Mullender

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Weird harddisk behaviour
    ... A couple of weeks ago my 400Gb SATA disk crashed. ... Partition Table for /dev/sda ... # Type Sector Sector Offset Length Filesystem Type Flag ... Superblock backups stored on blocks: ...
    (Linux-Kernel)
  • Re: raid-one
    ... The potential failure mode is that you get the wrong device name for the fdisk or mke2fs steps. ... There's not much sense in trying to describe Linux device names for anything but hd? ... copy the files from the old filesystem to the new. ... Once it all works with the new disk, fdisk the old one to match if it didn't already and mdamd --add the mirror partitions. ...
    (Fedora)
  • Partitioning attempt on a Maxtor 120G: wanted both fat32 and ext3
    ... I attempted to partition my new 120G Maxtor USB external hard disk ... to be able to back up the linux side, including ownership, etc. ... Minor Start End Type Filesystem Flags ... Superblock backups stored on blocks: ...
    (comp.os.linux)
  • Re: problem mounting filesystem
    ... After using fdisk in a disk is recommended to reboot the server so ... Maximum filesystem blocks=8388608 ... 255 heads, 63 sectors/track, 1662 cylinders ...
    (RedHat)
  • Re: where is data on disk when using a live CD
    ... time time and did a reboot from my live CD. ... user I couldn't find my data that is on the disk. ... Then maybe you need to know what the filesystem is, ... Replace FILESYSTEM with the filesystem as in the fdisk output (reiserfs, ...
    (Ubuntu)