Network doesn't work after every reboot

Quote

I had the same setup with same hardware on old USB (last Unraid version there was 6.5.3).

I hadn't encountered this issue then.

Are you saying that after upgrading from 6.5.3 to 6.6.1 this issue occurred?

 

Or are this different systems?

Edited October 13, 2018 by bonienl

No, I had to replace the USB in the process.

Now I am trying to configure the server on the new USB. 

Not sure when things changed since I had the old config for some time.

 

Maybe I did something different on the original setup.

But in any case the LAG doesn't seem to be in best shape.

In your posted set up you have eth0 as a separate port (this interface is used to manage Unraid)

and bond1 with interfaces eth1 - eth4.

 

Is this what you want, or you want the bonded interface to be used as management interface?

 

In case eth0 is your management port and bond1 is a separate connection, you need to set eth0 as a bond interface too (with only eth0 as member).

Edited October 13, 2018 by bonienl

I was using the eth0 as a fallback when the config of the bond0 fails.

But, the expectation was that if all is fine, the eth0 would have its cable disconnected.

 

That is, management and normal communication should go through the bond0.

 

Good new though:

It seems to work now.

I set bond0=eth0-eth3 and then eth4.

Maybe for some reason the bonded ports should be first.

 

I would hesitate to put it back to eth0 and bond0=eth1-eth4.

 

PS: In both cases the same MAC addresses are involved in the bond0. (re-order them in rules section)

 

Ah, one more weird thing:

- start with new usb.

- the MAC address on each interface is the same as the first interface (making it very difficult to distinguish them).
However, in the rules section correct MAC addresses are shown.

 

After something is changed and a reboot, it shows correct MAC addresses. 

Edited October 13, 2018 by ks2016
Clarify

I was too quick to say that it works.

Short story:
- start with new USB

- configured all related to network (bonding, tested that it works after reboots etc)
- start array (still all seems fine)

- start VM Manager and reboot (it doesn't work any more)

 

It doesn't work to the point that even the server name has changed to "Tower", from what I had configured.

 

Edited October 13, 2018 by ks2016
Add more info

That sounds like data may not be being written to the flash drive.  Are you getting errors in the syslog relating to the flash drive?

Indeed, sounds like a corrupted flash device.

Shutdown your system and test+repair your flash device in a Windows machine.

Well, I just did:

cat /dev/zero > /dev/sdc (sdc being the USB drive)

fresh install of unraid 6.6.2 without any customization with latest tool. 1.5

first boot in gui mode (on the server itself)  ... see attached image

 

What could I do on Windows to check it?

Maybe the USB creation tool should verify all is written correctly as final step?

Maybe related to the comment here:

 

"In general, avoid USB 3. Just a little less reliable when booting from them in my experience, and unRAID loads the entire system into RAM anyway so it doesn’t make a difference in operation."

 

The new USB is SanDisk Cruzer Fit 32GB USB 3.0. 

Well, I guess I should try with a different USB drive.

5 minutes ago, ks2016 said:

What could I do on Windows to check it?

When you insert a USB device into a Windows 10 machine, it will do a quick scan and ask you to repair if some corruption is found.

1 minute ago, ks2016 said:

The new USB is SanDisk Cruzer Fit 32GB USB 3.0.

Some USB3 devices have issues, a safer bet is to use a USB2 device

Update:

I did the checks on the USB 3.0 drive in Windows and all was fine. All files could be read without any issue.

Then I got myself the same USB 2.0 model as the original drive. So, far I haven't seen the issue with the network not working. However, the GUI boot mode disappeared. I was working the first time after making the USB, but after couple of reboots it is not working any more. 

By not working, I mean that the output before that seem just fine. At the moment when the login page of GUI is expected to be shown only a black screen appears with blinking cursor.

I don't mind that at the moment, since the server seems to be fine otherwise.

 

Conclusion: Stay far away from USB 3.0 drives!

 

THANKS EVERYONE FOR YOUR ASSISTANCE

 

Edited October 15, 2018 by ks2016
Clarification

Changed Status to Closed