January 25, 20233 yr Hello! Well the title says it all. I am having a very very peculiar issue where usually overnight but also sometimes throughout the day, something is continually reading and writing to the array (usually Disk2). Now this is sometimes a "common" problem with unraid. The part that is thrown me for a curve is that it is ALSO reading and writing an equivalent amount of data to the parity drive. No errors being corrected that I can see. 1) I have tried restarting docker which I thought fixed the problem for a couple days... but then it came back. 2) iotop was not useful given the intermittent issue 3) I tried disabling party check scheduler which again stopped the problem for a couple days I think but could be a coincidence 4) I disabled ALL docker containers which did nothing so I dont think it is a container writing that much. Any help or guidance or direction is appreciated! I got to solve this before my drives go bust! apollo-diagnostics-20230125-0955.zip
January 25, 20233 yr 30 minutes ago, CybranNakh said: The part that is thrown me for a curve is that it is ALSO reading and writing an equivalent amount of data to the parity drive This sounds normal to me. Any writes to any disk in the array will need the corresponding part of parity to be recomputed and written. That is how parity works See here - https://wiki.unraid.net/Parity#How_parity_works
January 25, 20233 yr Solution 40 minutes ago, CybranNakh said: something is continually reading and writing to the array (usually Disk2) Perhaps you can try file activity plugin to narrow down the cause of writes
January 25, 20233 yr Community Expert 47 minutes ago, CybranNakh said: The part that is thrown me for a curve is that it is ALSO reading and writing an equivalent amount of data to the parity drive. That's expected, anything written to an array disk will also be written to parity, and with default read/write/modify, parity is also read.
January 25, 20233 yr Author 1 hour ago, apandey said: This sounds normal to me. Any writes to any disk in the array will need the corresponding part of parity to be recomputed and written. That is how parity works See here - https://wiki.unraid.net/Parity#How_parity_works 1 hour ago, JorgeB said: That's expected, anything written to an array disk will also be written to parity, and with default read/write/modify, parity is also read. Thank you guys for the comments! I guess I was thrown by the parity reads matching the array disks. I have downloaded and set up the file activity plugin. I ran it so I guess I will just have to wait and see if it catches anything suspicious going on. I will report back once it happens again to see if it catches anything. Cheers!
February 5, 20233 yr Author On 1/25/2023 at 10:42 AM, apandey said: Perhaps you can try file activity plugin to narrow down the cause of writes So from inspecting the file activity, I could not find the culprit... however... the weird writing issue has gone away... the only major change I have made was disabling NZBget from writing logs for every action, but that would only impact my writes to the cache drives.... so, oh well. I guess it solved itself! Thank you!
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.