April 23, 20251 yr Migrated to a new server and all of the disks were recognized fine, but I can't write to any disk it seems, and it says the cache is full when it's not. I tried a new config to see if that would help, but it did nothing useful. tower-diagnostics-20250422-2309.zip
April 23, 20251 yr Community Expert Filesystem Size Used Avail Use% Mounted on /dev/md17p1 9.1T 9.1T 16K 100% /mnt/disk17 /dev/md19p1 5.5T 5.5T 20K 100% /mnt/disk19 /dev/md26p1 9.1T 9.1T 16K 100% /mnt/disk26 /dev/md28p1 7.3T 7.3T 20K 100% /mnt/disk28 These disks cannot be written to because they are completely full, only a few KB left, and mosts of your other disks are at 100% as well, though they still have a few GB free.
April 23, 20251 yr Community Expert It also looks like you have .cfg files on the flash drive in config/shares for shares that no longer exist. If you use the Clean Up button on the Shares tab it will remove these which will make diagnostics cleaner (or manually delete them if there is no Clean Up button available).
April 24, 20251 yr Author Hi Thanks for the help so far. I'm also getting errors that the cache is full, and it's not. Nothing at all can be written to the array, even outside of those mentioned disks. I cleared the old config files, but the issues persist.
April 24, 20251 yr Community Expert 47 minutes ago, IDontBelongHere said: Nothing at all can be written to the array, Which share are you writing to?
April 27, 20251 yr Author On 4/24/2025 at 10:32 AM, JorgeB said: Which share are you writing to? I was trying to write to my "Data" share. I've fixed that issue by updating my docker which was trying to write to it, and doing another reboot. Most of the issues seem to have resolved following a reboot and updating/reinstalling of dockers. However, I am still having issues with my parity sync and extremely high CPU usage (95%). The sync starts off fine going about 90MB/s, but it's at 15.4% and has slowed down to a range of about 300KB/s to 1.5 MB/s. I've tried disabling the docker service to se if it speeds up, but it doesn't seem to help at all. Thanks again for all of y'alls help thus far. tower-diagnostics-20250427-0824.zip
April 27, 20251 yr Community Expert In the diagnostics you have something writing to disk8. Any disk activity will slow down the parity check significantly.
April 30, 20251 yr Author Thanks again for the help guys. Everything is working back as it should, and my parity sync finished successfully the other night. Didn't realize writing to the drive would slow down the parity sync that significantly. Is it because it was doing a fresh sync? I've never had a parity sync go that slowly previously even with the array being heavily used.
April 30, 20251 yr Community Expert Just now, IDontBelongHere said: Didn't realize writing to the drive would slow down the parity sync that significantly. Is it because it was doing a fresh sync It is because you get lots of disk head movements on the drives between the position the parity sync has reached and the position at which the I/O is taking place. Writing is worse than reading because both the target drive and the parity drive are involved.
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.