*

[hugovsky]

 

[Bidule0hm]

Oh god, this is insane :D

But there's more room in the top, you should fill this empty space with more drives (you don't have enough drives I think...) :P

 

[TinTIn]

[emoji28]


Sent from my iPhone using Tapatalk

 

[jgreco]

It's scary, the amount of storage we can cram into half a rack.

 

[TinTIn]

Anyone know a quick way I can run a SMART test on all these drives to check they're ok?


Sent from my iPhone using Tapatalk

 

[Darren Myers]

For my 21 drives i just had a crap ton of putty windows open running 4 tests per window using https://forums.freenas.org/index.php?threads/how-to-hard-drive-burn-in-testing.21451/

Specifically the tmux and

1. badblocks -ws /dev/adaX

After 4 passes on each drive, i also ran:

1. smartctl -t long /dev/adaX

 

[danb35]

A simple script should do it. Best would be if there were a command to list the device identifiers of all the disks, which I'm sure there is, but I don't know it. But this should be a start:

Code:

#!/bin/bash
for disk in {0..75}
do
smartctl -t long /dev/da$disk
done

Obviously you'd change the number range to match whatever disks you have, and this assumes they're all /dev/da(something).

 

[Bidule0hm]

I think you should make a script with a for loop like this:

Code:

#!/bin/sh

drives=`sysctl -n kern.disks | awk '{for (i=NF; i!=0 ; i--) print $i }'`

for drive in $drives
do
    smartctl -t long /dev/${drive}
done

 

[danb35]

Like I said, I figured there would be a command (or series of commands) to list the identifiers of all installed disks... One of these days I really need to learn a bit about awk...

Actually, do you really need the awk command? The sysctl command appears to list all the disks, and the order shouldn't matter to this application. You could probably simplify to

Code:

for drive in `sysctl -n kern.disks`

...or am I missing something?

 

[Apollo]

I only see what seems to be 72 active disks and 12 unoccupied bay or spares. Is this intended?

 

[Bidule0hm]

Like I said, I figured there would be a command (or series of commands) to list the identifiers of all installed disks... One of these days I really need to learn a bit about awk...

Actually, do you really need the awk command? The sysctl command appears to list all the disks, and the order shouldn't matter to this application. You could probably simplify to

Code:

for drive in `sysctl -n kern.disks`

...or am I missing something?

Yep, we've replied at the same time :)

Yes, you can omit the awk part. It's just that I copy-pasted it from my scripts thread ;)

 

[TinTIn]

Disks at the back of the JBODs too.


Sent from my iPhone using Tapatalk

 

[jgreco]

Like I said, I figured there would be a command (or series of commands) to list the identifiers of all installed disks... One of these days I really need to learn a bit about awk...

Actually, do you really need the awk command? The sysctl command appears to list all the disks, and the order shouldn't matter to this application. You could probably simplify to

Code:

for drive in `sysctl -n kern.disks`

...or am I missing something?

Yeah, that this could encompass the boot device and other resources like SLOG or L2ARC. There's a reason that the array test script provides a few different options to target drives.

 

[danb35]

Sure, but does the awk expression do anything to avoid that? It didn't seem to on my system. All it did was (1) break out each listing to a new line, and (2) reverse the order.

 

[Bidule0hm]

No, it's a very basic script. The smartctl command will just fail to start the test on the drives that doesn't support it, not a big problem. Of course you can add a test to avoid that but I'll let that as a reader exercise :p

 

[TinTIn]

Anyone know much about smartctl 'non-medium error count'? I'm getting figures like 17, 19, 21 on the drives after running short smart tests however all other info looks good and health status is ok.


Sent from my iPhone using Tapatalk

 

[TinTIn]

Thanks for all the help, advice and support.


Sent from my iPhone using Tapatalk

 

[TinTIn]

Anyone got any thoughts on using this to burn-in and test the drives. Create a zpool share it out and run for a day?

http://www.attotech.com/disk-benchmark/

Thanks

 

[cyberjock]

Not a chance I'd ever recommend that. I've seen a lot of people use it for benchmarks, and it is pretty poor at providing good benchmarks too.

 

[cyberjock]

Honestly, I find that the best "benchmark" is to use the FreeNAS machine exactly how you intend to use it. If you plan to copy large files on and off the server, then do exactly that.
Of course, if you are looking for things like raw zpool speed, you'll have to do local stuff like dd. Those are generally what I would consider "synthetic" as you are somewhat cheating by doing things locally. dd does give you a "general" feel for how good/bad your zpool is performing. Other things like iperf can help with network testing.