meaning

Hm, ok, it looks like on your system Disk Talkers is running again, but still cannot attach the activity to a named app/container/process. Could you please share the output of this command after one of those disks has spun up and still shows unattributed activity? cat /tmp/disk.talkers/state.json Also useful: - your Unraid version - whether the apps use /mnt/user/... or /mnt/diskX/... paths - any syslog lines around the spin-up time That should show me where the attribution is being lost.

Hey mmm77, Thanks for the report. This should be fixed in Disk Talkers 2026.06.03a. The error means that one of the Unraid mount paths Disk Talkers was watching briefly disappeared or changed while the collector was running. Disk Talkers was handling that too aggressively and could disable fanotify permanently until restart, which then made historical attribution fall back to “Other activity”. This is not, by itself, proof of a failing disk. But if you keep seeing similar mount-related warnings after updating, it would be worth checking your Unraid syslog, disk/pool mount state, and SMART reports for any recurring disk, controller, or filesystem issues. Existing historical “Other activity” entries will not be retroactively fixed, but new samples after updating should keep fanotify active and preserve attribution much better. Let me know if it's allright now ! :)

Yes, you were right. I profiled it and Disk Talkers was doing too much work every 5 seconds, mainly repeated fuser scans and history recalculation. This is fixed in 2026.05.03a; on my test server it dropped from about 15.6% of one CPU to about 1.25%, while keeping the 5s UI refresh.

Thanks for the report. This was caused by Disk Talkers starting after reboot with a reduced service PATH, so it could not find Unraid’s mdcmd binary. This should be fixed in 2026.04.26a: update/reinstall the plugin and it should recover after reboot without needing an uninstall/reinstall. let me know if the problem is fixed at your next reboot ;)

Thanks, you were right: on Unraid 6.12+ exclusive pool-only shares can make /mnt/user/<share> resolve directly to the pool and bypass shfs/FUSE. Disk Talkers 2026.04.21a now treats those mounts as safe, while non-exclusive pool-only /mnt/user mounts remain low-severity informational warnings.

I’ve pushed a light-theme compatibility fix. :)

can you update and let me know if this would be ok ?

Fixed in 2026.04.17c. The historical summary panels were using a layout combination that could visually overflow the parent card. I’ve corrected the panel sizing/containment and published the update. Please update the plugin and hard-refresh the page and let me know ;)

Hey there, can you update the plugin and see how it looks now ?

Disk Talkers adds a dedicated Unraid page to show what is actively keeping array disks and pools spun up. The goal is simple: make it easier to understand which apps, containers, VMs, or host-side activity are touching your storage, and help reduce unnecessary array spin-ups. What it shows - Per-disk live status spun up / spun down) - Current read/write throughput - Live disk users, including: - Docker containers - VMs - host services - user-share access through shfs - Array-wide summary of apps currently keeping HDDs spun up - Historical usage views across: - Daily - Weekly - Monthly - Yearly - Historical attribution estimates showing which apps were most involved in keeping disks active - Estimated HDD energy usage and electricity cost based on configurable watt ranges and tariffs - Mount audit to highlight containers using /mnt/user or array-backed paths where a direct pool/cache path may help avoid unnecessary spin-ups Why this exists On many Unraid systems, disks stay spun up and it is not always obvious why. Sometimes the cause is direct array access. Sometimes it is a container using /mnt/user/... instead of a direct cache or pool path. Sometimes it is a service or background scan that keeps touching files often enough to prevent spindown. Disk Talkers is meant to make that visible. ## Main features - Dedicated Unraid WebUI page - Live refresh - Disk-by-disk visibility - Historical usage overview - Mount-path audit for Docker containers - Estimated power and cost visibility - Quick actions and configuration inside the plugin UI Install Until Community Applications listing is live, the plugin can already be tested with the direct plugin URL. WebUI method 1. Open your Unraid WebUI 2. Go to Plugins 3. Click Install Plugin 4. Paste this URL: https://raw.githubusercontent.com/silkyclouds/unraid-disk-talkers/main/disk.talkers.plg CLI method installplg https://raw.githubusercontent.com/silkyclouds/unraid-disk-talkers/main/disk.talkers.plg GitHub Source and releases: https://github.com/silkyclouds/unraid-disk-talkers Notes - Attribution is best-effort. Very short-lived activity may still appear as residual or unattributed activity in history views. - Energy and electricity cost values are estimates based on HDD uptime history plus user-configured watt and tariff settings. - This plugin is intended to help identify real-world storage behavior, not to claim perfect block-level forensic attribution. Feedback Bug reports, screenshots, edge cases, and UI/UX feedback are very welcome, especially for: - shfs / user-share attribution - incorrect container attribution - historical attribution gaps - cases where cache/pool mounts should be preferred over array-backed paths - installs and upgrades across different Unraid versions

Hey, I’m running into the same headaches with S3 sleep on Unraid, so I figured I’d share my setup and ask for advice. Main server with a big array + HBA → ~95 W idle Base system alone (CPU/RAM/fans, no HBA/array) → ~25 W idle So ~70 W are literally wasted 24/7 just to keep the array/HBA alive Electricity here is ~0.38 €/kWh → that’s expensive over a year So, I've built a low-power N100 box at ~12 W idle to host all Dockers/VMs and be the “master” Idea: keep the array sleeping and only wake it with WOL + autofs/NFS when files are needed The problem: one wake ended up with a disabled/emulated disk and a full rebuild. That scared the hell out of me, and honestly I don’t trust S3 sleep anymore with this setup. So I’m thinking: instead of sleep, maybe just fully shutdown the array server when idle and WOL it when needed. Downside: boot time ~1–2 minutes, which is annoying. But this box does nothing except serve the array (no Dockers, no VMs). But the idea of waiting 2 minutes before I can start a movie or listen to a music album ain't nice... Question: is there a way to make Unraid boot in a really “lightweight” mode just for the array? Like, disable every unnecessary service/plugin so the boot + array mount is as fast as possible? Has anyone here tuned Unraid this way? Or, is anyone here actually happy and safely using S3 using a great pre-sleep script ?

Done. Thanks !

OK you were right, the server started, all disks are detected, all plugins are running ! but the array wont start as I already had a usb key failure a few months ago and transferred it to the "new" one that failed as well. So I guess I made too much key transfers in less than a year : what now ?

ok well, I am copying the "CONFIG" (upper case) folder I got back from my previous key back to the newly flashed one. I'll try a reboot in a few seconds. fingers...and toes...

By the way, the data I've got back was recovered by testdisk, and even with a copy result that is OK, it seems like some folders are now in upper case : I believe this will make things harder... I think I did enable flash backups on Unraid connect, but fr some reason, when I head there, I keep seeing the Loading message, and cannot see my backups. I also tried using another browser and incognito mode, same result. Is there a chance I could find my "connect" backups somewhere ? If not, is it safe to pass ALL the folders and files I see in the above list in lower cap ?

Thanks for the quick reply @JorgeB So, am I right thinking I should : 1. flash a new key with the usb creator tool 2. one finalised, copy the config folder (all lower caps folder names) to the root of my newly created usb boot key 3. start unraid and cross fingers and toes

Hi all, It all started with a notification telling me, suddenly, that my usb key was not writable / readable anymore in Unraid webui. After a reboot, I've got the nice Syslinux 6.XX loard error / Boot error message. I took the usb key out of my server and made the usual disk checks, it's full of errors. testdisk was actually able to find the UNRAID partition on the usb drive, and eventually copied 1275 files out of 1275, successfully. ```` Copy done! 1275 ok, 0 failed ```` This seems to be good news, but once I started looking at the files several a first severe strange thing popped-up: 1. here is a recent screenshot I've made of my array : but here is what the "DISK_ASSIGNMENTS.txt" file on my key is listing : ````` Disk Assignments Disk: parity Device: ST20000NM007D-3DJ103_ZVT5JD71 Status: DISK_OK Disk: disk1 Device: WDC_WD140EDFZ-11A0VA0_9MGJZH6K Status: DISK_OK Disk: disk2 Device: WDC_WD140EDFZ-11A0VA0_9MGH0SWK Status: DISK_OK Disk: disk3 Device: WDC_WD140EDFZ-11A0VA0_9RJ9AXPC Status: DISK_OK Disk: disk4 Device: WDC_WD80EDAZ-11TA3A0_VG02A8XG Status: DISK_OK Disk: disk5 Device: WDC_WD80EFZX-68UW8N0_VK0V8N6Y Status: DISK_OK Disk: disk6 Device: WDC_WD180EDGZ-11B2DA0_3FHEU4PT Status: DISK_OK Disk: disk7 Device: ST6000DM003-2CY186_ZR10LGGX Status: DISK_OK Disk: disk8 Device: WDC_WD180EDGZ-11B2DA0_3FHSBHAT Status: DISK_OK Disk: disk9 Device: WDC_WD140EDFZ-11A0VA0_XHG4ZE5H Status: DISK_OK Disk: disk10 Device: WDC_WD140EDFZ-11A0VA0_9RHVA5KC Status: DISK_OK Disk: disk11 Device: ST6000DM003-2CY186_ZR10PK1V Status: DISK_OK Disk: disk12 Device: TOSHIBA_MG09ACA18TE_6250A5Z7FG0H Status: DISK_OK Disk: disk13 Device: TOSHIBA_MG09ACA18TE_6260A3JGFG0H Status: DISK_OK Disk: disk14 Device: ST18000NM000J-2TV103_ZR53Z8L8 Status: DISK_OK Disk: disk15 Device: Status: DISK_NP Disk: disk16 Device: Status: DISK_NP Disk: disk17 Device: Status: DISK_NP Disk: disk18 Device: Status: DISK_NP Disk: disk19 Device: Status: DISK_NP Disk: disk20 Device: Status: DISK_NP Disk: disk21 Device: Status: DISK_NP Disk: disk22 Device: Status: DISK_NP Disk: parity2 Device: Status: DISK_NP_DSBL Disk: cache Device: KINGSTON_SA2000M81000G_50026B76844E1A84 Status: DISK_OK Disk: vms Device: PNY_120GB_SATA_SSD_PNA0322700061AT04833 Status: DISK_OK Disk: flash Device: DataTraveler_3.0 Status: DISK_OK ```` In regards to everything else, docker, plugins, etc. I don't really mind, but I really would like to get my array back. since I do have my parity drive ID, it must be possible. it is safe to think this is not the place where my array config actually is stored on my usb stick ? Is it afe to assume I could simply re-flash an unraid usb drive, and copy the whole config folder to its root, and that I4d get all my previous config back in place ? What are the steps to follow here ? thanks !

I did reboot, everything is back up. For which reason could the HBA have been reset ? electrical problem ? anyway, the new zip is attached ! thanks ! tower-diagnostics-20230317-1227.zip

Hi all, I've got a pushover notification a few minutes ago telling me there was 1 read error, but it appeared on all my drives at once. I stupidly decided to start a parity sync and noticed non of my drives were reachable anymore : https://app.screencast.com/3rYhKTK4EHjzQ I also tried to access /mnt/user -> root@Tower:~# cd /mnt/user/ -bash: cd: /mnt/user/: Input/output error here is an extract of what syslog tells me: ``` Mar 17 10:54:51 Tower root: ddns-updater: Could not download icon https://github.com/DiamondPrecisionComputing/unraid-templates/blob/main/templates/img/ddnsgopher.png?raw=true Mar 17 11:16:54 Tower kernel: md: disk1 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk2 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk3 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk4 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk5 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk6 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk7 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk8 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk9 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk10 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk11 read error, sector=0 Mar 17 11:16:54 Tower kernel: md: disk0 read error, sector=0 Mar 17 11:16:54 Tower kernel: XFS (md1): metadata I/O error in "xfs_alloc_read_agfl+0x84/0xc3 [xfs]" at daddr 0x3 len 1 error 5 Mar 17 11:16:54 Tower kernel: md: disk1 read error, sector=12886351208 Mar 17 11:16:54 Tower kernel: md: disk0 read error, sector=12886351208 Mar 17 11:16:54 Tower kernel: md: disk1 read error, sector=12886351216 Mar 17 11:16:54 Tower kernel: md: disk0 read error, sector=12886351216 Mar 17 11:16:54 Tower kernel: XFS (md1): log I/O error -5 Mar 17 11:16:54 Tower kernel: XFS (md1): Corruption of in-memory data (0x8) detected at xfs_defer_finish_noroll+0x479/0x503 [xfs] (fs/xfs/libxfs/xfs_defer.c:573). Shutting down filesystem. Mar 17 11:16:54 Tower kernel: XFS (md1): Please unmount the filesystem and rectify the problem(s) Mar 17 11:17:33 Tower kernel: mdcmd (36): check correct Mar 17 11:17:33 Tower kernel: md: recovery thread: check P ... Mar 17 11:17:33 Tower kernel: md: recovery thread: multiple disk errors, sector=0 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=8 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=16 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=24 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=32 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=40 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=48 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=56 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=64 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=72 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=80 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=88 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=96 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=104 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=112 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=120 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=128 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=136 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=144 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=152 Mar 17 11:17:33 Tower kernel: md: disk1 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk2 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk3 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk4 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk5 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk6 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk7 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk8 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk9 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk10 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk11 read error, sector=160 Mar 17 11:17:33 Tower kernel: md: disk0 read error, sector=160 ``` Can someone help me out figuring out what's happening and what broke ? It's pretty urgent, all my dockers are running from there I've attached full diagnostics zip. thanks ! tower-diagnostics-20230317-1141.zip