scott.harris

As I said, this is where the terminology used is confusing. In pretty much any other context a new drive does not contain data and would be formatted after starting the array. I have done the new config, add drive, start array and things are all looking pretty great. I really appreciate this and will be sure to remember it should this happen again. Now I just need to get that new backplane in on the other enclosure.

This is where it gets confusing. "Do the new config first". So I set new config before I add the drive back to slot 16? Won't that result in that drive being viewed as a "new" drive and require formatting and loss of all data and a parity rebuild of that disk?

And the correct procedure for that is to stop the array, assign the drives where I want them, set the new config using the preserve current assignments (all) option, then starting the array?

Ok. I completed the file check and repair. Prior to starting the array after the repair it no longer says it is unmountable but it does warn that starting the array will begin data rebuild. I mounted it in UA and the data appears intact. Starting the array with the disk unassigned and the emulated files are again browseable. Thank you! Now...is there a way to not rebuild the data but instead just use what is already present and only recalculate parity? I think that may be what the "new config" option is for but the wording on it is unclear, referring to the drives as new.

I think I am going to move everything off of disk16 and on to other array drives via UA and then add it and format. Everything I see in the options leaves me with the fear that I will lose the data like I did with the previous drive (tried repairing the file system and adding the drive back in and lost 12TB). When I start the array with nothing assigned to that slot it does say it is disabled and emulated but it cannot be browsed like a disabled disk usually can, only that it is unmountable. Frankly, I lack the confidence in my knowledge of the process of adding a full drive to the array and having it remain intact to go with that. I will work on that while I wait for the replacement backplane to arrive. I truly appreciate your time with this.

New diags attached. Here is a screenshot of what happens when I assign the disk to its slot in the array now: And when I don't select it the option is either one of my unassigned disks or "unassigned" where previously it was a disk or "No device". bigboy-diagnostics-20251016-1119.zip

The disk is not emulated. It shows up with an "Unmountable: wrong or no file system" notice and an option to format. If I remove it from the array (set that slot to No Device) and then start the array it pops up in UA and is mountable and the data is present. The disk itself appears to be fine and now that it is again in the old server there shouldn't be any problems with the HBA, cables, or backplane. It ran there fine for days during testing over the previous weekend. I am hoping there is a way to get this disk recognized as part of the array again but without having to reformat and with no data loss.

Damn it. Everything moved again. Started it all back up and now the drive with the read errors on the previous attempt is now showing as "Unmountable: wrong or no file system". This is a full 24TB disk. Doesn't even come up as emulated. I can stop the array, set that slot to no device, and start again and then mount via UA and everything is still present. No complaints about the file system at all. This is becoming extremely frustrating. Is there a way to add this disk back into the array? I don't want to go poking around too much as doing that previously cost me everything on another drive.

Damn. So the move back to the old hardware went smoothly. I lost the data on the "bad" drive but that can be replaced. No read errors at all. Gave it a few days to settle in and everything was still running smoothly. That brings us to today. Got a new HBA and cables in moved the drives back to the new hardware. Started the array in maintenance mode without any problems. Started a read check and BAM, 2048 errors immediately followed by the drive dropping to disabled then popping up in UA. I guess the next step is the backplane which will likely not be available for a couple of months. I guess we're sticking with the old server for a while.

Interesting. Sometimes the "unassigned" drive would show up in UD with either "Array" or "InArray", can't recall exactly which, and if I remember correctly those might not have been mountable? But they connected and Unraid recognized them as supposed to be in the array. It is all very odd and I'll admit I'm not doing a great job of communicating all of the details. I appreciate the insight, though. I didn't realize that if a drive lost connection and reconnected it could be with a different ID. That helps. I am in the process now of moving all of the drives back to my old server so I can at least get the original down drive rebuilt, if possible, and to at least confirm the drives are all fine. A new HBA and another set of cables will be here some time in the next week and hopefully that will get things resolved. Otherwise I will need to wait until I can get a replacement backplane from China. Fingers crossed and thanks for the help.

But it is still mountable and useable in Unassigned Devices so the connection is still present. That's what is throwing me off. If Unraid has lost connection why is it still connected?

On the "Main" tab the indicator for the drives with the read errors are a light green dot and when the cursor is over it the description is, roughly from memory as the server is currently offline, the disk is in standby and I have the option to spin up the drive. Selecting that option does nothing and my spin down setting is set to never on all drives.

I'm curious; if it was losing power or data connection would it not switch to offline or disabled instead of standby? The connections are still seemingly good. The drive goes to standby in the array but then gets listed to Unassigned Devices where it is mountable and the data can be accessed form there which would seem to indicate all of the connections were good.

All new cables, same problem. Moved the HBA to a different slot, no change. New diagnostics are attached if anyone is interested. I am working on getting a replacement backplane and HBA but the first I won't have a quote on until next week and it probably will be another month+ before it gets here and I didn't pull the trigger fast enough on a replacement HBA and someone else snapped it up so am waiting for another to pop up. bigboy-diagnostics-20251007-1858.zip

That's one of the things I really fear. Getting a replacement backplane is going to be a massive PITA if I can even get it on its own. New cables will be here tomorrow and I will update with the results then.