Hi guys.

 

So, i have run into a rather frustrating issue. I am no longer able to access my unraid box GUI since updating from 6.1.9 to any of the 6.2.x versions that are currently out. I have been using v6 since it came out and have had no major problems until I ran into this one. When i initially ran into this problem, i just rolled back to 6.1.9 and kept chugging along, but i have since copied everything off my unraid server and am wanting to "start fresh" with it. I have tried all of the 6.2.x versions that are currently out, and all of the beta releases with exactly the same issue. I can revert back to a fresh 6.1.9 and hey, what do you know, it boots right up.

 

The only error message i am getting is ERR_CONNECTION_REFUSED. I have tried releasing its dhcp lease, changing the ip the MAC is associated with on my router, putting :8080 after the ip, http://tower wont connect either, giving off the same ERR_CONNECTION_REFUSED.

 

I am able to telnet into the machine, and from there i can ping google.com, i am able to ping the IP of the box from my desktop, but no browser lets me connect to the web GUI. When i start unraid 6.2.4 with GUI (screen etc plugged directly into the machine) i get exactly the same error message in the firefox window that opens up.

 

Do you have any suggestions on how to fix this, or what may be causing the issue?

 

Thanks in advance!

No ideas off hand, but there were a lot of networking changes in v6.2.  Make sure you check them out in the Additional Upgrade Advice.

Thanks for the quick reply!

 

I have cables attached to all 3 Ethernet ports on my mobo and I am able to tenet into the box using the IP my router is giving unraid, but no GUI.

 

ill continue to read through the posts in the link you posted

 

Is there any value in posting the syslog if its a totally fresh os copy on the usb?

Can you access the GUI by using the IP address instead of //tower?

 

Also, unless you've change the default port emhttp runs on by modifying the "go" file, the UI is on port 80, not port 8080 (unless you've got unMenu installed and running which really isn't necessary under v6)

 

Also, since you are able to telnet in, post the diagnostics file

 

diagnostics

No matter what i try, i am not able to see the diagnostics .zip file on the USB when i plug it into my desktop, so i ran this command: tail -f --lines=1000000 /var/log/syslog and have saved and uploaded the output of that. Is this useful? Sorry, i am not the best with linux, and/or command line, so without a GUI i struggle to do even basic tasks....

 

I have tried all of the IP's it could be being given by my router, with many different port options that people suggested in other threads, but no luck. I have also tried the ip's in the file i uploaded and all of them either timed out, or had the same ERR_CONNECTION_REFUSED as i usually get.

 

I appreciate your help!

syslog.txt

That syslog covers roughly 10 seconds from when the system started booting up, and at the time there's no evidence that emhttp even tried to load.

 

Have you tried waiting a minute or so after booting up to access the UI?

 

What is the contents of the file config/go on the flash drive?

i followed the instructions on this website

 

https://lime-technology.com/wiki/index.php?title=Troubleshooting#Capturing_your_syslog

 

and i cant see the syslog.zip file on the usb.

 

No matter how long i wait (left it a couple hours when i was at work) it wont load the GUI...

 

Here is the contents from the go file:

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

Best suggestion right now would be to grab another flash drive, set up unRaid on it and try booting from that one. 

 

You don't need to set up the drives or anything.  The key here is to see if unRaid boots properly off of the new stick completely 100% stock.

will i run into any issues with my license key being associated with the original USB?

 

We're just trying an experiment right now to see how unRaid works on the new stick.

 

If it does, then you'll either copy the .key file from the original, reformat and set up the original stick again (and copy the .key file back on to it) or transfer the registration over to the new stick.

 

BTW, what size is the original stick?  Is it formatted as FAT32 or exFAT?

Its a PNY 32gb usb formatted to FAT32. Ill tray a couple of USB drives i have laying about, i remember it being really picky when i initially installed unraid so i bought the 32gb one and its worked for a while.

If it was >32gb then its a PITA to format at FAT32.  Hence why I asked

so i just copied to OS onto a FAT32 formatted 64gb PNY drive, and it flew through boot up and the GUI loads. I find that very strange as i thought it was a hassle to deal with FAT32 over 32gb...?

 

Im going to try copying this usb drives contents back to the original, and also with a couple of other usb drives i have.

 

It works with a whole host of other usb drives. One thing i did notice during the bootup process was the line:

 

waiting for /dev/disk/by-label/UNRAID (will check for 30 seconds)

 

This only appears on my original USB drive, which i just put through exactly the same steps as the other usb drives i have tested with, all from different manufacturers and of differing sizes.

 

Now to get my license transferred....

 

Thanks for your help @squid

 

Now to get my license transferred....

 

Copy the .key file from the original stick to the replacement (config folder).  unRaid will complain about it and walk you through the transfer process

Yup, followed the process through and am now creating shares. Is there any benefit to XFS over btrfs? Iv always run mine as btrfs but i have always wondered...

Yup, followed the process through and am now creating shares. Is there any benefit to XFS over btrfs? Iv always run mine as btrfs but i have always wondered...

btrfs has some great features which may soon be leveraged, but it is also very fragile when it comes to power-loss and unclean restarts.  I personally use XFS on all the drives.  But if you want a cache-pool then you have no choice but to use btrfs on the cache.