i have a disk9 that was clicking so i wanted replace it with another disk. upon doing so, disk 10 got disabled. i fixed the cables for disk 10 but when i started the array i got Unmountable: wrong or no file system for both disks now. i noticed the icon where you typically browse the data on that disk is missing for both so i am afraid that if i start the array now, the unraid will ask me to checkmark to format this disk but if i format this, i fear that the array wont restore this data now. i just dont know why i am getting this Unmountable: wrong or no file system message now never seen it in like 6 years of using unraid.

server-diagnostics-20250711-1801.zip

Check filesystem on disk9 and disk10. Your first parity drive also has read errors. But first, check filesytem on disk9,10. And do NOT format any drives.

Edited July 12, 2025Jul 12 by strike

Also looks like the drive with serial 9JG49BVT has some crc errors which usually means a bad cable connection. So check that too. It could be an old value as the crc value never resets. If it increases, maybe try to change cable.

22 minutes ago, strike said:

Also looks like the drive with serial 9JG49BVT has some crc errors which usually means a bad cable connection. So check that too. It could be an old value as the crc value never resets. If it increases, maybe try to change cable.

appreciate it, will reconnect all these cables. the 9JG49BVT drive is the one i was going to replace disk 9 with when i turned off the array to remove disk 9 and install 9JG49BVT in its place, thats when all this happened. i am unsure how to continue after checking the filesystem if disk 9 was supposed to be rebuilt and now disk 10 being disabled. how likely is it that disk 10 will try to rebuild as if it was blank? thats what i fear so want to verify this somehow. so im not sure if i should put disk 9 back for now or of its too late now since i had selected the new disk when i started the array not knowing about the filesystem thing. i think it was just bad luck that i was attempting to replace the disk and do this check so dont know what to do...

Edited July 12, 2025Jul 12 by droopie

It's been a while since I've checked the filesystem on a drive, but IIRC, you'll get an option to repair it if it needs to. Then, it'll try to do that, and you might get a lost+found directory on the root of the drive, which contains files that were not able to be determined where they should be and what they are, and they could be renamed as random filenames.

When repaired, the next step is to check the emulated drive to see if all the files are there, and if they are, rebuild the drive onto itself. And of course, check for the lost+found folder first. Since your first parity drive had read errors also you have to do this one drive at a time to be safe.

I've had like 12 drives unmountable at the same time once. And after checking and repairing the filesystem, then rebuilding one drive at a time, I was able to recover all data except for one season of a tv show.

And since disk10 is also unmountable, it will not be rebuilt until you have fixed the filesystem on it.

The only thing I'm not quite sure about is how your parity drive with read errors will impact the rebuild. Since you have two, it shouldn't matter, but I'm not 100% sure, only 80%.. So, after reconnecting all the cables, you should check the syslog for this kind of message:"error md: disk0 read error, sector=280" Disk0 is parity1. If it still appears in the log, I would wait for the resident experts like @JorgeB or someone else to comment on this before going any further, to be sure you don't lose any data by mistake.

ima have to come back at this tomorrow. i think i fixed the parity but without even touching the rest i now have disk 4 acting up.
i tried to do that check on disk 10 but it failed so tomorrow ill swap that cable for all the 4 connections to the hba

server-diagnostics-20250711-2056.zip

When you started the array with the replaced disk9 a rebuild would start. Did you cancel that? Or what happened, and what did you do? Yeah, probably best to call it a night and come back strong tomorrow.

And disk4 has a very high crc error count so proably also cable releated.

Edited July 12, 2025Jul 12 by strike

4 minutes ago, strike said:

When you started the array with the replaced disk9 a rebuild would start. Did you cancel that? Or what happened, and what did you do? Yeah, probably best to call it a night and come back strong tomorrow.

i dont think i canceled i dont think anything actually started besides i guess assigning them? it wanted me to confirm starting the rebuild process for disk10 since that was disabled but unsure if the contents are in the array to actually rebuild or if its going to start fresh. very confusing i tell ya, i am reading online but i think in my case is that this happened right before replacing a drive so that just adds to it.

Ah ok. Sound like you didn't start the rebuild then. Anyway, go over the cables again when you start tomorrow and finish checking the filesystem.

Recommend trying to fix the power/connection issues before attempting to fix the filesystems or doing any rebuilding, or it may cause more damage.

10 hours ago, JorgeB said:

Recommend trying to fix the power/connection issues before attempting to fix the filesystems or doing any rebuilding, or it may cause more damage.

i swapped out the cable on the hda and fixed the filesystem for disk10 which gave me a long list. i also didnt see anymore connection issues. but when i started the array in without mounting the disks, i see the yellow icon on disk 10 and x icon on disk 9. i would like to verify that both disks 9 and 10 contents are being emulated before it gets written to especially disk10 as thats the same drive so if its not emulated i dont want to overwrite it. for disk9 i still have the original disk so yolo it if its blank. i could always put disk9 back but every now and then it just hangs. so, should i set the disk10 to unassigned and starting the array?

server-diagnostics-20250712-1244.zip

Edited July 12, 2025Jul 12 by droopie

You need to start the array in normal operation to be able to see the emulated drives. But since disk9 is replacement drive a rebuild will start once you start the array with it assaigned. So to be able to verify the data on the emaulated drives you should unassign disk9 and 10 and start the array. You should then be able to see both disk9 and 10 emulated. Verify the data is correct, then you need to stop the array and reassign disk10 to start the rebuild on that drive first (since you have the old disk9, disk10 is more important.) . You could rebuild both at the same time since you have dual parity, but I would do one at the time to be safe.

13 hours ago, JorgeB said:

Recommend trying to fix the power/connection issues before attempting to fix the filesystems or doing any rebuilding, or it may cause more damage.

the reason i was replacing disk9 is because that drive kept clicking but i dont think it was the drives fault now because i am noticing the same issues with its replacement. so could it be my power supply? i have like 1100 or 1300watts and i do have the powerdisable connector for most of those drives 8tb and all 14tb. i dont have any molex connected and was going to install more fans to molex.

also, thanks @strike i set them to unassigned and see the contents for both thankfully. so starting like this, i do see errors again for serial 9JG49BVT but that aside, disk9 looks like its still the 8tb disk i originally had. so serial 9JG49BVT not been assigned to disk9 because i rather see whats causing the problem in hopes the original disk9 is actually fine and the problem is something else because that original disk didnt have any signs of death in the SMART. i could use this 14tb to replace another 14tb elsewhere so if i can save it i will but i was ready to use it in the array to replace 8tb.

server-diagnostics-20250712-1515.zip

22 minutes ago, droopie said:

also, thanks @strike i set them to unassigned and see the contents for both thankfully. so starting like this, i do see errors again for serial 9JG49BVT but that aside, disk9 looks like its still the 8tb disk i originally had. so serial 9JG49BVT not been assigned to disk9 because i rather see whats causing the problem in hopes the original disk9 is actually fine and the problem is something else because that original disk didnt have any signs of death in the SMART. i could use this 14tb to replace another 14tb elsewhere so if i can save it i will but i was ready to use it in the array to replace 8tb.

Sounds like a plan. Don't know what the clicking sound could be. If the smart looks good, maybe just do a smart test, then if good, just put the original disk9 back. But either way, both drives still have to be rebuilt.

There are still what look like power/connection issues logged with sdh and sdj, any power splitters in use?