Barry Rimmer Posted October 8, 2019 Share Posted October 8, 2019 Hi, thanks for reading I have just moved my config into a server with room for more disks, and added a parity drive. before I added the parity drive, most of the disks would spin down and only active disks would spin up, now, all of my disks are permanently spun up, and if I hit the spin down button they spin straight back up, the majority of the disks are empty and so there is no need for them to be spinning all the time Any help you can provide will be hugely welcome :-) Quote Link to comment
trurl Posted October 8, 2019 Share Posted October 8, 2019 Go to Tools-diagnostics and attach the complete Diagnostics zip file to your next post Quote Link to comment
Barry Rimmer Posted October 8, 2019 Author Share Posted October 8, 2019 I have tried, but each time I do I get the attached error, the file is 178mb, could that be why? Quote Link to comment
Barry Rimmer Posted October 8, 2019 Author Share Posted October 8, 2019 Redownloaded and it was smaller plex-diagnostics-20191008-1724.zip Quote Link to comment
Gragorg Posted October 8, 2019 Share Posted October 8, 2019 Are you running plex and other dockers on a cache drive or are they stored on the array? Quote Link to comment
trurl Posted October 8, 2019 Share Posted October 8, 2019 Your appdata, domains, and system shares have data on the array. Ideally those shares would only have data on cache so docker and VMs would not keep disks spinning and so docker and VM performance would not be impacted by slower parity writes. Do you actually have any VMs? Doesn't look like it since there is no libvirt image mounted. Quote Link to comment
trurl Posted October 8, 2019 Share Posted October 8, 2019 Go to Settings - Docker, Disable then Delete docker image. Set your domains and system share to cache-prefer. Run mover and wait for it to complete. Post a new diagnostic. Quote Link to comment
trurl Posted October 8, 2019 Share Posted October 8, 2019 What is the purpose of the user shares anonymized as 'H--s' and 'P--X'? They are cache-only but have files on the array. Quote Link to comment
trurl Posted October 8, 2019 Share Posted October 8, 2019 Is your SAS controller configured for non-RAID operation? It isn't passing SMART reports or disk serial numbers so it isn't providing enough information to allow Unraid to detect disk problems. Quote Link to comment
trurl Posted October 9, 2019 Share Posted October 9, 2019 Probably should have posted this link: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383 Quote Link to comment
adgilcan Posted March 6, 2020 Share Posted March 6, 2020 (edited) Hi trurl Thanks so much for helping the OP in this. I have a similar problem in that one of my disks will not stay spun down. I recently replaced the drive as it was beginning to fail (possibly because of being in a permanently energised state?). I have checked the files on the drive and stopped the Nextcloud docker in case that was the cause. There are no shares that should be on the cache drive, to my knowledge, and only download data from dockers such as Radarr, Sonarr and NZBGet amongst other private data shares. Something is causing the disk to spin up. If I manually spin all disks down and leave the server completely alone, disk 5 and the two parity disks will automatically spin up again within 10 minutes. I am not an expert in this by any means but I have tried to keep all appdata, domains and system files on the cache pool drives only, so I am at a bit of a loss. I attach the system diagnostics log. Hoping for an expert eye to pick up the problem Many thanks D tower-diagnostics-20200306-0530.zip Edited March 6, 2020 by adgilcan rearrange images Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.