Hi guys,
First post, long time reader of the forum to help solving my problems, needing your support this time.
I am successfully powering on my home made Ubuntu Server 18.04 NAS1 from my PC1 Linux Mint 19.2 Build (Ubuntu 18.04 based).
Both have their IP addresses reserved in my router according to their MAC Addresses and are on the same subnet.
When NAS1 has been shut down (with sudo shutdown - h now), I can turn it on from PC1 by sending wake-on-lan (WoL) magic packets to it either with the powerwake or wakeonlan command.
I showed this to a friend and it ended up with him wanting the same solution, so I made him one similar Ubuntu Server 18.04 build, let's call it NAS2.
As you may guess, NAS2 is not responding to WoL, no way to power it on remotely. :(
NAS1 and NAS2 components are very similar, and both are based on the very same motherboard, an Asrock J3455-ITX.
One difference though is that NAS1 has got an 1.40 UEFI version while NAS2 is on a 1.60 UEFI version.
Both have the following UEFI setup that, to my understanding, should enable WoL:
Code:
Onboard LAN : Enabled
Deep S5 : Disabled
PCIE Devices Power On : Enabled
Boot From Onboard LAN : Enabled
Secure Boot : Disabled
For NAS2, here is what
$ sudo dmidecode | less shows me for the network card:
Code:
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x6DC50000.
Handle 0x0009, DMI type 9, 17 bytes
System Slot Information
Designation: mPCIE
Type: x1 PCI Express
Current Usage: Available
Length: Short
ID: 33
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported*
Bus Address: 0000:ff:1f.7
*Power Management Events, which include WOL
For your information, other NAS2 parts are:
- Kingston Value RAM 8GB, DDR3L-1600, SODIMM 204 (KVR16LS11/8 which is on the
memory compatible list of the Asrock J3455-ITX)
- Micron SSD - 256GB
- WD 4TB Red HDD (not connected yet)
- Seagate 4TB Ironwolf HDD (not connected yet)
- Silverstone ST30SF 300W SFX PSU
This is what
$ sudo inxi -Fxz tells for NAS2:
Code:
System: Host: NAS2 Kernel: 4.15.0-96-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: MATE
Distro: Ubuntu 18.04.4 LTS
Machine: Device: desktop Mobo: ASRock model: J3455-ITX serial: <filter> UEFI: American Megatrends v: P1.60 date: 01/16/2018
CPU: Quad core Intel Celeron J3455 (-MCP-) arch: N/A cache: 1024 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11980
clock speeds: max: 2300 MHz 1: 1697 MHz 2: 1135 MHz 3: 1206 MHz 4: 1637 MHz
Graphics: Card: Intel Device 5a85 bus-ID: 00:02.0
Display Server: X.Org 1.19.6 driver: i915 Resolution: 2560x1080@60.00hz
OpenGL: renderer: llvmpipe (LLVM 9.0, 128 bits) version: 3.3 Mesa 19.2.8 Direct Render: Yes
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 01:00.0
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 256.1GB (1.8% used)
ID-1: /dev/sda model: MTFDDAK256MAM size: 256.1GB temp: 0C
Partition: ID-1: / size: 234G used: 4.4G (2%) fs: ext4 dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 31.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
For your information. nfo: Processes: 142 Uptime: 6 min Memory: 168.8/7637.8MB Init: Other NAS2 parts aresystemd runlevel: 5 Gcc sys: N/A
Client: Shell (sudo) inxi: 2.3.56
NAS2 IP Address has also been reserved according to its MAC Address in my router.
$ ifconfig -a shows:
Code:
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.39 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::7285:c2ff:fe7f:4412 prefixlen 64 scopeid 0x20<link>
ether a1:b2:c3:d4:44:12 txqueuelen 1000 (Ethernet)
RX packets 37320 bytes 50510413 (50.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 20378 bytes 1703704 (1.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 679 bytes 238416 (238.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 679 bytes 238416 (238.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
On the NAS2 itself, the enp1s0 network controller is set for DHCP,
$ nano /etc/netplan/01-netcfg.yaml:
Code:
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
dhcp4: yes
That's it for the system I think, if you need some more info please let me know.
With NAS2 turned on, I am able to check for incoming packets using ngrep or netcat, when sending Magic Packets from PC1 with
$ wakeonlan a1:b2:c3:d4:44:12.
For instance with netcat
$ sudo nc -ul -p 9, I get:
Or with ngrep
$ sudo ngrep '\xff{6}(.{6})\1{15}' -x port 9, I get:
Code:
interface: enp1s0 (192.168.1.0/255.255.255.0)
filter: ( port 9 ) and ((ip || ip6) || (vlan && (ip || ip6)))
match: \xff{6}(.{6})\1{15}
#
U 192.168.1.31:40566 -> 255.255.255.255:9 #1
ff ff ff ff ff ff a1 b2 c3 d4 44 12 a1 b2 c3 d4 ......p...D.p...
44 12 a1 b2 c3 d4 44 12 a1 b2 c3 d4 44 12 a1 b2 D.p...D.p...D.p.
c3 d4 44 12 a1 b2 c3 d4 44 12 a1 b2 c3 d4 44 12 ..D.p...D.p...D.
a1 b2 c3 d4 44 12 a1 b2 c3 d4 44 12 a1 b2 c3 d4 p...D.p...D.p...
44 12 a1 b2 c3 d4 44 12 a1 b2 c3 d4 44 12 a1 b2 D.p...D.p...D.p.
c3 d4 44 12 a1 b2 c3 d4 44 12 a1 b2 c3 d4 44 12 ..D.p...D.p...D.
a1 b2 c3 d4 44 12 p...D.
Strangely, I get nothing when trying to send packets with
$ powerwake a1b2c3d44412.
However I experience exactly the same with my working NAS1, even though a wakeonlan or powerwake command is able to power it on.
And I don't know if that indicates something, but with
$ sudo etherwake a1:b2:c3:d4:44:12 -i enp1s0, I see this (on both NAS though):
Code:
SIOCGIFHWADDR on enp1s0 failed: No such device
So finally, as said above after shutting it down with
$ sudo shutdown -h now, impossible to turn it back on either with
$ wakeonlan a1:b2:c3:d4:44:12 or with
$ powerwake a1b2c3d44412.
And this even though the results of the above tests seem to point to an available WoL functionnality.
Am I missing something?
Are there other tools that could help me point out where the problem is?
Lastly, I tried to change the OS to Ubuntu 18.04 Desktop, Linux Mint 19.3, and I even tried to clone the NAS1 OS SSD to check it on NAS2. But all attempts to power on the build with WoL failed.
Which makes me think, especially because of the cloned SSD, that the problem comes from the UEFI of NAS2, or an hardware problem on this motherboard.
I am very interested in seeing what you think about all this!
Thanks for reading, I was rather long!