Quantcast
Channel: TerraMaster Forum
Viewing all articles
Browse latest Browse all 4149

Networking • Re: Why does the IP address of my TNAS appear as 169.254.x.x and is inaccessible?

$
0
0
My F4-223 running TOS 5.1 has a problem connecting to the LAN. After every power down, whether scheduled, manual or following an OS upgrade, the subsequent boot reliably fails to obtain an IP address. The four drive lights are lit and unblinking and the LAN light remains off. The NAS is inaccessible over the LAN, whether I've set the IP address statically or using DHCP.

The status of the front panel lights, together with the fact that a short press on the power button takes the NAS down instantly, seems to indicate that the machine has booted into a very low target level.

The workaround is to boot the machine manually for a second time, which reliably puts it fully functioning back onto the LAN.

My default first diagnostic step would be to ssh in and diff /var/log/dmesg and /var/log/dmesg.0. Sadly, although the dmesg utility works as expected, I can't find the location of any of its historic logs. Obviously I'm interested in ../dmesg.0, which I'm hoping will document the low target boot that fails to join the LAN. TOS 5 splits its logs between /var/log and (a couple of very old entries in) /var/logs but I can't find any trace of dmesg in either of them.

There is a dmesg.txt file in the zip file produced from WebUI Technical Support/Report Issues (I've used this feature to report this problem) but this log of course only documents the latest healthy boot. It's mainly dmesg.0 I'm looking for.

Any help with this would be very welcome. It might be particularly useful if I could track down dmesg.0.

--
Chris

Statistics: Posted by bidmead — Today, 18:14



Viewing all articles
Browse latest Browse all 4149

Trending Articles