I am in the middle of my harddrive burn-in process. I did not notice it at first but in the dev list, all drives are listed with passX, daX save for the bootdrive wich is the only drive connected via the chipset SATA ports (the rest are connected via LSI3008 SAS controller with P12 IT-firmware) and da5 which also has this reverse order.
The smart test for da5 returned the following message:
This naturally made me suspicious, but I thought I would run all the tests on the other drives before I RMA:ed it, so I started badblocks testing.
As I half expected da5 started showing ridiculous amounts of errors. The test has now been going on for about 120 houers (been running more tests than I have threads so I expect it to take a while) All WDRED drives except for da5 are so far without error which is pleasing. However, I also received the following output from FreeNas email smartservices (I think?)
http://pastebin.com/aSa6YFWf
Since I am abit of a novice on these things I have the following questions:
1. Is there any reason why da5 (and the bootdrive) have their devicename and their pass listed in reversed order? Does it mean anything of significance?
2. Does the pastbin output log indicate that the error could be outside the drive? (E.g the SAS-controller)? Seems unlikely since all the other drives seem to be working.
Code:
[root@Darwin] ~# tmxo show-buffer tmxo: Command not found. [root@Darwin] ~# tmux show-buffer root@Darwin] ~# camcontrol devlist <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 0 lun 0 (pass0,da0) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 1 lun 0 (pass1,da1) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 2 lun 0 (pass2,da2) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 3 lun 0 (pass3,da3) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 4 lun 0 (pass4,da4) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 5 lun 0 (da5,pass5) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 6 lun 0 (pass6,da6) <ATA WDC WD40EFRX-68W 0A82> at scbus0 target 7 lun 0 (pass7,da7) <Corsair CSSD-F90GB2 2.0> at scbus2 target 0 lun 0 (ada0,pass8)
The smart test for da5 returned the following message:
Code:
Device: /dev/da5 [SAT], Self-Test Log error count increased from 0 to 1
This naturally made me suspicious, but I thought I would run all the tests on the other drives before I RMA:ed it, so I started badblocks testing.
As I half expected da5 started showing ridiculous amounts of errors. The test has now been going on for about 120 houers (been running more tests than I have threads so I expect it to take a while) All WDRED drives except for da5 are so far without error which is pleasing. However, I also received the following output from FreeNas email smartservices (I think?)
http://pastebin.com/aSa6YFWf
Since I am abit of a novice on these things I have the following questions:
1. Is there any reason why da5 (and the bootdrive) have their devicename and their pass listed in reversed order? Does it mean anything of significance?
2. Does the pastbin output log indicate that the error could be outside the drive? (E.g the SAS-controller)? Seems unlikely since all the other drives seem to be working.