July 23, 20241 yr Having a similar issue to: When there is high IO Wait on Unraid, for some reason I start to see tons of accesses on /boot/bzfirmware. My flash USB is constantly reaching reads of 10MB/s and I'm unsure why. Doing an FATrace doesn't tell me much, here is some example output: ``` emhttpd(6734): RO /boot/config/shares/zfs_backup.cfg emhttpd(6734): C /boot/config/shares/zfs_backup.cfg kworker/u24:4+loop1(3905389): R /boot/bzfirmware kworker/u24:4+loop1(3905389): R /boot/bzfirmware kworker/u24:4+loop1(3905389): R /boot/bzfirmware kworker/u24:4+loop1(3905389): R /boot/bzfirmware kworker/u24:4-loop1(3905389): R /boot/bzfirmware parity_list(3752825): RO /boot/config/plugins/dynamix/dynamix.cfg parity_list(3752825): C /boot/config/plugins/dynamix/dynamix.cfg emhttpd(6734): O /boot/config emhttpd(6734): R /boot/config emhttpd(6734): RCO /boot/config/Trial.key emhttpd(6734): RO /boot/config/Basic.key emhttpd(6734): C /boot/config/Basic.key emhttpd(6734): RCO /boot/config/Plus.key ``` I'm at a bit of a loss here, I'm not sure why these kworker accesses on /boot/bzfirmware startwhen I startdocker containers with high IO (in this example Storj). Any ideas on how to debug or what I can do to solve this? Almost ready to give up on unraid at this point since its causing a ton of system instability (the whole docker daemon slows down, causing the dashboard and the docker page to take forever to load). I think the main dashboard triggers a `docker info` which takes ages when this happens.
August 8, 20241 yr Hello, I think I had the same problem and was searching for a solution for a long time but couldn’t find one. I experienced the exact same issue with increased read access on the USB stick. After a server restart, these accesses increased over hours and days until the USB stick was fully utilized, causing the web interface to crash (php-fpm crashes in log) and become inaccessible regularly. Also the CPU load was shown near 100%. I managed to solve the whole problem by increasing my RAM from 8 to 32 GB. In my specific case, the mainly Backblaze Personal Backup Container caused the issues, but i guess other applications that also used RAM in combination with this container contributed to the problem. Now after the upgrade to 32 GB I found that the Backblaze Container was very RAM-hungry, and my previous RAM capacity was insufficient for the proper operation of the container. I believe it had something to do with the RAM since the problem is now resolved. I should also mention that even when my RAM was still at 8 GB, it was never fully utilized. I believe it never exceeded arround 80% usage, yet the issues mentioned above still occurred. Another thing that comes to mind is that I also tried, as suggested in other threads, to monitor the read operations on the USB stick. I found that numerous read accesses occur on the USB stick, regardless of whether the web interface shows a high read load or not. Unfortunately, I was not able to determine which specific read operation was primarily responsible for the high read load. However, I can say that many read accesses on the USB stick do not necessarily cause a visible write load and are not necessarily mainly responsible for the problem. Up until now, I've been using more RAM for 3 days and the problems have normally occurred by now at the latest. I'll let you know if this changes again. Good luck, maybe this will help!
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.