thezyth

I'll try to buy a different controller when I get a chance and see if that makes a difference.

Hey guys, I'm just getting this error from the fix common problems and I'm not sure what it could be. There is a rebuild of drive6 that is curerntly happening in this diagnostic. zeus-diagnostics-20210810-1641.zip

I'm not sure what could be causing this issue then. Do you have any other possible suggestions to try?

I think I may have fixed it. Details below. The mother board that I have currently is a : Supermicro X9QRi-F+ with the following expansion slots -Two (2) PCI Express 3.0 x16 slots (Slot2/Slot4), Slots -Two (2) PCI Express 3.0 x8 in x 16 slots (Slot1/Slot3) The raid controller was plugged into SLOT1. Swapped over to slot 4 and now. I'm getting much better speeds. Will update if the speeds stay steady.

I did end up swapping out disk2 for a new hdd but the rebuild seems to be going equally slow now. I'm more leaning towards maybe a controller issue? Any recommendations on a SAS controller that I can use with my Supermicro 848?

Nope I don't have a spare controller to test with. I did end up running the pairty check for longer and it seems like one of the drives did end up dying during the check....and another one of the sas drives is now throwing up major issues. This may have just been due to dying drives. Will update when I get new drives and get the system up and running. WHile the parity check was running I was getting some regular speeds instead of the abysmal 20mb/s.

Ran a controller bench mark and I don't see anything out of the ordinary here either. Anyone have any suggestions to what else I could check?

I just looked at the CPU scaling governor and it is currently set to ON-Demand.

The last build was using breakout cables direclty from the drives to the motherboard. The new build is using ASR 72405 raid controller with a BPN-sas-846a backplane. I will look into what the CPU scaling is enabled or not.

The slowest drive is at 73 mb/s. So disk 1-4 are my slowest drives and they were also used in my previous build but I was getting much better parity check speeds. Maybe it's due to the change in the interface for the drives?

Yeah I swapped out the cache drive already. I realized that was causing some issues with dockers also. No sure what could possibily decrease the speed by 1/3. I used disk speed to check for issues and it seems like the sas 2tb drives are much much slower than the other drives maybe this could cause the issue. But I had these drives in the previous setup also.

Hey Guys, I swapped to new hardware and was doing a pairty check but I seem to be getting much slower pairty check than before. This system's specs are much better than the previous hardware. Just curious as to what could be the issue. The previous hardware was going roughly 60-80 mb/s but this is barely hitting 20 mb/s. Diagnostics are attached. Thanks for any help, zeus-diagnostics-20210721-1542.zip