Dear Bodhi, Thank you for your support and guide. Debian is working well on this box and it looks the wrong nand content poisoned the environment. Since I am not using the built-in kernel all NAND Bad CRC errors gone, saving the environment config and debian booting perfectly. Maybe if I can get the mtd nand backups from somebody about mtd0/1/2/3/4/5/6 partitions that I can restore toby mazsola2k - Debian
I can execute the debian guide, just I can see saveenv also part of the procedure, that actually not working on my board to keep env config in uboot. Last resort: nand scrub ? ok you anwered. In this case what about to replace the nand chip to a factory one? after that what is the actual way after to fill in uboot and mtd volumes?by mazsola2k - Debian
I executed the steps and even I modify 16 to 4, it re-sets after reboot.s / # vi /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundant # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR and SPI-dataflash. # Futhermore, if the Flash sector size is ommittby mazsola2k - Debian
If I try to make a correlation among bad blocks and zyxel uboot nand env settings: In a factory zyxel uboot the NAND Env address is here: U-Boot Environment: 0x00200000:0x00280000 (NAND) I can see that sector 280000 is a bad block nand_read_bbt: bad block at 0x000006280000 Is not simply this causing the problem? Even the save env is working, but because the first address of the U-by mazsola2k - Debian
followed your suggestion: u-boot: Hit any key to stop autoboot: 0 Marvell>> setenv next_bootfrom 2 Marvell>> setenv change_boot_part 1 Marvell>> setenv test_mazsola2k yes Marvell>> saveenv Saving Environment to NAND... Erasing Nand... Writing to Nand... done Marvell>> printenv CASset=max CONTRY_TYPE=FF FEATURE_BIT=00 MALLOC_len=5 MODEL_ID=B30by mazsola2k - Debian
uboot - change next_bootfrom 2 change_boot_part 1 Hit any key to stop autoboot: 0 Marvell>> setenv next_bootfrom 2 Marvell>> setenv change_boot_part 1 Marvell>> boot NAND read: device 0 offset 0xe00000, size 0xf00000 Skipping bad block 0x01240000 Skipping bad block 0x01ac0000 15728640 bytes read: OK * kernel: cmdline image address = 0x02000000 Starting kernby mazsola2k - Debian
Executed u-boot setenv Marvell>> setenv next_bootfrom 1 Marvell>> boot fw_printenv / # 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=tby mazsola2k - Debian
What do you think guys what can cause this situation? Failing NAND or simple a config issue? *** Warning - bad CRC, using default environment Erasing Nand... Writing to Nand... done Marvell>> nand bad Device 0 bad blocks: 3e0000 580000 1240000 1ac0000 1de0000 1e00000 2b80000 3e00000 44c0000 5f6by mazsola2k - Debian
Let me clarify: the problem is that if the system booted up and I get the shell and UI is up, everything is factory new. Everytime I reboot/restart/power cycle the system all settings wiped. Not saving my admin password / interface settings / iscsi settings. Always expanding like a fresh install after a recovery, even I do not push recovery or factory reset.by mazsola2k - Debian
I have a zyxel 326 nas (second hand), pre-owned by somebody and looks already bricked: before I install debian I would like to restore fully to original condition. I do not have the original nand backup files because I just got the NAS without any disk. At the moment the box always starting up a new/fresh factory environment regardless what you are doing or saving anything in the GUI or in filby mazsola2k - Debian