Hi guys

 

Let me give you a brief background. I was running x4 3.5" HHD and x1 2.5" HDD (cache drive). A few weeks ago my M/B and CPU fried, just stopped working. So I replaced the M/B and CPU (higher spec). My new M/B take only takes x2 Memory slots (had 16gb, now have 8gb) and x4 Sata ports (previously 6, so I can't use the cache drive).

 

After adding the new components and using the same setup, I can't view the GUI.

The server boots and I can get to the Unraid terminal and GUI. The IP shows on the network but I can't access the web gui.

 

I have tried the following topics with no luck.

and updating the GO file to specify the port to use.

 

I am using unraid 6.2, I have the full version. Booting of a usb drive.

type diagnostics at the command line, then poweroff. Put your flash drive in your PC and post the diagnostics zip from it.

Just saw your comment now... but lucky I backed up the flash.

 

I removed all the sata connections and load a new copy of Unraid. Works like a charm.

 

Is it possible to use existing hdds with data on a new Unraid install?

@trurl, attached are my logs.

Had that old install on flash. No hdds connects. New M/B and CPU.

tower-diagnostics-20170804-1005.zip

Boom.

 

Fixed it. Here's my solution:

 

1) Unplug all drives.

 

2) Browse the flash using your computer. (make a backup just incase)

 

3) edit \config\network.cfg. Set to default values. (I got the defaults from looking at a fresh install)

# Generated network settings
USE_DHCP="yes"
IPADDR=
NETMASK=
GATEWAY=
BONDING="yes"
BRIDGING="yes"

 

4) edit  \config\go. (xx being the port)

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp -p xx &

 

5) Put the flash into the NAS and boot up. Select the GUI. Using Firefox access localhost:xx. Then boom. .

 

6) Take a picture of the "Main" tab to identify the order of your drives. Then switch off.

 

7) Setup all your drives in the correct order and you're done.

 

This worked for me. Not sure if it will help you

Not sure what your problem was (is?), but ordinarily it isn't necessary to specify a port. The default http port is 80 and that is what unRAID uses by default. So, if you don't change the go file you would go to http://tower (or whatever you have named your server).

 

And of course, going to localhost:xx will only work on the localhost; i.e., using the Firefox GUI on a monitor connected to unRAID. And even there it should be possible to use the default port.

 

So, there shouldn't have been anything to fix, and your "fix" shouldn't be necessary.

That's the thing. Previously the port didn't open, step 4 didn't help. But adding step 3 made a difference.

Sent from my ONEPLUS A3003 using Tapatalk

7 hours ago, Jarrodr said:

That's the thing. Previously the port didn't open, step 4 didn't help. But adding step 3 made a difference.

Sent from my ONEPLUS A3003 using Tapatalk
 

So you are saying that your "fix" was setting network.cfg to the default. Some of your other steps could actually cause problems rather than fixing them so I would recommend other users avoid this.