| Walt Mankowski on 19 Dec 2009 18:18:15 -0800 |
|
A few weeks ago the hard drive died on my trusty old 2004-vintage Powerbook G4 laptop. Fortunately I had most of the data backed up, but there are still few things I'd really like to get off of it. After a number of attempts to recover the data, I decided I had nothing else to lose, so I disassembled the powerbook, removed the drive, put it into a 2.5" USB drive enclosure, and tried to mount it in Linux. No luck. I also tried freezing the drive overnight, but Linux still wouldn't recognize it. Here's what dmesg reports when I plug in the drive: [776169.444040] usb 1-5: new high speed USB device using ehci_hcd and address 15 [776169.577562] usb 1-5: New USB device found, idVendor=05e3, idProduct=0702 [776169.577567] usb 1-5: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [776169.577571] usb 1-5: Product: USB Storage [776169.577685] usb 1-5: configuration #1 chosen from 1 choice [776169.578070] scsi15 : SCSI emulation for USB Mass Storage devices [776169.578341] usb-storage: device found at 15 [776169.578344] usb-storage: waiting for device to settle before scanning [776174.576278] usb-storage: device scan complete [776174.576869] scsi 15:0:0:0: Direct-Access FUJITSU MHT2040AT 0014 PQ: 0 ANSI: 0 [776174.969985] sd 15:0:0:0: [sdb] 78140160 512-byte hardware sectors: (40.0 GB/37.2 GiB) [776174.970979] sd 15:0:0:0: [sdb] Write Protect is off [776174.970985] sd 15:0:0:0: [sdb] Mode Sense: 03 00 00 00 [776174.970988] sd 15:0:0:0: [sdb] Assuming drive cache: write through [776174.972983] sd 15:0:0:0: [sdb] Assuming drive cache: write through [776174.972992] sdb:<6>usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776236.112057] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776267.112030] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776298.112042] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776329.116031] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776360.116059] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776360.256461] sd 15:0:0:0: [sdb] Unhandled error code [776360.256468] sd 15:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK [776360.256475] end_request: I/O error, dev sdb, sector 0 [776360.256484] Buffer I/O error on device sdb, logical block 0 [776391.100034] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776422.116029] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776453.112038] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776484.116048] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776515.116041] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776546.112074] usb 1-5: reset high speed USB device using ehci_hcd and address 15 [776546.248445] sd 15:0:0:0: [sdb] Unhandled error code [776546.248449] sd 15:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK [776546.248455] end_request: I/O error, dev sdb, sector 0 [776546.248461] Buffer I/O error on device sdb, logical block 0 [776577.100063] usb 1-5: reset high speed USB device using ehci_hcd and address 15 What's really frustrating is that it seems so close to recognizing the drive, and if it would just create /dev/sdb then I could try to use something like ddrescue to get the data off the drive. But without a device name there's nothing I can do. I should also add that my load goes up to 100% when I plug in the drive. Top doesn't show anything running, so I assume the kernel's looping trying to access the drive. One other odd thing about this drive -- most IDE drives have 44 pins. However, this drive has 50 pins. Here's a picture of what it looks like: http://www.myrightdrive.com/images/IDE-connector.jpg My enclosure only has the normal 44 pins, so when I plug it in those extra 4 pins on the side are open. I believe they're used to set master/slave. Someone has told me that he thinks it should default to master when they're not jumpered, but I haven't been able to confirm this. There are no jumper settings printed on the drive case, and the connector Apple used covered all 50 pins. Of course the drive's probably dead (it's making the dreaded clicking sound) but these extra pins have given me a glimmer of hope that maybe it's the drive's configuration and not the drive itself that's confusing Linux. If anyone has any advise or experience on accessing data from these drives, I'd appreciate it. Thanks. Walt Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|
