Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) EXT3-fs: hda8: couldn't mount because of unsupported optional features (2000200). EXT3-fs: hda8: couldn't mount because of unsupported optional features (2000200) Previously this partition can be mounted without problem. I also tried adding -t ext3 without result still having the same warning. # e2fsck -f /dev/hda8 e2fsck 1.38 (30-Jun-2005) e2fsck: Filesystem revision too high while trying to open dev/hda8 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 -f 8193 /dev/hda8 Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_journal] [-E extended-options] device Emergency help: -p Automatic repair (no questions) -n Make no changes to the filesystem -y Assume "yes" to all questions -c Check for bad blocks and add them to the badblock list -f Force checking even if filesystem is marked clean -v Be verbose -b superblock Use alternative superblock -B blocksize Force blocksize when looking for superblock -j external_journal Set location of the external journal -l bad_blocks_file Add to badblocks list -L bad_blocks_file Set badblocks list Please advise how to fix the problem. TIA B.R. SL
On Jan 17, 2006 14:31 +0800, Stephen Liu wrote:> # dmesg | tail > via82cxxx: timeout while reading AC97 codec (0x9A0000) > via82cxxx: timeout while reading AC97 codec (0x9A0000) > via82cxxx: timeout while reading AC97 codec (0x9A0000) > EXT3-fs: hda8: couldn't mount because of unsupported optional features > (2000200). > EXT3-fs: hda8: couldn't mount because of unsupported optional features > (2000200)It certainly looks like your disk is corrupted with "0x0200" data. I'm not sure where that would come from. Please attach output from: dd if=/dev/hda8 bs=4k count=1 | gzip -9 > /tmp/hda8-sb.gz> # e2fsck -f /dev/hda8 > e2fsck 1.38 (30-Jun-2005) > e2fsck: Filesystem revision too high while trying to open dev/hda8 > 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>I believe modern e2fsck's already try the backup superblocks automatically, but I coul dbe wrong. In any case, the number after "-b" usually depends on the size of the filesystem. For smaller filesystems (< 512MB) it is 8193 or 24576 or 8192 * {3,5,7}^n + 1. For larger filesystems it is 32768 or 98304 or 32768 * {3,5,7}^n by default. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc.