EXT3-Error when mounting

haukew · 2009-02-09 13:15:41

Hi!
I get this strange error when connecting my external drive:

org.freedesktop.Hal.Device.Volume.UnknownFailure: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error 
In some cases useful info is found in syslog - try        
dmesg | tail  or so

dmesg | tail says this:

EXT4-fs warning (device sdb1): ext4_fill_super: extents feature not enabled on this filesystem, use tune2fs.
EXT4-fs: sdb1: couldn't mount because of unsupported optional features (4000400).
EXT4-fs warning (device sdb1): ext4_fill_super: extents feature not enabled on this filesystem, use tune2fs.
EXT4-fs: sdb1: couldn't mount because of unsupported optional features (4000400).

I didn't touch the external drive for some weeks now (it worked perfectly last time). It is ext3 by the way, not ext4.
So - before i use tune2fs or something like it i thought: Better ask before i lose data or worse...

Thanks in advance, Hauke

pointone · 2009-02-09 15:26:31

What happens if you explicitly try to mount it as ext3? It seems like HAL is convinced it's an ext4 filesystem. Try:

mkdir /mnt/sdb1
mount -t ext3 /dev/sdb1 /mnt/sdb1

Please also post the output of:

tune2fs -l /dev/sdb1

For information about the filesystem.

haukew · 2009-02-09 16:19:24

Hi!
When mounting explicitly as ext3 pretty much the same happens:

bash-3.2# mkdir usb
bash-3.2# mount -t ext3 /dev/sdb1 usb
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       Manchmal liefert das Syslog wertvolle Informationen – versuchen
       Sie  dmesg | tail  oder so

bash-3.2# dmesg | tail
sd 5:0:0:0: [sdb] Assuming drive cache: write through
sd 5:0:0:0: [sdb] 781422768 512-byte hardware sectors: (400 GB/372 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 5:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
EXT3-fs: sdb1: couldn't mount because of unsupported optional features (4000400).
bash-3.2#

and:

bash-3.2# tune2fs -l /dev/sdb1
tune2fs 1.41.3 (12-Oct-2008)
tune2fs: Filesystem revision too high beim Versuch, /dev/sdb1 zu öffnen
Kann keinen gültigen Dateisystem-Superblock finden.
bash-3.2#

That's translated roughly to
"tune2fs: Filesystem revision too high while trying to open /dev/sdb1"
"Can't find valid filesystem-superblock"

Last edited by haukew (2009-02-10 00:30:52)

haukew · 2009-02-19 12:01:54

i didn't find a solution yet :-/
any ideas anybody?

ataraxia · 2009-02-19 16:30:51

I wonder if your filesystem's superblock is corrupted. e2fsck can try to fix it, if you can find another superblock that's still good. See the "-b" option to e2fsck for how to find one, and how to use it.

This seems risky, but if your data is otherwise gone, you may as well try it.

haukew · 2009-02-21 21:00:51

Hm...is there any possibility to be certain? This disk contains data important to me and i'd very much not like to lose everything i saved on it...

wonder · 2009-02-21 21:18:37

i'm sure that you didn't merged /etc/mke2fs.conf. do that and reformat that partition

EDIT: ignore that. i was thinking that is a ext4 partition when i saw logs from dmesg

Last edited by wonder (2009-02-21 21:20:42)

haukew · 2009-03-02 14:06:33

*bump*

toad · 2009-03-02 14:15:19

Plug it into a different system/live system? Same message?

zatricky · 2009-03-08 12:29:30

wonder wrote:

i'm sure that you didn't merged /etc/mke2fs.conf

If it hasn't been done already, its probably a good idea to merge /etc/mke2fs.conf and /etc/mke2fs.conf.pacnew anyway.

haukew · 2009-03-11 16:20:44

Hi!
Thanks for the answers, i still couldn't solve the problem...

First: I don't have a mke2fs.conf.pacnew, only the original which reads as follows:

[defaults]
    base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
    blocksize = 4096
    inode_size = 256
    inode_ratio = 16384

[fs_types]
    ext3 = {
        features = has_journal
    }
    ext4 = {
        features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
        inode_size = 256
    }
    ext4dev = {
        features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
        inode_size = 256
        options = test_fs=1
    }
    small = {
        blocksize = 1024
        inode_size = 128
        inode_ratio = 4096
    }
    floppy = {
        blocksize = 1024
        inode_size = 128
        inode_ratio = 8192
    }
    news = {
        inode_ratio = 4096
    }
    largefile = {
        inode_ratio = 1048576
        blocksize = -1
    }
    largefile4 = {
        inode_ratio = 4194304
        blocksize = -1
    }
    hurd = {
         blocksize = 4096
         inode_size = 128
    }

Then after considering the risks i tried this:

e2fsck -b 8193 /dev/sdb1

This comes out, and it has no effect:

bash-3.2# e2fsck -b 8193 /dev/sdb1
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Bad magic number in super-block beim Versuch, /dev/sdb1 zu öffnen

SuperBlock ist unlesbar bzw. beschreibt kein gültiges ext2
Dateisystem.  Wenn Gerät gültig ist und ein ext2
Dateisystem (kein swap oder ufs usw.) enthält,  dann ist der SuperBlock
beschädigt, und sie könnten e2fsck mit einem anderen SuperBlock:
    e2fsck -b 8193 <Gerät>

Which translates to "Bad magic number in super-block while trying to open /dev/sdb1
Superblock is not readable or describes no valid ext2 filesystem. If device is valid and contains a ext2 (which it does) then the superblock is damaged and could be replaced by another SuperBlock:
e2fsck -b 8193 <device>
(which didn't work...)

And yes, other mediums (fat32, ext3) do work

haukew · 2009-03-27 14:59:50

Woohoo, i managed to fix it:
I used the command

mke2fs -S /dev/sdb1

And done :-)

Thank you all for your replies!

Found this solution here: http://www.webhostingtalk.com/showthread.php?p=5273409

Last edited by haukew (2009-03-27 15:03:31)

Arch Linux

#1 2009-02-09 13:15:41

EXT3-Error when mounting

#2 2009-02-09 15:26:31

Re: EXT3-Error when mounting

#3 2009-02-09 16:19:24

Re: EXT3-Error when mounting

#4 2009-02-19 12:01:54

Re: EXT3-Error when mounting

#5 2009-02-19 16:30:51

Re: EXT3-Error when mounting

#6 2009-02-21 21:00:51

Re: EXT3-Error when mounting

#7 2009-02-21 21:18:37

Re: EXT3-Error when mounting

#8 2009-03-02 14:06:33

Re: EXT3-Error when mounting

#9 2009-03-02 14:15:19

Re: EXT3-Error when mounting

#10 2009-03-08 12:29:30

Re: EXT3-Error when mounting

#11 2009-03-11 16:20:44

Re: EXT3-Error when mounting

#12 2009-03-27 14:59:50

Re: EXT3-Error when mounting

Board footer