Zyxel NAS326 Installation Instruction

~ $ cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR and SPI-dataflash.
# Futhermore, if the Flash sector size is ommitted, this value is assumed to
# be the same as the Environment size, which is valid for NOR and SPI-dataflash

# NOR example
# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
#/dev/mtd1              0x0000          0x4000          0x4000
#/dev/mtd2              0x0000          0x4000          0x4000

# MTD SPI-dataflash example
# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
#/dev/mtd5              0x4200          0x4200
#/dev/mtd6              0x4200          0x4200

# NAND example
/dev/mtd1               0x0000          0x80000         0x20000                 16
~ $ fw_printenv
Error opening lock file /var/lock/fw_printenv.lock

CP2102 seem very inexpensive indeed, but please take a look at this:

UBI: attaching mtd2 to ubi2
UBI: scanning is finished
UBI: attached mtd2 (name "Config", size 10 MiB) to ubi2
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1497890039
UBI: available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 40
UBI: background thread "ubi_bgt2d" started, PID 1566
UBIFS: background thread "ubifs_bgt2_0" started, PID 1570
UBIFS error (pid 1568): ubifs_recover_master_node: failed to recover master node
UBIFS: background thread "ubifs_bgt2_0" stops
UBI: detaching mtd2 from ubi2
UBI: mtd2 is detached from ubi2
UBI: attaching mtd2 to ubi2
UBI: scanning is finished
UBI: empty MTD device detected
UBI: attached mtd2 (name "Config", size 10 MiB) to ubi2
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 0, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 1899997034
UBI: available PEBs: 36, total reserved PEBs: 44, PEBs reserved for bad PEB handling: 40
UBI: background thread "ubi_bgt2d" started, PID 1589
UBIFS: default file-system created
UBIFS: background thread "ubifs_bgt2_0" started, PID 1594
UBIFS: mounted UBI device 2, volume 0, name "ubi_config"
UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS: FS size: 3301376 bytes (3 MiB, 26 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS: reserved for root: 155931 bytes (152 KiB)
UBIFS: media format: w4/r0 (latest is w4/r0), UUID 0A079606-A8CB-43EB-9EDA-C4A58341FB0D, small LPT model

Looks like some error makes UBI reset Config partition...

achlebek,

Sorry, it has been many years since I see stock boot log, no idea what happended there.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ok I prepared USB-attached SSD with Debian but it boots stock firmware when connected to front port.
I attach dmesg and fw_printenv - what could I do wrong?

achlebek,

It's much better if you connect a serial console and post the serial boot log so I can see what's wrong during u-boot booting. dmesg output is irrelevant at this this time.

However, your current envs are

curr_bootfrom=1
next_bootfrom=1
change_boot_part=0

And you cannot boot to Debian, so I'm guessing that the last stock kernel was booted from kernel 2.

So do this:

fw_setenv change_boot_part 1

Ad reboot.

Regardless whether you can boot into Debian, do

fw_printenv

and post here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Seems to revert to boot part 0...

CASset=max
CONTRY_TYPE=FF
FEATURE_BIT=00
MALLOC_len=5
MODEL_ID=B303
MPmode=SMP
PRODUCT_NAME=STG-328
VENDOR_NAME=MitraStar Technology Corp.
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
bootargs=console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
core_checksum_1=139349010a3b93b7a367f6a1534d09b3
core_checksum_2=0c9501a8f617f096cec0cc08925ae2a1
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:38:32:25
eth1mtu=1500
eth2addr=00:50:43:38:a6:25
eth2mtu=1500
eth3addr=00:50:43:32:a6:38
eth3mtu=1500
ethact=egiga0
ethaddr=88:AC:C0:3E:10:31
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.21(AAZF.17)
fwversion_2=V5.21(AAZF.18)
ide_path=/
image_name=uImage
img_checksum_1=95240628ae4708825a107927404881ba
img_checksum_2=93b489b3860466332964586e5a36d4a0
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_2=0x08700000
kernel_addr_r=2080000
kernel_mtd_1=3
kernel_mtd_2=5
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
loadaddr=0x02000000
loads_echo=0
modelid_1=B303
modelid_2=B303
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:25:a6:38
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
revision_1=51287
revision_2=51288
romfile_checksum_1=AB65
romfile_checksum_2=AD92
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serial_number=S200Y20059736
serverip=10.4.50.38
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
sysimg_mtd_1=4
sysimg_mtd_2=6
usb0Mode=host
usbActive=0
usbType=2
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=51f90098260baa6bfd5d1999c142be40
zld_checksum_2=149d454d0b779dbe4fbdfd1dde6031c2
curr_bootfrom=1
next_bootfrom=1
load_initrd_addr=0x2900000
load_image_addr=0x02000000
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
bootcmd_stock_1=run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000
bootcmd_stock_2=run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/uImage; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootm $load_image_addr $load_initrd_addr
bootcmd_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
kernel_addr_1=0x00000000; run bootcmd_custom;
change_boot_part=0

Try

fw_setenv curr_bootfrom 2
fw_setenv next_bootfrom 1
fw_setenv change_boot_part 1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

It freezed.

achlebek,

Connect serial console. Power up, interrupt u-boot count down, and

printenv
boot

And then post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Linux hackers!

I want to try install debian onto my old good Zyxel NAS326.
But before I begin, I have some questions.
1. In case of NAS unable to boot after modifying u-boot environment, I want to be able to connect with serial console and revert environment to the original state. I have an USB-UART converter with "3.3V / 5V" switch. Which signal voltage to use? I don't want to broke my NAS or converter...
2. Which connection parameters to use? I found this info on some zyxel forum:
- Speed: 115200 bps
- Data Bits : 8
- Parity : None
- Stop Bit : 1
- Flow Control : Off
Is this correct?

3. What you do with device after installing bare Linux onto it? Is there any instruction to install software needed to turn bare linux into NAS on such a limited hardware as NAS326? Or even better, is there some sort of script or "ansible playbook" to achieve this goal? I don't fear to do it myself, but maybe there is a shorter and better way? The main purpose of NAS is to be a NAS, isn't it?

Timo1979,

> I want to try install debian onto my old good
> Zyxel NAS326.
> But before I begin, I have some questions.

> 1. In case of NAS unable to boot after modifying
> u-boot environment, I want to be able to connect
> with serial console and revert environment to the
> original state.

> I have an USB-UART converter with
> "3.3V / 5V" switch. Which signal voltage to
> use? I don't want to broke my NAS or
> converter...

Don't connect 3.3V or 5.5V. The only connections you need are GND, TX, abd RX. You could fry the serial port if power is connect.


> 2. Which connection parameters to use? I found
> this info on some zyxel forum:
> - Speed: 115200 bps
> - Data Bits : 8
> - Parity : None
> - Stop Bit : 1
> - Flow Control : Off
> Is this correct?

Yes. It is correct.

> 3. What you do with device after installing bare
> Linux onto it? Is there any instruction to
> install software needed to turn bare linux into
> NAS on such a limited hardware as
> NAS326? Or even better, is there some sort of
> script or "ansible playbook" to achieve this goal?
> I don't fear to do it myself, but maybe there is a
> shorter and better way? The main purpose of NAS is
> to be a NAS, isn't it?

The rootfs I provided is a basic Debian rootfs. You need to install whatever packages you want. For a NAS, install things such that NFS (already in the rootfs), Samba, autofs. Those are the basics. This is a learning vehicle for beginners, and a small rootfs for the advance users (no bloat). Look in the Wiki thread for ideas what can it be used for, in addition to a basic NAS.

This box hardware seems limited, but it is more than adequate for a home NAS, i.e. media server box. Try to use NFS as much as you can. Use Samba only when you hav no choice (i.e. the client is a Window box).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Timo1979,
>
> > I have an USB-UART converter with
> > "3.3V / 5V" switch. Which signal voltage to
> > use? I don't want to broke my NAS or
> > converter...
>
> Don't connect 3.3V
> or 5.5V. The only connections you need are GND,
> TX, abd RX. You could fry the serial port if power
> is connect.

I know this. My question was about signal levels (RX and TX). As far as I know, UART signal levels may 3.3v, 5v and even 12 volts.

Anyway, I already modified u-boot using fw_setenv on stock firmware, installed rootfs on USB flash and it is working.

Thank you for reply and your great work on rootfs for NAS326!

Try to install OMV7 on Debian. It's good work on this board from USB SSD

RRRrrr,

> Try to install OMV7 on Debian. It's good work on
> this board from USB SSD

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

BTW, I've updated the installation Notes about WOL and Auto Resume.

Quote

Normal Operation

...

3. Setup WOL and Auto Resume

For WOL, see this post.
For Auto Resume and other i2c commands, see this post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)