DanielCoffey

It sounds like you may have a use case for putting an Aquaero fan controller in your server. When I watercooled I had a temperature sensor on the intake air, another on the water and used the difference to dictate the speed of the fan groups. If the difference was under a certain amount, the radiator fans were shut down.

If you want to know more about the flash drive and backing it up, SpaceInvaderOne has a youtube channel and has covered that topic.

Works perfectly, thanks.

I have no idea why there is activity on the parity drive though. The array is idle, mover has completed and it is not doing any rebuilds. S3 Sleep does have "Wait for Array Inactivity (exclude Cache)" set as default. If the Spin Down state is unimportant, I suspect my question is why is Parity 1 holding the array active. Would it be better if I started a separate thread? EDIT : Forcing the drives to spin down causes the S3 Sleep plugin to correctly start counting down towards Sleep.

Does the S3 Sleep plugin require disks to be spun down in order to permit sleep? My array has Default Spin Down Delay - Never. Not sure when or why it was set to that but that is the current status. I have checked logging for the plugin and it certainly seems to be checking but keeps reporting disk activity on sdb (my Parity 1 drive). Oct 28 07:06:42 NAS-PLEX s3_sleep: Disk activity on going: sdb Oct 28 07:06:42 NAS-PLEX s3_sleep: Disk activity detected. Reset timers. Oct 28 07:07:42 NAS-PLEX s3_sleep: Disk activity on going: sdb Oct 28 07:07:42 NAS-PLEX s3_sleep: Disk activity detected. Reset timers. Oct 28 07:08:43 NAS-PLEX s3_sleep: Disk activity on going: sdb Oct 28 07:08:43 NAS-PLEX s3_sleep: Disk activity detected. Reset timers.

Thanks - checking it overnight.

I have changed the BIOS to default to PWM fans and it still has not exposed the PWM sensor to sensors-detect. Any suggestions?

Plugin : Dynamix S3 Sleep Version : 2018.02.04 My server (in signature) will not go to sleep with the S3 Sleep plugin installed so I would like to find if there are any logs giving clues to issues. Which folder and log file should I look in for sleep-related messages?

There we go - all resolved, thank you. Array is rebuilt and protected again. Just under 20h30 for a Rebuild and Parity pass of 8Tb. Regular Parity check comes in at between 17h40 and 18h20.

Cheers - I've set it to run in a few days time so the rebuild will complete first. I'll set it back to the normal schedule once I am protected.

Quick question... the Rebuild is progressing nicely but I have just remembered that there are files on the cache that were due to be moved to the array. The array will still be building when that next schedule falls due. Is the scheduled cron job for Mover suspended while the array is being rebuilt?

Got it, thanks. It is now doing the rebuild. Assuming all is well, I'll report back and update.

Which menu is the Rebuild on? When I looked on the Main page I saw that the Parity Check button had been replaced with the Read Check so I assumed that was where I had to start. I currently have Data 1 and Parity 1 emulated.

Thank you for the quick reply. I have re-seated all the SAS-SATA cables and Started the array. It came up without warnings so I started a Read Check. I got a green notification saying "Notice [NAS-PLEX] - array turned good. Array has 0 disks with read errors" and it is now starting a read check. On the assumption that it finishes properly, I will report back in a day and mark the thread as solved.

Hello folks - I was transferring three movie files from my desktop PC to my array when the transfer failed on the last file. I checked the unRAID Main page and saw that there were some errors displayed by the Notification tool. See picture below. I then tried to capture Diagnostics as requested but the process hung. I left it for 20 minutes but nothing was generated. I then looked at the Dashboard and saw the CPU pegged at 100% on all 4 cores. I clicked Stop Array and left it for another 10 minutes but nothing happened. I tried to Shut Down the array but nothing happened. The only option left was a Forced Shutdown from the power switch. I am aware this will probably have lost all the logs from the situation that caused the error. I took the server into the other room and attached a monitor and turned the server back on. The SAS card found all drives with no warnings. The unRAID command prompt appeared exactly as expected with no errors displayed so I looked at the Dashboard on my browser. The notifications about the errors were gone of course (with a new complaint that it could not see the UPS). Now I am aware that I had been disturbing the SAS-SATA leads during my recent rebuild but my concern now is how to check the HDDs for failure warnings and how to recover the data on the array. The current situation is that the array is stopped and has some files in the cache which I do have local copies of. Please can you advise on the health of the array and the steps I should take to check and recover it. My array is dual parity, 5 data, cache pool. All drives are under warranty. Thanks. nas-plex-diagnostics-20181026-0705.zip

Have a look at some of SpaceInvaderOne's youtube videos as he goes into how to set up a server and get the best out of dockers and VMs. Some of his videos are for earlier versions of unRAID but the gist of it should be the same. He loves his multi-core monsters too.

After my recent "magic smoke" incident, I have had to replace the power supply, motherboard, cpu and ram in my small NAS and unfortunately it appears that sensors-detect cannot spot any PWM fan sensors on the new motherboard. I would appreciate some help sorting this out if possible. Motherboard : ASUS ROG Strix H370-I Gaming On-board FAN Headers : CPU and Chassis Fan Header Mode : Auto (it offers PWM, DC, Auto) CPU Fan : 1x Noctua NF-F12 PWM Chassis Fan : 1x Noctua NF-S12A PWM, 2x NF-F12 PWM Firstly I have perl installed via the nerdpack. Dynamix System Temperature correctly shows coretemp and the cpu, mb and core temps. I have updated the motherboard BIOS. I can see the HDD temps and CPU temp in unRAID. I do not see any fan speeds I have captured the output of sensors-detect and attached it below. I will first try to change the fan header type to PWM in the BIOS but why can't sensors-detect spot anything? sensors-detect.txt

I have been enjoying my little NAS for the past four years and yesterday it unexpectedly died, losing a little of the "magic smoke" in the process. I noticed stuttering yesterday afternoon when my AppleTV requested a bluray which needed transcoding so I was investigating using the Plex Optimize feature when the connection to the server dropped. I went into the spare room and looked and the power light was off. There was an unwelcome "hot plastic" smell in the room. Flicking the power switch just resulted in a "ping" noise from the PSU. Ah well, time to open it up... Pulling ALL leads from the PSU and only attaching the 24-pin motherboard cable with that trick jumper you can get to fool it into thinking it is connected showed immediately that the PSU was dead. Each time it was switched on I just got the "ping" noise and no PSU fan movement. Fortunately it is still under warranty. I suspect an internal fuse is blown. Next I got out a spare PSU and tested it with the same cable and jumper... worked perfectly as expected. I plugged it into the motherboard via the 24-pin and aux power leads but left everything else off. Ping and shutdown. Unplugged the aux power lead and got a flick of fans for half a second before a ping and shutdown. I pulled the motherboard out and took off the CPU cooler. The TIM showed some suspicious brown at one edge. Evidence of high heat I wonder? No evidence of burning under the CPU however and a visual of the motherboard looks fine to me. Assuming the CPU has fried, I have no idea if the motherboard is OK or not as I don't have a spare processor to test it with. If the PSU was taken out too, I would not really be able to trust the motherboard any more. This is a bit of a shame as the CPU and motherboard are one full year out of their warranties. The PSU is still covered although at four years I would only expect a "return and repair" which is fair enough. Time to go shopping I think. Legacy Haswell stuff is too expensive for its age so it is time to enter the Century of the Fruitbat. Mini-ITX board, a small Coffee Lake CPU and some DDR4 RAM should do nicely. As it is simply a domestic NAS for serving movies to a single viewer, I don't feel ECC and a server board are really necessary. RIP Haswell i3.

I have a 9201-8i but my SSD drives are both on the motherboard SATA I am afraid (because I have 8 HDDs on the card). There does seem to be a lot of conflicting advice on whether it works or not.

I would still like to know what to look for to see why S3 Sleep is not performing as it used to. Any advice on what I should search for in the logs?

Hello bonienl - I am finding that while my server responds to the Sleep button on the UI, it is ignoring the S3 Sleep plugin when left idle. I am fairly sure I have enabled S3 Sleep in the BIOS but since the server is running headless it is not convenient to get a monitor on it. Is there a terminal command to check whether S3 Sleep is firing as expected and if any messages are returned indicating why it was prevented from sleeping? The server spec is as in my signature.

Lovely - went from 6.5.1 stable to 6.5.2 with no issues.

Phew - that was it... once I tried to access https:// I was in with the anticipated certificate warning. Huge thanks!

Hello folks - I have been using unRAID 6.5.1 for a while but have had to change my router from a Huawei HG612/ASUS RT-AC86U to the BT HomeHub 6 to troubleshoot some broadband speed issues. Since doing to I cannot access the unRAID web gui at all. I had previously assigned a fixed address to the server (192.168.1.202) but now it is under DHCP on the BT HomeHub6 and is (currently) 192.168.1.115. As soon as I enter 192.168.1.115 in the browser (Firefox), I get a long pause then it comes up with the error... "Server Not Found : We can’t connect to the server at 47451451017659140b69fc701f291711f8f06833.unraid.net." Any ideas what I am supposed to do in order to access the GUI again? I can't put my old router back on until my broadband speed issues are resolved in around a week.

Squid - it wasn't blacklisted - there was file corruption as bonienl suggested. I decided to rebuild on a new flash and will request a key transfer later. Looks like the blacklist error was just a symptom of my underlying corrupted flash.