Diagnostics attached. The drive in question is /dev/sdk. The basic metadata about this drive can be read just fine, like model, serial number, free space etc, but running a smartctrl command gets a "scsi error badly formed scsi parameters" error for any items.

 

I've switched the drive to different bays, in case there's something wrong with the backplane or associated cables, but the errors remain the same, so it seems to be a pretty definitive indicator that the issue is with the drive, just wanted a 2nd opinion here.

 

FWIW, this is one of the black Friday Western Digital sale drives (WD161KFGX) that I just received, which is kind of laughable...

zeegee-filer-diagnostics-20241204-2031.zip

The fact that SMART cannot be read properly is not a good sign.

 

To eliminate it being something at the server I would suggest you try to plug it into a PC and running the manufacturers diagnostics software against it.   If that does not work then you definitely should do a RMA to get it replaced.

On 12/5/2024 at 1:09 AM, itimpi said:

The fact that SMART cannot be read properly is not a good sign.

 

To eliminate it being something at the server I would suggest you try to plug it into a PC and running the manufacturers diagnostics software against it.   If that does not work then you definitely should do a RMA to get it replaced.

 

I was able to finally shutdown my unraid server today after the pre-read part of preclear for all other drives have finished; took that drive out, connected to my Windows workstation and got WD's own "dashboard" tool, and sure enough, same deal: can't read SMART data, can't do long or short tests.

 

Also one of the other 16T WD Red Pro drive generated a lot of "Read Recovery Attempts" towards the end of the pre-read test with intermittent low read rates (single digit MB/s).

 

This kind of makes the quality control of WD questionable...