LinuxQuestions.org - bad superblock when trying to mount a USB hard drive

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - bad superblock when trying to mount a USB hard drive (https://www.linuxquestions.org/questions/linux-hardware-18/bad-superblock-when-trying-to-mount-a-usb-hard-drive-317953/)

bad superblock when trying to mount a USB hard drive

I have Slackware 10.1 on a Dell Latitude laptop. I have a 2.5 inch 30GB USB hard drive plugged into the USB port, and I am unable to mount the drive.

Code:

root@dell:/mnt# mount -t ntfs /dev/sda /mnt/usb/

mount: wrong fs type, bad option, bad superblock on /dev/sda,

      missing codepage or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so

If I try to mount any partition of sda, it says that it is not a valid block device.

When I look at dmesg I see:

Code:

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 3

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 4

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 5

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 6

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 7

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 70000

 I/O error: dev 08:00, sector 0

NTFS: Reading super block failed

The drive went bad, so I got a replacement. I can read the drive using Windows 2000. Any ideas why I cant see it in Linux?

How is your drive partitioned? And what does dmesg say immediately after you plug in the drive?

Also, does anyone know if something has to be enabled in the kernel to support USB hard drives? (Since it looks like you can read from the raw device but not from the non-existent partition devices).

It is partioned with one big partition, and a smaller hidden one (with the dell diags and stuff).

When I plug it in, dmesg says:

Code:

hub.c: already running port 1 disabled by hub (EMI?), re-enabling...

usb.c: USB disconnect on device 00:1d.0-1 address 2

hub.c: new USB device 00:1d.0-1, assigned address 3

input0: Logitech Trackball on usb2:3.0

hub.c: new USB device 00:1d.7-3, assigned address 2

usb.c: USB device 2 (vend/prod 0x402/0x5642) is not claimed by any active driver.

Initializing USB Mass Storage driver...

usb.c: registered new driver usb-storage

scsi1 : SCSI emulation for USB Mass Storage devices

  Vendor: USB 2.0  Model: Storage Device    Rev: 0100

  Type:  Direct-Access                      ANSI SCSI revision: 02

Attached scsi disk sda at scsi1, channel 0, id 0, lun 0

SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)

 sda: sda1 sda2

WARNING: USB Mass Storage data integrity not assured

USB Mass Storage device found at 2

USB Mass Storage support registered.

hub.c: port 3 over-current change

uhci.c: bf40: host controller halted. very bad

The problem with the hard drive why I had to replace it was that there were parts of the drive that had some un-recoverable sectors. Maybe that's why it wont read it? Doesnt explain why Windows still can.

From your dmesg output...

It found both partitions and created the sda1 and sda2 devices fine...

...then the usb host driver shut itself down because of "over-current change".

I'm not a usb expert, so I can only guess... but it looks like your drive has serious hardware problems and the windows driver is simply ignoring it whereas the linux driver shuts down.

Yeah, it looks like that was it. When I plugged it into a different linux machine it read it ok.

Thanks for the help zhangmaike.