This is a collection of information on the net regarding how to handle the Zyxel NAS542
Upgrade HDDs on Zyxel NAS542
Removing disks from Zyxel NAS542 RAID array
can be troublesome
How to configure iSCSI settings
Enable extra packages
Installing git on ANOTHER ZYXEL MODEL: https://tungchingkai.blogspot.com/2011/06/how-to-install-git-repo-in-zyxel-nsa.html
Add disk to NAS542 (and optionally change RAID level)
In general, in the GUI, you can change from
- no RAID(Basic) to RAID-1
- RAID-1 to RAID-5
- RAID-5 to RAID-6
(including some combinations with hot spares)
iSCSI without CHAP on NAS542
I have a different model, but I suspect your model uses the same underlying logic for iscsi. You can do the following:
- create the LUN(s) and target via the webgui
- login to your zyxel via ssh ([email protected]), BTW if your pass is longer than 14 chars, only use the first 14 chars, for some reason Zyxel allows you to choose a pass longer then 14 but only uses the first 14 chars.
- $ sudo -i (to get root)
- targetcli (this will open a shell where you can manage iscsi, use tab completion to get around in it)
- ls (to get an overview)
- cd /iscsi/iqn.2018-03.com.zyxel:targetname.randomstring/tpg1/ (again use tab completion, so cd /iscsi/iqn<tab<tab etc. etc.)
- set attribute authentication=0
- set attribute generate_node_acls=1
- set attribute demo_mode_write_protect=0
- I also deleted the ACLS by doing; cd acls, delete iqn
- targetcli saveconfig (normally if you exit targetcli, it will autosave, so this is just in case)
and that should be it, though a reboot of your nas wouldn’t hurt now. note that the above config is incredibly insecure, since anybody that can connect to your nas on port 3260 (default iscsi) can read/write to your iscsci portal. so you need some additional network level protection (my own nas is on a separate network, directly connected to my proxmox nodes via a switch).
I also had problems after I was able to add the iscsi storage (which I used as a volume for lvm), and I had to to do a vgchange -a y and a lvchange -a y /dev/MyLVMiSCSIStore/LUN-1 but that may be unrelated and caused by own futzing around.
The Twonky Server version 7.0.11-8.5 has a vulnerability ( CVE-2018-7171 ), which allows an attacker to access all files on the NAS542.
The version that is installed on firmware V5.21(ABAG.1) is Twonky_8.3-19_Release20161209
The suggestion is to password-protect the Twonky Server and disallow access from the internet
HDD-Installation of the fun_plug 0.7 on NAS-devices
The file named
fun_plug must be in the topmost directory of Volume_1 of your NAS and must be marked as executable (chmod 777)
Compiling for the NAS542
Links to the GPL source package are here (http://gpl.nas-central.org/ZYXEL/NAS542_GPL/)
Request Zyxel for GPL source here
Linux Device Tree for a NSA325 – may or may not be relevant
Compiling for NSA210
Fix high cpu usage on NAS
Copy files internally on NAS542 (Not via the PC)
Another way is used terminal to telnet/SSH to NAS, then use command “mv” to move the files you want to modify, and before the process finish, you only can wait or stop it by Ctrl+C.
The store folder will be here: /i-data/sysvol/, you can follow these steps to move files:
/i-data/partition1/#mv file ../partition2/target folder
three 2TB WD Enterprise SATA, a RAID5 array
Performance is unimpressive: our 25GB test file was read and written at disappointing speeds of 104MB/sec and 53MB/sec respectively. And the NAS542 really struggled with our backup test: a 22.4GB folder of 10,500 small files was written at just 27MB/sec average.
The NAS542 also supports thick and thinly provisioned iSCSI LUNS, although it isn’t straightforward to set up. ZyXEL insists on CHAP authentication and presents the target to only one iSCSI initiator, which must be declared using its full IQN.
Performance was again disappointing. Running Iometer against a 250GB target, we saw read and write speeds of only 74MB/sec and 56MB/sec respectively. The cause may not be a mystery: CPU utilisation maxed out at 100% more than once during the test.