So I've been trying to troubleshoot this issue for a week - I don't want to believe that the drive is shot - but it likely is...I can't get ANY data off the drive - I am having no luck.

drive is now in a usb enclosure - GODADDY dedicated box with CENTOS 5

120gig drive - USB enclosure
Not able to mount
Drive shows up in dev as sdb with no partitions
TESTDISK sees no partitions and is not able to locate any partitions...
Photorec doesn't help either...

I can not read the drive..getting I/O errors but I am also getting a few USB errors and I am hoping this is a USB or Kernal issue!

There are(was) 3 partitions on this drive now they are all missing...I desperately need the data off the 3rd partition

---------------

RESULTS OF sfdisk -l /dev/sdb :
Disk /dev/sdb: 0 cylinders, 64 heads, 32 sectors/track
read: Input/output error
sfdisk: read error on /dev/sdb - cannot read sector 0
/dev/sdb: unrecognized partition table type
No partitions found

----

The drive is showing up as 512Bytes (it's a 120 gig drive)

My guess is that the drive has fried...I am praying I can get some data off this drive but I am having no luck at all - everything I try to do I get communication errors with the drive.

----------- error FROM messages:

udevd-event[5305]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/host6/target6:0:0/6:0:0:0/ioerr_cnt' failed

is this related to my issue or different?

------------
uname -a:
Linux ip-XXX.ip.secureserver.net 2.6.18-194.3.1.el5.centos.plus #1 SMP Wed May 19 09:15:55 EDT 2010 i686 i686 i386 GNU/Linux

------------
At one time (a few days ago) I got this error in my messages:




08-176 kernel: usb 5-6: new high speed USB device using ehci_hcd and address 5
Jun 23 04:41:27 ip-208-109-108-176 kernel: usb 5-6: configuration #1 chosen from 1 choice
Jun 23 04:41:27 ip-208-109-108-176 kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Jun 23 04:41:36 ip-208-109-108-176 kernel: Vendor: WDC WD12 Model: 00JS-00NCB1 Rev:
Jun 23 04:41:36 ip-208-109-108-176 kernel: Type: Direct-Access ANSI SCSI revision: 02
Jun 23 04:41:36 ip-208-109-108-176 kernel: SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
Jun 23 04:41:36 ip-208-109-108-176 kernel: sdb: Write Protect is off
Jun 23 04:41:36 ip-208-109-108-176 kernel: sdb: assuming drive cache: write through
Jun 23 04:41:36 ip-208-109-108-176 kernel: SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
Jun 23 04:41:36 ip-208-109-108-176 kernel: sdb: Write Protect is off
Jun 23 04:41:36 ip-208-109-108-176 kernel: sdb: assuming drive cache: write through
Jun 23 04:41:40 ip-208-109-108-176 udevd-event[32595]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-6/5-6:1.0/host3/target3:0:0/3:0:0:0/ioerr_cnt' failed
Jun 23 04:41:41 ip-208-109-108-176 named[3289]: client 68.87.68.163#37415: query (cache) 'fibbersmusic.ca/MX/IN' denied
Jun 23 04:41:41 ip-208-109-108-176 named[3289]: client 68.87.68.163#54970: query (cache) 'mail.fibbersmusic.ca/A/IN' denied
Jun 23 04:41:48 ip-208-109-108-176 kernel: sdb:<3>ehci_hcd 0000:00:1d.7: port 6 reset error -110
Jun 23 04:41:48 ip-208-109-108-176 kernel: hub 5-0:1.0: hub_port_status failed (err = -32)
Jun 23 04:41:48 ip-208-109-108-176 kernel: hub 5-0:1.0: Cannot enable port 6. Maybe the USB cable is bad?
Jun 23 04:41:48 ip-208-109-108-176 kernel: usb 5-6: reset high speed USB device using ehci_hcd and address 5
Jun 23 04:41:50 ip-208-109-108-176 kernel: ehci_hcd 0000:00:1d.7: port 6 reset error -110
Jun 23 04:41:50 ip-208-109-108-176 kernel: hub 5-0:1.0: hub_port_status failed (err = -32)
Jun 23 04:41:51 ip-208-109-108-176 kernel: hub 5-0:1.0: Cannot enable port 6. Maybe the USB cable is bad?
Jun 23 04:41:51 ip-208-109-108-176 kernel: usb 5-6: reset high speed USB device using ehci_hcd and address 5
Jun 23 04:41:52 ip-208-109-108-176 kernel: sd 3:0:0:0: SCSI error: return code = 0x08000002
Jun 23 04:41:52 ip-208-109-108-176 kernel: sdb: Current: sense key: Medium Error
Jun 23 04:41:52 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error
Jun 23 04:41:52 ip-208-109-108-176 kernel:
Jun 23 04:41:52 ip-208-109-108-176 kernel: end_request: I/O error, dev sdb, sector 0
Jun 23 04:41:52 ip-208-109-108-176 kernel: Buffer I/O error on device sdb, logical block 0
Jun 23 04:41:54 ip-208-109-108-176 kernel: sd 3:0:0:0: SCSI error: return code = 0x08000002
Jun 23 04:41:54 ip-208-109-108-176 kernel: sdb: Current: sense key: Medium Error
Jun 23 04:41:54 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error


--------------
Notice above it recognizes the drive size and sectors...not anymore...But now I don't see those errors - now I just get this whenever I try and load the drive:

udevd-event[5305]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/host6/target6:0:0/6:0:0:0/ioerr_cnt' failed
Jun 27 14:13:02 ip-208-109-108-176 kernel: sd 6:0:0:0: SCSI error: return code = 0x08000002
Jun 27 14:13:02 ip-208-109-108-176 kernel: sdb: Current: sense key: Medium Error
Jun 27 14:13:02 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error
Jun 27 14:13:02 ip-208-109-108-176 kernel:
Jun 27 14:13:02 ip-208-109-108-176 kernel: end_request: I/O error, dev sdb, sector 0
Jun 27 14:13:02 ip-208-109-108-176 kernel: Buffer I/O error on device sdb, logical block 0
Jun 27 14:13:04 ip-208-109-108-176 kernel: sd 6:0:0:0: SCSI error: return code = 0x08000002
Jun 27 14:13:04 ip-208-109-108-176 kernel: sdb: Current: sense key: Medium Error
Jun 27 14:13:04 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error
Jun 27 14:13:04 ip-208-109-108-176 kernel:


-----------------------

testdisk sees nothing, photorec sees nothing(error reading sector 0), dd gives me IO errors, ddrescue does nothing...PLEASE HELP
Could this be a driver or Kernel issue or is my drive likely shot?

NOTE: I can NOT physically access the drive so I can not plug it in, unplug it, or even set it directly as SATA - it has to be USB enclosure according to my data center - they say the jumpers are set correctly...Should I load a different Kernel and different USB drivers?

-----
The Drive WD - keeps coming up now as HAWK which from my understanding means the drive is FUCKED...this just started since the drive was put in the enclosure.

---------
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Vendor: WDC ROM Model: MODEL-HAWK----- Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 1 512-byte hdwr sectors (0 MB)
sdb: Write Protect is off
sdb: Mode Sense: 34 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 1 512-byte hdwr sectors (0 MB)
sdb: Write Protect is off
sdb: Mode Sense: 34 00 00 00
sdb: assuming drive cache: write through
sdb:<6>sd 3:0:0:0: SCSI error: return code = 0x08000002
sdb: Current: sense key: Medium Error
Add. Sense: Unrecovered read error

end_request: I/O error, dev sdb, sector 0

I am confused as to whether it EVER worked in the new usb encloser.. if not, talk to your data-center about it.. since they apparently claim everything is set correctly.

As far as loosing your data.. and *needing* it desperately.. I doubt ANYONE will sympathize with you.. since you are responsible for making *GOOD* backups on a regular basis..

Either way, good luck, and lettuce know..

If at all possible, having failed through usb, put the drive on an ide or sata bus in a box and try there.
lastly, ring the manufacturer with the drive in your hand. I was able to get a copy drive once to my blown one, and swap the electronic cards and rescue data that way.

The drive has NEVER worked in the USB enclosure....but it was placed in the USB enclosure because it had been restarting the box intermittently (I didn't know this until it was too late). They gave me a new sda - a new main drive with the exact same partitions (3) and same geometry (but of course it was flushed).

I know I know - about backups - I haven't made one in a while of this particular site (it's a 50GIG site that I am trying to get) - I have the site in pieces on my home machine...scattered - not nearly a reflection of the live box. I have another dedicated box with GoDaddy and I have backups on it and I had planned to do backups of this dedicated box this month...now here I am.

I can't touch the drive, I can't unplug it, I can't move it - can't plug it in SATA - nothing...and the data center insists on a USB enclosure.

I am insisting they remove it from the USB enclosure and go from there...plug it in directly to the MB but they are saying they won't.

I can't call the manufacturer with the drive in hand...I can call the manufacturer though...GoDaddy won't mail me the drive...they will not physically mail any hardware - I am suspecting because they will just reuse the drive after 20 days - or try to - it may not work and they would simply send it to WD for an RMA and get a new one (I am sure their drives are in warranty)

Hi,

Welcome to LQ!

If you cannot get the data center to aid in the recovery then your just hitting a brick wall. You will need to get the hdd and either do a mirror image to try and recover from or use a third party service for recovery. It is possible that the enclosure is the problem. Request a change to a new enclosure. Ask for all the hardware specifications along with jumper settings for drive & enclosure. Whenever a hardware failure occurs then request the data center to send the equipment to a third party service for recovery. Very costly but do it once and you will be certain to perform backups for ever after for that $$ expenditure.

Sadly, no magic bullet for an issue of this type. Your at the mercy of the tech support and how willing they are to extend their service.

BTW, please use the vbcode tags to enclose your data or long lists. The # or Quote at the top of the reply window will make your posts cleaner therefore easier to read.

it's GoDaddy - and they will not replace the enclosure (saying it is working fine) they won't tell me the model of the drive...they won't tell me the jumper settings, they won't tell me how the drive is recognized in BIOS - they will NOT take the drive out of the enclosure - they will not place the drive on another machine (I have another dedicated box with them) and they will not 'ship' the drive anywhere...they are telling me now that they are 'shredding' the drive in 2 weeks.

they will not tell me what the hardware specs are for the enclosure or the drive. they will not send to 3rd party for any reason.

I have backups of my other dedicated box, just not this one (because it wasn't being used) I was just developing on it - getting ready to launch a project that has taken 4 years to code - I have backups scattered on several computers and I am certainly lost a ton of files/code because often I worked directly on the box and did not have a reflection of the data locally.

Hi,

Then apparently your out of luck or the means to recovery of that data. You could try to 'dd' the drive image and work from that but if the hdd/enclosure is faulty then 'garbage in = garbage out'. Lesson learned, backup periodically and grandfather.

still trying to get data off drive...no luck...
I would say the drive needs a new board. Nothing too serious but I do not have physical access to the drive and this can not be done by 3rd party providers. My data center has verified the usb is working properly ... but there is NOTHING in the message logs of any activity by them... ?? (UPDATE --- yes I see this in the logs now)
you know what I mean? I am going to request a reprovision with Fedora. I think I will get the same kernel but you never know could be a kernel problem though not very likely at this point...

I'm sifting through scattered/partial backups now trying to pick up the pieces.

Gary: dd just reports IO errors.


- Bond

testdisk
I entered the 'guessed' geometry for this drive (which shows up as 512 Bytes) Then in testdisk I select none and eventually I have an ext3 partition 'unknown partition' seeming to have the proper geometry.

search superblock doesn't find anything (comfortably goes to 100%) when I 'create image' it attempts to create image.dd on my sda.

it shits the bucket when it hits 2GB. The drive is 120.
I assume it's because it's on 32-bit. Is there a way I can trick testdisk to think I am on 64-bit?

I realize I'll throw a new drive in there to grab the image that's fine. With that said - it's likely just an image of garbage.

- Bond

talking with data center - we're going to change the enclosure - it's not an enclosure as it turns out it is just the adapter style to SATA but they are going to change the cables.

I'm reprovisioning to Fedora next but I am sure that is going to be the same kernel.

the other box I have is at a different data center location with them ...not in the same building so the drive apparently can not be moved to the other box for troubleshooting.

they are going to change the port numbers for the drive.

- Bond

Sounds great..please keep us informed of your results..

Ok, looks like the drive was recognized with proper geometry (for a moment) when it was moved to another port. Please look at this:


---------------------------------------

Jun 28 00:21:35 ip-208-109-108-176 kernel: usb 2-1: USB disconnect, address 3
Jun 28 00:22:04 ip-208-109-108-176 kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2
Jun 28 00:22:04 ip-208-109-108-176 kernel: usb 4-2: configuration #1 chosen from 1 choice
Jun 28 00:22:04 ip-208-109-108-176 kernel: scsi7 : SCSI emulation for USB Mass Storage devices
Jun 28 00:22:09 ip-208-109-108-176 kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 2
Jun 28 00:22:15 ip-208-109-108-176 kernel: Vendor: WDC WD12 Model: 00JS-00NCB1 Rev:
Jun 28 00:22:15 ip-208-109-108-176 kernel: Type: Direct-Access ANSI SCSI revision: 02
Jun 28 00:22:15 ip-208-109-108-176 kernel: SCSI device sdc: 234441648 512-byte hdwr sectors (120034 MB)
Jun 28 00:22:15 ip-208-109-108-176 kernel: sdc: Write Protect is off
Jun 28 00:22:15 ip-208-109-108-176 kernel: sdc: assuming drive cache: write through
Jun 28 00:22:15 ip-208-109-108-176 kernel: SCSI device sdc: 234441648 512-byte hdwr sectors (120034 MB)
Jun 28 00:22:15 ip-208-109-108-176 kernel: sdc: Write Protect is off
Jun 28 00:22:15 ip-208-109-108-176 kernel: sdc: assuming drive cache: write through
Jun 28 00:22:18 ip-208-109-108-176 udevd-event[7479]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/host7/target7:0:0/7:0:0:0/ioerr_cnt' failed
Jun 28 00:22:18 ip-208-109-108-176 kernel: sdc:<6>usb 4-2: reset full speed USB device using uhci_hcd and address 2
Jun 28 00:22:20 ip-208-109-108-176 kernel: sd 7:0:0:0: SCSI error: return code = 0x08000002
Jun 28 00:22:20 ip-208-109-108-176 kernel: sdc: Current: sense key: Medium Error
Jun 28 00:22:20 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error
Jun 28 00:22:20 ip-208-109-108-176 kernel:
Jun 28 00:22:20 ip-208-109-108-176 kernel: end_request: I/O error, dev sdc, sector 0
Jun 28 00:22:20 ip-208-109-108-176 kernel: Buffer I/O error on device sdc, logical block 0
Jun 28 00:22:21 ip-208-109-108-176 kernel: sd 7:0:0:0: SCSI error: return code = 0x08000002
Jun 28 00:22:21 ip-208-109-108-176 kernel: sdc: Current: sense key: Medium Error
Jun 28 00:22:21 ip-208-109-108-176 kernel: Add. Sense: Unrecovered read error

Given output in your posts #1 and #12 the disk has been in an USB enclosure always. SATA devices would never show the "SCSI emulation for USB Mass Storage device" line. You should definitely try but I wonder if any tools you ran earlier on will suddenly be able to see or do anything with the drive. The "sector 0" and "Unrecovered read" errors don't exactly turn the "and there was much rejoicing" level up to more than 0. Except for The Holy Hand Grenade of Antioch I doubt there's a Holy Grail for this type of HW problem, especially if you can't have physical access to the HW.

yes the drive has been in the usb enclosure (cable) since I posted this issue - when I said 'other port' I mean other USB port.

Before this post it was just sda - the only drive on the box (SATA). They replaced the sda and threw the main drive on usb because the server was intermittently restarting (I was not aware of this and never did see the logs for this).

I hear you about the tools - because the proper sector count is there...but the drive is physically removed from the machine at this exact moment and I can't run any tests at this moment - besides, eventually after x number of tries with IO errors the drive no longer was seen as 120 GIG - took about 20 minutes and the drive was then seen as 512 Bytes.

They are going to check the drive in BIOS in a moment and I will have the results of that soon - then the drive will be removed again - I am formatting the main drive and putting Fedora (reprovision) - reconnecting the usb drive and going from there.

- Bond

Running Fedora Core 8 now - same problems - the image I was creating...is just garbage all zeros. Looks like this drive is toast.