HDD issues.

[goontron]

Re: HDD issues.

get it on an internal PSU bus. Your case may not be providing enough power by the looks of it. Also if you're using the USB bridge you cant send SMART commands beyond the necessary ones for normal operation.

[Spork Schivago]

Re: HDD issues.

When you say power cycling on and off of the power drive. Are you saying the activation light goes out when you don't see the drive with the software? If this is the case then you could have a bad power connector to the drive. If it only happen in a read mode and not a write mode and it is just in one partition this could be a bad section of the disk. Do you have any test program on your computer that writes and read data to the hard disk. That should tell you the section of the disk you are having problems with. Use to be that one could could read and write to certain places on the disk to be able to tell which ones were bad. The program would not stop when it ran into the first bad section but would store it in memory and continue on. Some programs would remember the bad sections and not try to retrieve them. In this way some of the programs on the disk were recoverable and some programs were corrupt by the bad sectors. You could also retrieve bits of data from all good places on the disk. Then you would have to reverse engineer it to tell which part of the bad program needed to be fixed.

The hard drive completely looses power and then the power on the hard drive comes back, but this seems to only happen when I read (didn't try writing because the one partition I'm having trouble with was in hibernation mode and my Linux system makes me mount it read only because of this). I left the hard drive connected for over 24 hours, with no reads, and there where no problems. I'm not used to hard drives just turning off like this. It makes using a program like ddrescue a real pain in the ass. Every time the drive shuts down, ddrescue crashes, the drive disappears from /dev for a bit, and then reappears 10 seconds later or so. In X-Windows, it wants me to the type root's password to mount them. I tried setting up a udev rule to turn off USB auto-mount (I'm using a USB external hard drive enclosure) but it didn't work. This is what dmesg says:

[1998407.447046] usb 2-1: new high-speed USB device number 18 using ehci-pci
[1998407.561993] usb 2-1: New USB device found, idVendor=152d, idProduct=2351
[1998407.561999] usb 2-1: New USB device strings: Mfr=10, Product=11, SerialNumber=5
[1998407.562024] usb 2-1: Product: USB/eSATA To SATA Bridge
[1998407.562029] usb 2-1: Manufacturer: JMicron
[1998407.562031] usb 2-1: SerialNumber: D21E428696FF
[1998407.563805] usb-storage 2-1:1.0: USB Mass Storage device detected
[1998407.567876] scsi21 : usb-storage 2-1:1.0
[1998408.574153] scsi 21:0:0:0: Direct-Access   WDC WD75 00BPVT-80HXZT3    PQ: 0 ANSI: 2 CCS
[1998408.574503] sd 21:0:0:0: Attached scsi generic sg3 type 0
[1998408.805627] sd 21:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[1998408.809765] sd 21:0:0:0: [sdc] Write Protect is off
[1998408.809772] sd 21:0:0:0: [sdc] Mode Sense: 34 00 00 00
[1998408.810756] sd 21:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[1998408.905788] sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6
[1998408.912506] sd 21:0:0:0: [sdc] Attached SCSI disk
[1998670.350965] sd 21:0:0:0: [sdc] Unhandled sense code
[1998670.350973] sd 21:0:0:0: [sdc]
[1998670.350977] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[1998670.350981] sd 21:0:0:0: [sdc]
[1998670.350984] Sense Key : Medium Error [current]
[1998670.350991] sd 21:0:0:0: [sdc]
[1998670.350995] Add. Sense: Unrecovered read error
[1998670.350999] sd 21:0:0:0: [sdc] CDB:
[1998670.351028] Read(10): 28 00 00 d0 33 80 00 00 80 00
[1998670.351055] end_request: critical medium error, dev sdc, sector 13644672
[1998700.880045] usb 2-1: reset high-speed USB device number 18 using ehci-pci
[1998701.350447] usb 2-1: device firmware changed
[1998701.350490] usb 2-1: USB disconnect, device number 18
[1998701.355400] scsi 21:0:0:0: rejecting I/O to offline device
[1998701.355408] scsi 21:0:0:0: [sdc] killing request
[1998701.355425] scsi 21:0:0:0: [sdc] Unhandled error code
[1998701.355427] scsi 21:0:0:0: [sdc]
[1998701.355429] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[1998701.355432] scsi 21:0:0:0: [sdc] CDB:
[1998701.355434] Read(10): 28 00 00 d0 34 01 00 00 7f 00
[1998701.355442] end_request: I/O error, dev sdc, sector 13644801
[1998701.468035] usb 2-1: new high-speed USB device number 19 using ehci-pci
[1998701.583068] usb 2-1: New USB device found, idVendor=152d, idProduct=2351
[1998701.583073] usb 2-1: New USB device strings: Mfr=10, Product=11, SerialNumber=5
[1998701.583076] usb 2-1: Product: USB/eSATA To SATA Bridge
[1998701.583079] usb 2-1: Manufacturer: JMicron
[1998701.583081] usb 2-1: SerialNumber: D21E428696FF
[1998701.584040] usb-storage 2-1:1.0: USB Mass Storage device detected
[1998701.593172] scsi22 : usb-storage 2-1:1.0
[1998702.600231] scsi 22:0:0:0: Direct-Access   WDC WD75 00BPVT-80HXZT3    PQ: 0 ANSI: 2 CCS
[1998702.604286] sd 22:0:0:0: Attached scsi generic sg3 type 0
[1998702.831828] sd 22:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[1998702.834450] sd 22:0:0:0: [sdc] Write Protect is off
[1998702.834456] sd 22:0:0:0: [sdc] Mode Sense: 34 00 00 00
[1998702.835837] sd 22:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[1998702.929902] sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6
[1998702.936577] sd 22:0:0:0: [sdc] Attached SCSI disk

This kind of makes me think it is bad sectors on the drive. So essentially, there's no way to repair this, right? Even with a clean room and the proper tools, the platters would have to be replaced, correct? Even though we could use ddrescue to get data off the partition, something is so horribly wrong, when it try reading a bad sector, the drivers actually have to restart the device.

[stj]

Re: HDD issues.

internal drive, or external?

[keeney123]

Re: HDD issues.

When you say power cycling on and off of the power drive. Are you saying the activation light goes out when you don't see the drive with the software? If this is the case then you could have a bad power connector to the drive. If it only happen in a read mode and not a write mode and it is just in one partition this could be a bad section of the disk. Do you have any test program on your computer that writes and read data to the hard disk. That should tell you the section of the disk you are having problems with. Use to be that one could could read and write to certain places on the disk to be able to tell which ones were bad. The program would not stop when it ran into the first bad section but would store it in memory and continue on. Some programs would remember the bad sections and not try to retrieve them. In this way some of the programs on the disk were recoverable and some programs were corrupt by the bad sectors. You could also retrieve bits of data from all good places on the disk. Then you would have to reverse engineer it to tell which part of the bad program needed to be fixed.

[ddscentral]

Re: HDD issues.

It could be anything: bad heads, bad sectors, dying electronics, etc. But does it really matter ?
Knowing why the drive behaves like that most likely will not help you save the data.

Try to save what you can and replace the drive.

[Spork Schivago]

Re: HDD issues.

Oh, I always want to say I don't think it's anything with the heads, I don't hear any clicking noise or anything like that. Granted, the internals of a hard drive aren't really my strong suite here. Thanks.

[Spork Schivago]

Hi,

I have a 750 WD Blue drive here and it keeps power cycling. Every time I try to read data off the partition that contained the OS / user data, the drive disappears and after a few seconds, reappears. This makes it very difficult to use ddrescue.

I've been able to successfully recovery the recovery partitions. My question is simple. Does anyone knows what causes a hard drive to power cycle like this? ddrescue reports bad sectors, but I think that might just be because when the drive powers down, it's marking it as bad. I haven't seen it mark any sectors bad while it's actually recovering data.

Is this bad sectors on the drive or is it something with the heads or the PCB? I'm thinking it's probably not circuitry because I was successfully able tor recover 4 other partitions, 300MB, 600MB, 2.9GB and 20GB in size. I would think if it was because of a dying PCB, I wouldn't of been able to get that 20GB without having issues.

ddrescue has recovered 5.6GB so far and the drive has power cycled about 20 times now.

Thanks.