Been troubleshooting a display adapter issue, and tried to roll back my boot flash drive to an earlier configuration.  I currently have my flash drive (original one for license key) loaded with the My Servers backup files.

 

When I boot up, it asks for me to reset my password.  OK, no problem.  But now all of my array drives are no longer in my array, but now in Unassigned Devices.

 

It would really ruin my life day to zero out 40TB of data.  How should I proceed?

 

Attached is diag from before I created this mess.

malta-tower-diagnostics-20230122-0926.zip

You can see your drive assignments in several different ways in those diagnostics. Take a look in the smart folder, for example.

 

I encourage everyone to examine their diagnostics. They are text files (except super.dat), mostly settings from the webUI, logs, smart reports, and the results from several commands that tell about your hardware.

And many of the files in the config folder of your diagnostics can be used just as they are in the config folder of your flash drive.

The file config/super.dat is where Unraid keeps your disk assignments.

Fortunately, I have a hard copy of the array drive config.  (and easy enough to see from Unassigned devices which is my Parity Drive).

 

Because if you look in the disk.cfg file, it has a bunch of info *except* the drive ID/slot info.  Probably why it isn't configured correctly on the server at the moment.

 

Really need to know the safe procedure to New Config and assign things correctly.  The Manual isn't all that clear to me.

6 minutes ago, ConnerVT said:

it has a bunch of info *except* the drive ID/slot info.  Probably why it isn't configured correctly on the server at the moment.

 

11 minutes ago, trurl said:

The file config/super.dat is where Unraid keeps your disk assignments.

 

7 minutes ago, ConnerVT said:

assign things correctly

 

16 minutes ago, trurl said:

You can see your drive assignments in several different ways in those diagnostics. Take a look in the smart folder, for example.

 

I encourage everyone to examine their diagnostics. They are text files (except super.dat), mostly settings from the webUI, logs, smart reports, and the results from several commands that tell about your hardware.

 

https://wiki.unraid.net/Manual/Changing_The_Flash_Device#What_to_do_if_you_have_no_backup_and_do_not_know_your_disk_assignments:

Thanks for that last link.  I was looking in the Troubleshooting chapter of the manual, and it wasn't really a step-by-step.  Too much to lose if I did something out of order.

 

Maybe just a nervous Nellie, but after New Config (Array) I still had nothing assigned in MAIN array slots.  I have addedthe drives back to their original slots, and have checked "Parity is already valid".  Put the "All existing data on this device will be OVERWRITTEN when array is Started" message is still a bit concerning. 

 

I am all set to start the array, correct?

 

 

Edited January 22, 20233 yr by ConnerVT

51 minutes ago, ConnerVT said:

all set to start the array

correct

Thank you  sir!  I look to be back on the road to recovery.  Thank you so much for holding my hand through this.  I've read too many threads in this forum where people blindly move forward without knowing for sure what they do is correct.  I didn't wish to be one of them.

Since it doesn't save your passwords in the backup those have to be reentered. The missing piece of the puzzle is why your backup didn't have your disk assignments. I just downloaded mine from My Servers and config/super.dat was there.

 

Check your download again and see if it contains config/super.dat. If so then why didn't it get on your restored flash drive?

This is one reason I was hesitant moving forward with the recovery.  Everything was there as expected, yet it wasn't behaving as it should.

 

I have been troubleshooting an issue with this new configuration (new 5700G processor with iGPU and new motherboard) which won't correctly display the Unraid GUI when the nVidia Quadro P400 is also installed.  I had been switching back/forth between UEFI and Legacy, GUI and GUI in Safe Mode, adding/removing P400, etc.  It has been two days of troubleshooting, and my brain can't even remember all I've done.  On the good side, the array hasn't been set to auto start, as I've been rebooting so much.  It should not have contributed to the config/super.dat issue, but may have helped avert more trouble.

 

I've taken a little break from it after seeing my data back and safe.  I does seem all is back where it was - Dockers and plugins all installed, no unexplained errors logged.  So crisis averted, thanks to your help.

3 hours ago, ConnerVT said:

Dockers and plugins all installed

Do you mean you reinstalled them? Or they were already installed when you booted? Those should have been part of config backup also. As well as any other setting you had made in webUI like settings for each user share, etc.

 

  

8 hours ago, trurl said:

And many of the files in the config folder of your diagnostics can be used just as they are in the config folder of your flash drive.

 

Settings for each of your user shares were in those diagnostics, in config/shares, for example.

I went through the entire server to see what was correct, and what was missing.  All dockers and plugins were fine, as were defined Users and Shares, and things like network configurations, etc.

 

Seems it was limited to resetting passwords (lost the password on the User for SMB access from my Win10 machine as well as root) and all of the Array and Pool drive assignments.

 

 

9 hours ago, ConnerVT said:

Seems it was limited to resetting passwords

This is by design since your passwords are not saved in My Servers.