I've been trying to get a VM on to a different, tagged vlan. The vlan is set up on pfSense and the tagging is done on Unifi APs and switches. I have 2 tagged vlans, 50 and 70, the former carries all my IOT traffic and the latter carries the CCTV traffic. Until I tried to make changes to accommodate an Ubuntu server on the IOT vlan, they both worked without issue since I put them in place a year or so ago.

I created tagged vlans in the network section for both 50 and 70, didn't put the ip details in at the bottom of either connection and dhcp defaulted to automatic. I added 2 entries to the routing table below, pressed save and restarted Unraid. It came up fine, I checked that the settings I had made persisted and I started to build the VM using the the IP within the 50 vlan scope (10.16.50.0/24)  and the gateway of my LAN (192.168.52.1) in doing so. After it was built, I rebooted Ubuntu. When the Ubuntu came back up, I logged into it using VNC and found that I could not ping out to any device including the chosen gateway. I could not ping it from Unraid and the assigned IP did not show up in the ARP tables in pfSense. I checked the device VM settings and Ubuntu was in br0.50, where I would've expected it to be.

I then went back into network settings, down to the vlan section and added 10.16.50.0/24 to the 50 tag and 192.100.0/24 to the 70tag and saved and then lost everything on the browser. I ssh into Unraid and restarted it, hoping that it would come back up ok, it did not. At this point I was able to ssh into the though, so I thought I could fix the issue by editing the /boot/config/network.cfg file, where I first made a copy and then removed all the entries that referred to the vlans. When I restarted Unraid, the box made all the usual noises, but this time, even after a considerable wait, I was unable to ping it, nor ssh into it (but for some reason, it came back up on to the ARP table afer reboot).

I'm really struggling with what to do to fix this. All my services are down now and I have no idea what to do next or even how to access the OS if I can't ssh into Unraid, will I need to access the usb stick and make changes to that on my pc?

Any pointers greatly received. TIA

Access in local and delete /boot/config/network.cfg, then reboot again.

Edited July 12, 20205 yr by Benson

Just to clarify, by accessing in local, do you mean plugging in a keyboard and monitor into the Unraid box and booting it up that way?

1 minute ago, Boyturtle said:

Just to clarify, by accessing in local, do you mean plugging in a keyboard and monitor into the Unraid box and booting it up that way?

Yes

I've plugged a keyboard and monitor in, started the server, got the Supermicro splash screen and then get stuck with a blank screen with a white strip  with "DXE --Legacy Boot Start" across the bottom and a cursor in the middle of the screen that doesn't blink or do anything; I think this might be something to do with IPMI, but I'm not sure as it's not something I've dealt with a great deal.

I've tried booting up into bios to see my options and confirmed boot order, but when I chose either the UEFI usb card or plain vanilla here, I just get a totally blank screen in the process.

Should I remove the usb drive from the server and plug it into an already booted up computer and go in to delete the /boot/config/network.cfg there and then put it back in the server, or will this not work/cause more problems?

Problem should relate USB boot problem, delete network.cfg used to reset network setting to default, it won't affect booting.

 

Do you know you boot Unraid by Lagacy or UEFI mode previously ?

 

BTW, either boot mode will see a "blue" menu, if not, you are not booting in Unraid. Delete network.cfg also safe.

 

Edited July 12, 20205 yr by Benson

So, just to clarify, am I ok to remove the usb drive from the server and plug it into an already booted up computer and go in to delete the /boot/config/network.cfg there and then put it back in the server, or will this not work/cause more problems? Will the network.cfg be recreated on boot after deletion?

I think IPMI is interfering with boot process on the server and I'm unsure how to circumvent it at this point.

11 minutes ago, Boyturtle said:

So, just to clarify, am I ok to remove the usb drive from the server and plug it into an already booted up computer and go in to delete the /boot/config/network.cfg there and then put it back in the server, or will this not work/cause more problems? Will the network.cfg be recreated on boot after deletion?

Yes, no problem, safe to do that.

 

11 minutes ago, Boyturtle said:

I think IPMI is interfering with boot process on the server and I'm unsure how to circumvent it at this point.

May be, I also not sure how IPMI switching between display output.

Edited July 12, 20205 yr by Benson

I deleted the /boot/config/network.cfg file in another PC, put the usb back in my server and tried to boot it up in both UEFI and Legacy and neither worked. I'm beginning to wonder if the USB drive or mobo are failing. Tomorrow I will download a fresh image of Unraid onto a known working USB drive and put that in the server to see if it works. For testing purposes, if I put the current USB drive into a different device and boot it up, will it change the configs on the drive?

Have you any other suggestions that I might try?

3 hours ago, Boyturtle said:

will it change the configs on the drive?

No.