March 29, 20242 yr My Server was running flawless since the Update to 6.12.6 but today i decided to optimize my power use and "disk usage". But after my "optimization" my VMs were gone, Docker service couldnt start and after a system reboot Unraid started to do some Parity checks with 5MB/s. At first i installed powertop and tried to autotune my system. In the next step I found that part of my System share was on a HDD (libvirt), so in the next step disabled the secondary storage. As Unriad wasnt moving the libvirt.img I manually moved it to the cache drive. After activating the VM Service my VM was gone, I remapped the libvirt file and made a new VM as it was a relativ new system without any special purpose. Then I manually Moved some Directories as one of my HDDs got 100% and activated the Mover afterward because my Cache Drive had 300GB "too much" on it, despite running every day. (Probably because the one drive it wanted to move was full?) In the next step I changed the Spin down time to check if my steps so far worked and was happy to see that all drive spun down after 15min. So I finally activated docker Service, as I was finished for today and got greeted by a "Docker service failed to start". After the initial F*CK Moment passed, I restarted the server and found that my Server started a Parity-Check at a whopping 5-7MB/s. What can I do if my speed isnt rising over the night and why did it come to this in the first place? Thanks in advacne! _Promi nimbus-diagnostics-20240329-2038.zip
March 30, 20242 yr Community Expert There's appears to be something reading from disk3, stop the docker service and re-test.
March 30, 20242 yr Author So first things first, During the night the the Speed increase to normal values. Sadly I don´t understand what I should re-test, can you please clarify? Right now some of my Dockers and the VM Service is running, and My Disks spun down after the Parity Check is only running on my Parity Drives now.
March 31, 20242 yr Community Expert Could have been a device issue, or something was accessing a disk, if it happens again On 3/30/2024 at 8:58 AM, JorgeB said: stop the docker service and re-test.
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.