J-NAS
Dabbler
- Joined
- Oct 27, 2014
- Messages
- 42
OK, please go easy on me as this is my first post! I've been reading up on FreeNAS for about a month now--probably longer. I've read all the setup guides, watched the PP presentation (a few times actually) and went with hardware strictly off the "recommended" list. I've read the burn-in threads with great interest and have a game-plan I'm implementing.
I completed the build (actually used an anti-static strap as suggested) and ran 12 hours of memtest with ECC off, and 12 with it on. That got me...3 passes each? No errors.
Moved on to the drives. I'm running the SMART commands from the Shell from within FreeNAS. The conveyance test doesn't appear to work on HGST drives, but that seems to be the expected result after re-searching these forums.
All drives passed the short SMART test. I've begun testing with the long SMART test and I'm collecting my results in an excel sheet for future reference. I'm only four drives in, but I'd like feedback on two things that have happened:
a) I've been testing the drives with
I waited the 10 hours requested to print results with
The first drive I tested returned a value very different from the next two drives for SEEK TIME PERFORMANCE. ADA0 returned "0", while the next two drives were "32" and "33". My google-fu only reveals that if this number drops, I should be concerned.
Can someone elaborate as to why my drive would read 0? From what I've read, 33 is also very low...
b) I awoke this morning to find that my shell window in FreeNAS was glitched out, showing two screens stacked on top of one another, with a GUI "login" prompt. I was unable to login, as the screen wasn't actually accepting input. Not sure if this was some overlay issue or why I'd been "logged out". I had to close my FreeNAS browser window and login again to re-launch the shell.
I ran and although it looks the test completed in the summary, START/STOP COUNT and POWER CYCLE COUNT are "2", while the preceding drives all read "3". All the drives were connected and powered on in unison for each session. They should be identical.
I don't understand this discrepancy and whether I should pay it any mind.
If the drives clear a long SMART test I will move on to a run of dd, and then badblocks and then a final pass of SMART to see if anything has changed.
I am an adult, capable of following directions, and more than willing to put in the legwork required to get this up and running. If there is a resource which directly addresses what I'm seeing then I've missed it, and will gladly go back to do my homework if you'd be so kind as to point me in the correct direction.
I could never have gotten this far without following the wonderful guides provided on the background of FreeNAS, the underpinnings of ZFS, and how to properly create safe Pools. Quite interesting how an entire pool can be brought down by a single drive failure with the wrong collection of vdevs! Anyhow, I believe I have followed best practices to this point and hope to continue.
Would love to hear your thoughts--should I rerun a SMART long on ADA0 and see if I get a different result? I was initially using but that only provided me with the briefest of summaries. My own research is what lead me to use
I hope that's correct...
Thanks!
edit(s): figured out how to format code, and added hardware to .sig
I completed the build (actually used an anti-static strap as suggested) and ran 12 hours of memtest with ECC off, and 12 with it on. That got me...3 passes each? No errors.
Moved on to the drives. I'm running the SMART commands from the Shell from within FreeNAS. The conveyance test doesn't appear to work on HGST drives, but that seems to be the expected result after re-searching these forums.
All drives passed the short SMART test. I've begun testing with the long SMART test and I'm collecting my results in an excel sheet for future reference. I'm only four drives in, but I'd like feedback on two things that have happened:
a) I've been testing the drives with
Code:
smartctl -t long /dev/adaX
I waited the 10 hours requested to print results with
Code:
smartctl -a /dev/adaX
The first drive I tested returned a value very different from the next two drives for SEEK TIME PERFORMANCE. ADA0 returned "0", while the next two drives were "32" and "33". My google-fu only reveals that if this number drops, I should be concerned.
Can someone elaborate as to why my drive would read 0? From what I've read, 33 is also very low...
b) I awoke this morning to find that my shell window in FreeNAS was glitched out, showing two screens stacked on top of one another, with a GUI "login" prompt. I was unable to login, as the screen wasn't actually accepting input. Not sure if this was some overlay issue or why I'd been "logged out". I had to close my FreeNAS browser window and login again to re-launch the shell.
I ran
Code:
smartctl -a /dev/ada3
I don't understand this discrepancy and whether I should pay it any mind.
If the drives clear a long SMART test I will move on to a run of dd, and then badblocks and then a final pass of SMART to see if anything has changed.
I am an adult, capable of following directions, and more than willing to put in the legwork required to get this up and running. If there is a resource which directly addresses what I'm seeing then I've missed it, and will gladly go back to do my homework if you'd be so kind as to point me in the correct direction.
I could never have gotten this far without following the wonderful guides provided on the background of FreeNAS, the underpinnings of ZFS, and how to properly create safe Pools. Quite interesting how an entire pool can be brought down by a single drive failure with the wrong collection of vdevs! Anyhow, I believe I have followed best practices to this point and hope to continue.
Would love to hear your thoughts--should I rerun a SMART long on ADA0 and see if I get a different result? I was initially using
Code:
smartctl -l xselftest /dev/adaX
Code:
smartctl -a /dev/adaX
I hope that's correct...
Thanks!
edit(s): figured out how to format code, and added hardware to .sig
Last edited: