Can't assign IP to my TrueNAS machine

zealios

Dabbler
Joined
Dec 5, 2021
Messages
28

Attachments

  • IMG_20211208_200038.jpg
    IMG_20211208_200038.jpg
    99.9 KB · Views: 235

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Go ahead and delete all the IP config on bge0, and recreate it on bge1. Move the cable over.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
I went spelunking through the Internet for some more information about this firmware handshake error. According to https://dev.haiku-os.org/ticket/13933, this is because a custom HP BIOS has tweaked enough of the onboard Broadcom NIC so it fails to load the TrueNAS (FreeBSD) bge driver. You'll have to use a PCI-E Intel Gigabit NIC, sorry.
 

zealios

Dabbler
Joined
Dec 5, 2021
Messages
28
I went spelunking through the Internet for some more information about this firmware handshake error. According to https://dev.haiku-os.org/ticket/13933, this is because a custom HP BIOS has tweaked enough of the onboard Broadcom NIC so it fails to load the TrueNAS (FreeBSD) bge driver. You'll have to use a PCI-E Intel Gigabit NIC, sorry.
But it worked fine on a wifi-extender 3 days ago?
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Typically these things work OK on Windows, because HP has tweaked the drivers to work with the BIOS. In your case, the bge driver is trying to upload firmware to initialize the PHY, and failing. The OS configuration is correct, but it's not communicating with the NIC hardware.
 

zealios

Dabbler
Joined
Dec 5, 2021
Messages
28
Typically these things work OK on Windows, because HP has tweaked the drivers to work with the BIOS. In your case, the bge driver is trying to upload firmware to initialize the PHY, and failing. The OS configuration is correct, but it's not communicating with the NIC hardware.
I was running TrueNAS on it before too. Its just super weird that switching from a wifi-extender ethernet connection to a direct connection to my main router would make my NAS unusable.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Can you draw up your network before and after the move? We're still having difficulty visualizing what you did.
 

zealios

Dabbler
Joined
Dec 5, 2021
Messages
28
Before:
NAS connected to a network-extender via cable. The network extender had the IP of 192.168.0.21/51, i dont quite remember.
The wifi-extender pointed down to another extender that was connected to the main router.

Now:
I moved my NAS in a place where i get a cabled connection directly to my main router.

I hope this explains it better, thank you for the help so far :).
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
What happens if you set the TrueNAS to DHCP?

Reset config for both bge0 and bge1. Then activate DHCP for one of them. Make sure (ifconfig) the cable is in the right port. Reboot for good measure ...

Sorry, this is definitely weird. Looks like both @Samuel Tai and me are at a bit of a loss here.
 

zealios

Dabbler
Joined
Dec 5, 2021
Messages
28
What happens if you set the TrueNAS to DHCP?

Reset config for both bge0 and bge1. Then activate DHCP for one of them. Make sure (ifconfig) the cable is in the right port. Reboot for good measure ...

Sorry, this is definitely weird. Looks like both @Samuel Tai and me are at a bit of a loss here.
I will have to check for tommorrow, but thanks.
Yeah i think i worded my situation poorly, apologies.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
Yeah i think i worded my situation poorly, apologies.
That's not what I tried to say. No worries. I am really not getting what might be going on with your hardware.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Also try powering off your TrueNAS server, and disconnecting the power supply for 2 minutes, to all all capacitors to drain. Then powering up again. See if the firmware download error reappears.
 
Top