danb35
Hall of Famer
- Joined
- Aug 16, 2011
- Messages
- 15,504
...while the more foolhardy among us do the update on a live FreeNAS system with the pool mounted.You don't strictly need to disconnect the drives, but the paranoid among us often do.
...while the more foolhardy among us do the update on a live FreeNAS system with the pool mounted.You don't strictly need to disconnect the drives, but the paranoid among us often do.
Apparently it's unreliable. It's on my list of things to check next month...P.S. There is already alerting ability built into FreeNas for Hard Drive Temps (not sure if you were aware of this)
Apparently it's unreliable. It's on my list of things to check next month...
Hmm.. Now I got to go get all paranoid... :PApparently it's unreliable. It's on my list of things to check next month...
Yeah, guess I should have mentioned that.Also it is only going to work at whatever the SMART polling frequency is.
Nope, just over cautious :) I run this script also to get a reminder in the morning with the current status, so I know when it's time to adjust the fan controller (in the summer for example). I always try to stay between 30-35 celsius :)Seems to me that you may have had more than one instance with overheating if you had to go that far.
Same goes for any alternative, since you can't get the temperature without getting all of -A's output. A separate script doesn't bring anything to the table (assuming FreeNAS' does work...), since you can set the frequency to whatever you want.Also it is only going to work at whatever the SMART polling frequency is.
Same goes for any alternative, since you can't get the temperature without getting all of -A's output. A separate script doesn't bring anything to the table (assuming FreeNAS' does work...), since you can set the frequency to whatever you want.
Apparently it's unreliable. It's on my list of things to check next month...
Supermicro has released now the 20.00.07.00-IT firmware.
See: ftp://ftp.supermicro.com/driver/SAS/LSI/2308/Firmware/IT/
I flashed my X10SL7-F's LSI controller to the new version 20.00.07.00 today. So far, so good.Thank you zoon. I guess I will wait some time and then gather some feedback from the community to see is someone flashed this version.... I dont want to be the first one to do it :D
I still am on 20.00.04.00I flashed my X10SL7-F's LSI controller to the new version 20.00.07.00 today. So far, so good.
EDIT: But to be honest, you can probably stay at version 20.00.04.00 and be just fine. I've been running my system with the older version forever, with no problems whatsoever. So go ahead, procrastinate! :)
Well, it's not really new, it's something like half a year old. It fixes a few weird edge cases, so it's definitely recommended for new flashes or if there are weird issues. I wouldn't bother updating from .04 if no issues are present, though.I flashed my X10SL7-F's LSI controller to the new version 20.00.07.00 today. So far, so good.
I flashed my X10SL7-F's LSI controller to the new version 20.00.07.00 today. So far, so good.
EDIT: But to be honest, you can probably stay at version 20.00.04.00 and be just fine. I've been running my system with the older version forever, with no problems whatsoever. So go ahead, procrastinate! :)
Yes, I got a PAL error when I first tried to run the DOS version on my X10SL7, so I've used a UEFI shell ever since.Yeah, maybe I will upgrade nex time I power down the NAS for the next cleaning :)
However, please allow me to ask you something. I remember that I've had a lot of troubles inserting the SAS address (the last 9 digit you're supposed to insert). What happened to me was that I couldn't type anything, and if I just typed enter, the system returned me a weird error. At this point it might be useful to mention that I run the UEFI version, not the DOS one. Anyways, I dont remember what I did, but I sort of remember that I edited the SMC2308T.NSH file, inserting "sas2flash.efi -o -sasaddhi 5003048xxxxxxxxx" (with the correct last 9 digits) instead of just "sas2flash.efi -o -sasaddhi 5003048". Is it possible that you found the same problem?
-sasaddhi
to -sasadd
to do this. They're slightly different: the first prompts you for the remaining SAS address digits, the second lets you specify the complete address. So, you want something like this:echo -off sas2flash.efi -o -e 7 sas2flash.efi -f 2308T207.ROM sas2flash.efi -b mptsas2.rom sas2flash.efi -b x64sas2.rom sas2flash.efi -o -sasadd 5003048xxxxxxxxx
You're welcome!Very well explained, thank you! One last thing, is it true that you could remove the "sas2flash.efi -b mptsas2.rom" line of code if using with FreeNAS?