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

Just to be sure. Do you want me to replace the replacement drives in bay 5 & 6 with the original discs, or swap out two other discs? Bay 5 and 6 are the two bays where the original discs resided when they failed.

i have a Seasonic FOCUS SSR-750FM 750W 80+ Gold power supply. I've been using it for 3 - 4 years.. I put the original discs in 2 open drive bays. They have power. I can't see them in the gui though. I have a total of 24 bays. Here are the diagnostics tower-diagnostics-20240124-1025.zip

Yes, I do still have the two original drives untouched since I removed them. They were reporting data errors and unraid disabled the two drives a few days later on it's own. maybe the config corruption occurred at that time and the drives are still usable? How should I proceed? Should I shut shutdown the unraid server after unassigning the two replacement drives and then put the old drives back into their old location? Then boot up hoping for the best?

The SAS adapter BIOS was corrupted. To clear the BIOS I had to reset the sas card configuration to the default. That was a new problem for me. Just an FYI. My parity drives were on the second card and when I booted up into unraid, my Parity disks were unassigned. I reassign them to the proper drives. I also assigned the two replacement drives to drive 5 & 6. I am now getting a "too many wrong and missing drives" message near the start array button and the array won't start. Do I just create a new config and accept a loss of data, or am I already screwed anyway? I attached 2 screenshots of what I see and a diagnostic. tower-diagnostics-20240124-0748.zip

Yes, I have a backup from april 2023. Im trying to recover from that but I am having problem with 1 of my 2 lsi sas adapters now so I am working on that issue. I will let the system rest for a few hours and try again. Sometimes when you shutdown a system and unplug the power something may reset. I will let you know what I find out regarding the config. I agree that it is probably corrupt.

Okay, I created a stock trial key and booted directly into the gui. Not headless. I was able to assign the two drives that I have not been able to assign with the licensed usb stick. I have done nothing else and I am waiting for more guidance. I am happy to see some progress.

FYI, I tried booting directly into the gui. Not using the headless browser method from my laptop. Same results I shutdown my vms and plugins and turned them off so that they do not start on reboot. I clicked the safe mode checkbox and rebooted. I tried to assign each device but both devices still refreshed and remained unassigned

Yes., I have tried firefox and chrome. I will try logging directly into the gui without using a browser. When I do #5 I assign one of the disks to one in the dropdown and the screen refreshes and the drive I try to assign the dropdown disk to remains unassigned. I never see a checkbox. I have a feeling that something is corrupted in the unassigned devices plugin or unraid. I just can't seem to figure out what happened and how to fix it. I have replaced drives in the past with no issue. I have never seen a disabled disk warning before, or have "not installed" message after starting the array.

I have two drives that had errors and while I procured two new drives and precleared them, they became disabled and now refuse to be assigned to the new drives that are now in the drive bays where the disabled drives were located. The two new drives have a preclear signature. When I try to assign the drives, I select the drive in the “unassigned” drop down, the screen refreshes, and the drives remain unassigned. This started to occur two months ago and I have had my server off and on while I researched the issue and tried to resolve the issue through responses to other forum posts. I have exchanged the SATA cables to see whether that was the issue because I received a udma error before this all started, but it didn’t help. I noticed that the drives show up in the servers BIOS but when I start the unraid array the two drives, 5 & 6, show as “not installed”. The data for the drives still appear when I click on the devices, “drive 5” and “drive 6”. A red x appears beside each drive. I also click on the unassigned devices mount button for each drive but the buttons do nothing. I am at a lost as to what to do now and I am worried that I will lose the data for the drives. Is there a way I can recover the data from parity and is there any solution for a problem like this situation that I now find myself? I have attached a system log, and diagnostics attached to this post. I also have screenshots of what I see on my unraid server. tower-diagnostics-20240111-1710.zip tower-syslog-20240110-2325.zip