TrueNAS Core 13.0-U3.1 won't boot up via wake on LAN

[GBillR]

What does BMC mean.

baseboard management controller... he is saying a MB with IPMI.

 

[jgreco]

What does BMC mean.

Baseboard Management Controller. It controls stuff like power, fans, monitors environmentals, etc., on most server boards.

Intelligent Platform Management Interface - Wikipedia

en.wikipedia.org

 

[Whattteva]

What does BMC mean.

Baseboard Management Controller.

Basically, it's a separate mini computer integrated into the motherboard usually with its own dedicated NIC that provides you with power control as well as a remote console so you never need a keyboard/mouse/monitor. Typically, only available with server-grade motherboards.

Lol, looks like I came in way too late.

 

[jgreco]

Lol, looks like I came in way too late.

You're in good company. I sometimes open several things to reply to in different tabs and then find someone beat me to it by an hour. Heh.

 

[NAGL95]

Have you looked at trying to see if the packet is arriving with tcpdump as described in this thread?

I explored deliver of WoL packet's to NIC and packet's sended from router doesn't catched by TrueNAS OS.

Next step i found script for power shell that reach the NAS:

Code:

 $mac = '04:7c:16:3e:7e:f0';
>> [System.Net.NetworkInformation.NetworkInterface]::GetAllNetworkInterfaces() | Where-Object { $_.NetworkInterfaceType -ne [System.Net.NetworkInformation.NetworkInterfaceType]::Loopback -and $_.OperationalStatus -eq [System.Net.NetworkInformation.OperationalStatus]::Up } | ForEach-Object {
>>     $networkInterface = $_
>>     $localIpAddress = ($networkInterface.GetIPProperties().UnicastAddresses | Where-Object { $_.Address.AddressFamily -eq [System.Net.Sockets.AddressFamily]::InterNetwork })[0].Address
>>     $targetPhysicalAddress = [System.Net.NetworkInformation.PhysicalAddress]::Parse(($mac -replace '[^0-9A-f]','').ToUpper())
>>     $targetPhysicalAddressBytes = $targetPhysicalAddress.GetAddressBytes()
>>     $packet = [byte[]](,0xFF * 102)
>>     6..101 | Foreach-Object { $packet[$_] = $targetPhysicalAddressBytes[($_ % 6)] }
>>     $localEndpoint = [System.Net.IPEndPoint]::new($localIpAddress, 0)
>>     $targetEndpoint = [System.Net.IPEndPoint]::new([System.Net.IPAddress]::Broadcast, 9)
>>     $client = [System.Net.Sockets.UdpClient]::new($localEndpoint)
>>     try { $client.Send($packet, $packet.Length, $targetEndpoint) | Out-Null } finally { $client.Dispose() }
>> }

And result on NAS:

Code:

root@truenas[~]# tcpdump -i re0 -x port 9
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes
07:02:42.370426 IP 192.168.1.110.52268 > 255.255.255.255.discard: UDP, length 102
        0x0000:  4500 0082 5f11 0000 8011 1944 c0a8 016e
        0x0010:  ffff ffff cc2c 0009 006e d61c ffff ffff
        0x0020:  ffff 047c 163e 7ef0 047c 163e 7ef0 047c
        0x0030:  163e 7ef0 047c 163e 7ef0 047c 163e 7ef0
        0x0040:  047c 163e 7ef0 047c 163e 7ef0 047c 163e
        0x0050:  7ef0 047c 163e 7ef0 047c 163e 7ef0 047c
        0x0060:  163e 7ef0 047c 163e 7ef0 047c 163e 7ef0
        0x0070:  047c 163e 7ef0 047c 163e 7ef0 047c 163e
        0x0080:  7ef0
^C
1 packet captured
67 packets received by filter
0 packets dropped by kernel

In this steps i thoht that issue solved, turned off NAS and tried send WoL by script - no result.

You could also unplug everything install a temp HDD and install Windows then under Device Manager > Network Adapter > Your NIC set it up/confirm that it is enabled for Magic Packer and it is allowed to wake the computer, then test it out to wake from another PC using the utility above. This way if you will have tried to systems.

Under Win10 NAS boot up by WOL normal.


I think trouble inside TureNAS v.13 will try install v.12 to check it.

 

[socra]

No much of a sample size but I upgraded my backup TrueNAS server from 12 -> 13 and WOL is still working fine under v13.
The system is up only one day per week to receive snapshots from my main NAS.
It's an older board : Asrock H170-mITX where I use the motherboards Intel NIC.

 

[NAGL95]

No much of a sample size but I upgraded my backup TrueNAS server from 12 -> 13 and WOL is still working fine under v13.
The system is up only one day per week to receive snapshots from my main NAS.
It's an older board : Asrock H170-mITX where I use the motherboards Intel NIC.

Yeah it's true, i cheked it no result.

I found same issue FreeBSD 8.2, but i can't finde same file or directory inside TrueNAS.

 

[NAGL95]

Anyone know possible solution?

 

[Ripinda]

Anyone know possible solution?

I have no definitive answer, but you mentioned not finding C-states. Msi often burries c states in some CPU or OC submenu, so make sure to look there.

 

[ck-bbw]

Hello everyone,
I hope this is the right place to share my experience with a similar problem. Cause I've been troubleshooting quite long and hope people can profit from my solution. If that's not the right place to post such a thing feel free to correct me.

My Problem
After I upgraded my TrueNAS from Version 12 to 13 I had troubles starting it again with wake on lan.

Solution
Had to do a fresh install of TrueNAS 12. I assume, that the TrueNAS 13 (or FreeBSD?) had troubles with the driver of my NIC. (I'm using an old Realtek NIC) and I think that's why TrueNAS wouldn't start with this new version.

Doing that I learned, that I can't import a configuration backup from a newer version. So I had to reconfigure my NAS. In the future I will always save a configuration backup of my NAS before upgrading it - if I ever upgrade it.