Zyxel NAS326 Installation Instruction
Posted by bodhi
|
Re: Zyxel NAS326 Installation Instruction November 16, 2019 07:33PM |
Admin Registered: 13 years ago Posts: 18,543 |
I have not yet been able to use my NAS326 to verify the envs changes in the updated instruction.
However, I've updated the 1st post to clarify that if it is the 1st time installation, then users should go ahead with the existing instruction.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
However, I've updated the 1st post to clarify that if it is the 1st time installation, then users should go ahead with the existing instruction.
Quote
Zyxel NAS326 Installation
Updated 20 Aug 2019
I'm in the process of updating the installation instruction for this box to boot with kernel linux-5.2.9-mvebu-tld-1 or later. For 1st time installation, please use the instruction below. Or wait until I have a chance to use my NAS326 to verify the new installation steps (there are only some envs changed as described here).
Installation Instruction
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Dzanar
Re: Zyxel NAS326 Installation Instruction December 17, 2019 04:52PM |
|
Re: Zyxel NAS326 Installation Instruction December 17, 2019 08:09PM |
Admin Registered: 13 years ago Posts: 18,543 |
Dzanar,
> So, I can check it. How i need change the envs to
> boot from HDD and USB?
Have you installed using the current instruction for the first time installation? is it running OK? and do you have serial console?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> So, I can check it. How i need change the envs to
> boot from HDD and USB?
Have you installed using the current instruction for the first time installation? is it running OK? and do you have serial console?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 22, 2020 12:44PM |
Admin Registered: 13 years ago Posts: 18,543 |
NAS326 Upgrade to kernel linux-5.2.9-mvebu-tld-1 or later version
The instruction below is to be executed after logged into Debian. At the time of this writing, the latest kernel is linux-5.3.5-mvebu-tld-1.
1. Install kernel
Please see the kernel upgrade instruction in the main MVEBU kernel release thread:
https://forum.doozan.com/read.php?2,32146
Scroll down to section
After installing kernel linux-5.3.5-mvebu-tld-1, immediately follow Step 2 below to modify u-boot envs.
2. Modify u-boot envs
If you have serial console connected, the envs change below can be executed at serial console prompt using setenv, too. As a matter of fact, testing these modification using serial console is recommended (to avoid committing the changes until you can boot successfully).
2.a. USB rootfs
2.b. HDD rootfs
TBD
3. Done
Reboot the box. If you have serial console, observe the boot progress and save the bootlog for future reference or troubleshooting.
After you've done the u-boot env change in step 2a, there will be no need to do it again in future kernel upgrade.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 5 time(s). Last edit at 01/23/2020 05:23AM by bodhi.
The instruction below is to be executed after logged into Debian. At the time of this writing, the latest kernel is linux-5.3.5-mvebu-tld-1.
1. Install kernel
Please see the kernel upgrade instruction in the main MVEBU kernel release thread:
https://forum.doozan.com/read.php?2,32146
Scroll down to section
Quote
Updated 12 Oct 2019:
Kernel linux-5.3.5-mvebu-tld-1 package has been uploaded.
After installing kernel linux-5.3.5-mvebu-tld-1, immediately follow Step 2 below to modify u-boot envs.
2. Modify u-boot envs
If you have serial console connected, the envs change below can be executed at serial console prompt using setenv, too. As a matter of fact, testing these modification using serial console is recommended (to avoid committing the changes until you can boot successfully).
2.a. USB rootfs
fw_setenv 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'
2.b. HDD rootfs
TBD
3. Done
Reboot the box. If you have serial console, observe the boot progress and save the bootlog for future reference or troubleshooting.
After you've done the u-boot env change in step 2a, there will be no need to do it again in future kernel upgrade.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 5 time(s). Last edit at 01/23/2020 05:23AM by bodhi.
|
Re: Zyxel NAS326 Installation Instruction January 23, 2020 04:52AM |
Admin Registered: 13 years ago Posts: 18,543 |
I've updated the NAS326 Installation Instruction to add new section:
E. Instruction for kernel upgrade after installation
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
E. Instruction for kernel upgrade after installation
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 23, 2020 11:37PM |
Registered: 4 years ago Posts: 9 |
I try to install Debian according to the instruction "B. Instruction for booting the NAS326 with a USB rootfs (setup without serial console)", but nothing happens, standard OS boots up and the password is reset. Perhaps this does not work on firmware V5.21 (AAZF.5)?
Edited 1 time(s). Last edit at 01/26/2020 03:04AM by leshk.
Edited 1 time(s). Last edit at 01/26/2020 03:04AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction January 27, 2020 05:58AM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
> I try to install Debian according to the
> instruction "B. Instruction for booting the NAS326
> with a USB rootfs (setup without serial console)",
> but nothing happens, standard OS boots up and the
> password is reset.
> Perhaps this does not work on
> firmware V5.21 (AAZF.5)?
Could be the newer FW. I don't recall which version I had when I wrote the instruction to run Debian (It might have been 5.11 since the GPL source was NAS328_511AAZF3C0.tar.gz).
The best thing to do is to connect serial console and see what possible problem might be as it occurs during booting. We will see exactly what adjustment is needed.
This box serial console is quite easy to connect. The header is factory installed, so you only need to get a serial converter module and 3 wires that usually come with it. See here:
https://forum.doozan.com/read.php?8,13263.
UPDATE:
Found FW version at the time I got this working:
fwversion_1=V5.11(AAZF.3)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 01/27/2020 06:03AM by bodhi.
> I try to install Debian according to the
> instruction "B. Instruction for booting the NAS326
> with a USB rootfs (setup without serial console)",
> but nothing happens, standard OS boots up and the
> password is reset.
> Perhaps this does not work on
> firmware V5.21 (AAZF.5)?
Could be the newer FW. I don't recall which version I had when I wrote the instruction to run Debian (It might have been 5.11 since the GPL source was NAS328_511AAZF3C0.tar.gz).
The best thing to do is to connect serial console and see what possible problem might be as it occurs during booting. We will see exactly what adjustment is needed.
This box serial console is quite easy to connect. The header is factory installed, so you only need to get a serial converter module and 3 wires that usually come with it. See here:
https://forum.doozan.com/read.php?8,13263.
UPDATE:
Found FW version at the time I got this working:
fwversion_1=V5.11(AAZF.3)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 01/27/2020 06:03AM by bodhi.
|
Re: Zyxel NAS326 Installation Instruction January 27, 2020 06:04AM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
In stock OS,
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
In stock OS,
fw_printenvAnd please post the output here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 27, 2020 10:17AM |
Registered: 4 years ago Posts: 9 |
bodhi,
today I tried to execute point "A" using a serial console. Failure again. Apparently I'm making a mistake somewhere, maybe the problem is in preparing usb drive. However, I am using Debian/Ubuntu in a virtual machine.
Edited 3 time(s). Last edit at 01/27/2020 10:50AM by leshk.
today I tried to execute point "A" using a serial console. Failure again. Apparently I'm making a mistake somewhere, maybe the problem is in preparing usb drive. However, I am using Debian/Ubuntu in a virtual machine.
~ # fw_printenv
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 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial
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_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
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;
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
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
core_checksum_1=ef8a9629888e1ceec7460982d09cb77b
core_checksum_2=2f15113ab9fcc197123bcdbe440d7a5c
curr_bootfrom=2
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1mtu=1500
eth2mtu=1500
eth3mtu=1500
ethact=egiga0
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.21(AAZF.4)
fwversion_2=V5.21(AAZF.5)
ide_path=/
image_name=uImage
img_checksum_1=4f8482d456f3aa06b3d7a4769916fa45
img_checksum_2=02f236d559abf64ae3dcd35d76269370
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom;
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
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
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)
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
next_bootfrom=2
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=51163
revision_2=51166
romfile_checksum_1=55FA
romfile_checksum_2=B86D
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serial_number=S190Y30132893
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
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
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
zld_checksum_1=fb6f99502a16990e237befde4540abd0
zld_checksum_2=e17c70cd6cf445429aa851d08f1f4269
change_boot_part=0
I changed the parameter "change_boot_part = 0" to 1. It is reset when it cannot boot from the usb.Edited 3 time(s). Last edit at 01/27/2020 10:50AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction January 27, 2020 02:05PM |
Admin Registered: 13 years ago Posts: 18,543 |
Hi leshk,
It is OK to use Debian/Ubuntu in a VM. As long as you can become root while creating the rootfs (doublecheck it with whoami command).
Since you have serial console, it is much easier to see now. Plug in the USB rootfs, and remove any HDD.
Start serial console on the VM (use picocom or minicom). Note that the /dev/tty/USB0 could be different on your VM (use dmesg to find the correct device name).
Power up the NAS326, interrupt serial console at countdown. If it does not show any output and seems to get stuck, you might need to run kwboot to get the box to boot:
And then afer you see the u-boot prompt,
And then post the entire serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It is OK to use Debian/Ubuntu in a VM. As long as you can become root while creating the rootfs (doublecheck it with whoami command).
Since you have serial console, it is much easier to see now. Plug in the USB rootfs, and remove any HDD.
Start serial console on the VM (use picocom or minicom). Note that the /dev/tty/USB0 could be different on your VM (use dmesg to find the correct device name).
picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0
Power up the NAS326, interrupt serial console at countdown. If it does not show any output and seems to get stuck, you might need to run kwboot to get the box to boot:
kwboot -t -B 115200 /dev/ttyUSB0 -d
And then afer you see the u-boot prompt,
printenv boot
And then post the entire serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 28, 2020 10:46AM |
Registered: 4 years ago Posts: 9 |
bodhi,
I do it using Putty guess there isn’t much difference? USB is connected at this time.
Quit loading:
Run boot command:
I do it using Putty guess there isn’t much difference? USB is connected at this time.
Quit loading:
Hit any key to stop autoboot: 0
Marvell>>
nknown command 'ry 'help'
Marvell>> printenv
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 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial
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_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
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;
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
bootdelay=3
cacheShare=no
change_boot_part=0
console=console=ttyS0,115200
core_checksum_1=ef8a9629888e1ceec7460982d09cb77b
core_checksum_2=2f15113ab9fcc197123bcdbe440d7a5c
curr_bootfrom=2
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1mtu=1500
eth2mtu=1500
eth3mtu=1500
ethact=egiga0
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.21(AAZF.4)
fwversion_2=V5.21(AAZF.5)
ide_path=/
image_name=uImage
img_checksum_1=4f8482d456f3aa06b3d7a4769916fa45
img_checksum_2=02f236d559abf64ae3dcd35d76269370
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom;
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
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
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)
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
next_bootfrom=2
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=51163
revision_2=51166
romfile_checksum_1=55FA
romfile_checksum_2=B86D
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serial_number=S190Y30132893
serverip=10.4.50.38
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
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
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=fb6f99502a16990e237befde4540abd0
zld_checksum_2=e17c70cd6cf445429aa851d08f1f4269
Environment size: 5158/524284 bytes
Run boot command:
Marvell>> boot
NAND read: device 0 offset 0x8700000, size 0xf00000
15728640 bytes read: OK
* kernel: cmdline image address = 0x02000000
Starting kernel ...
Power on HDD1 ...
Power on HDD2 ...
Power on USB ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.10.39 (root@SDD2SVR2) (gcc version 4.8.5 20150209 (prerelease) (crosstool-NG 1.21.0) ) #1 Wed Sep 4 14:10:07 CST 2019
CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Marvell Armada 380/381/382/385/388 (Device Tree), model: Marvell Armada 380 STG-328
bootconsole [earlycon0] enabled
Memory policy: ECC disabled, Data cache writealloc
CPU: All CPU(s) started in SVC mode.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2) earlyprintk=serial
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 504452k/504452k available, 19836k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xe0800000 - 0xfff00000 ( 503 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc081c8a8 (8275 kB)
.init : 0xc081d000 - 0xc0e3cd5c (6272 kB)
.data : 0xc0e3e000 - 0xc0e950e0 ( 349 kB)
.bss : 0xc0e950e0 - 0xc0ee2c70 ( 311 kB)
NR_IRQS:16 nr_irqs:16 16
LSP version: linux-3.10.39-2014_T3.0p7
sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410054c9, AUX_CTRL 0x16070000, Cache size: 1048576 B
Console: colour dummy device 80x30
Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc063c590 - 0xc063c5e8
mvebu-pmsu: Initializing Power Management Service Unit
Initializing CPU Reset module
devtmpfs: initialized
mvebu-soc-id: MVEBU SoC ID=0x6810, Rev=0x4
xor: measuring software checksum speed
arm4regs : 2368.000 MB/sec
8regs : 1458.800 MB/sec
32regs : 1408.000 MB/sec
xor: using function: arm4regs (2368.000 MB/sec)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
irq: Cannot allocate irq_descs @ IRQ194, assuming pre-allocated
irq: Cannot allocate irq_descs @ IRQ226, assuming pre-allocated
bio: create slab <bio-0> at 0
raid6: int32x1 203 MB/s
raid6: int32x2 270 MB/s
raid6: int32x4 283 MB/s
raid6: int32x8 323 MB/s
raid6: using algorithm int32x8 (323 MB/s)
raid6: using intx1 recovery algorithm
gpio-ms: gpio_dev = fe00000 (M: 254, m: 0)
[kernel] gpio_request for GPIO[24] failed with error number: -517
[kernel] gpio_request for GPIO[31] failed with error number: -517
[kernel] gpio_request for GPIO[44] failed with error number: -517
mvebu-pcie pcie-controller.3: PCIe0.0: link down
mvebu-pcie pcie-controller.3: PCIe1.0: link down
mvebu-pcie pcie-controller.3: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe8000000]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI: bus1: Fast back to back transfers enabled
PCI: bus2: Fast back to back transfers enabled
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:02.0: PCI bridge to [bus 02]
PCI: enabling device 0000:00:01.0 (0140 -> 0143)
PCI: enabling device 0000:00:02.0 (0140 -> 0143)
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[kernel] gpio_request for GPIO[46] failed with error number: -517
[kernel] gpio_request for GPIO[49] failed with error number: -517
[kernel] gpio_request for GPIO[39] failed with error number: -517
PTP clock support registered
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource armada_370_xp_clocksource
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
[kernel] gpio_request for GPIO[46] failed with error number: -517
Key type id_legacy registered
[kernel] gpio_request for GPIO[49] failed with error number: -517
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[kernel] gpio_request for GPIO[39] failed with error number: -517
fuse init (API version 7.22)
bio: create slab <bio-1> at 1
Btrfs loaded
msgmni has been set to 985
async_tx: api initialized (async)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
****** turn off all LEDs that turned on in u-boot ******
****** blink SYS LED ******
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR: ( xor cpy intr )
mv_xor f1060800.xor: freeing 1 in use descriptors!
mv_xor f1060800.xor: Marvell XOR: ( crc32c )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR: ( xor cpy intr )
mv_xor f1060900.xor: freeing 1 in use descriptors!
mv_xor f1060900.xor: Marvell XOR: ( crc32c )
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 44) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
brd: module loaded
loop: module loaded
ahci_mv f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
ahci_mv f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
scsi0 : ahci_mv_platform
scsi1 : ahci_mv_platform
ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 58
ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 58
armada-nand f10d0000.nand: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC
NAND device: Manufacturer ID: 0xc2, Chip ID: 0xda (Macronix NAND 256MiB 3,3V 8-bit), 256MiB, page size: 2048, OOB size: 64
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
7 cmdlinepart partitions found on MTD device armada-nand
Creating 7 MTD partitions on "armada-nand":
0x000000000000-0x000000200000 : "u-boot"
0x000000200000-0x000000400000 : "env"
0x000000400000-0x000000600000 : "config"
0x000000600000-0x000001500000 : "kernel1"
0x000001500000-0x000008300000 : "rootfs1"
0x000008300000-0x000009200000 : "kernel2"
0x000009200000-0x000010000000 : "rootfs2"
m25p80 spi0.0: unrecognized JEDEC id ffffff
SoC: model = 0x6810, revision = 0x4
o 3 Giga ports supported
o SKB recycle supported for SWF (Disabled)
o NETA acceleration mode 1
o RX Queue support: 8 Queues * 256 Descriptors
o TX Queue support: 8 Queues * 532 Descriptors
o GSO supported
o GRO supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Driver ERROR statistics enabled
o Driver INFO statistics enabled
o Driver DEBUG statistics enabled
port #0: is_sgmii=0, is_rgmii=1, phy_addr=1
o Loading network interface(s) for port #0: cpu_mask=0x1, tx_csum_limit=9800
o Port 0 is connected to Linux netdevice
o eth0, ifindex = 2, GbE port = 0
giga p=0: mtu=1500
libphy: orion_mdio_bus: probed
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-orion: EHCI orion driver
orion-ehci f1058000.usb: EHCI Host Controller
orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
orion-ehci f1058000.usb: irq 50, io mem 0xf1058000
orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.10.39 ehci_hcd
usb usb1: SerialNumber: f1058000.usb
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
xhci-hcd f10f0000.usb3: xHCI Host Controller
xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb2: SerialNumber: f10f0000.usb3
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
xhci-hcd f10f0000.usb3: xHCI Host Controller
xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 3
usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: xHCI Host Controller
usb usb3: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb3: SerialNumber: f10f0000.usb3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
xhci-hcd f10f8000.usb3: xHCI Host Controller
xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000
usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb4: SerialNumber: f10f8000.usb3
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
xhci-hcd f10f8000.usb3: xHCI Host Controller
xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5
usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: xHCI Host Controller
usb usb5: Manufacturer: Linux 3.10.39 xhci-hcd
usb usb5: SerialNumber: f10f8000.usb3
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
mvebu-rtc f10a3800.rtc: rtc core: registered f10a3800.rtc as rtc0
i2c /dev entries driver
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
cpuidle: using governor ladder
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA
sdhci-pltfm: SDHCI platform and OF driver helper
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources: Total CESA HW channels supported 2
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources: CESA feature: int_coalescing(1)
armada-cesa-ocf f109d000.crypto: mv_get_cesa_resources threshold 0x2, threshold_time 0xff
mvCesaInit: channels=2, session=640, queue=256
armada-cesa-ocf f109d000.crypto: cesa_ocf_probe: CESA driver operate in ocf(0) mode
cesadev_init(c0836b3c)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
mvebu-rtc f10a3800.rtc: setting system clock to 2020-01-28 16:30:17 UTC (1580229017)
Freeing unused kernel memory: 6268K (c081d000 - c0e3c000)
+ ECHO=/bin/echo
+ RM=/bin/rm
+ IFCONFIG=/sbin/ifconfig
+ IP=/bin/ip
+ MOUNT=/bin/mount
+ MKDIR=/bin/mkdir
+ RMDIR=/bin/rmdir
+ CAT=/bin/cat
+ MDEV=/sbin/mdev
+ SETTING_PATH=/etc/settings
+ [ -f /etc/settings/firmware_info_path ]
+ cat /etc/settings/firmware_info_path
+ BASE_PATH=/firmware
+ BASE_PATH=/firmware
+ NAND_PATH=/firmware/mnt/nand
+ DISK_PATH=/firmware/mnt/sysdisk
+ INFO_PATH=/firmware/mnt/info
+ MRD_MAC=/firmware/sbin/mrd_mac
+ INFO_PRINTENV=/firmware/sbin/info_printenv
+ INFO_SETENV=/firmware/sbin/info_setenv
+ IMG_PATH=/ram_bin
+ USB_PATH=/mnt/partnerkey
+ awk -F= {prusb 4-1: new high-speed USB device number 2 using xhci-hcd
int $2}
+ /firmware/sbin/info_printenv curr_bootfrom
+ CURR_BOOTFROM=2
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv next_bootfrom
usb 4-1: New USB device found, idVendor=0930, idProduct=6545
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-1: Product: DataTraveler 2.0
usb 4-1: Manufacturer: Kingston
usb 4-1: SerialNumber: 408D5CBF5F0AB0A07979FDC0
usb-storage 4-1:1.0: USB Mass Storage device detected
scsi2 : usb-storage 4-1:1.0
hotplug1103add:
hotplug1104add:8
+ NEXT_BOOTFROM=2
+ [ 2 != 2 ]
+ /bin/echo -e \033[031m*** Stage 1: Setup system and device drivers ***\033[0m
*** Stage 1: Setup system and device drivers ***
+ setLED SYS WHITE BLINK
Fail to open gpio device
+ /bin/mount -t proc /proc /proc
+ /bin/mount -t sysfs /sys /sys
+ /bin/mount -t usbfs none /proc/bus/usb
mount: mount point /proc/bus/usb does not exist
+ /bin/mount -t devpts devpts /dev/pts
+ awk {print $1}
+ grep gpio
+ cat /proc/devices
+ mknod -m 644 /dev/gpio c 254 0
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv fwversion_2
+ FWVERSION=V5.21(AAZF.5)
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv revision_2
+ REVISION=51166
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv modelid_2
+ MODELID=B303
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv core_checksum_2
+ CORE_CHECKSUM=2f15113ab9fcc197123bcdbe440d7a5c
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv zld_checksum_2
+ ZLD_CHECKSUM=e17c70cd6cf445429aa851d08f1f4269
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv romfile_checksum_2
+ ROMFILE_CHECKSUM=B86D
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv img_checksum_2
+ IMG_CHECKSUM=02f236d559abf64ae3dcd35d76269370
+ [ ! -d /firmware/mnt/info ]
+ /bin/mkdir -p /firmware/mnt/info
+ echo V5.21(AAZF.5)
+ echo 51166
+ echo B303
+ echo 2f15113ab9fcc197123bcdbe440d7a5c
+ echo e17c70cd6cf445429aa851d08f1f4269
+ echo B86D
+ echo 02f236d559abf64ae3dcd35d76269370
+ echo /sbin/mdev
+ /sbin/mdev -s
+ /bin/echo 32769 42768
+ /bin/echo 8192
+ /bin/echo 100
+ /bin/echo 5
+ /bin/echo 10
+ /bin/echo 512 87380 2048000
+ /bin/echo 512 65536 2048000
+ /bin/echo 524288
+ /bin/echo 524288
+ /sbin/ifconfig eth0 down
+ /firmware/sbin/mrd_mac eth0
+ /sbin/ifconfig eeth0: mac address changed
+ /bin/ip link set dev eth0 name egiga0
+ /sbin/ifconfig egiga0bmPoolId = 0 has unknown buf_size
pool #0: pkt_size=1536, buf_size=1600 - 4096 of 4096 buffers added
up
egiga0: started
IPv6: ADDRCONF(NETDEV_UP): egiga0: link is not ready
+ /sbin/ifconfig lo add 127.0.0.1 netmask 255.0.0.0
+ /sbin/ifconfig lo up
+ /sbin/ethtool -K egiga0 gso on
+ /sbin/ethtool -s egiga0 advertise 0x2f
Cannot set new settings: Invalid argument
+ /sbin/ethtool -s egiga0 autoneg on
Cannot set new settings: Invalid argument
notscsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6
setting autoneg
+ /sbin/rtcAccess show
sd 2:0:0:0: [sda] 15249408 512-byte logical blocks: (7.80 GB/7.27 GiB)
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sda: unknown partition table
sd 2:0:0:0: [sda] Attached SCSI removable disk
hotplug1115add:[/devices/soc.0/internal-regs.1/f10f8000.usb3/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sda][sda]Mass Storage device
+ rtc_time1=2020-01-28 16:30:29
+ sleep 1
+ /sbin/rtcAccess show
+ rtc_time2=2020-01-28 16:30:30
+ [ 2020-01-28 16:30:29 = 2020-01-28 16:30:30 ]
+ awk -F- {print $1}
+ echo 2020-01-28 16:30:29
+ year1=2020
+ awk -F- {print $1}
+ echo 2020-01-28 16:30:30
+ year2=2020
+ awk -F- {print $1}
+ /sbin/rtcAccess show
+ year3=2020
+ [ 2020 != 2020 ]
+ /sbin/rtcAccess rtctosys
+ echo 2
+ echo 80
+ /linuxrc
+ . /etc/profile
+ SETTING_PATH=/etc/settings
+ [ -f /etc/settings/firmware_info_path ]
+ cat /etc/settings/firmware_info_path
+ BASE_PATH=/firmware
+ PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/firmware/sbin:/usr/local/zy-pkgs/bin:/firmware/htp
+ export PATH
+ LD_LIBRARY_PATH=/lib:/usr/lib:/usr/lib/private
+ export LD_LIBRARY_PATH
+ ECHO=/bin/echo
+ CAT=/bin/cat
+ RM=/bin/rm
+ MOUNT=/bin/mount
+ UMOUNT=/bin/umount
+ IP=/bin/ip
+ IFCONFIG=/sbin/ifconfig
+ SED=/bin/sed
+ MKDIR=/bin/mkdir
+ RMDIR=/bin/rmdir
+ AWK=/bin/awk
+ MD5SUM=/sbin/md5sum
+ REBOOT=/sbin/reboot
+ BUZZERC=/sbin/buzzerc
+ LN=/bin/ln
+ INSMOD=/sbin/insmod
+ RMMOD=/sbin/rmmod
+ LSMOD=/sbin/lsmod
+ DEPMOD=/sbin/depmod
+ NAND_PATH=/firmware/mnt/nand
+ DISK_PATH=/firmware/mnt/sysdisk
+ INFO_PATH=/firmware/mnt/info
+ HTP_PATH=/firmware/htp
+ IMG_PATH=/ram_bin
+ USB_PATH=/mnt/partnerkey
+ [ -f /etc/settings/config_on_nand_path ]
+ cat /etc/settings/config_on_nand_path
+ CONF_PATH=/etc/zyxel
+ CONFIG_MTD_NUM=2
+ CONFIG_MTD=/dev/mtd2
+ CONFIG_MTD_BLOCK=/dev/mtdblock2
+ GET_MAC_MCU=/sbin/get_mac_mcu.sh
+ WRITE_MAC_MCU=/sbin/write_mac_mcu.sh
+ INFO_PRINTENV=/firmware/sbin/info_printenv
+ INFO_SETENV=/firmware/sbin/info_setenv
+ MRD_MAC=/firmware/sbin/mrd_mac
+ MRD_MODEL=/firmware/sbin/mrd_model
+ NAND_FS_TYPE=ubifs
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv curr_bootfrom
+ CURR_BOOTFROM=2
+ [ 2 = 1 ]
+ IMG_MTD=6
+ NEW_ROOT=
+ SYSINIT_PASSWD=$1$$4eHwTd8s1.UjO3wA36fmX1
+ SYSINIT_PATH=/mnt/sysinit
+ /firmware/sbin/mrd_model -p
+ MODEL_ID=B303
+ RAM_BOOT_ABLE=YES
+ echo 1
+ rescan_lost_scsi_device
+ wc -l
+ ls /sys/class/scsi_host
+ hostNum=3
+ cut -c 5
+ ls /sys/class/scsi_host
+ hostIdLst=0
1
2
+ hddId=3
+ cat /proc/hdd3_detect
cat: can't open '/proc/hdd3_detect': No such file or directory
+ [ == 1 ]
+ hddId=2
+ cat /proc/hdd2_detect
cat: can't open '/proc/hdd2_detect': No such file or directory
+ [ == 1 ]
+ hddId=1
+ cat /proc/hdd1_detect
cat: can't open '/proc/hdd1_detect': No such file or directory
+ [ == 1 ]
+ /bin/echo -e \033[031m*** Stage 2: Prepare the root file system ***\033[0m
*** Stage 2: Prepare the root file system ***
+ /bin/echo -e \033[033EXT4-fs (sda): Unrecognized mount option "iocharset=utf8" or missing value
mMount system partition...\033[0m
Mount system partition...
+ /bin/mkdir -p /firmware/mnt/nand
+ ls -l /dev/ubi_ctrl
crw-rw---- UBI: attaching mtd6 to ubi6
1 root root 10, 59 Jan 28 16:30 /dev/ubi_ctrl
+ [ ! -e /dev/ubi_ctrl ]
+ check_and_run_usbkey
+ USB_CHECK_FILE=/mnt/partnerkey/nas3xx_check_file
+ grep sd
+ ls /sys/block/
+ any_usb=sda
+ /bin/echo sda
sda
+ [ -n sda ]
+ /bin/mkdir /mnt/partnerkey
+ /bin/echo checking sda
checking sda
+ grep -c ?
+ grep ^/dev/sda
+ fdisk -l /dev/sda
+ qmark_num=0
+ grep ^/dev/sda
+ fdisk -l /dev/sda
+ partition_num=
+ [ 0 == 4 ]
+ [ == ]
+ mnt_point=/dev/sda
+ /bin/echo Trying to mount /dev/sda
Trying to mount /dev/sda
+ /bin/mount -o iocharset=utf8,shortname=mixed /dev/sda /mnt/partnerkey
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
+ grep /mnt/partnerkey
+ /bin/cat /proc/mounts
+ mount_SUC=
+ [ != ]
+ /bin/echo Fail to mount /dev/sda
Fail to mount /dev/sda
+ /bin/rmdir /mnt/partnerkey
+ ls -l /dev/ubi_ctrl
crw-rw---- 1 root root 10, 59 Jan 28 16:30 /dev/ubi_ctrl
+ ubidetach -d 0
ubidetach: error!: cannot remove ubi0
error 22 (Invalid argument)
+ ubiattach -m 6 -d 6
UBI: scanning is finished
UBI: attached mtd6 (name "rootfs2", size 110 MiB) to ubi6
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: 872, bad PEBs: 8, 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: 299540170
UBI: available PEBs: 32, total reserved PEBs: 840, PEBs reserved for bad PEB handling: 32
UBI: background thread "ubi_bgt6d" started, PID 1349
UBI device number 6, total 872 LEBs (110723072 bytes, 105.6 MiB), available 32 LEBs (4063232 bytes, 3.9 MiB), LEB size 126976 bytes (124.0 KiB)
+ ls -l /dev/ubi6 /dev/ubi6_0 /dev/ubi_ctrl
crw-rw---- 1 root root 249, 0 Jan 28 16:30 /dev/ubi6
crw-rw---- 1 root root 249, 1 Jan 28 16:30 /dev/ubi6_0
crw-rw---- 1 root root 10, 59 Jan 28 16:30 /dev/ubi_ctrl
+ [ ! -e /dev/ubi6 ]
+ ls -l /dev/ubi6 /dev/ubi6_0 /dev/ubi_ctrl
crw-rw---- 1 root root 249, 0 Jan 28 16:30 /dev/ubi6
crw-rw---- 1 root root 249, 1 Jan 28 16:30 /dev/ubi6_0
crwUBIFS: mounted UBI device 6, volume 0, name "ubi_rootfs2", R/O mode
-rw---- 1 rooUBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
t root UBIFS: FS size: 100691968 bytes (96 MiB, 793 LEBs), journal size 5079040 bytes (4 MiB, 40 LEBs)
10, 59 Jan 28 UBIFS: reserved for root: 4755930 bytes (4644 KiB)
16:30 /dev/ubi_cUBIFS: media format: w4/r0 (latest is w4/r0), UUID 92DC2E57-1707-42E0-AAF7-9AFF03C25156, small LPT model
trl
+ mount -t ubifs -o ro ubi6:ubi_rootfs2 /firmware/mnt/nand
+ [ ! -e /firmware/mnt/nand/sysdisk.img.gz ]
+ cat /proc/htp_pin
cat: can't open '/proc/htp_pin': No such file or directory
+ HTP_PIN=
+ [ == 1 ]
sh: 1: unknown operand
+ /bin/storage_asm_mntfw_swap.sh /firmware/mnt/sysdisk
/bin/storage_asm_mntfw_swap.sh: line 366: can't open /tmp/intern_disk.list: no such file
can not found fw raid uuid
can not found swap raid uuid
/bin/storage_asm_mntfw_swap.sh: line 376: can't open /tmp/intern_disk.list: no such file
/sbin/mdadm --grow /dev/md0 --raid-devices=2 --force
mdadm: /dev/md0 is not an active md array - aborting
/sbin/mdadm --grow /dev/md1 --raid-devices=2 --force
mdadm: /dev/md1 is not an active md array - aborting
storage_asm_mntfw_swap.sh can not swap on /dev/md1
+ Flag_HD_Exists=1
+ echo 1
1
+ [ 1 == 0 ]
+ echo WARNING: No valid partition on HDD or no HDD plugged!
WARNING: No valid partition on HDD or no HDD plugged!
+ [ YES == YES ]
+ BOOTDEV=RAM
+ export BOOTDEV
+ [ RAM == RAM ]
+ echo WARNING: No valid partition on HDD or no HDD plugged
WARNING: No valid partition on HDD or no HDD plugged
+ echo Boot from RAM disk
Boot from RAM disk
+ /bin/mkdir -p /firmware/mnt/sysdisk
+ /bin/mount -t ramfs none /firmware/mnt/sysdisk
+ gzip -cd /firmware/mnt/nand/sysdisk.img.gz
+ [ 0 -ne 0 ]
+ grep change_boot_part
+ /firmware/sbin/info_printenv
+ IS_CHANGE_BOOT_PART_EXIST=change_boot_part=0
+ [ change_boot_part=0 != ]
+ awk -F= {print $2}
+ /firmware/sbin/info_printenv change_boot_part
+ CHANGE_BOOT_PART=0
+ [ 0 == 1 ]
+ /bin/mount -o remount,ro /firmware/mnt/sysdisk
+ [ -e /firmware/mnt/sysdiskEXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
/mount.sda1.rw.fEXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
lag ]
+ [ -f /firmware/mnt/sysdisk/sysdisk.img ]
+ echo -e \033[033mMount system disk image ...\033[0m
Mount system disk image ...
+ /bin/mkdir -p /ram_bin
+ /bin/mount -t ext2 -o loop,ro /firmware/mnt/sysdisk/sysdisk.img /ram_bin
+ [ 0 -ne 0 ]
+ /bin/mount --bind /ram_bin/usr /usr
+ /bin/mount --bind /ram_bin/lib/security /lib/security
+ /bin/mount --bind /ram_bin/lib/modules /lib/modules
+ /bin/mount --bind /ram_bin/lib/locale /lib/locale
+ cp -a /ram_bin/bin/lld2d /ram_bin/bin/sg_mapUBI: attaching mtd2 to ubi2
/bin/
+ cp -a /ram_bin/sbin/DAV_httpd /ram_bin/sbin/controlSSHUBI: scanning is finished
.sh /ram_bin/sbin/dosfsck /ram_bin/sbin/exfatfscUBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 12, need 40
k /ram_bin/sbin/fsck.fat /ram_biUBI: attached mtd2 (name "config", size 2 MiB) to ubi2
n/sbin/fsck.hfs UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
/ram_bin/sbin/ipUBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
notify /ram_bin/UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
sbin/ipnotify_exUBI: good PEBs: 16, bad PEBs: 0, corrupted PEBs: 0
ec.sh /ram_bin/sUBI: user volume: 0, internal volumes: 1, max. volumes count: 128
bin/makekey /ramUBI: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 494224370
_bin/sbin/makepwUBI: available PEBs: 0, total reserved PEBs: 16, PEBs reserved for bad PEB handling: 12
d /ram_bin/sbin/UBI: background thread "ubi_bgt2d" started, PID 1438
mdir /ram_bin/sbin/mkdosfs /ram_bin/sbin/mkexfatfs /ram_bin/sbinUBIFS error (pid 1440): ubifs_mount: cannot open "ubi2:ubi_config", error -19
/mkfs.fat /ram_bin/sbin/monitord /ram_bin/sbin/mount.exfat-fuse /ram_bin/sbin/mount.fuse /ram_bin/sbin/mtools /ram_bin/sbin/sftp-server /ram_bin/sbin/ssh /ram_bin/sbin/ssh-keygUBI: detaching mtd2 from ubi2
en /ram_bin/sbinUBI: mtd2 is detached from ubi2
/sshd /ram_bin/sbin/target.init /ram_bin/sbin/targetcli /ram_bin/sbin/targetcli-ng /ram_bin/sbin/usbzync /ram_bin/sbin/usbzync.sh /ram_bin/sbin/usbzync_rm_rf.sh /sbin/
+ /bin/mkdir /tmp/tmpfs
+ /bin/mount -t tmpfs /dev/ram0 /tmp/tmpfs -o size=5m
+ /bin/mkdir /tmp/tmpfs/usr_etc
+ /bin/cp -a /usr/local/etc/mt-daapd /usr/local/etc/mt-daapd.conf /tmp/tmpfs/usr_etc
+ /bin/mount --bind /tmp/tmpfs/usr_etc /usr/local/etc
+ /bin/mkdir /tmp/tmpfs/usr_var
+ /bin/mount --bind /tmp/tmpfs/usr_var /usr/local/var
mount: mount point /usr/local/var does not exist
+ /bin/mkdir -p /tmp/zyxel
+ cp -a /etc/zyxel/BackupPlanner /etc/zyxel/conf /etc/zyxel/dservice.disable /etc/zyxel/hd-idle.conf /etc/zyxel/pkg_conf /etc/zyxel/storage /etc/zyxel/webdav /etc/zyxel/zyfw /tmp/zyxel
+ ubiattach -m 2 -d 2
UBI device number 2, total 16 LEBs (2031616 bytes, 1.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
+ ls -l /dev/ubi2 /dev/ubi6 /dev/ubi6_0 /dev/ubi_ctrl
crw-rw---- 1 root root 248, 0 Jan 28 16:30 /dev/ubi2
crw-rw---- 1 root root 249, 0 Jan 28 16:30 /dev/ubi6
crw-rw---- 1 root root 249, 1 Jan 28 16:30 /dev/ubi6_0
crw-rw---- 1 root root 10, 59 Jan 28 16:30 /dev/ubi_ctrl
+ [ ! -e /dev/ubi2 ]
+ /bin/mount -t ubifs ubi2:ubi_config /etc/zyxel
mount: unknown filesystem type 'ubifs'
+ [ 32 != 0 ]
+ /bin/echo mount /etc/zyxel failed
mount /etc/zyxel failed
+ prepare_config_partition
+ [ /etc/zyxel != ]
+ echo --- remove all files in /etc/zyxel
--- remove all files in /etc/zyxel
+ rm -rf /etc/zyxel/BackupPlanner /etc/zyxel/conf /etc/zyxel/dservice.disable /etc/zyxel/hd-idle.conf /etc/zyxel/pkg_conf /etc/zyxel/storage /etc/zyxel/webdav /etc/zyxel/zyfw
+ echo --- umount /etc/zyxel
--- umount /etc/zyxel
+ umount /etc/zyxel
umount: /etc/zyxel: not mounted
+ echo --- remove "ubi_config" volume
--- remove "ubi_config" volume
+ ubirmvol /dev/ubi2 -N ubi_config
ubirmvol: error!: cannot find UBI volume "ubi_config"
error 2 (No such file or directory)
+ echo --- detach ubi2 from /dev/mtd2
--- detach ubi2 from /dev/mtd2
+ ubidetach -m 2
+ sleep 1
+ [ 0 == 0 ]
+ echo --- flash_erase /dev/mtd2 0 0
--- flash_erase /dev/mtd2 0 0
+ flash_erase /dev/mtd2 0 0
ErasUBI: attaching mtd2 to ubi2complete
ing 128 Kibyte @ 20000 -- 6 % cUBI: scanning is finished
ErasingUBI: empty MTD device detected
Erasing 128 Kibyte @ a0000 -- 31UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 12, need 40
Erasing 128 Kibyte UBI: attached mtd2 (name "config", size 2 MiB) to ubi2
@ c0000 -- 37 % UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ErasinUBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
g 128 Kibyte @ eUBI: VID header offset: 2048 (aligned 2048), data offset: 4096
0000 -- 43 % comUBI: good PEBs: 16, bad PEBs: 0, corrupted PEBs: 0
Erasing 1UBI: user volume: 0, internal volumes: 1, max. volumes count: 128
28 Kibyte @ 1000UBI: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 1331785283
00 -- 50 % complUBI: available PEBs: 0, total reserved PEBs: 16, PEBs reserved for bad PEB handling: 12
Erasing 128UBI: background thread "ubi_bgt2d" started, PID 1457
Erasing 128 Kibyte @ 140000 -UBIFS error (pid 1459): ubifs_mount: cannot open "ubi2:ubi_config", error -19
Erasing 128 Kibyte @ 1e0000 -- 100 % complete
+ echo --- mount /etc/zyxel back
--- mount /etc/zyxel back
+ ubiattach -m 2 -d 2
UBI device number 2, total 16 LEBs (2031616 bytes, 1.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
+ ubimkvol /dev/ubi2 -N ubi_config -m
ubimkvol: error!: UBI device does not have free logical eraseblocks
+ /bin/mount -t ubifs ubi2:ubi_config /etc/zyxel
mount: unknown filesystem type 'ubifs'
+ /bin/cp -af /tmp/zyxel /etc/
+ rNTFS driver 2.1.30 [Flags: R/O MODULE].
m -rf /tmp/zyxel
+ [ -f /etc/zyxel/zyconf.tgz ]
+ /bin/chmod 777 /etc/zyxel
+tntfs: module license 'Commercial. For support email ntfs-support@tuxera.com.' taints kernel.
/ram_bin/etc/inDisabling lock debugging due to kernel taint
it.d/rcS2
Start rcS2 of ZyXEL sTuxera NTFS driver 3015.1.29 [Flags: R/W MODULE].
tyle
*** Stage 3: Start services on HDD ***
PPP generic driver version 2.4.2
PPP MPPE Compression module registered
PPP Deflate Compression module registered
NET: Registered protocol family 24
PPP BSD Compression module registered
HTP finished, reUBI error: ubi_attach_mtd_dev: mtd2 is already attached to ubi2
-mount /etc/zyxel
ubiattach: erUBIFS error (pid 1502): ubifs_mount: cannot open "ubi2:ubi_config", error -19
ror!: cannot attach mtd2
error 17 (File exists)
mount: unknown filesystem type 'ubifs'
Press ENTER to continue...
Starting zylogd...
zylog starts.
Starting uamd...
Starting WSGI server...
CherryPy Checker:
The Application mounted at '' has an empty config.
[28/Jan/2020:16:30:46] [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[28/Jan/2020:16:30:49] [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[28/Jan/2020:16:30:49] [network_main_model_back.py.pre](ipv6_dhcp_static_setting_apply)(229): The interface bond0 is down!
[28/Jan/2020:16:30:49] [network_common.py.pre](check_link_status)(278): the interface egiga1 is down or unusable
[28/Jan/2020:16:30:51] [network_common.py.pre](check_link_status)(278): the interface egiga1 is down or unusable
[28/Jan/2020:16:30:51] [network_main_model_back.py.pre](ipv6_dhcp_static_setting_apply)(229): The interface egiga1 is down!
[28/Jan/2020:16:30:53] [network_main_model_back.py.pre](ipv6_dhcp_static_setting_apply)(229): The interface egiga0 is down!
[28/Jan/2020:16:30:54] [network_main_model_front.py.pre](apache_config_setting)(627): There is no statement '#WebService Start#' in httpd_zld.conf. keep going...
killall: pure-ftpd: no process killed
no printer device detected.
Usage:
umount [-hV]
umount -a [options]
umount [options] <source> | <directory>
Options:
-a, --all unmount all filesystems
-A, --all-targets unmount all mountpoints for the given device in the
current namespace
-c, --no-canonicalize don't canonicalize paths
-d, --detach-loop if mounted loop device, also free this loop device
--fake dry run; skip the umount(2) syscall
-f, --force force unmount (in case of an unreachable NFS system)
-i, --internal-only don't call the umount.<type> helpers
-n, --no-mtab don't write to /etc/mtab
-l, --lazy detach the filesystem now, clean up things later
-O, --test-opts <list> limit the set of filesystems (use with -a)
-R, --recursive recursively unmount a target with all its children
-r, --read-only in case unmounting fails, try to remount read-only
-t, --types <list> limit the set of filesystem types
-v, --verbose say what is being done
-h, --help display this help and exit
-V, --version output version information and exit
For more details see umount(8).
Usage:
umount [-hV]
umount -a [options]
umount [options] <source> | <directory>
Options:
-a, --all unmount all filesystems
-A, --all-targets unmount all mountpoints for the given device in the
current namespace
-c, --no-canonicalize don't canonicalize paths
-d, --detach-loop if mounted loop device, also free this loop device
--fake dry run; skip the umount(2) syscall
-f, --force force unmount (in case of an unreachable NFS system)
-i, --internal-only don't call the umount.<type> helpers
-n, --no-mtab don't write to /etc/mtab
-l, --lazy detach the filesystem now, clean up things later
-O, --test-opts <list> limit the set of filesystems (use with -a)
-R, --recursive recursively unmount a target with all its children
-r, --read-only in case unmounting fails, try to remount read-only
-t, --types <list> limit the set of filesystem types
-v, --verbose say what is being done
-h, --help display this help and exit
-V, --version output version information and exit
For more details see umount(8).
BusyBox v1.19.4 (2019-09-04 14:02:35 CST) multi-call binary.
Usage: rmdir [OPTIONS] DIRECTORY...
No more ZySH daemon and client...
cat: can't open '/var/run/syslog-ng.pid': No such file or directory
Try to KILL SIGHUP to syslog-ng: pid=0
syslog-ng not running, start /usr/sbin/syslog-ng
server'1' has been reset
Jan 29 00:30:57 NAS326 syslog-ng[1771]: syslog-ng starting up; version='2.0.10'
argv[0]=/usr/sbin/zylog_config
argv[1]=mail
argv[2]=1
argv[3]=subject
argv[4]=NAS326 Log Report
mail server'1' subject:NAS326 Log Report
argv[0]=/usr/sbin/zylog_config
argv[1]=mail
argv[2]=1
argv[3]=schedule
argv[4]=hourly
mail server '1' schedule is : hourly
Starting "/etc/init.d/zypkg_controller.sh".
Starting to set up zy-pkgs environment ...
-> No volume exists now. zy-pkgs will not work.
Starting smbd...
Starting nmbd...
Jan 29 00:30:59 NAS326 smbd[2044]: [2020/01/29 00:30:59.975993, 0] ../source3/printing/print_standard.c:68(std_pcap_cache_reload)
Jan 29 00:30:59 NAS326 smbd[2044]: Unable to open printcap file /etc/printcap for read!
Starting NSU Agent...
Starting AFP... avahi-daemonJan 29 00:31:00 NAS326 avahi-daemon[2309]: avahi-daemon 0.6.31 starting up.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Loading service file /etc/avahi/services/afp.service.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Loading service file /etc/avahi/services/web.service.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Network interface enumeration completed.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Registering HINFO record with values 'ARMV7L'/'LINUX'.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Server startup complete. Host name is NAS326.local. Local service cookie is 3659712259.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Service "NAS326" (/etc/avahi/services/web.service) successfully established.
Jan 29 00:31:00 NAS326 avahi-daemon[2309]: Service "NAS326 (AFP)" (/etc/avahi/services/afp.service) successfully established.
netatalk.
There is no usable system volume! Do nothing...
GMT offset=28800s
setting system time zone to tz_minuteswest=-480
egrep: /etc/zyxel/conf/startup-config.conf: No such file or directory
sh: g: unknown operand
killall: hd-idle: no process killed
Jan 29 00:31:01 NAS326 netatalk[2352]: Netatalk AFP server starting
Jan 29 00:31:01 NAS326 netatalk[2352]: Registered with Zeroconf
schedule_controller is already running now.
setLED COPY OFF
led_state_map_addr = 400
setLED USB OFF
led_state_map_addr = 300
Jan 29 00:31:02 NAS326 cnid_metad[2409]: CNID Server listening on localhost:4700
hotplug_add_storage.sh:devsdx=/dev/sda
hotplug_add_storage.sh: get Legal disk node /dev/sda
EXT4-fs (sda): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sda): recovery complete
EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: errors=continue
Starting app_wd...
setLED COPY OFF
Update zypkg list
led_state_map_addr = 400
setLED COPY GREEN ON
led_state_map_addr = 406
setLED USB OFF
led_state_map_addr = 300
setLED USB GREEN ON
led_state_map_addr = 306
There is no sysvol "/i-data/.system"
===> Generate zysync server config ...
===> Generating volume list ...
===> Generating zysync config file ...
rm: can't remove '/tmp/zysync_modules': No such file or directory
===> Starting zysync server ...
[INFO]: Starting server mode ...
Done
Jan 29 00:31:05 NAS326 rsyncd[2928]: rsync: failed to open log-file /i-data/.system/zysyncd.log: No such file or directory (2)
Jan 29 00:31:05 NAS326 rsyncd[2928]: Ignoring "log file" setting.
Jan 29 00:31:05 NAS326 rsyncd[2928]: zysync server v2.00 starting, listening on port 873.
===> Generating stunnel server config file ...
===> Starting stunnel server ...
[.] stunnel 5.02 on arm-unknown-linux-gnu platform
[.] Compiled/running with OpenSSL 1.0.2h 3 May 2016
[.] Threading:FORK Sockets:POLL,IPv6 SSL:FIPS
[ ] errno: (*__errno_location ())
[.] Reading configuration from file /etc/stunneld.conf
[.] FIPS mode disabled
[ ] Compression disabled
[ ] Snagged 64 random bytes from //.rnd
[ ] Wrote 1024 new random bytes to //.rnd
[ ] PRNG seeded successfully
[ ] Initializing service [szysync]
[ ] Loading cert from file: /etc/zyxel/BackupPlanner/zysync/zysync.cert
[ ] Loading key from file: /etc/zyxel/BackupPlanner/zysync/zysync.key
[:] Insecure file permissions on /etc/zyxel/BackupPlanner/zysync/zysync.key
[ ] Private key check succeeded
[ ] DH initialization
[ ] Could not load DH parameters from /etc/zyxel/BackupPlanner/zysync/zysync.cert
[ ] Using hardcoded DH parameters
[ ] DH initialized with 2048-bit key
[ ] ECDH initialization
[ ] ECDH initialized with curve prime256v1
[ ] SSL options set: 0x01000004
[.] Configuration successful
[ ] Service [szysync] (FD=7) bound to 0.0.0.0:9527
[!] Cannot open log file: /i-data/.system/stunneld.log
[ ] Closing service [szysync]
[ ] Service [szysync] closed (FD=7)
[ ] Sessions cached before flush: 0
[ ] Sessions cached after flush: 0
[ ] Service [szysync] closed
Done
[ ok ] The Linux SCSI Target is already stopped
[warn] Creating missing directory /var/target/pr ... (warning).
[warn] Creating missing directory /var/target/alua ... (warning).
[info] The Linux SCSI Target looks properly installed.
[warn] The configfs filesystem was not mounted, consider adding it to fstab ... (warning).
Rounding down aligned max_sectors from 4294967295 to 4294967288
[info] Loaded core module target_core_file.
[warn] Core module target_core_mod already loaded ... (warning).
[info] Loaded fabric module iscsi_target_mod.
[warn] Startup config /etc/target/scsi_target.lio is empty, skipping ... (warning).
[ ok ] Started The Linux SCSI Target
2020/01/29 00:31:07 [ipnotify] : execute ipnotify STARTUP
[ipnotify_exec.sh]: ******** run ipnotify_exec.sh STARTUP********
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface egiga1 is down or unusable
the interface egiga0 is down or unusable
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
[29/Jan/2020:00:31:07] [network_common.py.pre](check_link_status)(278): the interface egiga1 is down or unusable
[29/Jan/2020:00:31:08] [network_common.py.pre](check_link_status)(278): the interface bond0 is down or unusable
[29/Jan/2020:00:31:08] [network_common.py.pre](check_link_status)(278): the interface bond1 is down or unusable
[29/Jan/2020:00:31:08] [network_common.py.pre](check_link_status)(278): the interface egiga1 is down or unusable
Device "egiga1" does not exist.
killall: httpd: no process killed
killall: httpd: no process killed
----------------------------------------------
admin
/i-data/sysvol/admin doesn't exist. Skip it.
----------------------------------------------
music
/i-data/sysvol/music doesn't exist. Skip it.
----------------------------------------------
photo
/i-data/sysvol/photo doesn't exist. Skip it.
----------------------------------------------
video
/i-data/sysvol/video doesn't exist. Skip it.
----------------------------------------------
Kingston-DataTraveler-2-0-PMAP
Jan 29 00:31:10 NAS326 ifplugd(egiga0): started: BusyBox v1.19.4 (2019-09-04 14:02:35 CST)
Jan 29 00:31:10 NAS326 ifplugd(egiga0): using SIOCETHTOOL detection mode
Jan 29 00:31:10 NAS326 ifplugd(egiga0): link is down
===> Stopping crond ...
Jan 29 00:31:12 NAS326 httpd[3194]: [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
Jan 29 00:31:12 NAS326 httpd[3194]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Jan 29 00:31:12 NAS326 httpd[3194]: [warn] RSA server certificate CommonName (CN) `NAS326' does NOT match server name!?
Jan 29 00:31:12 NAS326 httpd[3194]: [error] mod_auth_zyxel: initialized.
===> Starting crond ...
core_checksum : 2f15113ab9fcc197123bcdbe440d7a5c
fwversion : V5.21(AAZF.5)
img_checksum : 02f236d559abf64ae3dcd35d76269370
modelid : B303
revision : 51166
romfile_checksum : B86D
zld_checksum : e17c70cd6cf445429aa851d08f1f4269
OK
check time zone and modify time zone
led_state_map_addr = 6
Please press Enter to activate this console. Jan 29 00:31:14 NAS326 httpd[3195]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Jan 29 00:31:14 NAS326 httpd[3195]: [warn] RSA server certificate CommonName (CN) `NAS326' does NOT match server name!?
Jan 29 00:31:14 NAS326 httpd[3195]: [error] mod_auth_zyxel: initialized.
Jan 29 00:31:16 NAS326 afpd[2408]: dsi_tcp: couldn't find network interface with IP address to advertice, check to make sure "NAS326" is in /etc/hosts or can be resolved with DNS, or add a netinterface that is not a loopback or point-2-point type
Jan 29 00:31:16 NAS326 afpd[2408]: Netatalk AFP/TCP listening on 0.0.0.0:548
^CJan 29 00:33:01 NAS326 ntpdate[3342]: can't find host time.stdtime.gov.tw
Jan 29 00:33:01 NAS326 ntpdate[3342]: no servers can be used, exiting
|
Re: Zyxel NAS326 Installation Instruction January 28, 2020 12:33PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
> I do it using Putty guess there isn’t much
> difference? USB is connected at this time.
That's OK. With putty, you can not use kwboot. But the trick of "inserting serial console after 1 or 2 second" will allow booting. I guess that's what you did to get to the u-boot prompt.
=====
OK, let me take a look at the log and come back later today with suggestion.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I do it using Putty guess there isn’t much
> difference? USB is connected at this time.
That's OK. With putty, you can not use kwboot. But the trick of "inserting serial console after 1 or 2 second" will allow booting. I guess that's what you did to get to the u-boot prompt.
Quote
Hit any key to stop autoboot: 0
=====
OK, let me take a look at the log and come back later today with suggestion.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 28, 2020 11:38PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
The first few lines in serial console log were missing! however, I can guess what they look like. We'll give it a couple tries with putty, if not successful then you need to run Linux VM to start kwboot.
Run putty on Windows. Plug in the USB rootfs to the NAS326. Power up and let it boot into stock. Log in. And execute these 2 commands:
And then reboot. Interrupt serial console and
Please capture the entire putty log and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The first few lines in serial console log were missing! however, I can guess what they look like. We'll give it a couple tries with putty, if not successful then you need to run Linux VM to start kwboot.
Run putty on Windows. Plug in the USB rootfs to the NAS326. Power up and let it boot into stock. Log in. And execute these 2 commands:
fw_setenv change_boot_part 1 fw_setenv kernel_addr_2 '0x00000000; run bootcmd_custom;'
And then reboot. Interrupt serial console and
printenv boot
Please capture the entire putty log and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 29, 2020 01:27AM |
Registered: 4 years ago Posts: 9 |
bodhi Wrote:
-------------------------------------------------------
> leshk,
>
> And then reboot. Interrupt serial console and
>
>
> Please capture the entire putty log and post here.
When I boot after all operations
"No partition table..." - so the reason is a badly prepared usb drive?
I would like to repeat before providing full logs.
Edited 1 time(s). Last edit at 01/29/2020 01:29AM by leshk.
-------------------------------------------------------
> leshk,
>
> And then reboot. Interrupt serial console and
>
>
> printenv > boot >>
> Please capture the entire putty log and post here.
When I boot after all operations
Marvell>> boot
NAND read: device 0 whole chip
Attempt to read outside the flash area
0 bytes read: ERROR
Booting from USB ...
(Re)start USB...
USB0: Port (usbActive) : 0 Interface (usbType = 2) : USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
scanning usb for ethernet devices... 0 Ethernet Device(s) found
** No partition table - usb 0 **
** No partition table - usb 0 **
** No partition table - usb 0 **
* kernel: cmdline image address = 0x02000000
Bad Linux ARM zImage magic!
Booting from NAND kernel 1 ...
"No partition table..." - so the reason is a badly prepared usb drive?
I would like to repeat before providing full logs.
Edited 1 time(s). Last edit at 01/29/2020 01:29AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction January 29, 2020 08:23AM |
Registered: 4 years ago Posts: 9 |
bodhi Wrote:
-------------------------------------------------------
> Please capture the entire putty log and post here.
Logs are too long to be posted on the forum.
https://drive.google.com/file/d/1HTyoNaWUuTXBNlXcikbjZyu_C4Oql4F_/view?usp=sharing
-------------------------------------------------------
> Please capture the entire putty log and post here.
Logs are too long to be posted on the forum.
https://drive.google.com/file/d/1HTyoNaWUuTXBNlXcikbjZyu_C4Oql4F_/view?usp=sharing
|
Re: Zyxel NAS326 Installation Instruction January 29, 2020 02:30PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
> Logs are too long to be posted on the forum.
>
> https://drive.google.com/file/d/1HTyoNaWUuTXBNlXcikbjZyu_C4Oql4F_/view?usp=sharing
Please either attach the log file to your post (should be less than 1MB), or use pastebin.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/29/2020 05:31PM by bodhi.
> Logs are too long to be posted on the forum.
>
> https://drive.google.com/file/d/1HTyoNaWUuTXBNlXcikbjZyu_C4Oql4F_/view?usp=sharing
Please either attach the log file to your post (should be less than 1MB), or use pastebin.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/29/2020 05:31PM by bodhi.
|
Re: Zyxel NAS326 Installation Instruction January 29, 2020 02:34PM |
Admin Registered: 13 years ago Posts: 18,543 |
Quote
Marvell>> boot
NAND read: device 0 whole chip
Attempt to read outside the flash area
0 bytes read: ERROR
Booting from USB ...
That looks good! what we expected to see.
Quote
(Re)start USB...
USB0: Port (usbActive) : 0 Interface (usbType = 2) : USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
scanning usb for ethernet devices... 0 Ethernet Device(s) found
** No partition table - usb 0 **
Yes, the rootfs is suspected. Recreate it in Linux VM. Remember that you must be able to run the commands listed in the instruction with copy/paste (if not, please post questions).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/29/2020 02:35PM by bodhi.
|
Re: Zyxel NAS326 Installation Instruction January 29, 2020 11:21PM |
Registered: 4 years ago Posts: 9 |
Now I tried to prepare a usb drive and this time using terminal in safe mode. After all the actions and attempts to synchronize (sync command), a timeout error or something like that appears:
task sync:405 blocked.
When I try to unmount a device:
target is busy
"umount" only works with "-l" key or "-t". I'm starting to get confused...
task sync:405 blocked.
When I try to unmount a device:
target is busy
"umount" only works with "-l" key or "-t". I'm starting to get confused...
|
Re: Zyxel NAS326 Installation Instruction January 30, 2020 01:59AM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
You need to post the log of what you did. Usually, in Linux, that error could be because of a few different reasons.
As always, a log will tell the whole story, and therefore cutting down the amount of back and forth questions and answers in a technical forum like this (where we all are in different time zones).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You need to post the log of what you did. Usually, in Linux, that error could be because of a few different reasons.
As always, a log will tell the whole story, and therefore cutting down the amount of back and forth questions and answers in a technical forum like this (where we all are in different time zones).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 30, 2020 07:52AM |
Registered: 4 years ago Posts: 9 |
bodhi, thanks!
I used an 8 Gb flash drive and it did not work. Now I tried a 4 Gb drive and was able to boot Debian. For some reason Linux could not create a boot record on a drive larger than 4 Gb. Its presence is very easy to check the fdisk -l command.
Edited 3 time(s). Last edit at 01/30/2020 08:23AM by leshk.
I used an 8 Gb flash drive and it did not work. Now I tried a 4 Gb drive and was able to boot Debian. For some reason Linux could not create a boot record on a drive larger than 4 Gb. Its presence is very easy to check the fdisk -l command.
Edited 3 time(s). Last edit at 01/30/2020 08:23AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction January 30, 2020 05:03PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
> I used an 8 Gb flash drive and it did not work.
> Now I tried a 4 Gb drive and was able to boot
> Debian. For some reason Linux could not create a
> boot record on a drive larger than 4 Gb
That does not sound right.Tthat 4GB size is only relevant when you create the old FAT partition. It is not applicable to Ext3.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I used an 8 Gb flash drive and it did not work.
> Now I tried a 4 Gb drive and was able to boot
> Debian. For some reason Linux could not create a
> boot record on a drive larger than 4 Gb
That does not sound right.Tthat 4GB size is only relevant when you create the old FAT partition. It is not applicable to Ext3.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction January 31, 2020 08:53AM |
Registered: 4 years ago Posts: 9 |
bodhi, unfortunately I can’t provide logs of everything I do. I have to perform a lot of actions to find an approach, to understand the pattern. I managed to run Debian on an 8 Gb pendrive. All drives that I used with a volume of 4 or less than 4 Gb automatically assign Active (Active in Windows or Boot in linux) to partition, if you do use an 8 Gb pendrive the "parted / dev / sdb set 1 boot on" command helps. This has nothing to do with the structure of the FAT file system.
Edited 1 time(s). Last edit at 01/31/2020 08:57AM by leshk.
Edited 1 time(s). Last edit at 01/31/2020 08:57AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction January 31, 2020 02:11PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
That's OK. I don't need to see the log! it is apparent that you have some problem creating the rootfs on your VM. And you can see why in Debian later doing the following.
Boot you NAS326 with your 4GB rootfs into Debian. And then SSH in, or using serial console. Plug in another 8GB or greater USB flash drive, use fdisk to create 1 partition, and then format it as Ext3 using mkfs.ext3.
Note that the active boot flag is no longer needed.
Once you've done that, you can use fdisk to examine the partition and boot record of each drive.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
That's OK. I don't need to see the log! it is apparent that you have some problem creating the rootfs on your VM. And you can see why in Debian later doing the following.
Boot you NAS326 with your 4GB rootfs into Debian. And then SSH in, or using serial console. Plug in another 8GB or greater USB flash drive, use fdisk to create 1 partition, and then format it as Ext3 using mkfs.ext3.
Note that the active boot flag is no longer needed.
Once you've done that, you can use fdisk to examine the partition and boot record of each drive.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction March 08, 2020 05:39AM |
Registered: 4 years ago Posts: 9 |
bodhi, how can I return to the stock OS so that it loads right away without trying to find usb? Command from section (A4. Reverse to stock OS permanently) does not help. When loading is displayed
"Uncompressing Linux..."
upd: I successfully booted into the stock OS after changing kernel address (setenv kernel_addr_1 0x08700000). Not sure if this is correct...
Edited 1 time(s). Last edit at 03/08/2020 07:25AM by leshk.
"Uncompressing Linux..."
upd: I successfully booted into the stock OS after changing kernel address (setenv kernel_addr_1 0x08700000). Not sure if this is correct...
Edited 1 time(s). Last edit at 03/08/2020 07:25AM by leshk.
|
Re: Zyxel NAS326 Installation Instruction March 08, 2020 05:33PM |
Admin Registered: 13 years ago Posts: 18,543 |
leshk,
> upd: I successfully booted into the stock OS after
> changing kernel address (setenv kernel_addr_1
> 0x08700000). Not sure if this is correct...
That's OK. It is almost the right thing to do. Setting kernel 1 to 0x08700000 does not hurt.
The correct addrress are:
kernel 1: 0x00E00000
kernel 2: 0x08700000
You understand it correctly! basically, when you set both kernel address to stock location, it will boot back to stock after choosing one of them.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> upd: I successfully booted into the stock OS after
> changing kernel address (setenv kernel_addr_1
> 0x08700000). Not sure if this is correct...
That's OK. It is almost the right thing to do. Setting kernel 1 to 0x08700000 does not hurt.
The correct addrress are:
kernel 1: 0x00E00000
kernel 2: 0x08700000
You understand it correctly! basically, when you set both kernel address to stock location, it will boot back to stock after choosing one of them.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction March 14, 2020 06:42AM |
Registered: 4 years ago Posts: 3 |
Hi,
I've managed to boot from USB stick attached to front USB with method B. Is it also possible to boot from USB HDD attached to back USB3 ports? What I have read in the "Zyxel NAS326 - Debian / Boot from USB?" thread I have to install the kernel to NAND, right?
Edit: Is there a way to use ext4 on rootfs instead of ext4?
Edited 1 time(s). Last edit at 03/14/2020 02:15PM by mahowi.
I've managed to boot from USB stick attached to front USB with method B. Is it also possible to boot from USB HDD attached to back USB3 ports? What I have read in the "Zyxel NAS326 - Debian / Boot from USB?" thread I have to install the kernel to NAND, right?
Edit: Is there a way to use ext4 on rootfs instead of ext4?
Edited 1 time(s). Last edit at 03/14/2020 02:15PM by mahowi.
|
Re: Zyxel NAS326 Installation Instruction March 14, 2020 05:07PM |
Admin Registered: 13 years ago Posts: 18,543 |
mahowi,
> I've managed to boot from USB stick attached to
> front USB with method B. Is it also possible to
> boot from USB HDD attached to back USB3 ports?
> What I have read in the "Zyxel NAS326 - Debian /
> Boot from USB?" thread I have to install the
> kernel to NAND, right?
No, it is not possible to use the USB 3.0 port for booting. However, you can use it for the rootfs and keep the kernel files (/boot folder) in USB 2.0 port. There is a little bit more set up before you can use this configuration.
There is no need to install kernel to NAND if the kernel files are on USB 2.0 drive.
> Edit: Is there a way to use ext4 on rootfs
> instead of ext4?
I don't think this stock u-boot has that capability, but I might not remember this correctly.
If the rootfs is kept separately in a USB drive attached to USB 3.0 port, and the kernel files are in USB 2.0 drive, then yes for sure you can use Ext4 for rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I've managed to boot from USB stick attached to
> front USB with method B. Is it also possible to
> boot from USB HDD attached to back USB3 ports?
> What I have read in the "Zyxel NAS326 - Debian /
> Boot from USB?" thread I have to install the
> kernel to NAND, right?
No, it is not possible to use the USB 3.0 port for booting. However, you can use it for the rootfs and keep the kernel files (/boot folder) in USB 2.0 port. There is a little bit more set up before you can use this configuration.
There is no need to install kernel to NAND if the kernel files are on USB 2.0 drive.
> Edit: Is there a way to use ext4 on rootfs
> instead of ext4?
I don't think this stock u-boot has that capability, but I might not remember this correctly.
If the rootfs is kept separately in a USB drive attached to USB 3.0 port, and the kernel files are in USB 2.0 drive, then yes for sure you can use Ext4 for rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Zyxel NAS326 Installation Instruction March 15, 2020 05:28AM |
Registered: 4 years ago Posts: 3 |
Thanks bodhi!
I will try to setup /boot and rootfs on different drives.
But now I have the problem I can't boot anymore from my USB stick. :-(
On friday I was able to boot Debian with the help of you instructions (B). I upgraded the kernel (E) and upgraded Debian from Jessie to Stretch to Buster. All this worked and I could boot Debian Buster from my stick.
Yesterday I tried out if I could use ext4 for rootfs. So I reformatted my stick, followed the steps in B2 again, replacing ext2load with ext4load and tried to boot. This didn't work. But as you said u-boot isn't capable to read from ext4 drives.
So I reformatted my stick again to ext3, followed again all steps in B2 and rebooted my NAS. But this time my NAS won't boot. It seems to be stuck at some point because it doesn't use the alternative kernels in NAND. Only way to reboot is to pull out the stick and unplug the power chord. Power button doesn't work. Without USB stick the NAS boots to stock OS without problems.
Here is my u-boot env before entering the commands from B2 step 4:
Here's the diff after entering the commands:
Unfortunately I don't have a serial console installed. Could bad blocks in NAND be related to the problem:
There are also two different firmware versions installed:
Before I tried to use Debian I upgraded to V5.21(AAZF.7) but it seems only Kernel-2 and RootFS-2 got updated. When I reboot to stock OS now it boots to Kernel-1 and offers me to update firmware. But if I do that it still doesn't update Kernel-1 but boots to Kernel-2 telling me firmware upgrade was successful.
Is there any chance I can upgrade both NANDs and go back to default u-boot env? Are there NAND dumps available I can write back to mine? I found the scripts "fwupgrade_erase_write_ras.sh" and "fwupgrade_extract_verify.sh" in /sbin. Could I use them to manually update both kernels?
I would be happy to get Debian working on my NAS as all programs in stock OS are really outdated.
I will try to setup /boot and rootfs on different drives.
But now I have the problem I can't boot anymore from my USB stick. :-(
On friday I was able to boot Debian with the help of you instructions (B). I upgraded the kernel (E) and upgraded Debian from Jessie to Stretch to Buster. All this worked and I could boot Debian Buster from my stick.
Yesterday I tried out if I could use ext4 for rootfs. So I reformatted my stick, followed the steps in B2 again, replacing ext2load with ext4load and tried to boot. This didn't work. But as you said u-boot isn't capable to read from ext4 drives.
So I reformatted my stick again to ext3, followed again all steps in B2 and rebooted my NAS. But this time my NAS won't boot. It seems to be stuck at some point because it doesn't use the alternative kernels in NAND. Only way to reboot is to pull out the stick and unplug the power chord. Power button doesn't work. Without USB stick the NAS boots to stock OS without problems.
Here is my u-boot env before entering the commands from B2 step 4:
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_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
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;
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
bootdelay=3
cacheShare=no
change_boot_part=0
console=console=ttyS0,115200
core_checksum_1=9553ffa12382d5f49b3a38d491bd571b
core_checksum_2=361e10e8ff47b7fde6b5213473f63133
curr_bootfrom=2
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=1C:74:0D:6F:35:72
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.21(AAZF.3)
fwversion_2=V5.21(AAZF.7)
ide_path=/
image_name=uImage
img_checksum_1=d2e3440742fe5c471ab578e65f5a15c7
img_checksum_2=4a4cdf7455490a82699a8aff31a6b3c0
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom;
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
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
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
next_bootfrom=2
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=51163
revision_2=51173
romfile_checksum_1=5588
romfile_checksum_2=0943
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serial_number=S160Y18002580
serverip=10.4.50.38
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
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
usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=528e609d8bc88f809be753d814f63243
zld_checksum_2=deb847f4b52645c143e6ba18ea25fab3
Here's the diff after entering the commands:
--- nas326env 2020-03-15 10:36:00.528390997 +0100
+++ nas326envafter 2020-03-15 10:38:58.438494082 +0100
@@ -15,20 +15,15 @@
bootargs_root=root=/dev/nfs rw
bootcmd=nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
-bootcmd_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
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;
-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
bootdelay=3
cacheShare=no
-change_boot_part=0
console=console=ttyS0,115200
core_checksum_1=9553ffa12382d5f49b3a38d491bd571b
core_checksum_2=361e10e8ff47b7fde6b5213473f63133
-curr_bootfrom=2
device_partition=0:1
disaMvPnp=no
eeeEnable=no
@@ -60,7 +55,6 @@
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
-kernel_addr_1=0x00000000; run bootcmd_custom;
kernel_addr_2=0x08700000
kernel_addr_r=2080000
kernel_mtd_1=3
@@ -68,9 +62,6 @@
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
-load_dtb_addr=0x1000000
-load_image_addr=0x02000000
-load_initrd_addr=0x2900000
loadaddr=0x02000000
loads_echo=0
modelid_1=B303
@@ -83,7 +74,6 @@
netbsd_en=no
netmask=255.255.255.0
netretry=no
-next_bootfrom=2
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
@@ -100,7 +90,6 @@
script_name=boot.scr
serial_number=S160Y18002580
serverip=10.4.50.38
-set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
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
@@ -110,10 +99,21 @@
usb0Mode=host
usbActive=0
usbType=2
-usb_bootcmd=echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
-usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
-usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=528e609d8bc88f809be753d814f63243
zld_checksum_2=deb847f4b52645c143e6ba18ea25fab3
+curr_bootfrom=1
+next_bootfrom=1
+load_dtb_addr=0x1000000
+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/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_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=1
Unfortunately I don't have a serial console installed. Could bad blocks in NAND be related to the problem:
NAND device: Manufacturer ID: 0xc2, Chip ID: 0xda (Macronix NAND 256MiB 3,3V 8- bit), 256MiB, page size: 2048, OOB size: 64 Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 nand_read_bbt: bad block at 0x000002320000 nand_read_bbt: bad block at 0x000006b60000 nand_read_bbt: bad block at 0x00000cd60000 nand_read_bbt: bad block at 0x00000d920000 nand_read_bbt: bad block at 0x00000f500000 nand_read_bbt: bad block at 0x00000f940000 7 ofpart partitions found on MTD device armada-nand Creating 7 MTD partitions on "armada-nand": 0x000000000000-0x000000200000 : "U-Boot" 0x000000200000-0x000000400000 : "U-Boot env" 0x000000400000-0x000000e00000 : "Config" 0x000000e00000-0x000001d00000 : "Kernel-1" 0x000001d00000-0x000008700000 : "RootFS-1" 0x000008700000-0x000009600000 : "Kernel-2" 0x000009600000-0x000010000000 : "RootFS-2"
There are also two different firmware versions installed:
fwversion_1=V5.21(AAZF.3) fwversion_2=V5.21(AAZF.7)
Before I tried to use Debian I upgraded to V5.21(AAZF.7) but it seems only Kernel-2 and RootFS-2 got updated. When I reboot to stock OS now it boots to Kernel-1 and offers me to update firmware. But if I do that it still doesn't update Kernel-1 but boots to Kernel-2 telling me firmware upgrade was successful.
Is there any chance I can upgrade both NANDs and go back to default u-boot env? Are there NAND dumps available I can write back to mine? I found the scripts "fwupgrade_erase_write_ras.sh" and "fwupgrade_extract_verify.sh" in /sbin. Could I use them to manually update both kernels?
I would be happy to get Debian working on my NAS as all programs in stock OS are really outdated.
|
Re: Zyxel NAS326 Installation Instruction March 15, 2020 08:15AM |
Registered: 4 years ago Posts: 3 |
|
Re: Zyxel NAS326 Installation Instruction March 15, 2020 05:22PM |
Admin Registered: 13 years ago Posts: 18,543 |
mahowi,
> Ok, one problem solved. :-) u-boot doesn't like
> GPT. I accidentally used GPT instead of MBR when
> creating a new partition on my stick. Now my NAS
> boots into Debian.
Good to hear!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Ok, one problem solved. :-) u-boot doesn't like
> GPT. I accidentally used GPT instead of MBR when
> creating a new partition on my stick. Now my NAS
> boots into Debian.
Good to hear!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
