WD 5000AAJB
March 27th, 2012, 20:59
Problems with HDD It spinns up fine
when you connect it to linux it connects fine without error detects (USB adapter) just fine however when you go to mount the device here is what you get.
any help would be greatly appricated.
Thanks
Steven
when you connect it to linux it connects fine without error detects (USB adapter) just fine however when you go to mount the device here is what you get.
any help would be greatly appricated.
Thanks
Steven
- Code:
[2155270.870979] sd 9:0:0:0: [sde] No Caching mode page present
[2155270.870984] sd 9:0:0:0: [sde] Assuming drive cache: write through
[2155270.870988] sd 9:0:0:0: [sde] Attached SCSI disk
[2155304.873568] usb 1-6: USB disconnect, device number 9
[2155304.874149] scsi 9:0:0:0: [sde] killing request
[2155304.877558] scsi 9:0:0:0: [sde] Unhandled error code
[2155304.877563] scsi 9:0:0:0: [sde] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[2155304.877568] scsi 9:0:0:0: [sde] CDB: Read(10): 28 00 3a 38 4b bf 00 00 08 00
[2155304.877579] end_request: I/O error, dev sde, sector 976767935
[2155304.877585] Buffer I/O error on device sde1, logical block 488383936
[2155304.877590] Buffer I/O error on device sde1, logical block 488383937
[2155304.877593] Buffer I/O error on device sde1, logical block 488383938
[2155304.877597] Buffer I/O error on device sde1, logical block 488383939
[2155304.877619] Buffer I/O error on device sde1, logical block 488383936
[2155304.877624] Buffer I/O error on device sde1, logical block 488383937
[2155304.877628] Buffer I/O error on device sde1, logical block 488383938
[2155304.877632] Buffer I/O error on device sde1, logical block 488383939
[2155304.877664] Buffer I/O error on device sde1, logical block 488383992
[2155304.877668] Buffer I/O error on device sde1, logical block 488383993
Re: WD 5000AAJB
March 27th, 2012, 21:16
I think that's an IDE (PATA) disk, isn't it?
What did your customer tell you about the history of that disk - i.e. what happened between it working OK, and you receiving it to attempt recovery?
What were the symptoms that they reported (presumably when it was attached via PATA)?
Based on those messages, and assuming there is no power problem, it looks like the disk is doing something (we can't see exactly what, although I could make some guesses) which causes the USB adapter to unenumerate it - hence the USB disconnect message. This is not uncommon with USB adapters; they are not designed to cope with all the various behaviours of flaky disks. This is a good example of why you can't rely on using USB to attach those disks.
I suggest you either outsource the recovery to someone with appropriate PATA equipment, or get a system which allows for PATA connection, if you want to diagnose further and are accepting the risks of those diagnosis attempts.
P.S. I expect that the USB adapter will behave the same way, at some point during the process, if you try to clone the flaky disk (unmounted) while it is attached through that adapter, which is why I'm not suggesting to do that yet. Of course that is something you could try (again, if you accept the risks).
What did your customer tell you about the history of that disk - i.e. what happened between it working OK, and you receiving it to attempt recovery?
What were the symptoms that they reported (presumably when it was attached via PATA)?
Based on those messages, and assuming there is no power problem, it looks like the disk is doing something (we can't see exactly what, although I could make some guesses) which causes the USB adapter to unenumerate it - hence the USB disconnect message. This is not uncommon with USB adapters; they are not designed to cope with all the various behaviours of flaky disks. This is a good example of why you can't rely on using USB to attach those disks.
I suggest you either outsource the recovery to someone with appropriate PATA equipment, or get a system which allows for PATA connection, if you want to diagnose further and are accepting the risks of those diagnosis attempts.
P.S. I expect that the USB adapter will behave the same way, at some point during the process, if you try to clone the flaky disk (unmounted) while it is attached through that adapter, which is why I'm not suggesting to do that yet. Of course that is something you could try (again, if you accept the risks).
Re: WD 5000AAJB
March 27th, 2012, 21:48
Ya this is my personal drive.
so i dont mind any risk
I will try connecting it directly and see what happens.
The history on this drive is below
It served its entire life in a removable bay enclosure for about 2 years when one day it just would not be recgonized in windows. There is not mission critical data on it just music and some homemade videos so i dont mind if i lost it but it would be nice to get it back.
So i am trying to get the data off of the drive
Thanks
Steven
so i dont mind any risk
I will try connecting it directly and see what happens.
The history on this drive is below
It served its entire life in a removable bay enclosure for about 2 years when one day it just would not be recgonized in windows. There is not mission critical data on it just music and some homemade videos so i dont mind if i lost it but it would be nice to get it back.
So i am trying to get the data off of the drive
Thanks
Steven
Re: WD 5000AAJB
March 27th, 2012, 22:05
Thanks for the info.
Oh, OK - you've mentioned several other disks in previous postings, so I was guessing you did recovery for other people
After doing that, personally I still wouldn't try mounting the filesystem(s) on that disk (as there must be a problem with the drive, for the USB adapter to behave that way). Instead, with a PATA attachment, you've a better chance of successfully cloning it, in my experience.
It would also be useful to see if the drive is correctly reported (inc its capacity) by the BIOS, in the disk setup screen.
OK, thanks. No specific clues there, but it's always worth asking.
niceguy167 wrote:Ya this is my personal drive.
so i dont mind any risk
Oh, OK - you've mentioned several other disks in previous postings, so I was guessing you did recovery for other people
niceguy167 wrote:I will try connecting it directly and see what happens.
After doing that, personally I still wouldn't try mounting the filesystem(s) on that disk (as there must be a problem with the drive, for the USB adapter to behave that way). Instead, with a PATA attachment, you've a better chance of successfully cloning it, in my experience.
It would also be useful to see if the drive is correctly reported (inc its capacity) by the BIOS, in the disk setup screen.
niceguy167 wrote:one day it just would not be recgonized in windows
OK, thanks. No specific clues there, but it's always worth asking.
Powered by phpBB © phpBB Group.