I have no idea what to do. I upgraded to V7. Seemed to go fine. No warnings, no issues. However, I couldn't connect anywhere via browser to my server ip. I went to my machine, manually restarted, and checked my attached monitor and watched bootup. I didn't see any real standout warnings. All drives seemed to mount. emhttp seemed to start. It finishes, and tells me it's on Version 7, and that my normal ip4 static IP is set. However, the machine does not show up on any lan scans and I cannot connect to it remotely with a browser as I always do. I've logged in as root at local terminal, but I don't know commands to dump diags, or really to do much to check status of anything. I'm comfortable in terminal, but I don't do much as root in UNraid as I hardly ever need to -

Attach diagnostics please.  

If unable, here's some general pointers.

Check network cables. 

Look for link light on nic and switch.

Under Network Settings:

Set inactive all network ports except the one you are plugging in to.

Disable bonding.

Enable bridging.

Bridging member Eth0.

Network protocol ipv4 only.

Set a static IP address outside the DHCP range if known.  If not make it a high number such as xxx.xxx.xxx.251

Assign gateway address as appropriate.

DNS server assignment Static.

DNS server Use 1.1.1.1

 

See if that gets you connected.

 

Enter the command “diagnostics” (without quotes) in the terminal. This will download the diagnostics to your flash drive. You can copy them on another machine and post them.

@wgstarksThank you for this. The point is, I can't get anything to launch EXCEPT the terminal locally. I didn't know how to do much in the bare terminal as root when Unraid launches. I will do this and report back. I've been swamped on other priority life and work issues since I wrote this. More to come -

9 hours ago, BigSpoonzz said:

@wgstarksThank you for this. The point is, I can't get anything to launch EXCEPT the terminal locally. I didn't know how to do much in the bare terminal as root when Unraid launches. I will do this and report back. I've been swamped on other priority life and work issues since I wrote this. More to come -

I get that. My point was that if you can post your diagnostics then others can help you resolve the issue.

Hello again, to anyone who can help -

I can see what the issue is. My eth0/Br0 is not connecting at all.

Here is some info that is pertinent I think -

1. I have a mobo nic port

2. I have an addtl NIC card with 2 ports - Lights are blinking, etc
3. I set a bond inside Unraid for the 3 ports (that was working just fine before upgrade to V7)

4. I have a reservation in my router for 192.168.4.200 and I've got a couple ports forwarded

5. V7 seems to boot fine. It even sets the ip for 192.168.4.200 - but that address does not show up on my network (see ip table jpg)

 

However, it seems my DNS is not right?, and it seems eth0 does not start.
I have no experience with setting ip table or DNS manually via command line, but I've seen some del ip range commands that make sense to me - if that's something I need to do.

I combined a few diag files in the diags file I made. They are separated by ____ lines

I found the route command to show the ip routing table, and it's attached.

 

Unriad-Diags-01.25.25.rtf

Edited January 25, 20251 yr by BigSpoonzz

On 1/16/2025 at 4:51 AM, Veah said:

If unable, here's some general pointers.

Bridging member Eth0.

Network protocol ipv4 only.

Set a static IP address outside the DHCP range if known.  If not make it a high number such as xxx.xxx.xxx.251

Assign gateway address as appropriate.

DNS server assignment Static.

DNS server Use 1.1.1.1

 

It seems all of these are in the right direction for what is wrong, but I have never done any of this in a command line. I'm a quick learner in Linux/python/commands but I've never done this specific bit of setting up eth0 / network table / etc. All of my info is in a post below, including diags

10 hours ago, BigSpoonzz said:

Unriad-Diags-01.25.25.rtf 198.56 kB · 0 downloads

Post the actual diags zip please.

diags from last night. So far, I've deleted the blacklisted NIC card. Now when it boots, it shows br0 is UP, but doesn't load a routing table.

I'll grab another diags shortly

rosebud-diagnostics-20250125-2357.zip

The NIC driver is still blacklisted on those diags.

I'm at least booted up and running now. Whenever I reboot, it blacklists the NIC again. Even if nothing is plugged into it, it still gets blacklisted and the machine won't boot until I pull the usb and go manually delete the blacklist. I need to fix that, but now my array won't launch because I'm getting an error that says invalid pool expansion. I've got the same 2 SSDs selected I've always had. I think the issue might be related to when I was trying to check my NICS and I used a linux boot drive. I went to install it to a 500gb SSD SCSI drive I have in the machine not doing anything, but I'm wondering if I screwed up the files system on my cache2 drive by accident. 

I can run a smart test on the drive. The system sees the M.2 cache pool 2 drive. The system won't let me remove it start the array without it, and I can't figure out a way to test/repair it. Seems I'll have to go the long way and do it in command line. It was formatted as BTRFS as is my cache 1 drive. they had been working fine up until v7 upgrade.

I'm attaching a new diag. Ignore the blacklist. I'm at least booted and have set a static IP again.

rosebud-diagnostics-20250126-1442.zip

9 hours ago, BigSpoonzz said:

Whenever I reboot, it blacklists the NIC again.

Remove this:

-rw------- 1 root root   7968 May 29  2024 unraid-r8125.plg