After adding and clearing and formatting a new drive (#7) got this error on disk 5.  
I searched the forums and ran the file system check in the docs, followed by the file system repair for xfs as per the docs.  Never got prompted for -L that I know of because it ran for a couple hours and finished on its own.  Now drive still shows the same unmountable error.  Ran another check and now the progress is full of entries whereas the first time it was short and all seemed ok.  Is this a failed/failing drive?  Can the drive or data be restored?  
Diagnostics attached.  
thanks!

deathstar-diagnostics-20250110-1216.zip deathstar-smart-20250110-1201.zip

Edited January 11, 20251 yr by Danoman
Added pic

Run it again without -n, and if it asks for -L use it.

That seems to have worked but during the night my parity drive has developed errors and got the red X but system said parity was valid so I removed the parity drive in unraid, re-started the array and re-assigned parity drive (same one) and started array and parity sync.  It got about 6% in and disk 7 got errors and a red X.  I’m starting to suspect my SATA controller and/or cables.  Got to the point that disk 7 showed as “not installed” so it allowed parity sync to complete without a problem.  
Now disk 7 was rather new and has like 0 data so I could care less about it.  Can I just set “new config” and remove it entirely?

 

I’m attaching latest diagnostics if somebody can help me determine what’s going on with multiple disk glitches all of a sudden.deathstar-diagnostics-20250111-1223.zip

 

 

There are errors with multiple disks on the same controller, and that controller has SATA port multipliers, that is not recommended and can cause these issues.

Ok, I was suspecting a controller issue because of multiple disks having issues suddenly.  It was quite stable until I added one drive the other day.  Maybe disturbed the controller somehow.  I wasn’t aware about the multiplier issue.  I managed to get disk 7 removed by a new config which is good.  Just need to get through parity sync but it’s moving at kps speed and saying 900 days to complete.  I’ve been doing all this remotely through Tailscale since of course this happens when I’m going out of town.  So I cancelled the parity sync until I can get home and check/replace the sata cables etc.  I ordered a replacement controller but it’s the same as the current one so not sure I’ll keep that.  Gonna look into the alternatives to Sata multipliers.

Thanks!

Just to close out this issue, I finally got home from a trip and was able to change the Sata cables around.  Long story short, changed Sata cables and then Parity disk showed red X.  Stopped the array, unassigned parity, started array without parity, stopped array and re-assigned old parity.  Started array and parity sync started and is running like normal, FINALLY!  I had been having issues with SLOW PARITY sync until this simple solution (replace Sata cables).  Parity running at 118MB/s still using the original “cheap” controller one of which has a multiplier on it.  I will let this finish to restore the array to proper state and then I have 2 new ASM1166 (6 port no multipliers) controllers ready to go which will optimize my throughput and future proof me as far as number of devices goes.  This thread and whole experience has been very educational and thanks to you guys for the guidance!