In the past I would have and issue with all drives starting in array after shutting down. I would move the power connects around to drives and reboot again. Would work most of the time. Having a 850 watt power supply I was thinking server was having issues with 8- HDD and 4 SSD drives or the HBA/ sata cables were failing. I replaced the PS with 1000 watts and a new HBA card. Now it is seeing more drives, but most are unassigned and has a active mount button. The parity drive does not have a mount button option. Tried to see if I could assign the parity drive back to it's configuration and unraid stated it was the wrong drive. Is there any way to fix this issue? Any help will be appreciated.

thecave-diagnostics-20260114-1754.zip

Still having issues with unraid. Tried to resign drives to corresponding disk number. Wrong drive is indicated even though it matches drive the information that is displayed.

Some drives changed IDs, likely due to the controller change. You possibly used a RAID controller before, but disk2 is actually missing. See if you can get it to show up; you should then be able to do a new config

What happen is the original Disk 2 was giving me intermittent read errors. These errors warring would disappear and reappear in a few days. So I decided to swap out the drive. When I brought the system back up, I was having this issue of not all drives in array. (missing drives. etc.) So multiple times I moved the drives sata power cable around to try to balance the power. This usually would work. But after a few days I was this maybe it is something else. I got a new 1000 watt power supply and similar hba drive controller. I swapped out the power supply first and started server, no change. Then swapped out the old hba with new hba and sata cables. Now I see all of the drives under the unassigned listing. I tried to assign the drives back to there original destination. I get wrong drive status.

There are a few steps I am thinking about trying:

Place Disk 2 back in server. (original drive still works. just give me the intermittent errors)

Place the original hba controller card back in server. ( It seems not to see the drives. Maybe it is fine?)

Hopefully, I can solve this issue.

1 hour ago, ButchR said:

I tried to assign the drives back to there original destination. I get wrong drive status.

This is expected,

4 hours ago, JorgeB said:

Some drives changed IDs, likely due to the controller change.

If you don't have the original disk 2, you can try doing a new config with a spare (same size or larger) and then disabling it to force a rebuild, but this will only work if parity is valid, can post the instructions if interested.

Update: I was able to reassign some drive back to the original slot. Except one drive is off by one character. Also warning that disk 2 is failing. See below.

Moreover, should try to see if i can make Disk 7 match or just try to start the array?

The options I have:

Just looking at disk history.

Anyone have similar experience and if so what did you do?

13 hours ago, JorgeB said:

If you don't have the original disk 2, you can try doing a new config with a spare (same size or larger) and then disabling it to force a rebuild, but this will only work if parity is valid, can post the instructions if interested.

Instructions

Tools - New Config - Retain All - Apply.

If any drives are not assigned, assign them as before.

Check BOTH Parity Valid and Maintenance Mode checkboxes then Start the array. This will accept all drives into the array without changing any of them

Stop the array, unassign disk2, start the array in Normal mode. This will disable disk2.

Then post new diagnostics so we can see if emulated disk2 is mountable.

I began the process. I have my fingers crossed. Before I started I physically looked at all drives and compare the serial numbers. Disk 7 like I stated before the serial numbers is off my a few characters (wondering what happen? Maybe I will find out later)

So Disk 7 is rebuilding now and the finish time is not normal. I hope this will change with time. ( I feel like there is some serious issues happening) Take a look:

The diagnostic has been running for a while. Maybe I should have ran before starting the current process of rebuilding. Never had anything like this happen before in 3.5 years running my Unraid server. I hope the server will survive. (Note the days count is constantly changing)

The diagnostic file.

thecave-diagnostics-20260115-2107.zip

Disk2 appears to be failing; it's not even giving a valid SMART report, try replacing its cables, but look more like a bad disk.

Well I took some different action on unraid before I had your insight on what steps to take. Yes. Disk 2 is failing while I was forced to rebuild disk 7, because disk 7 I’d was scrambled. Now estimated completion time is a crazy number like 2000 days plus keeps on going up and down at one time it was at 300 days.. I guess overall unraid server’s failure is eminent for me. Wish I knew what to do to make it better. It’s been quite a journey so far four years in and now it looks like the whole system is gonna fail on me.

At the moment, disk 7 is not being correctly rebuilt due to the issues with disk2, if the issue with disk 7 was just the wrong ID, a new config with the steps mentioned above would likely be the better option, and it may still be better to cancel and try that.

Doing the procedure above to rebuild disk 2, using the old disk7, and hopefully that disk is still mostly OK.

9 hours ago, trurl said:

Tools - New Config - Retain All - Apply.

If any drives are not assigned, assign them as before.

Check BOTH Parity Valid and Maintenance Mode checkboxes then Start the array. This will accept all drives into the array without changing any of them

Stop the array, unassign disk2, start the array in Normal mode. This will disable disk2.

Then post new diagnostics so we can see if emulated disk2 is mountable.

8 hours ago, ButchR said:

Disk 7 is rebuilding now

You were supposed to rebuild disk 2.

The instructions I gave specifically said disk 2.

I started before I received your instructions. I wish I had waited for your instructions. But I didn’t know I was going to get help at that time and made some not so great decisions. Any suggestions what I can do now?

5 hours ago, JorgeB said:

and it may still be better to cancel and try that.

Doing the procedure above to rebuild disk 2, using the old disk7, and hopefully that disk is still mostly OK.

  14 hours ago, trurl said:

Tools - New Config - Retain All - Apply.

If any drives are not assigned, assign them as before.

Check BOTH Parity Valid and Maintenance Mode checkboxes then Start the array. This will accept all drives into the array without changing any of them

Stop the array, unassign disk2, start the array in Normal mode. This will disable disk2.

Then post new diagnostics so we can see if emulated disk2 is mountable.

Thanks. I appreciate your help . I have a 16TB (never used in Unraid) drive that been precleared a few months ago. I am thing about rebuilding disk 2 with this drive.

Okay with end inside of tools now.

Preserve current assignment is gray out now. How to I select the option retain all?

Right next to the buttons it tells you what the problem is.

Okay. correct selection?e t

yes

Okay thanks.

9 hours ago, JorgeB said:

using the old disk7

Don't overlook this important bit

Should I use the spare unassigned precleared 16TB drive?