pbradley0

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

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. Thanks for the tip. I'll work on that once I have parity restored.

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

I just installed Unraid and paid for the basic key. Now when I try to sign into my serve it gives me a 403 error. I've tried rebooting the server and get the same thing. I haven't made any changes to anything other than adding the key. Any suggestions?

Attached. I went through all the logs and can't find anything. apollo-diagnostics-20220813-1906.zip

I have a drive that's about a year old that I'm having issues with. Every few months it will give me a single read error and then parity will have to be emulated. I've changed the cable and still have the same issue. I ran an extended SMART test and it returned no errors (report is attached). What am I missing here? I doesn't look like the drive is dying to me. Could it be the motherboard? MB4000GCWLV_PEGJJKHX-20220813-1540.txt