highgear

After I upgraded from 6.8.0 to 6.8.1 through the update plugin, my server hung while booting. I was unable to access the webgui and couldn't connect via telnet. I had to hard power down the server. I then pulled the USB stick and reverted to 6.8.0 by copying the previous folder into the main. I don't have an easy way to connect to a monitor so I'm unsure what was going on. Seems like others are having similar issues though?

Thanks for the detailed write up! Worked great on my Supermicro X11SSL-CF. No more cycling issues since. I used 20% less than my fan's lowest rated speed for the Lower Non-critical (rounded to nearest 100), then subtracted 100 from that for the second number, then subtracted another 100 from that for first number (Lower Non-Recoverable threshold. This method was mentioned in the linked thread on the freenas forums. Also, here is a direct link to the file needed: https://github.com/dmacias72/unRAID_6.0/releases/download/2015.03.22/ipmitool-1.8.13-x86_64-1_fs.tgz

Ok I'm ordering a new power supply but I'm going to hold out on buying new RAM at this point. There have been no more errors from memtest86, I ran it through 4 cycles each using one stick only in each slot.

Will do. Yeah it seems like PS or RAM are the most common causes for this type of problem. I still don't understand how/why the system would boot back up if it were either of these issues instead of just turning off. So even with the one memtest error you still think it could be the PS? RAM would certainly be the easiest thing to replace in this scenario...

Ok I visually inspected the mobo and I'm not seeing any issues. I'm now running a memtest86 cycle with just one stick of RAM. Just so you know I ran another set of memtest86 tests with both sticks in earlier and no errors came up.

Thanks for the response. I'll do a visual inspection and report back. So are you suggesting running Memtest86 with just one stick or what?

Hello all, I've been running my unRAID server for 4 years or so now with basically no issues. A few months ago, I noticed that it had seemingly randomly shut down (unclean) and was doing an unscheduled parity check. This has since happened 5 or 6 times with increasing frequency. I am running it with an APC UPS but I also know the power has not been turning off at the house during these times. The most recent times it has happened anywhere from 5-7 days apart. I just checked my bios and the "turn back on after power interruption" feature is turned OFF. I'm unsure why/how the server is turning itself back on after it goes down. It is at least going down according to unRAID, since the uptime counter always resets at these occurrences. Recently, I installed Fix Common Problems and ran Troubleshooting mode. I have attached those files but I am unable to see anything obvious in them but maybe you'll have more luck. I also ran Memtest86 overnight which did produce one error. Through my research it seems this error is unlikely to cause issues, but let me know if that is inaccurate. It failed 1/4 of test #13, the Hammer test, resulting in one error. Nothing has been recently changed hardware wise with the server to coincide with these issues. As far as dockers, I'm just running Sab, Transmission, Couchpotato, Sonarr, and Roon. I began running Roon not too long ago but I do not believe it coincides with these issues starting, but I could be wrong. My hardware is: ASRock FM2A85X-ITX AMD A6-5400K PC Power and Cooling Silencer MKIII 400 watt PS - PPCMK3S400 Kingston 4GB RAM x 2 - KHX1600C9D3 A number of 8tb and 3tb HD's. I am concerned about these random shutdowns because I obviously don't want to end up losing any data. This current build is getting a little old/underpowered so if the best course of action is to just toss the mobo/processor/RAM/power supply and upgrade I'm willing to do that. If it's just a minor issue that is easily fixed I'd go with that option if possible. Any thoughts on what may be causing this issue? Thanks in advance, I appreciate it! syslog.txt FCPsyslog_tail.txt MemTest86-Report-20170928-042059.html

Ha I didn't think it would work but figured I'd check. Also, there is no way to run trim commands unless the drive is formatted as ext4 right?

Thanks for the well written tutorial jumperalex! I had a quick question though. Since this drive is setup out of the array, can it be used just like a cache drive would? Right now I have a SSD setup as my cache/apps drive. I am considering doing this so that I can get the TRIM functionality. I know that in this use it is solely being used as a permanent apps drive. Can it also function as a cache drive for my server as well? If so, how would this be accomplished? Thanks!