This way you would capture everything that the kernel does during power off.

One thing that I have not figured out is how turn on the ethernet LED light correctly, so I need all the info I can get from a different box to compare with mine. The fact that you did not see the amber or green ethernet LED is a puzzle!

Quotebodhi
> At the moment, I think the MAC address stored in t
> he NIC itself is the problem (or one of the proble
> ms) with WOL.
>

> I was thinking the same. There's no way how to fi
> nd out what is the address and test then?

There are several MAC addresses defined in u-boot env. Perhaps one of them is the one stored in the NIC. I recall there is one of the Zyxel boxes (can't remember which) that can only WOL by using the Marvell MAC address (the NIC chip is Marvell), but not by the Zyxel MAC address.

Someone has to replace his NAS326 because the NAND gets corrupt ant it doesn't boot anymore..
The replacement from ZyXEL has issues when using the rootfs (kernel 4.9).
The ethernet device is coming up but DHCP timeouts (as seen on NSA310s / NSA320s).
Setting up the network staticly changes nothing.
rebooting directly from ZyXEL OS to Debian .. same thing ..
"cold" boot .. same thing ...

Well I have decided to move from stock OS to debian on my NAS326 using Method "A" in the corresponding thread. But not luck, it keeps booting back to stock OS all the time. I have tried different USB Ports and different USB sticks as well without any success. rootfs has been extracted as root (not sudo). Also verified multiple times the envs being set correct. Only difference to the guide is that I used gtkterm instead of kwboot to enter the envs but I guess that should not make a difference, or? kwboot did not detect anything and spinning forever. I'm clueless.

Please try WOL to see if you see the same behavior that I and others have seen.

I dont expect it to work. But it's good to compare notes on behavior to confirm. We should observe the ethernet LED during shutdown, and then try WOL with all ether addresses that are defined in the stock u-boot envs.

Unfortunately WoL not working. No LED is staying on after issuing the poweroff command. Seems like PHY is shut down completely. None of the ethaddr found in u-boot is able to wake the box up. Also not the current one (Marvell default?).

Could somebody pls give feedback about the SMB speeds that you guys get with the latest rootfs and kernel?
Read AND write speed are ~60 MB/s only, with many ups and downs. Tested with an ext4 Volume on the internal bay and GBit Network.
That is far below the file transfer speed with stock os. I have tried a few samba tweaks but that not made any big difference.
Speed of the disks is not the limiting factor:

bodhi, I checked that already and trimmed my smb.conf according to the instructions. Also played around with socket options without any difference in terms of read or write speed.
While testing the raw performance of the disk using dd and iperf for network I observed the system with htop and cpu was continously maxed out. I wonder if this is the normal behavior that raw disk I/O (dd) put such heavy load on the cpu?!
I did some more testing with FTP. Large files upload to the NAS with ~78 MB/s and download from the NAS to PC with ~86 MB/s. Even the FTP results are far below the stock SMB speeds.

> While testing the raw performance of the disk usin
> g dd and iperf for network I observed the system w
> ith htop and cpu was continously maxed out. I wond
> er if this is the normal behavior that raw disk I/
> O (dd) put such heavy load on the cpu?!

I would not worry about this. In a test using iperf or dd, those processes should max out the CPU since nothing else that CPU-intensive is running.

I have not paid attention to the performance tuning for Samba and NFS. I expect that some forum members will investigate and contribute with their setup. So far no one has :) I guess I should revisit this at some time in the future.

Please, enter the code that you see below in the input field.
This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right.
If you enter the wrong code, a new image is created and you get
another chance to enter it right.