schneeb Posted February 9, 2019 Share Posted February 9, 2019 (edited) I recently installed unraid with some older hardware, having it setup with just 3 disk to begin with before migrating data, now that the data is migrated it is now populated with 5 disks and I've also added a cache device. Once I moved my dockers to live on the cache, the disks will all spin down as expected apart from the parity drive which will stay active; if you manually request it to spindown it will do so and remain spun down until the other disks are active again but once again the parity will be left up after the others spin back down! Is this intended? Is there a setting i've missed somewhere? *edit* solved thankyou all! Edited February 9, 2019 by schneeb Quote Link to comment
trurl Posted February 9, 2019 Share Posted February 9, 2019 3 hours ago, schneeb said: Is there a setting i've missed somewhere? Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 attached! batcave-diagnostics-20190209-1230.zip Quote Link to comment
trurl Posted February 9, 2019 Share Posted February 9, 2019 Your domains share is set to cache-only but it has files on the array. Disable VM Manager then set it to cache-prefer and run mover. Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 whoops! will do and confirm spindown shortly! Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 no joy, same symptom; disk 1 & 3 spun down but parity still active! Quote Link to comment
trurl Posted February 9, 2019 Share Posted February 9, 2019 Are you sure you don't have anything writing to the array? There is a Write column on the Main page. Do you have Turbo Write enabled? Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 The data disks all spindown so that should mean nothing is using the array no? I assume nothing uses just the parity drive? I cleared the disk stats and the data drives spun down again after 0 read/writes to any of the HDDs. I'm not sure what Turbo Write is? I've disabled the folder caching plugin encase that is the culprit! Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 Nope same thing, disks all spun down but parity drive up with 0's on the stats: Quote Link to comment
bonienl Posted February 9, 2019 Share Posted February 9, 2019 Click on "Parity" and check the setting for "Spin down delay". 1 Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 oooooh - doh didnt realise you can set drives individually; was set to never! thanks for the advice. Quote Link to comment
trurl Posted February 9, 2019 Share Posted February 9, 2019 1 hour ago, bonienl said: Click on "Parity" and check the setting for "Spin down delay". "Never" isn't the default, but I just noticed I had that on one drive, a drive that I had previously run an Extended SMART test on. Does it get changed to Never and not changed back on a SMART test? 1 Quote Link to comment
bonienl Posted February 9, 2019 Share Posted February 9, 2019 22 minutes ago, trurl said: "Never" isn't the default, but I just noticed I had that on one drive, a drive that I had previously run an Extended SMART test on. Does it get changed to Never and not changed back on a SMART test? Yes, when a extended smart test is started, the spindown time for that disk is disabled, it should be restored to the previous setting when the test is finished/cancelled. 1 Quote Link to comment
schneeb Posted February 9, 2019 Author Share Posted February 9, 2019 5 hours ago, bonienl said: Yes, when a extended smart test is started, the spindown time for that disk is disabled, it should be restored to the previous setting when the test is finished/cancelled. I think I had a power cut during an extended smart test once so that could explain it! Quote Link to comment
sonisame Posted February 10, 2023 Share Posted February 10, 2023 I have same issue, very minimal system(running a few windows11 VM) and no shares, and one docker(sabnzbd) which is mostly off. Parity disk keeps spinning(and writing) when VMs are on. Please help Thanks Attaching the logs samsvm-diagnostics-20230210-1430.zip Quote Link to comment
itimpi Posted February 10, 2023 Share Posted February 10, 2023 It 56 minutes ago, sonisame said: I have same issue, very minimal system(running a few windows11 VM) and no shares, and one docker(sabnzbd) which is mostly off. Parity disk keeps spinning(and writing) when VMs are on. Please help Thanks Attaching the logs samsvm-diagnostics-20230210-1430.zip 137.55 kB · 0 downloads I suspect that your issue is due to the fact that all the shares relating to docker and V/ms which you normally want only on the cache for performance have Use Cache=Yes set. That means you want mover to transfer the files from ca he to array if it can, and if you have files on the array then any writes to them will cause the parity dtive to be Aldo updated. BTW: the release of Unraid you are running (6.11.) has a bug so that we cannot see all the information about your shares - you should consider upgrading to the 6.12.5 release which is the current Stable version. 1 Quote Link to comment
trurl Posted February 11, 2023 Share Posted February 11, 2023 2 hours ago, itimpi said: 6.11.5 release FTFY You can see how much of each disk is used by each user share by clicking Compute... for the share, or Compute All, on the User Shares page. Simplest is to have all the default shares on a fast pool (cache) and not on the array. https://wiki.unraid.net/Manual/Shares#Default_Shares That way your Dockers and VMs will perform better, and won't keep array disks spunup since these files are always open. To get these moved off the array, they must be set cache:prefer. Also, nothing can move open files, so you have to disable Docker and VM Manager in Settings so Mover can move these. 1 Quote Link to comment
sonisame Posted February 11, 2023 Share Posted February 11, 2023 Thanks Guys So what I understand! 1) All NVME drives should be part of cache pool, not main data array(spinning drives) 2) All dockers/VM stopped or docker/VM Manager turned off 3) Move the docker data and VM images to cache pool 4) Restart the dockers/VM Manager, and point to new locations of image files in gui and set to cache:prefer 5) Recheck parity with those NVME drives moved to cache pool( I guess I will have to rewrite config with those NVME removed). Please correct me if I missed a step. Does this mean my windows VM images are always NOT parity protected(I guess can always reinstall windows/ubuntu if NVME fails). Sam Quote Link to comment
trurl Posted February 11, 2023 Share Posted February 11, 2023 5 minutes ago, sonisame said: All dockers/VM stopped or docker/VM Manager turned off Just stopping them all isn't enough, must disable the services. 6 minutes ago, sonisame said: point to new locations Shouldn't need to since these are part of user shares 1 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.