Hi
I am running this burn in test, following the tutorial on this forum
The hdd is a 3TB WD30EFRX Nas 2.0. Believe it or not it is a brand new disk that I bought a few years back and didn't get a chance to put together a system with yet.
The exact model is: WD30EFRX-68EUZN0
When I run badblocks command after about 1h I get this error on one of the drives every second pretty much that creates probably tens of thousands of errors on it:
Is this just a bad drive? Am I missing anything?
I bought over the years 10 brand new drives of the same model 4 are Nas 3.0 and 6 are Nas 2.0
So far out of out of 7 I opened and installed in the system, one was "dead" (assumed since the system just doesn't see it) and this one is giving this errors at badblocks command.
I am running this on a Dell Poweredge T410 with HBA 200 flashed to it mode. (2 CPUs and 32GB ECC Ram)
Side question, is there any major risk on using the Nas 3.0 and Nas 2.0 together in the same dev pool?
Thank you
I am running this burn in test, following the tutorial on this forum
The hdd is a 3TB WD30EFRX Nas 2.0. Believe it or not it is a brand new disk that I bought a few years back and didn't get a chance to put together a system with yet.
The exact model is: WD30EFRX-68EUZN0
When I run badblocks command after about 1h I get this error on one of the drives every second pretty much that creates probably tens of thousands of errors on it:
Mar 8 05:20:13 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 06 0e 00 00 01 00 00
Mar 8 05:20:13HRetrying(da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:1343HCAM st(da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:139;43HSCSI(da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:13;43HRetry(da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:1425H(da5:m (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00 length 131072 SMID 364 terminated ioc 804b loginfo 31110d01 scsi 0 state c xfer 0
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): CAM status: CCB request completed with an error
Mar 8 05:20:14;25H (da5:mps0:0:5:0): Retrying command
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 09 47 00 00 01 00 00
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:14 freenas (da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00 length 131072 SMID 168 terminated ioc 804b loginfo 31110d01 scsi 0 state c xfer 0
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): CAM status: CCB request completed with an error
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): Retrying command
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0b 16 00 00 01 00 00
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): CAM status: SCSI Status Error
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): SCSI status: Check Condition
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): Retrying command (per sense data)
Mar 8 05:20:15 freenas (da5:mps0:0:5:0): WRITE(10). CDB: 2a 00 11 0c 7c 00 00 01 00 00 length 131072 SMID 759 terminated ioc 804b loginfo 31120303 scsi 0 state c xfer 0
Is this just a bad drive? Am I missing anything?
I bought over the years 10 brand new drives of the same model 4 are Nas 3.0 and 6 are Nas 2.0
So far out of out of 7 I opened and installed in the system, one was "dead" (assumed since the system just doesn't see it) and this one is giving this errors at badblocks command.
I am running this on a Dell Poweredge T410 with HBA 200 flashed to it mode. (2 CPUs and 32GB ECC Ram)
Side question, is there any major risk on using the Nas 3.0 and Nas 2.0 together in the same dev pool?
Thank you