Hi All

 

I just updated unraid to the latest RC and rebooted my server, it has not come back up at all.

 

After a while I connected a monitor to it, and logged into the GUI mode to try an troubleshoot it.

 

I am unable to open the UI while physically sitting in front of the server and am unable to browse the network \ internet at all - so I am leaning towards it being a NIC or network issue.

 

The symptoms I got were:

- Unraid taking forever to initialize SAMBA

- NIC lights flashing with no connection

- No UI started when logged into the server

- No network access of any kind

- Server not responding to ping

 

I have tried using the other network points on the server and rebooting to the same issue (there are 4 of them that are usually bonded together).

 

Any help here would be amazing, as I am a bit concerned about my data 

After some messing about I was able to launch the UI - just took forever to respond.

 

I can confirm that my NIC has not been picked up at all

From the command prompt / terminal,

diagnostics

then power down, and reply back with the resulting zip file that is stored in /logs on the flash drive.

I will give this a try in about 10 min - I have just restored the previous Unraid version on the server to see if the network comes back online, should that not work I will run a quick "diagnostics" on it and post the response 

Here you go - the restore did not work at all.

 

There was some output to the terminal while running the diagnostics that did not look ideal.

 

I am unable to mount my flash drive on my desktop - suggestions?

I did manage to pull down a previous backup of my flash drive through "My Servers" and this was the expected NIC configuration if that helps at all.

 

# Generated settings:
IFNAME[0]="br0"
BONDNAME[0]="bond0"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BONDING_MODE[0]="1"
BONDNICS[0]="eth0 eth1 eth2 eth3"
BRNICS[0]="bond0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.0.60"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.0.2"
DNS_SERVER1="1.1.1.1"
DNS_SERVER2="8.8.8.8"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
SYSNICS="1"

 

Strange errors.  Was there a zip file created in the logs folder?  Upload them here on your next post

Yes it was, however I do not have any means of uploading it,

 

I have shut down the server, removed the flash drive and plugged it into this PC.

 

There is a drive mounted in Windows when I do that, however it won't allow access to it without me formatting it - I have checked on diskpart \ manager and the only volume exposed is the uncountable one.

 

Do I need to do something special to be able to browse the /boot directory locally?

Woot - finally got the drive to mount

newnas-diagnostics-20220526-0851.zip

Your should update to v6.10.1, also your server should be affected by this issue, so please disable VT-d now, if it boots OK then post new diags after array start.

After a couple of hours of fighting with it I just reinstalled Unraid  6.10.1 to a new USB and rebooted the server, migrated my key and am now trying to figure out how to import my disks again, at the moment I am stuck looking at the following screen

 

I did make a backup of the original drive before the reinstall, but I don't know how to import my disks correctly without messing things up.

 

Any suggestions?

I have managed to resolve the correct disks to slots on the array, however I wont start it as I am getting the warning that the disks will be overridden.

 

I cannot for the life of me find the correct guide for migrating servers

All of your configuration is in the config folder of your flash backup. Without that you are starting from scratch. As long as you don't assign a data drive to a parity slot your data should be fine. The screenshot is showing parity disks will be overwritten, not your data. 

Thanks all - just closing the loop here.

 

I managed to configure the appropriate settings for virtualization as suggested by @Squid along with creating a new flash drive with the latest stable version of Unraid.

 

In addition to that I did a manual sync of all configuration and shares to the new flash drive from the backup I had.

 

I made use of the vars diagnostics file to ensure that I mapped the correct drives when assigning drives and took a leap of faith when it came to starting the array based on @trurl which seemed to work.

 

My Docker images and shares are all back along with the array rebuilding.

 

Thank you everyone who helped, awesome community!