I was using the latest stable Truenas Scale with OPNsense router and Cisco managed switch. This week, I disconnected it from that system and reset the Cisco switch to factory default and used it to connect my devices (unmanaged for now) to a new fibre modem/router. All the devices work except the Truenas box. The truenas box had a fixed ip 192.168.20.225 under the old system and I gave it a fixed ip of 192.168.2.10 under the new system. The new router/medem seems to be picking it up on wifi but not when wired.
What I’ve tried:
I cannot ssh (ssh root@192.168.2.10 or as an unprivileged user) into the Truenas box - connection refused
I cannot access the web gui - connection refused
I purchased a vga to hdmi adapter today to try and use the console but my monitor says no connection (I tried also without any success (black screen only) with an older monitor. Nothing shows up on the monitor when I hardware turn off and restart or reset the Truenas Box.
I downloaded the lastest Truenas Scale iso to try and reinstall the os but when I put it on a bootable USB, turn off the Truenas box, insert the USB (front or back of the box) and turn on the box, nothing shows up on the monitor. The Truenas box seems to be starting correctly.
I can ping the ip address 192.168.2.10.
I tried connecting the Truenas box directly to my computer (with a network cable) but don’t know how to access the box. When I try to ssh into Truenas box it says network is unreachable.
I am running out of ideas and am probably missing something obvious.
If you can’t attach a monitor for the console, you may have to use the management port. Pointing you to the Mini documentation.
Can you log into your router and see all its settings and a list of the devices attached? I don’t understand “The new router/medem seems to be picking it up on wifi but not when wired.” Wired and wireless should be the same network, unless you are plugging into a WAN port (Wide Area Network) that usually goes to an internet modem or something connecting you to the external (world) network.
Given you have renumbered your network, have you verified that the address you are using for the TrueNAS is not being used by something else inadvertently? On the system you are ping from, on the same subnet, you need to look at the ARP cache and see if the MAC of the system matches the IP.
❯ arp -a | grep barrel
barrel (192.168.22.252) at 1a:e1:43:xx:xx:xx on en11 ifscope [ethernet]
So for the example above my MiniXL is called barrel on IP 192.168.22.252 and I can look at the MAC address on the system and see that MAC 1a:e1… matched interface eno1 on the system.
If they do not match then some other system has taking the IP.
The command fping -g 192.168.2.0/24 (assuming your network mask is 255.255.255.0) will ping everything on the network and load your ARP cache. It will also sometimes pick up duplicate IPs.
@SmallBarky Thanks for the reply. Two things (both my errors). I couldn’t get into the console because my adapter needed a usb power source. When I applied it I got into the console and saw that the Truenas box ip was not changed but was still 192.168.20.225. I used the console to change the ip address and I can now log into my Truenas web gui. I looked at the Truenas docs you referenced and was ready to try the management port but it ended us not being necessary.
Thanks again for the quick reply.
@sah Thanks for the reply. As I mentioned to @SmallBarky, the ip address of my Truenas box was not the address that I thought it was. It was the same as I had on my old setup. So you were right, the 192.168.2.10 was a different item that I was trying to connect to, thinking it was my Truenas box. All is settled now. Thanks again.
