I attempted the 6.6 upgrade from 6.5.3, it failed with a (corrupt? check USB) error.  After this error I could no longer see my VMs or docker info in the web GUI.  Next, I assumed I could gracefully shut everything down, and try again. 

Except when i booted back up, i can no longer get an IP address.  I get a 169.x.  The MAC address is different than it used to be.  I think I had an eth0 before, but now i only see br0 and lo.

 

I did not try turning off autostart VMs yet, how can i set this in the cfg?

If we can get back up on either version i'll be happy, but i'm not sure how to do a 'restore' while keeping my VM and docker configs.

 

Other weird things;

root login on the local console doesn't ask for my root password.

attempted to turn off docker on startup DOCKER_ENABLED="no", same results.

 

Not my switch / router:

I used a completely different switch using the same cables, with the same results.

Used an ubuntu boot CD on same hardware and got a good ip address, and saw all hardware attached.

 

Not disk failure;

USB key is viewable and editable on windows.

Primary Unraid SSD is readable in ubuntu boot CD environment.

 

Not the USB key config;

I restored the USB key configs back to a previous backup, and i get the same 169.x address.

I ran a check disk in windows to verify it's not corrupt.

 

I'm at a loss here, and even though I've been using unraid for about a year - i feel like i'm new to managing unraid.  What can i do next?

 

 

Edited October 2, 20187 yr by TurboMyPC

Your diagnostics are from June.

 

Either boot into GUI mode and grab the diagnostics from there, or from the command prompt 

diagnostics

And toss the stick into another computer and upload the resulting file here (in the logs folder)

Good catch.  It was saving to /boot/logs and didn't persist on the USB key.  I've been attempting to copy it for about an hour so far with no luck.  Last attempt i uploaded it to a seperate mounted USB key, but now i cannot open the archive on windows (access denied), extract (no archives found).

 

I didn't unmount, but i did poweroff - so i'll try that tomorrow.

Edited October 1, 20187 yr by TurboMyPC

42 minutes ago, TurboMyPC said:

Good catch.  It was saving to /boot/logs and didn't persist on the USB key.  I've been attempting to copy it for about an hour so far with no luck.  Last attempt i uploaded it to a seperate mounted USB key, but now i cannot open the archive on windows (access denied), extract (no archives found).

 

I didn't unmount, but i did poweroff - so i'll try that tomorrow.

If it did not persist on the USB key then you probably have a problem with the USB key itself.    Either some sort of corruption is causing it to be set to Read-only or it is not being correctly mounted at /boot.    You could check the latter by doing a ‘df’ command from the CLI.    Corruption can be checked for by plugging the USB key into a windows Pc and letting it run a scan on the drive.

I will try the df next.  I attached the diagnostics in OP ^.  I did a lsblk and it appeared to be attached, but not mounted.  Windows just scanned without finding any problems (no further action required).

Problems with the flash drive:

 

Sep 30 21:15:52 Tower kernel: print_req_error: I/O error, dev sda, sector 512
Sep 30 21:15:52 Tower kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

 

Use an USB 2.0 port instead, USB 3.0 is not recommended.

I had it plugged into the BIOS port, which looks like it may have been part of my 3.1 USB hub.  I thought i was in trouble, because the only pure 2.0 ports are on the motherboard header.  However, it's now working fine in the 3.0/2.0 hub instead of the 3.1.

 

The strange thing is that it never gave me issues in this port until now.

 

Marking as Solved, Thank you all!

Chipset+Intel® USB 3.1 controller:
1 x USB Type-C™ port on the back panel, with USB 3.1 support
1 x USB 3.1 Type-A port (red) on the back panel
Chipset+2 Renesas® USB 3.0 Hubs:
8 x USB 3.0/2.0 ports (4 ports on the back panel, 4 ports available through the internal USB headers)
Chipset:
2 x USB 3.0/2.0 ports on the back panel
4 x USB 2.0/1.1 ports available through the internal USB headers

 

Edited October 2, 20187 yr by TurboMyPC