looks like your flash drive is either full or still has some issues. Try using a different flash drive.

 

The flash drive is newly formatted and prepped for 6.2.4.

 

I've tried using a different drive but it doesn't work since the key is locked to the previous drive.

 

If tower.local does not resolve. access the web ui using IP address.

 

Should've mentioned I tried the IP address next, it didn't work either.

You are running a trial - I'm fairly sure you can ignore the Trial.key file and apply for a new trial on the new usb flash drive.

I'm sure something is wrong if the WebUI is not accessible, but you can still ssh in.

 

Thank you for the suggestion.

 

I put it on an old Sony USB 2.0 16GB flash drive and got a new trial key.

 

The trial key installed fine. It never installed right on the Sandisk Ultra Fit even though I got it to work after manually copying the trial key over. I'm beginning to think it is the flash drive.

 

So I can boot into a clean unRAID install with the new drive.

 

But when I copied the /config files over (keeping the new trial.key on the flash drive), I have an "Invalid Trial Installation."

 

Invalid Trial Installation

Flash GUID: 054C-02A5-4001-202110005022
Registered GUID: 054C-02A5-4001-202110005022
Registered to: Trial User
Registered on: Tue 08 Nov 2016 09:02:15 AM EST
Expiration: Thu 08 Dec 2016 09:07:14 AM EST

 

I paste the trial.key url into the UI and click on install, I'm informed:

 

Downloading https://keys.lime-technology.com/unraid/16c446e0dfa45ca757e64f15bf5997723b00f0bd/Trial.key ... 
Installed ...

 

And I'm still getting the invalid installation.

 

Can someone tell me which are the /config files I can transfer between flash drives? I'm assuming something in my old config is causing this.

I think only the key file should be involved. Do you have multiple key files in config?

No I don't, just one key file.

 

I have a new install of unRAID on the new flash drive, with old /config from previous set up, making sure I have the new key file that's locked to the new flash drive.

 

What's confusing me is that in the error msg, Flash GUID and Registered GUID match.

 

I have not been able to make any headway in this and nobody seems to know what's causing this. I'm beginning to think I should redo the whole array, I have almost nothing to lose since I'm only 2 weeks into this and most of the time was spent reading and setting stuff up.

 

If I plug in the new flash drive and set everything up fresh, will my hard drives be formatted and prepared automatically, knowing that everything on them will be lost?

 

I'm just going to have a fear of this thing repeating again further down the line especially not knowing what's causing it and not being able to fix it.

 

I don't even know which flash drive to trust! How will I know the new flash drive I'm trying now is dependable? Should I purchase a new flash drive? I have a Sandisk Cruzer Fit USB 2.0 32GB in my Amazon shopping cart.

Ok this doesn't make sense at all.

 

I just formatted my new flash drive, put unRAID 6.2.4 on it. I copied my old /config folder over.

 

This time there is no key on the flash drive.

 

Booted into unRAID. The UI tells me it is an INVALID INSTALLATION again.

 

I pasted my key's URL into the text box, clicked on INSTALL. I get a popup telling me it's installed.

 

But the UI is still telling me invalid installation.

 

So there's something in /config that contains something about my old key that's messing with the new install.

 

Attached log.

tower-diagnostics-20161108-1843.zip

Yup, I can verify that something in my old /config is causing invalid installation even though I have the right key file, I just repeated the whole process again.

 

tower-diagnostics-20161108-1903.zip

unRAID will not format your data drives. Just make sure you don't assign a data disk to the parity slot.

Well I'm gonna rebuild the whole thing since nobody can figure out what's wrong. I didn't screenshot the drive assignments, did not know to do this until I started researching on my problem, would help if this was in the setup instructions.

 

So can I simply plug in the flash drive with the new trial key and do the drive assignments? What happens to the drive and existing data, it'll get overwritten eventually? There's nothing I need to do like a format to start over?

Well I'm gonna rebuild the whole thing since nobody can figure out what's wrong. I didn't screenshot the drive assignments, did not know to do this until I started researching on my problem, would help if this was in the setup instructions.

 

So can I simply plug in the flash drive with the new trial key and do the drive assignments? What happens to the drive and existing data, it'll get overwritten eventually? There's nothing I need to do like a format to start over?

Assign all drives as data drives. unRAID should recognize all but one as containing data. The one that doesn't contain data is the parity drive. Post a screenshot when you have assigned all the drives showing Array Devices and Array Operation.

Before you made that post I had gone to Tools, did a New Config, went to Main, assigned the drives arbitrarily, and clicked on Start array.

 

It is now almost 2hrs into "Parity-Sync/Data-Rebuild".

 

What I didn't expect is when I assigned the drives and started up the arrays, Shares appeared in the UI but settings like Split Level is gone. User is gone. Plug-ins like Community Applications and Fix Common Problems are gone.

 

I didn't think those stuff would show up since the /config folder on the flash drive is fresh.

 

But dockers are around; they started up and did the things they were suppose to do (CouchPotato, Sonarr, etc).

 

Dockers are kinda weird. They're all missing their icons and when I click on them, the Web GUI option is missing from the menu:

 

 

What should I do next? Let the Parity-Sync/Data-Rebuild finish running? Is this simply gonna rebuild itself and it'll run like normal again? Or should I continue with redoing everything after the Parity-Sync/Data-Rebuild is done?

I'd recommend a full redo since its kinda obvious a number of your config files/ etc stuff stored on the old USB is kinda not there. The dockers get preserved somewhat since they are on the cache drive, which seems to have survived intact. I don't remember where the now missing icons are stored though.

 

If you copied the shares dir over, the share definitions are mainly preserved, but not necessarily the details which would be inside the share cfg files.

 

Suggest you disable dockers under Settings|Dockers, delete the docker.img file and start over.

I'd recommend a full redo since its kinda obvious a number of your config files/ etc stuff stored on the old USB is kinda not there. The dockers get preserved somewhat since they are on the cache drive, which seems to have survived intact. I don't remember where the now missing icons are stored though.

 

If you copied the shares dir over, the share definitions are mainly preserved, but not necessarily the details which would be inside the share cfg files.

 

Suggest you disable dockers under Settings|Dockers, delete the docker.img file and start over.

 

Yup I don't think I can trust the current setup.

 

Can you help me out with some steps?

 

I stop the Parity-Sync/Data-Rebuild?

And then go into Settings / Dockers, disable that.

Go to /system/docker and delete docker.img.

 

What do I do after that? There's stuff on appdata and all the drives.

 

What's the equivalent of a format to redo everything?

Don't bother stopping the rebuild.

Stop docker

You can just delete the contents of the appdata share

You can do the same for all the shares if you want and nuke the shares to reset everything.

 

Normally the tools | new config is used to do a reset of the array, while simply formatting the usb drive and reinstalling does most of the work.

but you definitely need to delete the dockers.img to clear out the docker images.

 

<I've never had to start over so I'm not sure - Hopefully somebody else can point you the way>

Post another screenshot showing Array Devices and Array Operation.

Post another screenshot showing Array Devices and Array Operation.

 

Is this it?

 

 

Here's the dashboard:

 

 

Also attached logs if it helps.

tower-diagnostics-20161109-1920.zip

That all looks OK. Looks like disk2 and disk3 are mostly empty. Is that what you expect? Just wondering since you said you arbitrarily assigned your drives. I was concerned that you might have accidentally assigned a data disk to parity and overwrote your data.

 

You just need to go to Settings - Docker Settings and disable the Docker service then delete and recreate a fresh docker.img.

 

Then you can proceed to set things back up again. Did you get your key straightened out?

So the first time I set up unRAID, I simply selected the first drive from the dropdown list for Parity, and second drive for Disk 1, until they were all assigned.

 

I did the same the second time I set up unRAID, maybe I lucked out and they're in the same sequence on the dropdown list.

 

Disk 2 and 3 could be empty because I don't have enough data to require them yet. Or does unRAID automatically spread all data to all disks?

 

Some settings like Split Level and AFP and User are gone, I'll set those up again.

 

The key seems to be functioning for now, it's newly registered to an old Sony USB 2.0 16GB flash drive I'm testing.

 

I'll do a few reboots and see what happens, previously it becomes unregistered after a reboot—could be an issue with the Sandisk Ultra Fit I had before?

 

I have a suspicion this whole thing is because of the Sandisk Ultra Fit. From my very first install unRAID gave me an error-1 when I tried to install key with the URL.

 

So besides deleting docker.img and setting up the Dockers again, I don't have to do anything with the disks? (Coming from a typical experience of formatting and reinstalling OSes)

 

Should I delete everything in /appdata too?

 

 

unRAID fills up disks according to the user share's allocation method, split level, and min free settings. There is Help on the page to explain all that.

 

You can delete appdata if you want to start over with it. But you can keep it if it has anything you want to keep, such as plex library. You would just need to setup your dockers again like before so it would see the appdata.