Attempting to upgrade via the plugin on 6.2.4 to 6.3.2, but failing.

 

I have tried to reboot the machine, but when I go to download the update, I get the following error:

plugin: updating: unRAIDServer.plg
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.2-x86_64.zip ... failed (File I/O error)

plugin: wget: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.2-x86_64.zip download failure (File I/O error)

 

I also tried to download the latest 6.4.0 and simply replace bizroot and bzimage, but that wouldn't even let the system restart.

 

Are there additional logs that would be helpful in troubleshooting this?

 

Also, is it odd that the plugin updater offers 6.3.2 and NOT 6.4.0?

Edited April 6, 20188 yr by nautarch

If you download the 6.4.0 release you will need all of the bz* style files to be copied to the flash.

31 minutes ago, itimpi said:

If you download the 6.4.0 release you will need all of the bz* style files to be copied to the flash.

I moved all of the bz* files across and restarted. Still doesn't come up. 

Bumping for help

On 1/14/2018 at 2:03 PM, nautarch said:

Still doesn't come up. 

What does happen?  What appears on the locally attached monitor?

 

 

FInally got a monitor hooked up  It looks like it loads up, but network card and/or network is not being recognized (no lights on the ethernet and can't ping it)

 

I've attached the log file. Thanks for the help - hopefully can get this up and running.

tower-diagnostics-20180405-1957.zip

Your NIC starts.

Goes Promiscious

Uses a 1536 MTU

Gets a IP of 192.168.122.1

Sets itself to 192.168.122.1

Netmask of 192.168.122.1-.254

Gets a 1 hour lease time.

Reads /etc/resolv.conf

Uses DNS of 129.168.0.1 (which is out of the network)

looks in default.addnhosts - which is like a static DNS server

looks in default.hostsfile

Finds nothing, can't reach network - shuts itself down.

 

 

So post your flash\config\network.cfg

Weird, it should be a static IP of 192.168.0.194.

 

Network.cfg attached.

network.cfg

You are telling unraid that it's IP is 192.168.0.194 and it should use a gateway of 192.168.0.1

 

As I'm looking through the logs your system is grabbing a DHCP Ip address of 192.168.122.1

 

Do you have 2 seperate networks in your LAN?

 

Did you keep a copy of the old config from the flash drive? Might be easier to go back and look at it that way.

 

Do me a favor, open up a command/powershell window on your main pc and do a ipconfig >> %userprofile%\desktop\ipconfig.txt and upload that file (which will be on your desktop

and try these for dns servers 6.6.8.8 and 8.8.8.8 (both google dns servers)

That was my config file from my flash drive before I did the manual backup (I moved it over after copying 6.4.0)

 

DNS is currently 8.8.8.8 and 8.8.4.4

 

What is 6.6.8.8, i don't recognize that as a google DNS

 

ipconfig from my computer attached.

 

 

ipconfig.txt

Edited April 6, 20188 yr by nautarch

You're correct 6.6.8.8 is because I'm stupid. I'm using one google and a verizon (huh, really? Verizon? I thought I had a level3 DNS. crap.   )

 

Now I'm confused. Your network config is good, it's using your router as a DNS, and your network is correct...

 

I've got

USE_DHCP="no"

 

You have

USE_DHCP=no

 

Do the quotes count do you think? Every setting/ip address on my config are in quotes.

 

I also have

 

BONDING="no"
BONDING_MODE="1"

Edited April 6, 20188 yr by dimaestro

my full network config

 

# Generated settings:
USE_DHCP="no"
IPADDR="192.168.0.100"
NETMASK="255.255.255.0"
GATEWAY="192.168.0.250"
DHCP_KEEPRESOLV="no"
DNS_SERVER1="192.168.0.250"
DNS_SERVER2=""
DNS_SERVER3=""
BONDING="no"
BONDING_MODE="1"

 

added the quotes, still no joy.

 

I also deleted the previous static IP on my router that was assigned to the old MAC address from my previous NIC (just rebuilt tower) and reassigned it to the new mac address at eth0 from ifconfig.

 

failed again and still no lights on the ethernet cable.

 

even stranger is when i try to ping 192.168.0.194, it says 192.168.0.52: destination host unreachable

 

virbr0 is looking for inet 192.168.122.1

 

don't know what that is.

Edited April 6, 20188 yr by nautarch

remove the static mappings on the router. Let the server itself say "I am THIS!"

 

***EDIT

 

As long as the server proclaims it's IP is outside of the routers DHCP scope - it'll be fine. The server says I'm .100 router realizes it can only go to .75, allows the self assigned static IP to stick around

 

 

Edited April 6, 20188 yr by dimaestro
more info

if you could, give me the ifconfig from the terminal on the unraid server.

one sec, trying without the router static address.

 

I also tried deleted everything onthe flash and putting on 6.5 in the hopes that maybe it was a 6.4 issue.

 

Still no lights on ethernet and same issues.

 

I just don't get why the it looks like the ethernet is just plain off. When i ran 6.2.4 it was fine

 

the eth0 broadcast in that screenshot is 0.0.0.0

 

on unraid can you ping itself by ip address?

 

*** edit

 

No lights on the back of the card?

 

Edited April 6, 20188 yr by dimaestro

Correct, no lights on back of card when running 6.4/6.5 

 

Lights on when running 6.2.4

 

unraid pings itself successfully.

Edited April 6, 20188 yr by nautarch

I think either your NIC is dead, or we're on a dead port on the router - or the cable is shot.

 

Swap ports on the router, see if it comes up. If it doesn't, are you able to swap the cable? If you test with a different cable and still no go. I'd be 20 bucks the NIC died.

 

Flashing lights aren't software based - that's 100% hardware based. I get them on machines that aren't even powered on - it's a network connection saying 'hi!'

 

*** edit

Heck, boot into the bios. Your nic will flash if your in the bios, no nothing. If it's not flashing we're down to physical issues.

Edited April 6, 20188 yr by dimaestro
more ideas

It is 100% working on 6.2.4 and only stops after trying 6.4/6.5

 

But you're awesome and I'm an idiot  cable swap fixed it. Have no idea why it was fine on 6.2.4, but i'll take it. Up and running smoothly.

Glad to have helped.