My unraid array has been running fine with no issues until it tried to do a parity check a few days ago. I noticed that it was going very very slow and the estimate was that it would complete in 60 days. One of the drives was listed as "Unmountable: wrong or no file system." I have replaced that drive with a brand new drive and formatted it with unraid. I then added it to the array to rebuild parity but it again gives me the same error message and is rebuilding very very slow. My CPU usage is under 10%. I tried switching to another drive, another SATA cable, and a new spot on the motherboard and it still shows the error and rebuilds at an average rate of around 800 KB/sec. Attached are the diagnostics. Any idea what I'm missing?

Side note, I'm running unraid 7.2.6 because 7.3.2 won't boot on my machine for some reason.

apollo-diagnostics-20260709-1728.zip

Edited Thursday at 10:36 PM1 day by pbradley0

5 minutes ago, pbradley0 said:

My unraid array has been running fine with no issues until it tried to do a parity check a few days ago. I noticed that it was going very very slow and the estimate was that it would complete in 60 days. One of the drives was listed as "Unmountable: wrong or no file system." I have replaced that drive with a brand new drive and formatted it with unraid. I then added it to the array to rebuild parity but it again gives me the same error message and is rebuilding very very slow. My CPU usage is under 10%. I tried switching to another drive, another SATA cable, and a new spot on the motherboard and it still shows the error and rebuilds at an average rate of around 800 KB/sec. Attached are the diagnostics. Any idea what I'm missing?

Side note, I'm running unraid 7.2.6 because 7.3.2 won't boot on my machine for some reason.

apollo-diagnostics-20260709-1728.zip

check and replace the cables on disk2 "WD40EZAX-00C8UB0" and post new diagnostics

Edited Thursday at 10:47 PM1 day by MowMdown

13 minutes ago, pbradley0 said:

Side note, I'm running unraid 7.2.6 because 7.3.2 won't boot on my machine for some reason.

Unraid is now very strict about the partition created on the USB drive. You may need to back it up and re-create it, then restore the config folder. This can be addressed later.

8 minutes ago, MowMdown said:

check and replace the cables on disk2 "WD40EZAX-00C8UB0" and post new diagnostics

I had already done that once but I just did it again and that seemed to fix it. I must have two bad cables. Makes me think my drive wasn't bad after all.

6 minutes ago, MowMdown said:

Unraid is now very strict about the partition created on the USB drive. You may need to back it up and re-create it, then restore the config folder. This can be addressed later.

Thanks for the tip. I'll work on that once I have parity restored.

Well, let me take that back. It seems to be rebuilding parity at a normal speed now but still shows the error "unmountable: wrong or no file system."

Attached are the new diagnostics

apollo-diagnostics-20260709-1805.zip

7 minutes ago, pbradley0 said:

Well, let me take that back. It seems to be rebuilding parity at a normal speed now but still shows the error "unmountable: wrong or no file system."

Attached are the new diagnostics

apollo-diagnostics-20260709-1805.zip

17 minutes ago, pbradley0 said:

Well, let me take that back. It seems to be rebuilding parity at a normal speed now but still shows the error "unmountable: wrong or no file system."

Attached are the new diagnostics

apollo-diagnostics-20260709-1805.zip

It appears that disk2 connection issues have been corrected, I dont see any connection issues in the new logs but now you need to repair the filesystem

Stop the parity check.

Stop the array.

Check the "Maintenance Mode" checkbox, then click start array.

Once array is started in maintenance mode, click on disk2, then click the check filesystem button, and report back once it finishes. (you can find further information by clicking on the underlined text)
Note: If it cannot find a superblock after a few hours, it likely wont find one and you can stop the filesystem check.

Edited Thursday at 11:26 PM1 day by MowMdown