jeezany

Finaly, I have an acceptable speed for the disk rebuild So, I think my issue was that there was an ongoing scrub job for multiple of my disks at the same time that I wanted to do this disks swap activity. not really sure what was my lesson learned from this. check everything? :') I think this topic can be considered closed.

Updates. Looks like there was some scrub jobs in two of my drives. I stopped it for now and the speed rose to ~40MB Is there a way to do that?

Booting in safe mode and running in maintenance mode will return the speed to what should be 100~200 MB

So far, I have disabled NFS, FTP, SMB, all shared from global share settings. Downgraded from 7.2.2 to 7.1.3 and still same slow speed. Not really sure how to pinpoint the issue

I have placed the array in maintenance mode again and the speed went up to 100 MB + shutting down the docker engine did not really help. shutting down the VM manager also did not help. maintenance mode starts the array while stopping all other services beside it if I am not mistaken. I will try to troubleshoot more in the plugins or the shares if one of them is making this issue

But I think disk 3 should be involved in the disk rebuild. Correct me if I am wrong

Back again. The parity has been completed successfully. Now, I have swapped one of my data drives to increase the capacity "this was the final goal" unfortunately, I am facing the same issue as the parity. Speed is averaging 1.5-2 MB

All screenshots were taken while the parity check was running. I disabled docker completely from Settings --> Docker --> Enable Docker "No" I also disabled VMs just in case it will help or not "I am not running any VMs currently"

Increasing the zfs memory allocations did not help unfortunately. I have stopped the parity check and started the array in maintenance mode and now the parity sync speed is +- 100MB While it is unfortunate that my services will be down for three days but at least the parity check will not take half a year. Not really sure what was the issue here

Hello, No, I don't have Dynamix File Integrity plugin installed. I am not configuring any cache drives. 5 Data disks and one parity. Yes, I am configuring my drives to use ZFS. I will try to increase the ZFS memory allocation and see if it helps or not. If not, I will try the safe mode method to test

Sorry for the late reply. These are the disks while Docker is enabled. And these are the disks while Docker is disabled. Not really sure what is running the disks for 255 MB Read

I saw that a single container was restarting from the uptime like you mentioned. I stopped it for now. I have a scheduled restart for a multiple of my containers on daily basis at midnight but I don't think this is affecting it. NOTE: I have tried to stop docker engine and VM Manager to see if by stopping everything will it help or not. Unfortunately, it did not. This is what htop I/O tab looked like

Hello All, I have started the process of upgrading my parity drive from 18 TB to 22 TB. I have used the following steps on swapping the drive Replacing disks in array | Unraid Docs Which was simple 1. stop array 2. remove parity 3. start array 4. stop array 5. replace drive 6. start array 7. start parity check So far, 5 days have passed and only 11.1% from parity completed. My average speed looks around 1-2 MB/sec I was using my server as usual "downloading/reading/playing media" and while trying to troubleshoot the issue I read in the forum that read/write while doing the parity check will affect performance. I have currently disabled docker and VMs and the speed is still 1-2 MB/sec. Is there anything else I should look at? htop system load disk performance j-tower-diagnostics-20251228-1026.zip

Hello, so far the system is up and running. looks like it was the power state option in the bios that created the issue. Thank you for your help @JorgeB

Hello, Thank you for the reply. My Motherboard is x470 hero and it is already up to date. After upgrading my unraid server to AMD R9 3900X, I have reverted my memory setting to default "2444 MHz I think?". It was intel 6600 previously FYI and was working very fine. I now have disabled c-states option and changed Power Supply Idle control to typical in the bios. I will try to make sure the system is up and running during this week. will give update "hopefully" by the end of January if the system is still working fine. Or if it crashed again. Thanks,