Hi there,

 

I am trying to boot into UnRaid 6.3.3 from the flash drive setup files on the main site download page.

 

The usb drive boots fine, and I have no problem getting into command line or GUI Unraid with network automatically set up correctly and am immediately able to ping internet addresses. So far so good. Unfortunately then when I try to go to http://tower or the IP address of the server, I get nothing at all.

 

On port scanning the server nmap gives me the following output:

 

Discovered open port 445/tcp on 192.168.100.66
Discovered open port 22/tcp on 192.168.100.66
Discovered open port 139/tcp on 192.168.100.66
Discovered open port 23/tcp on 192.168.100.66
Discovered open port 111/tcp on 192.168.100.66
Discovered open port 21/tcp on 192.168.100.66
Discovered open port 37/tcp on 192.168.100.66

 

As you can see there are no web ports listed in the output at all. I can SSH into the server with no problem on port 22 which confirms there is no network issue going on. I have no errors during the unraid boot, 

 

I have been through the setup guide and documentation a million times. All it says is 'point your browser to http://tower'. There is no mention anywhere of what to do if there is no http://tower has no web server listening on it at all. Is there a troubleshooting guide somewhere I am missing that covers this? It seems a pretty big error not to mention anywhere on the documentation.

 

I'm pretty sure I am not being stupid, other people must have had this problem I am facing yet I can not find any mention of it anywhere on the forums or by googling. The only thing I found was to try running /usr/local/sbin/emhttp to try to get the webserver up but when I enter that command the cli just freezes.

 

Any help as to why this is happening, or pointing me towards some documentation which explains it would be much appreciated.

 

Thankyou very much.

Did you try   http://192.168.100.66   ?  I sortof assume you did but it was not explicitly stated.

 

Did you look at the assignment table of your router to see if tower was listed with an assigned port?  It has to be listed if http://tower is going to work. 

 

If this doesn't help, login into the command line and type   diagnostics   and that will write the diagnostics file to your flash drive.  (Look in the root of logs folder.)  Post that up with your next reply. 

 

One more thing.  Are you a new unRAID user and this is your first experience with unRAID?

Edited April 3, 20179 yr by Frank1940

6 minutes ago, Frank1940 said:

Did you try   http://192.168.100.66   ?  I sortof assume you did but it was not explicitly stated.

 

Did you look at the assignment table of your router to see if tower was listed with an assigned port?  It has to be listed if http://tower is going to work. 

 

If this doesn't help, login into the command line and type   diagnostics   and that will write the diagnostics file to your flash drive.  (Look in the root of logs folder.)  Post that up with your next reply. 

 

One more thing.  Are you a new unRAID user and this is your first experience with unRAID?

 

Hi Frank, thanks very much for your reply.

 

Yes, sorry to be vague. I did try to connect using the IP address. I am a network admin and so the protocols/net/dns area I am covered on. There is no problem in connecting to the machine using 'tower' as the hostname, the problem appears to be that there is no web server listening on either port 80 or 443.

 

This is my first Unraid experience and so I am happy to admit I am probably hitting some common pitfalls which is why I did search the forum thoroughly before posting.

 

I have included my 'tower-diagnostics' zip file as requested.

 

Thanks again.

tower-diagnostics-20170403-0615.zip

OK, I had a look at the diagnostics and the config folder of that file is empty.  This basically tells me that the config folder is empty on the Flash Drive.  I think you need to prepare that Flash Drive again.  This time be sure that you copy all of the files and folders that are in the download zip file to the Flash Drive.

 

I just downloaded the latest version of unRAID and the root of your Flash drive should have two folders (config and syslinux) in it.  The config folder itself should contain six files. 

12 minutes ago, Frank1940 said:

OK, I had a look at the diagnostics and the config folder of that file is empty.  This basically tells me that the config folder is empty on the Flash Drive.  I think you need to prepare that Flash Drive again.  This time be sure that you copy all of the files and folders that are in the download zip file to the Flash Drive.

 

I just downloaded the latest version of unRAID and the root of your Flash drive should have two folders (config and syslinux) in it.  The config folder itself should contain six files. 

 

Thankyou very much for your replies.

 

I went and looked at my flash drive, and there are definately 5 files and a directory named plugins in there. The files are named docker.cfg, domain.cfg, go, ident.cfg, network.cfg.

 

As you suggested I have redownloaded the 6.3.3 server zip file, formatted my flash drive and recopied/made it bootable just to rule it out. On boot it is exactly the same. No web server running, nothing listening on ports 80/443.

 

Is there something else that a blank config folder in the diagnostics zip could mean?

Edited April 3, 20179 yr by Ascii227

You did upzip the files when you copied them onto the drive?  (I know this may sound like a stupid question but it has happened before...)

 

What it sounds like to me is that the go file is not being run as a part of the boot process.  (In the base configuration, the go file's sole propose is to start the web sever.)

Apr  3 04:39:43 Tower kernel: FAT-fs (sda1): Can't find a valid FAT filesystem

I would suspect a problem with the USB port if the flash drive looks OK on another computer. Try another USB port, preferably USB2.

Probably the flash drive isn't formatted correctly. I'd use a different tool to format it and try again.

Thankyou very much Trurl, your point made me go and check the formatting on my USB Drive which led to me realising it was NTFS formatted, Doh!

 

@Jonathanm Thanks as well for the reply you are indeed correct.

 

I realise now that I completely skipped over point 2 int the setup guide - "Format the device using the FAT32 file system." After reformatting FAT32 and trying again it worked with no problems.

 

However I did find it very strange that unRAID fully booted and gave me no errors at all on the NTFS drive which is what led me to ask questions on the forum. Had the OS pointed it out to me it would have been the first thing I did.

 

Thanks a lot for helping out an unRAID beginner like myself so quickly, it looks like a fine and friendly community from where Im sitting.

5 minutes ago, Ascii227 said:

However I did find it very strange that unRAID fully booted

Well, that's a byproduct of how unraid is designed. It doesn't really run off the USB, it only stores the configuration files and the packed OS image on there. When it boots, it unpacks the entire OS into RAM, and runs from there. It couldn't find a valid configuration, or even the commands to start the webGUI, because it assumes the drive is FAT32. Theoretically I suppose it could be written to support NTFS, but since linux and NTFS don't really work well together it would probably open up more issues than it would solve.

It is also possible that the USB disk has not been labelled 'UNRAID' which can cause the symptoms described.

15 minutes ago, itimpi said:

It is also possible that the USB disk has not been labelled 'UNRAID' which can cause the symptoms described.

Same symptoms, different message in syslog.