solnet-array-test on FreeNAS-9.10

[Omega]

Hi,

Currently burning in my first FreeNAS build(*) and ran into a trivial OCD itch using @jgreco's solnet-array-test-v2 script (many thanks for providing this!). It wouldn't properly determine the disk size. 'Not fatal but odd!'; I simply adjusted the egrep in line 55 from

Code:

egrep "^${1}:.* byte sectors: .*"

to

Code:

egrep "^${1}:.*byte sectors.*"

Now running fine and satisfying the OCD itch :) Not sure whether that is a new problem, but my guess is that the log format changed in the newer OS version, afaict the changed pattern should still work for in the previous case (untested).

Thought I'd mention this since with 9.10 getting closer more people might hit this. Wasn't quite sure where to post, so happy if this is moved to wherever it is better placed; and apologies if that is already known, a forum search didn't yield anything.


(*) Xeon E3-1231, X10SL7-F, 32GB ECC from compatibility list, 500W Seasonic, 4 x WD Red 6TB (to be main pool, planning for mirror vdevs, might extend to 6x or 8x when the need arises), 2x500GB 850EVO (jails), 1x120GB 850EVO (boot - overkill, but didn't bother trying to find something smaller), 2U XCase RM 208 Pro

 

[jgreco]

It's certainly possible that the log format changed. For hopefully-obvious reasons, it's always best to try to keep regex patterns fairly tight. Is there any chance you could post a copy of the input in question, preferably in CODE tags?

 

[Omega]

Ah, sure:

Code:

[root@freenas] ~# egrep "byte sectors" < /var/run/dmesg.boot 
ada0: 114473MB (234441648 512 byte sectors)
da1: 5723166MB (11721045168 512 byte sectors)
da3: 5723166MB (11721045168 512 byte sectors)
da0: 5723166MB (11721045168 512 byte sectors)
da2: 5723166MB (11721045168 512 byte sectors)

There appears to be no colon after sectors any more (judging from the original regex).

 

[jgreco]

Okay, so they ditched the C/H/S description. In that case, it would be appropriate to eliminate the colon-space after "byte sectors".

 

[Omega]

True, not necessary to eliminate the space before 'byte' as well as I did.