Hi all,

When I loaded unraid yesterday(Friday) it worked fine. Then once I let it check parity on the system for the first time and then shut it down through the web gui so i can move it to my rack from where i had assembled the server after the parity check had finished. It now is giving me a hard time. not wanting to be accessible from any computer in the house. no web gui, no access through the on server gui. It was a clean install on recommended flashdrive (sandisk cruzer fit) (fat32 formated). 

my server specs are 

supermicro mb x11ssh-f

 crucial 16gb ecc ram single stick (mb manufacturer recommended)

(4x) 8tb seagate ironwolf hdd for storage

250gb wd blue sata ssd 

 

I am pulling my hair out not that I have much trying to figure out why I cant get the server back up and running. internet connectivity is available through my desktop computer when I link it to my 4glte Samsung s7 cell phone.

You need to supply way more information - collecting and posting the diagnostics data would give us more information about what the system is doing.

 

Or just connecting using a console - monitor+keyboard - and check if the system has received any IP and if the system detects that you have the network cable connected. By the way - have you verified that you don't have multiple network cards in the system and have connected the cable to the wrong connector? Lots of motherboards have dual connectors.

Yes I have an iP address. Not sure how to get the other information y'all need. It does see the cable and my switch sees it with same ip as it shows on the computer. My board has dual Ethernet and an impi location. Yes the cable is plugged into the right Ethernet jack.

 

I have built all my own computers since early 2000s and this is my first enterprise based system I have built.

Edited March 25, 20188 yr by Travis McCann
Need to add info

boot into non-gui mode, and once it hits the Login prompt, login and type

diagnostics

  If that fails

cp /var/log/syslog /boot/syslog.txt

and post the file

 

If none of that works, then take a picture of whats on the screen

Will do once I get home this afternoon. Thanks for the information.

Here is the diagnostic file From my system.  Can y'all help explain what I am looking for in it so I can understand them and see what the problem is also?

tower-diagnostics-20180325-1411.zip

Edited March 25, 20188 yr by Travis McCann

Your machine doesn't find any directory with a license key:

Mar 25 14:11:19 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:20 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:21 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:22 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:23 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:24 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:25 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:26 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:27 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:28 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key

Do you have any directories /boot/ and /boot/config/ ?

Like the previous post, you do have key-errors. You can find that from the diagnostics,  in the folder logs there is a file syslog.txt that has the system-log. At the end, there are a lot of errors regarding the key-file.

At 14:11:16 it read it once properly, but many other times it failed.

If I then look at the folder system, in the file lsusb.txt (which lists the USB devices) it seems that there is no name listed for the device 258a:001 but this USB list specifies it as a USB keyboard. Try connecting the unraid USB-key not to your keyboard, but in/on the computer itsself, and not on the USB 3.0 port, which can have issues too.

edit: I may have read that wrong, as in you didn't plug it in the keyboard. But try a different port anyway, the one you are using seems to have speed-issues.

Edited March 25, 20188 yr by Wody

I have no /boot/ and no /boot/config/ directories. I have tried many usb locations on the server. the keyboard does not have a usb pass through on it. I have no hubs installed either just usb on the mb. I have the trial licence if that makes any difference. 

Since you have seem to have USB issues, unRAID can't verify your key and doesn't mount or start anything. The relevant section of the logfile is here:

Mar 25 14:11:14 Tower emhttpd: shcmd (9): modprobe md-mod super=/boot/config/super.dat
Mar 25 14:11:14 Tower kernel: md: unRAID driver 2.9.3 installed
Mar 25 14:11:14 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Mar 25 14:11:14 Tower kernel: md: could not read superblock from /boot/config/super.dat
Mar 25 14:11:14 Tower kernel: md: initializing superblock
Mar 25 14:11:14 Tower emhttpd: error: get_key_info, 579: No such file or directory (2): fread: /boot/config/Trial.key
Mar 25 14:11:14 Tower emhttpd: Unregistered - unregistered (ENOKEYFILE)

So, something happens between 14:11:03 (when it mounts the drive) and 14:11:14 when it can't read it anymore.

Which means, try a different port, if that doesn't work, verify the file system, or try to copy the config folder to a different computer, format the drive, use the USB-creator and copy the config folder back.

Well I did the basic mistake of using usb 3 ports cause the mb didn't seperate the 2 and 3's by color. So fixed that now it still won't log the trial key as active.

Glad that part works now! Any messages? Maybe some new diagnostics would help, to see if the log-file has anything.

Will put new diagnostics up later tonight when I get home.

latest diagnostic file. still no connection to web when nothing has changed on the network since Friday, 

tower-diagnostics-20180325-2025.zip

Darn, still same errors. If you're sure you are using an USB 2 port now, what filesystem did you format the Cruzer USB with?

 

On second thought, I also found another error related to USB:

Mar 25 20:24:48 Tower kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload-210)

From googling, this seems an error in the BIOS, which is fixed by a version 11.1 of ACPICA, I have no idea what is currently used. There is a kernel bug report but I have no idea if it is included already or not. Maybe @limetech can tell us.

 

Also, you are currently using BIOS 2.0b, and since you're having issues, try flashing to BIOS revision 2.0c which is available at the Supermicro site (on the right, Update your BIOS). I have no idea what they fixed in that one, but since you're having issues, it shouldn't hurt. I'm hoping that will fix everything.

 

Edited March 26, 20188 yr by Wody

The ACPI error was fixed by the now removed bios 2.1, wait for the new bios to fix it, but that error won't cause any problems.

Could I just reformat the flash drive and reload it with the unraid software as well as reset the mb to factory settings help with my problems. Or could I just have a bad flash drive causing all my problems? And since I am only on a trial key it couldn't hurt to go grab a few more unraid safe usb drives?

 

On a side note could the fact that the flashdrive is a usb 3.0 model have anything to do with my problem?

Edited March 26, 20188 yr by Travis McCann

If you copy the config-folder with your key, then reformat and reload, and copy the config folder back might work. You'll want to at least save your key, since you might not get another for that USB (I'm not sure).

And yes, 3.0 ports or drives can cause issues, so it is possible. So, do try a 2.0 drive and port.

I got a lexar usb 2.0 16gb flash drive and loaded the initial boot files. I also got a new trial licence for the new drive. so all looks good so far. I will update once The parity rechecks and the system stays stable for over 12hrs. 

Okay bought pro license fixed that issue. Now it won't connect to the internet and I can only get on the server through the numeric address. 

Glad to hear the USB-thing got resolved. In your previous diagnostics, you were using DHCP and getting an address.

Try something like ping google.com and if that doesn't work, try to ping googles nummeric IP-address instead.

Since you can reach the server, even if it is just by IP-address, it could be something in the network is confused, so restarting the gateway/router may help.

 

I've seen the not-able-to-reach-by name on my own server with older unRAID versions and older windows, so I've set a static IP-address on my unRAID server and normally connect to it by that, but I noticed with unRAID 6.5 and windows 10 I can use the Tower-name as well. In the past, when I had issues like this, I've also turned off all my devices and computers on my network, and then started first the router, then unraid and then computers to make sure everything started fresh and didn't have old data or something.

 

Your system basically needs two things configured to reach internet (besides the obvious - having IP configured on the network interface the network cable is connected to).

 

1) A DNS so it can translate host names to IP. Easy to test if you can ping 8.8.8.8 but not ping www.google.com.

 

2) A default route that points to your router so any unknown IP gets sent to the router that can forward it out into the world. If you can ping IP inside your home (equipment within the same local network as the IP of your unRAID machine) but not 8.8.8.8 or global IP then your machine most probably doesn't have a default route.

Edited March 29, 20188 yr by pwm

You should also go to     Settings   >>>   Network Settings    and set the DNS servers to IPv4 IP addresses.  IF you don't know any DNS servers IP addresses, you can use Googles DNS Severs (anywhere in the world) of 8.8.8.8  and 8.8.4.4  

 

You might have to set the IPv4 default gateway:      (in your case) to      192.168.0.1     (Don't do this unless you still can't gain access to the Internet after assigning DNS server addresses.)  

My problem is I live in a rural area and have to connect to the internet through tethering to my cell phone. The internet providers feel it's not profitable to service my road with full internet land lines.

 

How would I set my unraid box to see internet before my computer that is my primary tethered device.

Edited March 29, 20188 yr by Travis McCann

10 minutes ago, Travis McCann said:

My problem is I live in a rural area and have to connect to the internet through tethering to my cell phone. The internet providers feel it's not profitable to service my road with full internet land lines.

 

How would I set my unraid box to see internet before my computer that is my primary tethered device.

 

It might be a good idea to give a simple diagram that shows how your network is configured?

 

Tethering is not normally an issue as long as:

• The unRAID server is connecting to the tethering service.
• you are using DHCP on the unRAID server so the tethering service provides the IP and Gateway addresses consistent with the tethering
• you set unRAID to use the google DNS servers (8.8.8.8 and/or 8.8.4.4)

the second step will not be necessary if the tethering process also provides a DNS address.    However it often does not, and even if it does then using the Google DNS servers will work regardless.

 

if you have a network where the unRAID server has to tunnel through your PC to get to the Internet then we need more details about what OS is running on the PC.