Broken disk HDIO_GET_IDENTITY

[djpig]

Hi,
I have a problem with a segate momentus 5400.3, my linux box report this errors:

Code:

Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] Write Protect is off
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] No Caching mode page present
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] Assuming drive cache: write through
Dec 11 09:07:31 porky kernel: sd 6:0:0:2: [sdf] Attached SCSI removable disk
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] No Caching mode page present
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] Assuming drive cache: write through
Dec 11 09:07:31 porky kernel: sd 6:0:0:0: [sdd] Attached SCSI disk
Dec 11 09:07:31 porky kernel: sd 6:0:0:1: [sde] Attached SCSI removable disk
Dec 11 09:07:31 porky ata_id[16192]: HDIO_GET_IDENTITY failed for '/dev/sdd'


after receive this errors the disk pass in standby mode!

I know a lot of tools to recovery data from disk but i can't read data if is in standby.

Code:

hdparm -gI /dev/sdd

/dev/sdd:
geometry      = 1024/0/62, sectors = 0, start = 0
SG_IO: bad/missing sense data, sb[]:  70 00 02 00 00 00 00 12 00 00 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media
Standards:
   Likely used: 1
Configuration:
   Logical      max   current
   cylinders   0   0
   heads      0   0
   sectors/track   0   0
   --
   Logical/Physical Sector size:           512 bytes
   device size with M = 1024*1024:           0 MBytes
   device size with M = 1000*1000:           0 MBytes
   cache/buffer size  = unknown
Capabilities:
   IORDY not likely
   Cannot perform double-word IO
   R/W multiple sector transfer: not supported
   DMA: not supported
   PIO: pio0


Code:

hdparm -i /dev/sdd

/dev/sdd:
SG_IO: bad/missing sense data, sb[]:  70 00 02 00 00 00 00 12 00 00 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
HDIO_GET_IDENTITY failed: Invalid argument


any ideas?
luca.

[Vulcan]

a) How is that drive attached to the PC (ATA / SATA / USB)? If it is attached via ATA or SATA (or if it is attached via USB and the PC has a new BIOS which recognises USB devices), what is reported for this drive by the BIOS (manufacturer / model / capacity)?

b) What is the history of this situation? What changed since that drive was last recognised OK?

c) Are you trying to recover data from the drive, or just to repair the drive (and you don't care about the data)?

[djpig]

Hi

The disk work attached sta on laptop.

The notebook launced by baby after not start...

I have plugged in with adaptor TO my Linux box

My inteteay is Only recover data i can use photorec and dd

[Vulcan]

Thanks for the reply. Unfortunately it did not translate completely into English. Here is what I guess you are saying:

The disk work attached sta on laptop.

Originally this SATA disk was in a laptop.

The notebook launced by baby after not start...

The laptop was dropped / bounced (???) by a baby, and after that, the laptop will not boot from this disk.

I have plugged in with adaptor TO my Linux box

You have now attached the SATA drive via USB to your Linux system.

My inteteay is Only recover data i can use photorec and dd

You want to recover data from the disk, and you were hoping to use photorec, if the disk was recognised by Linux.

Based on my guess about what you mean above, there has been physical shock to the disk. Although personally I would use a different DIY strategy, it is likely that you will not be successful using DIY (do it yourself) recovery, as the physical shock has caused internal damage (head / media / bearings / motor etc.), and that is why the drive is not correctly recognised (e.g. the Identify Device command is returning invalid or partial data).

If the data is important / valuable, then consider using a professional DR company, before more damage is done inside the disk during your DIY attempts.