View topic - WD5000ABYS - DID_BAD

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Page 1 of 1

[ 10 posts ]

Previous topic | Next topic

Author

Message

WDCrasher

Post subject: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 6:37

Joined: March 9th, 2010, 5:46
Posts: 5
Location: Germany

Hi folks,

one of my harddrives started showing strange kernel messages on my Ubuntu server some weeks ago. Unfortunately I did not see this unless my UPS failed last week and the server was shut down caused by power failure:

Code:

Feb  1 06:54:22 tux kernel: [1344329.015431] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.015445] end_request: I/O error, dev sdf, sector 10327                                                                      
Feb  1 06:54:22 tux kernel: [1344329.016347] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.016359] end_request: I/O error, dev sdf, sector 10327                                                                      
Feb  1 06:54:22 tux kernel: [1344329.016906] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.016917] end_request: I/O error, dev sdf, sector 10327                                                                      
Feb  1 06:54:22 tux kernel: [1344329.017444] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.017455] end_request: I/O error, dev sdf, sector 10327                                                                      
Feb  1 06:54:22 tux kernel: [1344329.017983] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.017994] end_request: I/O error, dev sdf, sector 10327                                                                      
Feb  1 06:54:22 tux kernel: [1344329.018523] sd 7:0:0:0: [sdf] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK                                  
Feb  1 06:54:22 tux kernel: [1344329.018534] end_request: I/O error, dev sdf, sector 10327

After powering up, the drive was not recognized by BIOS on that machine. On another machine it was shown as "0 GB".
Now I checked it on a third machine and it was recognized by BIOS.
Linux (Ubuntu 9.04) did not see the drive however, while my Windows XP installation recognized it as being partitioned with an "unknown file system" (it's EXT2/3, which Windows doesn't know about).

I tried several tools, but the drive does not run stable. Sometimes booting the system just stops and I have to power down and restart. Some Linux based tools (like GParted live CD) do not recognize the drive, some Windows/DOS based tools do not recognize the filesystem.

The drive is getting quite warm after 30 minutes compared with another drive of the same type.

Since I have an identical drive with same manufacturing date and the serial number "almost" the same (last 3 or 4 digits are different) I think about changing the PCB. I have been warned by many posts here to do this, but most of the questions here start with "where do I get an identical PCB". I already have one, so here are my questions:

1. Are there other tools to copy the faulty disk to the spare drive? Does MHDD clone a complete drive with 500G of data to another?
2. If it does, my favourite way to recovery would be: Clone drive with MHDD to spare drive, Change PCB from spare drive to broken drive, try to get the full data from broken drive. Your suggestions?

The drive contaings almost 450G of video files from my DV camera. I copied all of them during the last christmas holidays which took me two weeks. I still have the original tapes, so doing the complete work again is still possible. Complete loss of data of the drive is not a tragedy, but if I can avoid...

Any help appreciated!

Kind regards,

WDCrasher

Top

N.C.

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 9:10

Joined: March 28th, 2008, 7:52
Posts: 1466
Location: Europe, Hungary

Hi,

Your drive have SA problems and/or head problems, but not PCB.
Your drive have unique configured data inside the PCB, so exchange is not safe for your both drive, but surely will not solve your problem.

My suggestion:
Try to find a PC wich can recognize the drive under linux, and use dd_rescue to make a sector backup.

use this command:
dd_rescue -v -b 4096 -B 512 -d -e 1000 -l [logfile] /dev/[source] /dev/[destination]

If this is finished, fsck comes, than finally save the files to the 3rd hdd...

Good Luck,
Janos

Top

WDCrasher

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 10:36

Joined: March 9th, 2010, 5:46
Posts: 5
Location: Germany

Hi Janos,

thanks for your quick answer.

dd_rescue was my favourite to back up my drive, but Linux does not detect the device anymore, so /dev/[source] is missing, I only see the target drive although both drives are recognized by System BIOS.

Is there a way to copy SA information from target to source drive (both have identical manufacturing date)? I just checked in the PC3k page, but (besides from being much too expensive, I guess) my drive is not supported.

Thanks,

WDCrasher

Top

N.C.

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 10:41

Joined: March 28th, 2008, 7:52
Posts: 1466
Location: Europe, Hungary

WDCrasher wrote:

Your drive is supported by PC3K, but the tool is much more expensive than a simple one-time recovery in any lab.
Additionally, you can't copy the SA from one drive to another, the SA have a lot of calibration data wich was calculated in the factory.
If you copy the entire SA the another drive will die soon or immediately.
If the BIOS recognize the drive, Linux does it surely.
I do the most cases under linux.

Try to use another Live CD....
But don't power cycle the drive if not really needed, your drive is dieing, keep this in mind!

Good luck.

... or if you think, drop me a mail, and i can give a friendly price for this case...

Janos

Top

WDCrasher

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 15:07

Joined: March 9th, 2010, 5:46
Posts: 5
Location: Germany

Hi Janos,

I just tried another Linux Live Distribution (SuSE 11.0, probably not well known outside Germany). This is what dmesg says:

Code:

ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x1950000 action 0xa frozen
ata6: SError: { PHYRdyChg CommWake Dispar LinkSeq TrStaTrns }
ata6.00: cmd c8/00:20:00:00:00/00:00:00:00:00/e0 tag 0 dma 16384 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
ata6.00: status: { DRDY }
ata6: hard resetting link
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: configured for UDMA/133
ata6: EH complete
sd 5:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 5:0:0:0: [sdc] Write Protect is off
sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata6.00: cmd c8/00:20:3f:00:00/00:00:00:00:00/e0 tag 0 dma 16384 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata6.00: status: { DRDY }
ata6: port is slow to respond, please be patient (Status 0xd0)
ata6: device not ready (errno=-16), forcing hardreset
ata6: hard resetting link
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x5)
ata6.00: revalidation failed (errno=-5)
ata6: failed to recover some devices, retrying in 5 secs
ata6: hard resetting link
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x5)
ata6.00: revalidation failed (errno=-5)
ata6: failed to recover some devices, retrying in 5 secs
ata6: hard resetting link
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x5)
ata6.00: revalidation failed (errno=-5)
ata6.00: disabled
ata6: port is slow to respond, please be patient (Status 0xff)
ata6: device not ready (errno=-16), forcing hardreset
ata6: hard resetting link
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6: EH complete
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
Buffer I/O error on device sdc1, logical block 0
Buffer I/O error on device sdc1, logical block 1
Buffer I/O error on device sdc1, logical block 2
Buffer I/O error on device sdc1, logical block 3
Buffer I/O error on device sdc1, logical block 4
Buffer I/O error on device sdc1, logical block 5
Buffer I/O error on device sdc1, logical block 6
Buffer I/O error on device sdc1, logical block 7
Buffer I/O error on device sdc1, logical block 8
Buffer I/O error on device sdc1, logical block 9
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 65
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 65
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 67
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 69
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767935
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767935
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767937
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767939
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767941
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768047
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768049
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768051
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768053
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768047
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768049
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768051
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768053
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976772992
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976772992
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773152
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773152
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976767935
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976768047
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 71
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
bootsplash: status on console 0 changed to off
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 63
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 65
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 67
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 69
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 8
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 16
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 24
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
printk: 76 messages suppressed.
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 1
Buffer I/O error on device sdc, logical block 2
Buffer I/O error on device sdc, logical block 3
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 8
Buffer I/O error on device sdc, logical block 1
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 16
Buffer I/O error on device sdc, logical block 2
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 24
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
printk: 2 messages suppressed.
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 1
Buffer I/O error on device sdc, logical block 2
Buffer I/O error on device sdc, logical block 3
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 8
Buffer I/O error on device sdc, logical block 1
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 16
Buffer I/O error on device sdc, logical block 2
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 24
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
printk: 2 messages suppressed.
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 1
Buffer I/O error on device sdc, logical block 2
Buffer I/O error on device sdc, logical block 3
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 976773160
Buffer I/O error on device sdc, logical block 122096645
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 8
Buffer I/O error on device sdc, logical block 1
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 16
Buffer I/O error on device sdc, logical block 2
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 24
sd 5:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
end_request: I/O error, dev sdc, sector 0

After that, the rescue system is loaded, but

Code:

/dev/sdc

is not seen in

Code:

fdisk -l

Code:

fdisk /dev/sdc

says: No such device or something like that.

MHDD is recognizing the disk, however. I'm trying now to find out how to save data with MHDD.

Kind regards,

WDCrasher

Top

N.C.

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 15:23

Joined: March 28th, 2008, 7:52
Posts: 1466
Location: Europe, Hungary

WDCrasher wrote:

ata6.00: qc timeout (cmd 0xec)
ata6.00: failed to IDENTIFY (I/O error, err_mask=0x5)
ata6.00: revalidation failed (errno=-5)
ata6.00: disabled

The drive is dropped at this point.

WDCrasher wrote:

end_request: I/O error, dev sdc, sector 63
Buffer I/O error on device sdc1, logical block 0
Buffer I/O error on device sdc1, logical block 1
Buffer I/O error on device sdc1, logical block 2
Buffer I/O error on device sdc1, logical block 3
Buffer I/O error on device sdc1, logical block 4
Buffer I/O error on device sdc1, logical block 5
Buffer I/O error on device sdc1, logical block 6
Buffer I/O error on device sdc1, logical block 7
Buffer I/O error on device sdc1, logical block 8
Buffer I/O error on device sdc1, logical block 9

This was the point, when the kernel gives up the partition reading.
Your drive have UNC in the first some sector.
This is critical for linux recognization, anyway, this is not critical for your data.
Can you please send a screenshot (photo) from MHDD when scanning is just started, and we can see the LBA 0?
(I have an idea.)

KEEP THE DRIVE ON!

Janos

Top

WDCrasher

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 16:30

Joined: March 9th, 2010, 5:46
Posts: 5
Location: Germany

Hi Janos,

many thanks for your support!

Started MHDD about an hour ago and the result is awful. Did not see anything but exclamation marks. MHDD stopped after some time.

Had some difficulties trying to let my mobile talk to my notebook, but now I have something like a screenshot ;-)

Not very sharp, but I hope you can see the disaster...

Think I should give up now, don't you think?

Kind regards

WDCrasher

Attachments:

File comment: MHDD disaster

IMAG0003.jpg [ 729.98 KiB | Viewed 20708 times ]

Top

N.C.

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 9th, 2010, 18:42

Joined: March 28th, 2008, 7:52
Posts: 1466
Location: Europe, Hungary

WDCrasher wrote:

Not very sharp, but I hope you can see the disaster...

Think I should give up now, don't you think?

Kind regards

WDCrasher

Yes, you should stop right here.
Your drive have SA damage clearly.
You can't do nothign now without expensive tools.
If you interested, i still can offer you good price, but i need to diagnose this drive in my lab first to say more.

Sorry.

Actually all the sectors are unreadable, this is why linux can't handle your drive.

Janos

Top

WDCrasher

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 10th, 2010, 3:03

Joined: March 9th, 2010, 5:46
Posts: 5
Location: Germany

Hi Janos,

thanks for your offer! As stated in my first post, the disk "only" contains videos that still exist on my old DV tapes (which are digital as well, so I have plenty of time to copy them again).

Usually I keep all my important data in RAID arrays (and backup them daily), but in this case my backup are only the tapes. It was my first real HDD crash, unfortunately just this drive was concerned. WD5000ABYS was not the cheapest one, I bought it for my server's RAID array in 2007 but resized the array recently with 1TB drives.

Again, many thanks for your help, Janos!

Kind regards,

WDCrasher

Top

unknown

Post subject: Re: WD5000ABYS - DID_BAD_TARGET (Linux issue?)

Posted: March 10th, 2010, 3:13

Joined: October 21st, 2007, 8:48
Posts: 1712

Hello WDCrasher,

You will not find a ( free ) solution for SA damage.

I think that Mr.Janos offer will be good with a reasonable price at this case, even if you don't need your data you can just use it again.

good luck

Top

Page 1 of 1

[ 10 posts ]

Main » Forums home » Conventional hard drives

All times are UTC - 5 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 160 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum