A thunderstorm went thru today and we lost power for three hours.  When the power returned the Unraid restarted like normal BUT it now shows a wrong configuration AND it's running as if it were the free "basic" version with only three drives showing.  I looked at the flash drive and there is still a config folder and in it I see the pro2.key file.  Any ideas what went wrong and how to get it back.

Perhaps something got corrupted.  From a telnet session, can you cat /boot/config/pro2.key?

 

Also, check the Devices page for clues - it should tell you whether it found a key file, and whether it matches the GUID of your flash drive.

You also might try running Windows scandisk/checkdisk on the flash drive.

There is something really weird going on here.  I looked at the devices tab and here is what I see:

 

Flash Vendor: LEXAR MEDIA

Flash Product: JD FIREFLY

Flash GUID: 05DC-A560-7808-143744290706

Registered GUID: 04E8-0100-0000-137315402650 Wrong

Registered to: Richard P. Harvey

 

Obviously you can see that the key looks to be for a different flash but trust me this is the right flash.  I thought maybe the key somehow got corrupted so I went back to the original 2006 email from Tom and copied from it the correct key that is bound to the GUID ending in 706.  I first deleted the key off the flash drive just to make sure it was GONE, then I copied the nice fresh key to the config folder and still I get the same error as noted above.  Here is the text from Tom's original 2006 email:

 

The USB Flash device to which Pro2.key is bound is:

 

05DC-A560-7808-143744290706

 

As you can see from the above devices tab "cut and paste" action the file "pro2.key" is indeed bound to that very flash and putting a fresh copy of that key file yeilds the same mis-match error.  I must admit that I'm at a total loss here.

There is something really weird going on here.  I looked at the devices tab and here is what I see:

 

Flash Vendor: LEXAR MEDIA

Flash Product: JD FIREFLY

Flash GUID: 05DC-A560-7808-143744290706

Registered GUID: 04E8-0100-0000-137315402650 Wrong

Registered to: Richard P. Harvey

 

Obviously you can see that the key looks to be for a different flash but trust me this is the right flash.  I thought maybe the key somehow got corrupted so I went back to the original 2006 email from Tom and copied from it the correct key that is bound to the GUID ending in 706.  I first deleted the key off the flash drive just to make sure it was GONE, then I copied the nice fresh key to the config folder and still I get the same error as noted above.  Here is the text from Tom's original 2006 email:

 

The USB Flash device to which Pro2.key is bound is:

 

05DC-A560-7808-143744290706

 

As you can see from the above devices tab "cut and paste" action the file "pro2.key" is indeed bound to that very flash and putting a fresh copy of that key file yeilds the same mis-match error.  I must admit that I'm at a total loss here.

Do you have another file in either the root of the flash drive, or the config folder ending with a .key extension?  It does not really look for the word "Pro", it only looks for the .key extension.

 

As per the release notes for 4.5beta6, as a new "feature" the .key file is looked for as follows:

After looking in the 'config' directory on the Flash for the license key file (for backward compatibility), if not found, unRAID Server OS will look in the root of the Flash.  This allows easier backup/restore of the 'config' directory contents.

 

I'll bet you have two key files... (or two with a .key extension)  Just rename one to have a different extension.

I only wish it were that simple, sorry only one .key file anywhere.....

 

 

Oddball situations call for oddball suggestions!  I wonder if it's possible that your USB key has developed the flash equivalent of a bad sector - since the key is a generated hash, I imagine a single bit error could manifest itself in a variety of ways, including dramatically changing the apparent GUID.

 

Perhaps deleting the old key file before replacing it allowed Windows to write the good copy back to the exact same sectors that the previous copy had occupied, thus effectively recreating the error.  You might instead try renaming the key file on your flash (to .bad, for instance), and then copying it over anew from the original email.  Or if you have a binary file compare utility, try comparing the key file on the flash with the one extracted from the email.

 

Did you run scandisk over the flash drive as suggested, btw?

 

Oh and as a final sanity check, since this is apparently your second key file, was 04E8-0100-0000-137315402650 the GUID of your first one by any chance?

Well we may never really know what happened but it's corrected now.  Started from scratch, formatted the flash again and installed everything as if new including the key from the original email and it came back up as Pro again.  Had to be some sort of coruption ....