long story, left me beelink s12 off for a few weeks and couldnt get server to boot.  in the process of finding out it was just a problem with cms and legacy i ended up formatting my usb and reinstalling unraid from back up.  upon doing this i the server is still not accessible.  i did a fresh install to make sure the problem was from the unraid side not hardware/cmos etc.. fresh install boots fine. went back to install from backup and i get this.  sorry for quality, since i can't access via network this is what im doing. i dont mind starting over, as i havent put anything of importance on the server but want to get this for my own understanding incase i need to restore after this is live.  thanks for any help.

 

Edited April 23, 20251 yr by ConradA

Looks like the go file is missing, please post the diagnostics.

ok well oddly this is what happened

i moved the file over to my desktop tried to upload it here but the forum wont allow me to, probably because the file is 0 bytes in size.  i tried to open the file with 7zip

That confirms the go file is missing, restore it from the stock download zip.

you mean start from a new install?  is this confirmation that there is something wrong with the original back up. (i have tried restoring from backup multiple times).  Also, if there was data at stake, which there is not in this case, would this mean a complete loss of data?

The go file should be in your config folder on flash, in the config folder of your flash backup, or in the config folder of a fresh download.

 

Just put the go file where it belongs and reboot.

3 minutes ago, ConradA said:

you mean start from a new install?  is this confirmation that there is something wrong with the original back up. (i have tried restoring from backup multiple times).  Also, if there was data at stake, which there is not in this case, would this mean a complete loss of data?

Not quite.    You are being asked to download the zip file for the Unraid release you are using and then extract the config/go file to that location on the flash drive.   It appears the backup was incomplete and is missing that file.

ok,, i understand, in the process i noticed there is also no ident.cfg or network.cfg.

I transferred the go file, it did boot and is now accessible over the network, but is behaving like a new install, none of the apps or plugins are populating.  

i can see that there are plugins in the config/plugins folder, the drives from previous array are showing up as unassigned devices. 

 

If you don't have a good backup, you will need to reassign the devices and reconfigure the server:

 

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

okay, i need to work the next 5 days but will attempt to recover drives after that. 

ok finally got back to it.  I tried method #2 of mounting disks to determine which was parity.  i noticed that the second was not mountable but then i did the same in reverse and it turns out i can mount either depending upon order that i mount using unassigned.   since this did not give me a clear answer to which was parity i used method one and attempted to mount both disks as data disks.  To my dismay both of the disks mounted?!  both appear to have the same data on them and folder structure on them. again no data at risk just trying to learn.

 

You have a degenerate case, where in a 1 parity, 1 data disk system, the parity disk would contain identical bit-for-bit information as the data disk. 

ok so i am safe to assume I can move forward and assign one as parity one as data and rebuild the array?

 

You don't even need to rebuild anything.

 

New Config with one disk as parity and the other disk as disk1, check the parity valid box before starting the array.

And also run a parity check after, a few sync errors are expected.

ok a little nervous about this step so just  want to confirm:

 

 

im going to do this^ correct?

______________________

i think i could have just started the array as it currently is but since i had assigned both as data previously(to search for parity disk), i cant seem to move back as it believes one is missing?

 

 

 

 

4 minutes ago, ConradA said:

going to do this^ correct?

Then after you Apply, it will take you back to the screen with the disk assignments, and it will let you reassign disk2 as parity.

 

Then, check the parity valid checkbox and start the array.

 

12 hours ago, JorgeB said:

And also run a parity check after, a few sync errors are expected.