Error on Drive During Test With Badblocks

[hunter]

I have been testing a used 3 Tb drive I recently purchased. Currently it's on my TrueNAS box but not a member of any Zvol.

It passed the smartctl short and long tests, so I started badblocks and immediately found the following new errors in the log:

Jan 9 21:37:33 freenas ada0 at ahcich2 bus 0 scbus3 target 0 lun 0
Jan 9 21:37:33 freenas ada0: <HGST HUS724030ALA640 MF8OAA70> s/n PN2234P8J5BE9R detached
Jan 9 21:37:33 freenas (ada0:ahcich2:0:0:0): Periph destroyed
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): RES: 51 04 00 00 00 40 00 00 00 00 01
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): Retrying command, 0 more tries remain
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): RES: 51 04 00 00 00 40 00 00 00 00 01
Jan 9 21:37:37 freenas (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted


The badblocks test seems to be continuing despite the errors. The drive no longer shows up under Storage --> Disks, yet the badblocks program seems to continue running. Can anyone tell me if the errors mean I will have a problem using this drive for data? Or if the errors are due to the drive itself having a problem as opposed to the cable or something else I might be able to fix?

 

[JohnDigital]

This can be caused by cabling

<HGST HUS724030ALA640 MF8OAA70> s/n PN2234P8J5BE9R detached

It was bad enough to get kicked it looks like. Id be very leery of this drive.

 

[hunter]

Thank you very much @John Digital. I later found 7 reallocated sectors in the drive's SMART data so sending it back. I will also try some more testing to rule out a cabling issue, possibly in addition to the drive's problem(s).