Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've put it in an external usb enclosure and have tryed connecting it to both a windows server as well as my Fedora 8 laptop.
On the fedora laptop, when I plug in the drive I hear it click maybe 10 times and spin up. After that I hear no noise indicating head movement, but the drive is def. spinning and generating heat. Linux never sees it under fdisk. I've rebooted the laptop with the USB drive still plugged in but it has no effect.
When I look at /proc/partitions I see the drive as "/dev/sdb" however fdisk doesn't show it.
When I did through /sys/block/sdb I see information on the drive...
Anybody have any ideas of anything else to try to get my data off the drive? Anybody have any idea of what component on the drive failed?
Oh yeah, the windows box sees that new hardware was plugged in but never shows the drive under device manager.
type as root cfdisk and also -l fdisk type dmsg and see where sdb or sdb1 is. cfdisk /dev/sdb
as root type mount make a folder /mnt/sdb1 and and if it is a linux format mount -t /dev/sdb1 /mnt/sdb1 ext3 noauto,rw,users 0 0 if it is a linux format then it will be sdb1 windows
Quote:
# Usb device (assuming vfat)
mount -t /dev/sdb1 /mnt/sdb1 auto users,uid=1000,gid=100,utf8,dmask=027,fmask=137 0 0
the -t is a command that is short for touch it means if the /device/sdb1 exists then mount it in folder /mnt/sdb1.
FYI, actually the -t option is to specify the file system type i.e. vfat, ext2 etc.
If omitted the mount command will attempt to determine the file system automatically.
Have you verified the jumpers on the drive? Is this an IDE or SATA drive? Some enclosures require an IDE drive to be configured as master. There could be several problems with the drive and no way of knowing exactly. You can find different troubleshooting ideas by just googling. If it is a heat problem sticking it in the freezer for a short time might be enough to let you copy the data. If a component on the circuit board has failed you might be out of luck. Depending on how valuable the data is you can pay (not cheap) a hard drive recovery company.
if that is what you think that's cool I use -t for touch now for many years. I guess in that script it is -t for you. touch for me sugar in your -t. just a touch.
cfdisk doesn't show anything other then my main drive (sda).
Here is the output in /var/log/messages after plugging in the usb drive:
Quote:
Mar 10 00:04:57 z32 kernel: usb 1-1: new high speed USB device using ehci_hcd and address 6
Mar 10 00:04:57 z32 kernel: usb 1-1: configuration #1 chosen from 1 choice
Mar 10 00:04:57 z32 kernel: usb 1-1: New USB device found, idVendor=152d, idProduct=2339
Mar 10 00:04:57 z32 kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Mar 10 00:04:57 z32 kernel: usb 1-1: Product: USB to ATA/ATAPI Bridge
Mar 10 00:04:57 z32 kernel: usb 1-1: Manufacturer: JMicron
Mar 10 00:04:57 z32 kernel: usb 1-1: SerialNumber: 6415FFFFFFFF
Mar 10 00:04:58 z32 kernel: Initializing USB Mass Storage driver...
Mar 10 00:04:58 z32 kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Mar 10 00:04:58 z32 kernel: usbcore: registered new interface driver usb-storage
Mar 10 00:04:58 z32 kernel: USB Mass Storage support registered.
Mar 10 00:05:03 z32 kernel: scsi 6:0:0:0: Direct-Access TOSHIBA MK8034GSX PQ: 0 ANSI: 2 CCS
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] 156301488 512-byte hardware sectors (80026 MB)
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] Write Protect is off
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] 156301488 512-byte hardware sectors (80026 MB)
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] Write Protect is off
Mar 10 00:05:03 z32 kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 10 00:05:35 z32 kernel: sdb:<6>usb 1-1: reset high speed USB device using ehci_hcd and address 6
Mar 10 00:05:43 z32 kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 6
Mar 10 00:06:55 z32 kernel:last message repeated 7 times
Mar 10 00:07:56 z32 kernel:last message repeated 3 times
This is a SATA drive so there are no jumper settings that would matter here. This was the only drive in a laptop when it failed, so i took it out and put it in a usb sata enclosure to ease my troubleshooting.
And there is no "sdb" under /dev, or any device with that major/minor number.
I can even get more info from it out of sys....
Quote:
[root@z32 device]# pwd
/sys/block/sdb/device
[root@z32 device]# more state
running
[root@z32 device]# more vendor
TOSHIBA
[root@z32 device]# more type
0
[root@z32 device]# more scsi_level
3
[root@z32 device]# more model
MK8034GSX
[root@z32 device]# more ioerr_cnt
0x778a
I tried manually creating /dev/sdb with the major and minor number from above...
That didn't work either, fdisk would just hang when I ran a fdisk -l. cfdisk wouldn't show it. and if I tried to do a dd out of it then it would just hang too.
I know the drive is bad, I was hoping I would still be able to get stuff off of it. Does anybody know based off of what the symptoms have been for me what kind of failure this might be on the drive?
Put it back in your laptop and try spinrite. Finding /dev/sdb doesn't really help you since no partitions are found. It just means the drive is recognized (and it might just be recognizing the USB interface) but the drive can't be read.
Spinrite will save it if anything can; if spinrite doesn't save it I don't know of anything that will.
I would try either testdisk or foremost and recover whatever data you can get from it, but it may be already dead, in which case ... hope you backed up.
Actually, testdisk might indeed be worth a try. If it can read the drive at all, it might be able to identify partitions. if it can't read the drive, then spinrite is the only remaining choice.
It depends on why the drive isn't seen. Spinrite operates within the framework of a very rudimentary operating system, and operates directly on the hardware. This gives capability that doesn't exist within a more sophisticated OS; such capability is explicitly denied.
The author of spinrite formerly worked in the HD industry, as a designer. He knows how they work in great detail, and spinrite takes advantage of that knowledge. if the drive isn't seen because the interface is bad, spinrite can't do anything. Similarly if the platter won't turn or the heads won't move. But if those things do work, then there is an excellent chance that spinrite will be able to recover the drive, at least temporarily.
Depending on the fault, a failing HDD can sometimes be temporarily rejuvenated by putting it in a plastic bag and putting it in the freezer. This increases the critical dimensions between the moving parts, since the coefficient of expansion of the materials is proportional to temperature. They shrink. Google for the details.
Thereafter reinstall the HDD and immediately use dd or something like Clonezilla to make a copy to another HDD.
Good Luck
Last edited by thorkelljarl; 03-11-2009 at 06:39 PM.
I tried the freezer trick but it didn't make a difference. The hard drive showed the same behavior. Actually it seemed to stop spinning after first booting it up. Interesting.
Has anyone bought a similar drive off of ebay and replaced the external circuit board with any success?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.