Comment 1 for bug 543400

Revision history for this message
ionash. (janusz-arch) wrote :

When I try to mount my disk (ST3500418AS, with karmic installed and working) on lucid (installed on another disk, with the same motherboard Asus A8VX), system displays this message:
"Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdc5, missing codepage or helper program, or other error. In some cases useful info is found in syslog - try dmesg | tail or so"
dmesg | tail:
[ 68.828063] ata3: hard resetting link
[ 73.860025] ata3: softreset failed (device not ready)
[ 73.860034] ata3: reset failed, giving up
[ 73.860040] ata3.00: disabled
[ 73.860048] ata3: EH complete
[ 73.860559] sd 2:0:0:0: [sdb] Unhandled error code
[ 73.860564] sd 2:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 73.860572] sd 2:0:0:0: [sdb] CDB: Read(10): 28 00 02 71 94 39 00 00 02 00
[ 73.860589] end_request: I/O error, dev sdb, sector 40997945
[ 73.861517] EXT4-fs (sdb5): unable to read superblock

This problem occurred only with this specific combination of hardware. I try to run lucid LiveCD with this Seagate hard drive and another motherboards (two different MSI motherboards, newer than A8vx), and everything goes without errors; on my Asus - like above.
In karmic this hardware (Seagate disk and Asus motherboard) just works (with pci=nomsi grub command), so I think this is kernel bug.