Zyxel NAS326 Installation Instruction

IIRC, there is extra no internal port that can be used for that purpose.

You could run USB rootfs and let the HDDs sleep. Running USB rootfs is fine if you take precaution avoid wear. And do backup frequently.

-bodhi
===========================
Forum Wiki
bodhi's corner

Pardon the constant questions, but "running USB rootfs" means plugging a storage device into a port and running off of that?

I ask to confirm, because of the suggestion to back up frequently, which .... there isn't anything inherently unsafe about running off of an SSD, is there!? I assume the warning was because of USB implies possibly using a flash drive or the like???

> I ask to confirm, because of the suggestion to
> back up frequently, which .... there isn't
> anything inherently unsafe about running off of an
> SSD, is there!?

There isn't anything unsafe with SSD. It will be just a bit faster than a good flash drive when it's in an USB enclosure. So you might as well use USB flash drive and make the drive "disappear" (example: Sandisk Ultra Fit)

>I assume the warning was because
> of USB implies possibly using a flash drive or the
> like???

Yes.

-bodhi
===========================
Forum Wiki
bodhi's corner

Thanks very much for your comments and recommendations!

Just want to thank everyone who made this possible.

Picked up a NAS326 a couple months ago without even knowing installing a standard Linux was already solved.

Getting it up and running with Debian was a piece of cake thanks to you.

I tried to install Debian on my nas326. Everything went smooth. But at the end I was disappointed by transfer speed. Samba, nfs copying from drive to another ... transfers are around 1/2 of what you can get from stock firmware. I will try to repeat my measurements later, but for now I will stay with stock firmware.

If you prefer modern Linux OS then install this Debian with one of the latest kernel. If you prefer speed then you will probably stay with the stock firmware.

Anyway this is really good guide how to setup Debian on NAS326.

jaro,

It's a basic Debian rootfs without any performance tuning. You actually need to do the tuning yourself. See the Wiki thread:

https://forum.doozan.com/read.php?2,23630

Quote

Perfornance Tuning & Benchmarks

Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)
Samba Tuning
Mount NTFS with big_writes
Increase NFSD max_block_size
Reduce NFSD threads

-bodhi
===========================
Forum Wiki
bodhi's corner

Not much action in this topic since november, so here is my success report.

- Installed Linux version 5.13.8-mvebu-tld-1 with no issues.on Nas326
- Didn't upgrade kernel and stuff yet.
- Added my raid which was already set up on the stock OS and set up mountpoints
- Added swap and fixed up /etc/fstab to use it.
- Needed FTP but proftpd wants systemd, so i switched over to systemd

Some of the posts say to change 'bootargs' but when using USB i needed to use usb_set_bootargs, if i had done it as posted i would have hosed my original bootargs i guess :)

usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial init=/bin/systemd"

Rebooted, but at this point the /root/set_persistent_mac_address starts to freak out and gets stuck in a loop.
I had looked at this before so i knew the ifup/ifdn was looping since pinging would show the box come & go at different ip's and filling up my dhcp client table.I hardcoded the script a bit with some sleep added.

I would reboot into stock, plug in the USB and fix it from stock OS, then sync & reboot.

#
sleep 5
UBOOT_MACADDR=`/usr/bin/fw_printenv ethaddr |  cut -c9-25`
echo "Setting Persistent MAC address to "$UBOOT_MACADDR > /dev/kmsg
/usr/bin/logger -s -i "Setting Persistent MAC address to "$UBOOT_MACADDR
ifdown eth0
ifconfig -v eth0 hw ether $UBOOT_MACADDR
ifup eth0

After this i could get eth0 to stay up at the same IP but sshd would not come up, so that was added too.

/usr/sbin/sshd -f /etc/ssh/sshd_config &
exit 0

I did apt-get update & upgrade and everthing seems smooth from here, this also seems to have fixed sshd for me.

Installed proftpd, works with insecure root stuff added. It borks out on the 'debian' hostname so i fixed that to debian.local in /etc/hostname.
Minidlna logs redirect to /dev/null
Proftpd logs to /dev/null

In theory i could now go for OMV as that was my main goal, but i'm thinking it might be a bit bloated, and i need to minimize writes for logs, configs, etc so my disks will still sleep

All in all it required a bit more effort than i expected, but this is certainly not for newbies ghehe.

Thanks for the release Bodhi!

Todo: Maybe rip Twonky DLNA from the orignal stock and make some package for it.it's inside /md0/sysdisk.img (ext2)

Managed to get Twonky running instead of MiniDLNA, it's a bit lighter on the system:

root@debian:/usr/local/dmsf# ps -aux |grep mini
minidlna  1801  0.0  3.4 134368 17436 ?        SLsl 14:23   0:00 /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r

root@debian:/usr/local/dmsf# ps -aux |grep twonk
root      2453  0.0  0.0   1572    60 pts/1    SN   14:55   0:00 /usr/local/dmsf/binary/twonkystarter -appdata /media/raid/.media/twonkymedia
root      2454  0.6  1.4  22476  7336 pts/1    SNl  14:55   0:02 /usr/local/dmsf/binary/twonkyserver -appdata /media/raid/.media/twonkymedia

Asure,

> Rebooted, but at this point the
> /root/set_persistent_mac_address starts to freak
> out and gets stuck in a loop.
> I had looked at this before so i knew the
> ifup/ifdn was looping since pinging would show the
> box come & go at different ip's and filling up my
> dhcp client table.I hardcoded the script a bit
> with some sleep added.

That's interesting, I recall somebody suggested a nicer way to do this, i.e. to avoid too much noise (I forgot where I kept the link). I use static IP mostly, so did not notice if the looping can be that bad. I probably need to add to the installation instruction to suggest an alternate place other than rc.local.

> All in all it required a bit more effort than i
> expected, but this is certainly not for newbies
> ghehe.

Definitely not for newbies. We had to work around stock u-boot limitation.

Thanks for the successful report!

-bodhi
===========================
Forum Wiki
bodhi's corner