Problem with 8TB WD Red

[ukos]

I have a problem attaching a WD Red WD80EFAX-68KNB to my freenas setup. I have a pool with 2TB devices running with no problem but the 8TB disk is not recognized in freenas.

I can see it in the BIOS with the correct size. I have also tried plugging it to another SATA controller without any luck



During freenas startup I can see an error that has to do with the failing drive recognition but I can not understand what that means.

Code:

(aprobe5:ahcich8:0:0:0): SETFEATURES SET TRANSFER MODE. ACB: ef 03 00 00 00 40 00 00 00 00 46 00
(aprobe5:ahcich8:0:0:0): CAM status: ATA Status Error
(aprobe5:ahcich8:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe5:ahcich8:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00
(aprobe5:ahcich8:0:0:0): Retrying command
(aprobe5:ahcich8:0:0:0): SETFEATURES SET TRANSFER MODE. ACB: ef 03 00 00 00 40 00 00 00 00 46 00
(aprobe5:ahcich8:0:0:0): CAM status: ATA Status Error
(aprobe5:ahcich8:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(aprobe5:ahcich8:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00
(aprobe5:ahcich8:0:0:0): Error 5, Retries exhausted

Should I try the drive in another board to see if it is working at all or is it a FreeBSD specific issue that the disk size of 8TB produces the problem?

For the sake of completeness:

The board is a ASRock-EP2C602 with onboard Intel and Marvel Controllers.
This is the BIOS screen for my devices:

 

[Mr. Slumber]

During freenas startup

Which FreeNAS version runs on your machine?

 

[Chris Moore]

or is it a FreeBSD specific issue that the disk size of 8TB produces the problem?

This has nothing to do with FreeBSD. We have many forum members using 8TB drives and I have a server full of 10TB drives at work.
There is a problem with your system that we need to diagnose.

 

[HoneyBadger]

I have a feeling that this is related to the 3.3v reset issue that came about with old PSUs and newer drives.

https://www.tomshardware.com/news/hdd-sata-power-disable-feature,36146.html

 

[rvassar]

They changed the spec of the power plug for SATA 3.1, and the 3.3v PSU line is putting the drive to sleep. Try plugging it in using a 4-pin Molex to SATA adapter. The old 4 pin Molex power plug doesn't carry 3.3v.

 

[Mr. Slumber]

If you have the 3.3V pin 3 "problem" please watch this video. (helped me a lot to get my shucked drives running ;) )

 

[HoneyBadger]

They changed the spec of the power plug for SATA 3.1, and the 3.3v PSU line is putting the drive to sleep. Try plugging it in using a high quality, crimped and NOT injection-moulded, 4-pin Molex to SATA adapter. The old 4 pin Molex power plug doesn't carry 3.3v.

Added the bolded section, lest the OP discover the reason for the rhyme "Molex to SATA, lose all your data"

 

[SweetAndLow]

I have a feeling that this is related to the 3.3v reset issue that came about with old PSUs and newer drives.

https://www.tomshardware.com/news/hdd-sata-power-disable-feature,36146.html

The efax model number is a real wd red drive which doesn't have the 3.3v problem. Was this drive shucked?

 

[ukos]

> Which FreeNAS version runs on your machine?

FreeNAS-11.2-U3

> The efax model number is a real wd red drive which doesn't have the 3.3v problem.

Unfortunately WD does not state clearly in theier specs. https://www.wd.com/products/internal-storage/wd-red.html

I tried disabling the 3.3V anyway as I had 5 wires on my SATA power connector. I changed that with a MOLEX 4pin to SATA 4pin connector. Drive spins with some noises on power up but does not show up in freeNAS.

> Was this drive shucked?

I think that is the most probable soution. I will try the drive in a ubuntu machine. Maybe it is broken. Thank you for the feedback.

 

[russnas]

Here is wd documentation on this new feature for those who want to read about it
https://documents.westerndigital.co...h-brief-western-digital-power-disable-pin.pdf

Not much help sorry but your 8tb should be without this feature