search

dak180 / FreeNAS-Report

SMART & ZPool Status Report for FreeNAS/TrueNAS
GNU General Public License v3.0
38 stars 8 forks source link

Parse errors: bad token/bad expression #20

Closed TheSin- closed 1 year ago

TheSin- commented 1 year ago

These seem to be sed/awk errors, and I noticed on the report all my SSD drives are missing a value in the report (Load Unload Cycles) as well as I see this on each one

scsiPrintBackgroundResults Failed [scsi response fails sanity test]

I haven't dug in to find the line yet, thought I'd make a report first.

This repeats 8 times, which is how many Micron_5 SSD drives I have not including the 1 WDC SSD for a pool log

 ./report.sh -c report.cfg

Parse error: bad token
    <stdin>:1

Parse error: bad expression
    <stdin>:1

Parse error: bad expression
    <stdin>:1

Parse error: bad expression
    <stdin>:1

on a separate note, my boot flash drive on my TrueNAS X10 gives me a critical temp (40C) maybe that one needs to be able to run hotter then the others?

dak180 commented 1 year ago

Run ./report.sh -dc report.cfg and send me the dump file it emails you; I will have to take a look at what those drives output for smart data.

dak180 commented 1 year ago

@TheSin- just to make sure, self tests are set to run; both short and long?

dak180 commented 1 year ago

on a separate note, my boot flash drive on my TrueNAS X10 gives me a critical temp (40C) maybe that one needs to be able to run hotter then the others?

SSDs in general can have a separate temp warning level set for them from HDDs since they generally have different characteristics. Depending on the SSD 40C may not be unreasonable.

dak180 commented 1 year ago

Fixed in e86c4a55966b4dec7e0e3a6af210ac893d5d6108.