Have you checked out my update for it?
I deleted my last post, because it wasn't based on the current version of @dak180's script. If you use the script in the
topic/refactor branch, you need to specify a config file, like this: ./report.sh -c report.cfg. Since that file doesn't yet exist, the script will create it. You'll then need to edit report.cfg, set defaultConfig to 0 (to tell the script this isn't just a default file), enter your email address, and make any other desired changes. Then you can run the script with ./report.sh -c report.cfg, and you'll get the report.
That is on my list of things to do when I get a few free moments.
One major reason not to do that yet is that I have not really gotten any feedback or testing from anyone besides myself; so any thoughts or issues you or anyone else has would be very useful.
Multi-Report v1.4a
nas0sstp# ./multi_report_v1.4a.sh
Failed conversion of ``28-on-Tue_Dec'' using format ``%Y-%b-%e_%H:%M:%S''
date: illegal time format
usage: date [-jnRu] [-d dst] [-r seconds|file] [-t west] [-v[+|-]val[ymwdHMS]]
[-I[date | hours | minutes | seconds]]
[-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format]
nas0sstp# date
Tue Dec 28 21:09:23 EET 2021
nas0sstp#
root@nas2sstp[~]# ./multi_report_v1.4a.sh sysctl: cannot stat /proc/sys/kern/disks: No such file or directory date: invalid option -- 'j' Try 'date --help' for more information. date: invalid option -- 'j' Try 'date --help' for more information. sed: can't read : No such file or directory sed: can't read : No such file or directory sed: can't read : No such file or directory sed: can't read : No such file or directory sed: can't read : No such file or directory sed: can't read : No such file or directory root@nas2sstp[~]# root@nas2sstp[~]# date Tue Dec 28 21:32:01 EET 2021 root@nas2sstp[~]#
Yes indeed.
Dan,
root@scalenas[/mnt/ScratchSSD/SMB/Scale-Scripts]# smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/sdb -d scsi # /dev/sdb, SCSI device
/dev/sdc -d scsi # /dev/sdc, SCSI device
/dev/sdd -d scsi # /dev/sdd, SCSI device
/dev/sde -d scsi # /dev/sde, SCSI device
/dev/sdf -d scsi # /dev/sdf, SCSI device **SAS
/dev/sdg -d scsi # /dev/sdg, SCSI device **SMART Fail
/dev/sdh -d scsi # /dev/sdh, SCSI device
/dev/sdi -d scsi # /dev/sdi, SCSI device
/dev/sdj -d scsi # /dev/sdj, SCSI device **SMART Fail
/dev/sdk -d scsi # /dev/sdk, SCSI device
/dev/sdl -d scsi # /dev/sdl, SCSI device
/dev/sdm -d scsi # /dev/sdm, SCSI device
/dev/sdn -d scsi # /dev/sdn, SCSI device
/dev/sdo -d scsi # /dev/sdo, SCSI device
/dev/sdp -d scsi # /dev/sdp, SCSI device
/dev/sdq -d scsi # /dev/sdq, SCSI device
That is the built in SMART to the drive. I can't fix that, it's not the script, or I could restructure the script with a new column that is titled "Overall Results" for each drive. While I like to have all the data available at a glance, too much data is busy. I could change PASSED to red background as well. That is why I like the email Subject line with tells you all is good or something is wrong and you need to look at the data closer.
Same as the previous answer, this value comes from the smartctl command results, not a judgement on my part, except for the Critical Error message is defined by the other items (tempCrit, sectorsCrit, and crcErrors). What caused this was the UDMA CRC Errors for any one of the three drives that have these errors. You could zero these out in the script.
You are correct, I can see improvement by scanning the short/extended results and if they contain the word "failure" then I could mark the Last Test Type as RED so a user could go locate the actual error message. It's funny because you have MultiZone errors for these two drives which are likely a result of the read failures. I could include these values as well but unfortunately not all MultiZone failures cause this problem.
I'd love to fix this but unfortunately I do not have any SAS disks so I cannot recreate this situation. Maybe you could fin out the proper command to list this SAS disk and include it into the inventory? Looking at the script, about line 148 you will see this text:
# Get Hard Drive listing - MUST support SMART
# variable smartdrives
if [ $softver != "Linux" ]; then
smartdrives=$(for drive in $(sysctl -n kern.disks); do
if [ "$(smartctl -i /dev/"${drive}" | grep "SMART support is: Enabled")" ] && ! [ "$(smartctl -i /dev/"${drive}" | grep "Solid State Device")" ]; then
printf "%s " "${drive}"
fi
done | awk '{for (i=NF; i!=0 ; i--) print $i }')
else
smartdrives=$(for drive in $(fdisk -l | grep "Disk /dev/sd" | cut -c 11-13 | tr '\n' ' '); do
if [ "$(smartctl -i /dev/"${drive}" | grep "SMART support is: Enabled")" ] && ! [ "$(smartctl -i /dev/"${drive}" | grep "Solid State Device")" ]; then
printf "%s " "${drive}"
fi
done | awk '{for (i=NF; i!=0 ; i--) print $i }')
fi
I'll bet it is nice having a bunch or ratty old disks. Makes testing more inclusive.
That is okay, it's a test system. All I really need is for you to get to the shell and issue the command
fdisk -l | grep "Disk /dev/sd" and if this does not show the SAS drive, then just issue the command fdisk -l and see if that shows it. I would imagine the first command would be fine since the drive was identified as "sdf" when you ran the smartctl --scan command."
