jkwaterman

I had to wait an hour for the scan to start. I kept trying rescan but it did not help.

For those having issues with the upper left "not connected' problem, it is probably the settings for media path when you set up the app. I have been playing around with it and the connection only works with the attached screenshot. My problem is how do you get it off queued after you set up a watch folder

Thanks, I will. I am marking the thread solved

Good News, I think. I believe I can try the rebuild now.

I should place my drives back in their proper spots first. Correct?

I backed up the flash drive config at this point in time before I mucked with the April backup when we know I had parity. Yes if I understand you the two drives were disabled.

I have been going through this thread while waiting for confirmation that the original disks are bad. I noticed that I made a statement that may cause others to think that I did not back up the config before going down this path. I did back up the config from the original flash drive before doing anything. I do have a super.dat file in the config folder backup.

I swapped 7 & 8 with 4 & 6 Diagnostic attached tower-diagnostics-20240124-1545.zip

I think these two drives are in ports 7 & 8 on the MB. The MB actually has 10 ports. 2 of the first 6 are shared so 2 are not used

the first 8 drives use onboard Sata. I then have 2 lsi PCIE SAS cards. Each LSI card have 8 ports a piece. You should see 8 sata drives Including the 2 original drives that I just swapped out. When Unraid disables a drive, does/can it set a flag stating that the drive is unusable? Jumping at straws here.

I rebooted and brought up the system BIOS. Both drives appear in the proper SATA ports

FYI, i backed up te config from the original flash drive before doing anything

Okay, I swapped out the discs in bays 5 & 6 and still can't see the discs. Want me to check the servers Bios to see if they are there? Heres the newest diagnostics. tower-diagnostics-20240124-1157.zip

That suggests something in your /config is causing the issue, you can backup the current flash drive first and then redo it and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit. I followed this first but still couldn't assign disks then went with the backup not thinking.

Just to let you know the background of how the parity drives got unassigned, I recovered from an april 30th backup. In august, or september my parity discs failed and I replaced them successfully. I thought that I had backups but I can't find the later backups. I do use connect, unraid.net to do weekly backups but I haven't been taking them off the unraid server for a while I guess. I know that it is too late now, but I believe that is what happened. I should have thought better of using that backup, but that is water under the dam now