feins Posted September 29, 2022 Share Posted September 29, 2022 Like to know what might be the issue and how should i resolve it as i notice always one of my Drive wont spin down. Also does Parity usually spindown by itself as i ntoice my Parity is always up aswell. Â ts-p500-diagnostics-20220929-1244.zip Quote Link to comment
JorgeB Posted September 29, 2022 Share Posted September 29, 2022 Diags are not showing, so go to shares click on compute all and post a screenshot of the results. Quote Link to comment
feins Posted September 30, 2022 Author Share Posted September 30, 2022 19 hours ago, JorgeB said: Diags are not showing, so go to shares click on compute all and post a screenshot of the results. Quote Link to comment
SimonF Posted September 30, 2022 Share Posted September 30, 2022 2 hours ago, feins said: Have a look at the files in the system share as you have 44Gb on disk 4 what is that data. 1 Quote Link to comment
itimpi Posted September 30, 2022 Share Posted September 30, 2022 Your ‘system’ share seems to have content on disk4.  If this is the docker.img or libvirt.img giles then simply having the docker or VM services running respectively will keep this drive spinning as the services keep their respective files open..   Any writes to this drive would then also keep the parity disk spinning. 1 Quote Link to comment
Solution ChatNoir Posted September 30, 2022 Solution Share Posted September 30, 2022 The probable cause is the system share. It is set to 'Prefer' but Mover cannot move open files and will not remplace a file already present on the destination. As said by SimonF, look at the content of the share on both locations. I would guess that the part on cache is either empty or outdated and that the part being used is on Disk4. Â The stop Docker and VM from the Setting page and run the mover again. You should be good once this share is only on cache. 1 Quote Link to comment
feins Posted September 30, 2022 Author Share Posted September 30, 2022 2 hours ago, ChatNoir said: The probable cause is the system share. It is set to 'Prefer' but Mover cannot move open files and will not remplace a file already present on the destination. As said by SimonF, look at the content of the share on both locations. I would guess that the part on cache is either empty or outdated and that the part being used is on Disk4. Â The stop Docker and VM from the Setting page and run the mover again. You should be good once this share is only on cache. Ive just stop docker and VM and perform mover and see how's thing going. Will update as 44GB take sometime to move. Quote Link to comment
feins Posted September 30, 2022 Author Share Posted September 30, 2022 2 hours ago, SimonF said: Have a look at the files in the system share as you have 44Gb on disk 4 what is that data. i've just check its the docker.img and libvirt.img just donno how it turns up on the Disk its been like for months. 1 Quote Link to comment
Squid Posted September 30, 2022 Share Posted September 30, 2022 2 hours ago, feins said: i've just check its the docker.img and libvirt.img just donno how it turns up on the Disk its been like for months. If you started the array without a cache drive, then the OS would have automatically placed those 2 files onto the array. 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.