Other Suspected HDD failure

Hello,

I have a HDD that I suspect is failed somewhere along the line. I currently have it in an USB convertor. It has been removed from a failed Blu-ray player. It is a WD500AVCS. I was looking to format it and use as a spare disk but get the CAM error:

Code:
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
(da0:umass-sim0:0:0:0): Retrying command (per sense data)
I have used smartctl to probe further. Appears to "Pass".

The disk sort of responds to gpart. It sort of creates an UFS filesystem but won't pass fsck. Flatly refuses to do anything with ZFS.

To my mind; it is gone. Is there a tool that will give a definitive answer, or would others agree that it has expired?
 
... I was looking to format it and use as a spare disk but get the CAM error:
Code:
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: ABORTED COMMAND asc:0,0 (No additional sense information)
(da0:umass-sim0:0:0:0): Retrying command (per sense data)

This looks to me more like an error from the USB convertor. I got an USB3-HD case, which shows similar errors on FreeBSD 10.3-RELEASE up to 12-CURRENT. That case did not work at all on FreeBSD 10.3-RELEASE, it let me at least mount the HD on FreeBSD 11.0-RELEASE, but I saw random write errors. And on FreeBSD 12-CURRENT, I can work with it, even though it gives me the CAM status: SCSI Status Error.

I suggest to try another USB case, or to connect the disk directly to a SATA port.
 
I thought that. Took the disk out and put a different drive in (Hitachi). Drive worked flawlessly.

Have had the original Western Digital (problem drive) connected to a SATA port on separate computer. Although used Lubuntu that time and the computer was unable to communicate with the drive.
 
I thought that. Took the disk out and put a different drive in (Hitachi). Drive worked flawlessly.

Have had the original Western Digital (problem drive) connected to a SATA port on separate computer. Although used Lubuntu that time and the computer was unable to communicate with the drive.

You said, the WD500AVCS responds to gpart(8). Did you completely destroy the previous partition scheme? If not, then I suggest to format it from the beginning.

!!! make sure that you are operating on the correct device -- here da0 !!!:
gpart destroy -F da0
gpart create -s GPT da0
gpart add -a 4k -t freebsd-ufs -l PUT_A_NICE_DISK_LABEL_HERE da0

newfs -U /dev/da0p1

mount -o noatime /dev/da0p1 /mnt
 
I can create the GPT, add a UFS partition and use newfs.

gpart show da0 shows the correct result but every command is accompanied by a reported I/O error. It does not successfully mount either .

I'm probably being too miserly to give up on the drive as I was trying to recover some video files from it.

I tried dd too. To zero out the drive, but unsuccessful. I think it is bin time.

Thanks for the suggestions, however.
 
Back
Top