Problem installing NSA320 u-boot - continued

Sorted the above out... I noticed it was out of the first mb. I have sucessfully flashed the new u-boot now. :)
However, I can't boot stock zyxel image. It seems that I can boot debian stretch (haven't had time to fully boot it up yet, that's another thing anyway) which I flashed following instructions from https://forum.doozan.com/read.php?2,12096

I think I screwed it up when I should have set

fw_setenv mtdparts 'xxxxxxxxx'

since I didn't had that variable in the backup i took of the environment before, so I just didn't run that.

Any help to restore the ability to boot the stock zyxel image is greatly appreciated. I need to boot up that one one last time to recover data I have in the JOBD partition before going with OMV.

This is the u-boot log:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700)
ZyXEL NSA320 2-Bay Power Media Server

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: WDC WD30EFRX-68EUZN0 Firm: 82.00A82 Ser#:  WD-WCC4N6UX02JH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
  Device 1: Model: WDC WD30EFRX-68EUZN0 Firm: 82.00A82 Ser#:  WD-WCC4N5JCKKV6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

Partition Map for IDE device 0  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000800      0x000f3fff      "mitraswap"
        attrs:  0x0000000000000000
        type:   0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
        type:   swap
        guid:   8a6ebe8b-87c9-4dc7-9a85-9f670ef809cf
  2     0x000f4000      0x15d509fff     "eexxtt44"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        type:   data
        guid:   9a279fa3-46de-4fae-b268-e4e15c6064b3


Partition Map for IDE device 1  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000800      0x000f3fff      "mitraswap"
        attrs:  0x0000000000000000
        type:   0657fd6d-a4ab-43c4-84e5-0933c84b4f4f
        type:   swap
        guid:   31d9fc6d-19db-4264-b8e1-e7f43baed572
  2     0x000f4000      0x15d509fff     "eexxtt44"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        type:   data
        guid:   b2806883-140c-4bcc-bfdf-39b4a6603f0b
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: WDC WD30EFRX-68EUZN0 Firm: 82.00A82 Ser#:  WD-WCC4N6UX02JH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
  Device 1: Model: WDC WD30EFRX-68EUZN0 Firm: 82.00A82 Ser#:  WD-WCC4N5JCKKV6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
device ide 0:1
** File not found /boot/uImage **
device ide 1:1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-nsa320.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
NSA320>

And here the environment printenv:

arcNumber=3956
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa320.dtb
ethact=egiga0
ethaddr=MY_MAC_IN_RIGHT_FORMAT
fileaddr=1c00000
filesize=0
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3144/131068 bytes

Edited 1 time(s). Last edit at 03/07/2018 06:57PM by bodhi.

doblecero,

> Any help to restore the ability to boot the stock
> zyxel image is greatly appreciated. I need to boot
> up that one one last time to recover data I have
> in the JOBD partition before going with OMV.

You need to flash the orginal u-boot back to mtd0 to boot stock OS. When you installed new uboot, did you do step 3?

Quote

3. Be sure to save your current uBoot image in mtd0, or have a backup image saved somewhere as precaution. And save your current u-boot envs with fw_printenv, or just copy/paste the listing into a text file. Note the nanddump command below allows future restoration to the same box you're backing up, and also can be used to restore a differrent box's mtd0 if needed.

Dumping NAND mtd0:
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0

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

Thanks Bodhi, I will do that and come back here.
I understand steps will be, being in u-boot command line:

flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 mtd0_backup_uboot

mtd0_backup_uboot -> contains the back taken with
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0

will the above also restore environment as it previously was?
Isn't any way to boot stock zyxel image with your u-boot at all? Asking for future dual compatibility....

thanks

doblecero,

> I understand steps will be, being in u-boot
> command line:
>
>

> flash_erase /dev/mtd0 0 4
> nandwrite /dev/mtd0 mtd0_backup_uboot
>

>
> mtd0_backup_uboot -> contains the back taken with
>
> nanddump --noecc --omitoob -l 0x80000 -f mtd0
> /dev/mtd0
>
> will the above also restore environment as it
> previously was?

Yes, that's correct, in a way. Stock u-boot envs are stored in mtd1. So they are untouched by the new u-boot installation (which only deals with mtd0).


> Isn't any way to boot stock zyxel image with your
> u-boot at all? Asking for future dual
> compatibility....
>

This is something that I think is feasible , but I never had the time to test and write instruction for it (I need to test on my NSA325 which is running year round for other things), so I forgot all about this on my list, perhaps this is the reminder :)

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



Edited 1 time(s). Last edit at 03/08/2018 04:14AM by bodhi.

Hi,
reverted back to stock u-boot, backed my data up, installed again latest bodhi u-boot and then debian. Finally installed omv on top of it. Everything running fine now... Let's see how debian / omv performs for a house NAS.

Thanks so much!

doblecero,

Cool! glad you got everything working.

I've looked at the stock OS booting briefly. I was not able to boot the stock kernel with new u-boot (not yet). Perhaps it is time wasting to do this, because we already have a LEDE rescue system built for this box:

https://forum.doozan.com/read.php?4,29966

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