I had a 3 disk array (2 x data [3TB +4TB] and a 4TB parity) and was low on space so got a new 14TB EXOS drive to future proof any further storage upgrades.

I tested the new drive and precleared as it was used but all looked good and the preclear was running at approx 250MB/s.

I thought it would be safest to add the new drive as a 2nd parity disk and once rebuilt I'd move the old parity to the array. Maybe this is where I've gone wrong.

Anyway approx 36 hours later and I'm still only at 20% rebuild and the speeds seem to max at about 25MB/s but often drop to 3 or 4MB/s.
I had a look at the syslogs and don't see any SATA errors or anything, is that where they'd show?

Should I have done this differently? Should I restart using another method?
Appreciate any help. Diagnostics attached if someone could take a look.tower-diagnostics-20251130-1249.zip

Your syslog show a docker container continually crashing and being restarted. You can probably work out which one it is by looking at the uptime on the dockers tab.

2 minutes ago, itimpi said:

Your syslog show a docker container continually crashing and being restarted. You can probably work out which one it is by looking at the uptime on the dockers tab.

Thanks. I disabled docker about 30 minutes ago to see if activity there was causing any issue but its still the same.
I'll re-enable it now and take a look at that as it may be a side issue.

1 hour ago, commanding-barbarian8014 said:

Thanks. I disabled docker about 30 minutes ago to see if activity there was causing any issue but its still the same.
I'll re-enable it now and take a look at that as it may be a side issue.

OK, just figured out what that issue was. Teslamate was crashing due to MQTT issues which I wasn't using. Disabled MQTT for that container and its running fine now. My mover is running now which has interupted the parity, I'll report back when its steady again.