LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 04-28-2005, 12:52 AM   #1
shubb
Member
 
Registered: Oct 2003
Location: San Francisco
Distribution: Slackware 13.37
Posts: 150

Rep: Reputation: 16
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?
 
Old 04-28-2005, 02:03 AM   #2
zhangmaike
Member
 
Registered: Oct 2004
Distribution: Slackware
Posts: 376

Rep: Reputation: 31
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).
 
Old 04-28-2005, 10:48 PM   #3
shubb
Member
 
Registered: Oct 2003
Location: San Francisco
Distribution: Slackware 13.37
Posts: 150

Original Poster
Rep: Reputation: 16
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.
 
Old 04-28-2005, 10:54 PM   #4
zhangmaike
Member
 
Registered: Oct 2004
Distribution: Slackware
Posts: 376

Rep: Reputation: 31
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.
 
Old 04-29-2005, 12:00 AM   #5
shubb
Member
 
Registered: Oct 2003
Location: San Francisco
Distribution: Slackware 13.37
Posts: 150

Original Poster
Rep: Reputation: 16
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ERROR AT MOUNTING USB :mount: wrong fs type, bad option, bad superblock on /dev/sda1, saiket Linux - Hardware 3 04-12-2008 12:07 AM
Bad superblock when mounting hard drive... SamJ Linux - Hardware 5 06-04-2005 07:32 PM
mount: wrong fs type, bad option, bad superblock on /dev/cdrom, Adil_uk Linux - Hardware 9 02-16-2005 05:50 PM
mount: wrong fs type, bad option, bad superblock on /dev/sdb1 pmoreira Linux - Hardware 5 02-26-2004 10:31 AM
USB 2.0 memory stick mount: wrong fs type, bad option, bad superblock on /dev/sda1, o olivier.riff Linux - Hardware 2 11-12-2003 08:11 AM


All times are GMT -5. The time now is 10:00 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration