Zyxel NSA320 Bricked (3 replies)

November 27, 2019, 3:58 am

≫ Next: U-Boot for Zyxel NSA-325v2 kwboot didn't help (4 replies)

≪ Previous: U-Boot for Zyxel NSA-325v2 (1 reply)

Hello,

I've tried to install something different than stock system, but i failed. Now my Zyxel wont boot.I found cable from old Nokia, and connect to serial and thats the output:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Nov  9 2012 - 14:55:24) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
//---  stateButtonBit = 3, recovery ---//
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0, egiga1 [PRIME]
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
NSA320>>

Printenv

bootdelay=2
baudrate=115200
loads_echo=0
eth1addr=00:19:CB:00:51:82
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=DD01
PRODUCT_NAME=NSA-320
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
ethaddr=28:28:5D:0A:31:C0
arcNumber=3956
bootargs_stock=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootargs_linux=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/sda2 rw rootwait loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr)
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
console=100000
=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
CASset=min
ethprime=egiga1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::orion:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
bootcmd='run bootcmd_linux'
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=100000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=3
netbsd_en=no
vxworks_en=no
disaMvPnp=no
hddPowerCtrl=no
enaAutoRecovery=yes
kernel_addr=0xc80000
pcieTune=no
ethact=egiga1
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/sda2 rw rootwait loglevel=8

Environment size: 2464/131068 bytes

Could anybody help me with that problem? I stucked, and dont know what next...

↧

U-Boot for Zyxel NSA-325v2 kwboot didn't help (4 replies)

November 30, 2019, 2:17 am

≫ Next: Ramdisk Corrupt or Invalid (1 reply)

≪ Previous: Zyxel NSA320 Bricked (3 replies)

Hi,
There is no stock uboot or doesn't start. I don't know history of this hardware.
Is it hardware issue or I can try something else:

/kwboot-tool# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p 
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]
?

I have second nsa325v2 and it is working fine. Does it mean that this is hardware issue ? Is there any thing else I can try ?

↧

Ramdisk Corrupt or Invalid (1 reply)

December 1, 2019, 7:18 pm

≫ Next: PogoV3ReallyBrickedNow...... (no replies)

≪ Previous: U-Boot for Zyxel NSA-325v2 kwboot didn't help (4 replies)

While I was away on holidays, my home suffered a power outage. When I came home and tried to access my GoFlexHome (that I usually turn off when going away), I couldn't. The NC Console showed me this:

Found bootable drive on usb 0
Bootargs = console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) init=/bin/systemd
loading uImage ...
5102272 bytes read in 1603 ms (3 MiB/s)
loading uInitrd ...
12593467 bytes read in 2124 ms (5.7 MiB/s)
loading DTB /boot/dts/kirkwood-goflexhome.dtb ...
10249 bytes read in 1138 ms (8.8 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.3.2-kirkwood-tld-1
   Created:      2019-12-01  15:21:21 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5102208 Bytes = 4.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.3.2-kirkwood-tld-1
   Created:      2019-12-01  15:22:11 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    12593403 Bytes = 12 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Created:      2012-10-29  22:52:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...

I tried recreating initrd.img-5.3.2-kirkwood-tld-1 and uInitrd several times and came up with the same result. I haven't changed my u-boot env variables in months and a checked the ones mentioned in the install-a-new-kernel-instructions looked good. I don't know what to do next. Is what being tagged as bad uInitrd? Suggestions?

sparks

↧

PogoV3ReallyBrickedNow...... (no replies)

December 5, 2019, 6:40 am

≫ Next: [RESOLVED] GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 (3 replies)

≪ Previous: Ramdisk Corrupt or Invalid (1 reply)

First I would like to thank all people like Bodhi en many more to provide means to keep legacy hardware up and running.

Unfortunately to keep it running is something more challenging.

After a lot of fiddling en trying I manged to have a working PogoplugPro (oxnas) booting from USB.
I had it installed with U-Boot 2013.10-tld-5 and Debian running.

In an attempt to update the uboot to 2015.10 I managed to really brick the pogo.
What went wrong?

I had ssh ´d into debian on the pogo and created some directories to manage the files. Copied uboot.2015.10-tld-2.ox820.bodhi.tar to it with scp from my desktop system. (I could not download it directly from dropbox with wget)

untarred it etc and entered the command to erase the MTD0 device (I assumed this is the SPL aera, but it does not matter anyway)

root@debian:/home/pogobackup/tmp# /usr/sbin/flash_erase /dev/mtd0 0x0 6
Erasing 128 Kibyte @ 7f623f5c00000064 --  6 % complete

Because the result did not show values that I would expect and because the memory area seemed way beyond 0x000000 I made the assumption that a reboot would be an option. ( I know Bodhi advised otherwise...)

How wrong appeared that assumption to be...................

There was no reboot. Only a dead Pogoplug. No Led, no serial, no nothing.

I am out of options now.

The only hope I have is that I may be able to boot from sata. Is that an option?

Or maybe revival using JTAG ?

Or should I accept that I really killed the device beyond revival......

The sata way is more or less described here: https://forum.doozan.com/read.php?2,32994
however I am lost at:

8b.) Run Sata uboot SCRIPT

./disk_create_shv

But before I will attempt all this I would like to know if the sata boot procedure, if implemented properly, would make a revival of the box possible.

I have been working with single board computers and electronics way long ago, so assume I could manage a JTAG recovery. However I have found no information about that with reference to the PogoproV3 system. Only de V4. And I assume that this procedure cannot be used as is for the PogoPro. Bricking it again is not needed;)

I have also noticed the mentioning of kwboot. But have no idea of that could do the job.

Hoping for the best.

hacksome

↧

[RESOLVED] GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 (3 replies)

December 22, 2019, 12:45 am

≫ Next: Pogoplug V4 no longer boots (no replies)

≪ Previous: PogoV3ReallyBrickedNow...... (no replies)

[RESOLVED] GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645

When you boot up a Pogoplug which has a USB disk attached that is larger than 2TB you get these error messages:
GPT: first_usable_lba incorrect: 22 > 0
part_print_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_print_efi: *** ERROR: Invalid Backup GPT ***

and the Pogoplug will refuse to boot Linux from that disk. The only way that worked was to boot the Pogoplug from a smaller disk, even if the rootfs and other partitions were on a 2+TB disk. It is the /boot directory that must be readable by u-boot; the rootfs partition is read by the Linux, so it can be anywhere.

The root cause of this problem is that the u-boot code does not have any support for disks larger than 2TB. These disks must be formatted with a GPT partition table, but the GPT is not the problem; the size of the disk is the problem.

This update has been tested on several large disks, including 3TB and 8TB disks. Also tested with GPT formatted disks smaller than 2TB.

Also in this patch are some changes that will improve the USB disk detection and let u-boot work with some USB disks that it failed on before.

I have created a modified version of uboot.2017.07-tld-1....bodhi.tar, one for Pogo E02 and one for Pogo V4. Both kwb's and the patchfile are in one tarball. Flash this new uboot according to the instuctions here: https://forum.doozan.com/read.php?3,12381 At "A. Flashing Instruction:"

Download link: https://www.dropbox.com/s/5ezx8dljw2kunm1/uboot.2017.07-bigdisk.tar.gz?dl=0
(You can download without logging in or having an account.)
Also attached to this post.

The patchfile applies to this source: u-boot-kirkwood-2017.07-kirkwood-tld-1.zip

↧

Pogoplug V4 no longer boots (no replies)

December 28, 2019, 7:01 am

≫ Next: Synology DJ216j NAS unbrick error (1 reply)

≪ Previous: [RESOLVED] GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 (3 replies)

Hi there, first time poster on this forum.

I can no longer boot my pogoplug V4 (pink logo) to Debian after an unsuccessful upgrade to kernel 5.4.2.
Probably took the wrong turn somewhere in Step 4 (4b I guess).

Uboot messages:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK
## 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 **

no IDE devices available

Partition Map for MMC device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	31289344  	fd637859-01	83 Boot
loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
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: ide_preinit failed
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 23 ms (0 Bytes/s)
Found bootable drive on mmc 0
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Contents of messed-up uboot printenv:

arcNumber=3960
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-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:11:22:33:44:55
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_dtb_addr=0x1c00000
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
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
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_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_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_ready_retry=15

Environment size: 2921/131068 bytes

For comparison, this is the copy of the envs from the working uboot:

arcNumber=3960
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-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:11:22:33:44:55
if_netconsole=ping $serverip
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
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
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
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_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: 2863/131068 bytes

I attempted the kwboot, but still can't boot to Debian (I have a backup copy made prior to this attempt). Nor can I access the ext3-formatted USB stick with a copy of mtd0 partition.
Also, the envs are identical (kwboot and now-messed up uboot) if it matters.

What is the best way to recover from this mess?

The long term goal is to have the pogoplug serve as asterisk server and a light duty NAS if booting issue can be fixed.

Thanks in advance.
O.

↧

Synology DJ216j NAS unbrick error (1 reply)

January 14, 2020, 10:16 am

≫ Next: RN2120v2 bricked (1 reply)

≪ Previous: Pogoplug V4 no longer boots (no replies)

Hallo, may I ask someone kind and willing which skilled enough to help me to unbrick my NAS which bricked due to the power outage during DSM update? I am cable to connect through serial console (putty) and transfer zImage and rd.bin (tftpd32) into it but facing "no ATAGS support: can't continue" message after bootm... Synology assistant and hard factory reset are not working. Thanks in advance.

↧

RN2120v2 bricked (1 reply)

January 31, 2020, 8:02 pm

≫ Next: old uboot update (3 replies)

≪ Previous: Synology DJ216j NAS unbrick error (1 reply)

Hello Everyone,
i hope someone can help me..
I was playing (yes.. my bad) with my RN2120v2 u_boot and kernel image to see if i could update debian to a more recent version, the ultimate goal was to install Nextcloud on this hardware, and somehow i bricked everything.
It all happened when trying to erase the mtd partitions i typed .chip instead of the one for the partition. (it was late night..)
All i get from serial when i press the power button now is :

BootROM 1.20
Booting from NAND flash
BootROM: Bad header at offset 00000000
BootROM: Bad header at offset 00010000
BootROM: Bad header at offset 00020000
BootROM: Bad header at offset 00030000
BootROM: Bad header at offset 00040000
BootROM: Bad header at offset 00050000
....
BootROM: Bad header at offset 012A0000
BootROM: Bad header at offset 012B0000
BootROM: Bad header at offset 012C0000
BootROM: Bad header at offset 012D0000

But my problem is not this. I read other topics and found out it is possible to get u_boot transferred over serial and from there i can restore the mtd content (which i don't have..),
so i tried to use kwboot with different images (RN104), which i suspect don't work because targeting a different cpu
I then tried to download from NetGear the source code from:
ReadyNAS OS 6 (RN102/RN104/2120) thinking i can get u_boot from there and recompile it (i did this before for other boards).

But i couldn't find any u_boot in that package! It seems the package only provide sources for the kernel and OS.
Am i missing something here? I also searched for this version over the net and it seems very hard to find.
The u_boot version is this: (from a serial dump before the mess)

BootROM 1.20
Booting from NAND flash

General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.8  (COM-PHY-V22)
Update Device ID PEX0782311AB
Update Device ID PEX1782311AB
Update Device ID PEX2782311AB
Update Device ID PEX3782311AB
Update Device ID PEX4782311AB
Update Device ID PEX5782311AB
Update Device ID PEX6782311AB
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run with PBS.
DDR3 Training Sequence - Ended Successfully 
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2011.12-gd923454 (Sep 08 2015 - 18:59:32) Marvell version: v2011.12 2014_T2.0p1
Netgear version: 09/08/2015 ReadyNAS-2120 v2.0

Board: DB-78460-BP rev 2.0
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1600 [MHz]
       L2     @ 800 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 800 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  2 GiB

Map:   Code:		0x7fedf000:0x7ff9f204
       BSS:		0x7ffefc20
       Stack:		0x7f9deef8
       Heap:		0x7f9df000:0x7fedf000

NAND:  128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0.0(0-0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1-1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.0(2-2): Root Complex Interface, Detected Link X1, GEN 2.0
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Host Mode
Modules Detected:
Net:   egiga0, egiga1 [PRIME]
Power On!

Another problem i have when i try to send u_boot.bin over the serial is that on this machine i have to keep pressing the power button for the entire time (1+ hours..) until the image is downloaded, otherwise the power button lights up the power on led for only 2 seconds. Is this common on other models?

So at the end my question is: is there anybody so kind to point me to where the u_boot for this particular board could be? Or if anybody owns a 2120 would be so kind to dump the mtd partition for u_boot and post it here?

Thanks a lot!
Sandro

↧

old uboot update (3 replies)

February 3, 2020, 12:25 am

≫ Next: Nsa320 Kernelpanic (2 replies)

≪ Previous: RN2120v2 bricked (1 reply)

hi,
i have some goflex net with the doozan uboot from 2010.
U-Boot 2010.09 (Oct 23 2010 - 11:53:10)
Marvell-GoflexNet by Jeff Doozan, Peter Carmichael

unfortunately there is no rescue in flash and i dont have an old debian usb stick (ext2 lenny i think) anymore.

so i cant boot anything to update the uboot and use a new debian system.

how can i manage to update the uboot?
i have a serial cable and an tftp server.

tia
jay

↧

Nsa320 Kernelpanic (2 replies)

February 10, 2020, 6:25 am

≫ Next: Nsa320 boot from hdd (6 replies)

≪ Previous: old uboot update (3 replies)

hi folks,

i want to revive my old Nsa320 with Debian..but no luck.
kwboot the uboot 2017.07. runs fine but booting debian ends up with kernelpanic :-(

root@DebianWorkstation:~/Downloads/kwboot-tool# kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa320.mtd0.kwb  -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 13 % [......................................................................]
 15 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 20 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 25 % [......................................................................]
 27 % [......................................................................]
 29 % [......................................................................]
 30 % [......................................................................]
 32 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 37 % [......................................................................]
 39 % [......................................................................]
 41 % [......................................................................]
 42 % [......................................................................]
 44 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 49 % [......................................................................]
 51 % [......................................................................]
 53 % [......................................................................]
 54 % [......................................................................]
 56 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 61 % [......................................................................]
 63 % [......................................................................]
 64 % [......................................................................]
 66 % [......................................................................]
 68 % [......................................................................]
 70 % [......................................................................]
 71 % [......................................................................]
 73 % [......................................................................]
 75 % [......................................................................]
 76 % [......................................................................]
 78 % [......................................................................]
 80 % [......................................................................]
 82 % [......................................................................]
 83 % [......................................................................]
 85 % [......................................................................]
 87 % [......................................................................]
 88 % [......................................................................]
 90 % [......................................................................]
 92 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


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 
NSA320> printenv
arcNumber=3956
baudrate=115200
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
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa320.dtb
ethact=egiga0
ethaddr=50:67:f0:a3:1b:54
if_netconsole=ping $serverip
ipaddr=192.168.0.222
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:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
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
serverip=192.168.0.1
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_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: 2971/131068 bytes
NSA320>

boot

starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: ide_preinit failed

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	60479488  	2431b290-01	83

## 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 ...
** File not found /boot/uEnv.txt **

no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 723 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
4976833 bytes read in 1053 ms (4.5 MiB/s)
loading uInitrd ...
EHCI timed out on TD - token=0xd8d80
9713936 bytes read in 6707 ms (1.4 MiB/s)
loading DTB /boot/dts/kirkwood-nsa320.dtb ...
13153 bytes read in 2753 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-02-07  19:18:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4976769 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 0f6bc000, end 0ffff8d0 ... OK
   Loading Device Tree to 0f6b5000, end 0f6bb360 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Zyxel NSA320
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[    0.000000][    T0] Kernel command line: console=ttyS0,115200
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000][    T0] Memory: 504168K/524288K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 20120K reserved, 0K cma-reserved)
[    0.000000][    T0] random: get_random_u32 called from cache_alloc_refill+0x38c/0x928 with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] 	Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000047][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.000796][    T0] Console: colour dummy device 80x30
[    0.000847][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000873][    T0] pid_max: default: 32768 minimum: 301
[    0.001252][    T0] LSM: Security Framework initializing
[    0.001435][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001463][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002396][    T0] *** VALIDATE proc ***
[    0.002667][    T0] *** VALIDATE cgroup1 ***
[    0.002694][    T0] *** VALIDATE cgroup2 ***
[    0.002795][    T0] CPU: Testing write buffer coherency: ok
[    0.004464][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.004785][    T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.005066][    T1] rcu: Hierarchical SRCU implementation.
[    0.008262][    T1] devtmpfs: initialized
[    0.014260][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.014292][    T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.014534][    T1] xor: measuring software checksum speed
[    0.110110][    T1]    arm4regs  :  1088.800 MB/sec
[    0.210076][    T1]    8regs     :   654.000 MB/sec
[    0.310074][    T1]    32regs    :   950.800 MB/sec
[    0.310095][    T1] xor: using function: arm4regs (1088.800 MB/sec)
[    0.310116][    T1] prandom: seed boundary self test passed
[    0.314293][    T1] prandom: 100 self tests passed
[    0.314305][    T1] pinctrl core: initialized pinctrl subsystem
[    0.315735][    T1] NET: Registered protocol family 16
[    0.316183][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.316985][    T1] audit: initializing netlink subsys (disabled)
[    0.318232][   T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
[    0.318350][    T1] cpuidle: using governor ladder
[    0.318428][    T1] cpuidle: using governor menu
[    0.318876][    T1] Feroceon L2: Enabling L2
[    0.318927][    T1] Feroceon L2: Cache support initialised.
[    0.325220][    T1] No ATAGs?
[    2.560055][    C0] random: fast init done
[    6.251920][   T71] alg: No test for lzo-rle (lzo-rle-generic)
[    6.252278][   T73] alg: No test for lzo-rle (lzo-rle-scomp)
[    6.430650][    T1] raid6: int32x8  gen()   128 MB/s
[    6.600320][    T1] raid6: int32x8  xor()    86 MB/s
[    6.770250][    T1] raid6: int32x4  gen()   130 MB/s
[    6.940237][    T1] raid6: int32x4  xor()    84 MB/s
[    7.110092][    T1] raid6: int32x2  gen()   133 MB/s
[    7.280193][    T1] raid6: int32x2  xor()    94 MB/s
[    7.450399][    T1] raid6: int32x1  gen()   100 MB/s
[    7.620404][    T1] raid6: int32x1  xor()    69 MB/s
[    7.620416][    T1] raid6: using algorithm int32x2 gen() 133 MB/s
[    7.620424][    T1] raid6: .... xor() 94 MB/s, rmw enabled
[    7.620432][    T1] raid6: using intx1 recovery algorithm
[    7.620687][    T1] vgaarb: loaded
[    7.621194][    T1] SCSI subsystem initialized
[    7.621686][    T1] usbcore: registered new interface driver usbfs
[    7.621748][    T1] usbcore: registered new interface driver hub
[    7.621840][    T1] usbcore: registered new device driver usb
[    7.622019][    T1] pps_core: LinuxPPS API ver. 1 registered
[    7.622031][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    7.622059][    T1] PTP clock support registered
[    7.623271][    T1] clocksource: Switched to clocksource orion_clocksource
[    8.654336][    T1] VFS: Disk quotas dquot_6.6.0
[    8.654433][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.664241][    T1] NET: Registered protocol family 2
[    8.665058][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[    8.665093][    T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    8.665151][    T1] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    8.665204][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    8.665301][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    8.665327][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    8.665556][    T1] NET: Registered protocol family 1
[    8.666196][    T1] RPC: Registered named UNIX socket transport module.
[    8.666211][    T1] RPC: Registered udp transport module.
[    8.666220][    T1] RPC: Registered tcp transport module.
[    8.666228][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    8.666243][    T1] PCI: CLS 0 bytes, default 32
[    8.666564][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    8.667693][    T1] Initialise system trusted keyrings
[    8.667739][    T1] Key type blacklist registered
[    8.667961][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    8.668050][    T1] zbud: loaded
[    8.669133][    T1] NFS: Registering the id_resolver key type
[    8.669173][    T1] Key type id_resolver registered
[    8.669183][    T1] Key type id_legacy registered
[    8.669204][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    8.669220][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    8.669518][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    8.669755][    T1] fuse: init (API version 7.31)
[    8.670134][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    8.670328][    T1] orangefs_init: module version upstream loaded
[    8.670341][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[    8.673533][    T1] async_tx: api initialized (async)
[    8.673555][    T1] Key type asymmetric registered
[    8.673564][    T1] Asymmetric key parser 'x509' registered
[    8.673622][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    8.675020][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    8.676979][    T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    8.677002][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    8.677018][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    8.677032][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    8.677157][    T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[    8.677198][    T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    8.678724][    T1] PCI: bus0: Fast back to back transfers disabled
[    8.678753][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    8.680202][    T1] PCI: bus1: Fast back to back transfers enabled
[    8.680228][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    8.680431][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[    8.680449][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    8.681083][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    8.744063][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    8.746041][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    8.804109][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    8.806327][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    8.807612][    T1] printk: console [ttyS0] disabled
[    8.807682][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    9.628873][    T1] printk: console [ttyS0] enabled
[    9.641362][    T1] loop: module loaded
[    9.645839][    T1] sata_mv f1080000.sata: slots 32 ports 2
[    9.654264][    T1] scsi host0: sata_mv
[    9.658715][    T1] scsi host1: sata_mv
[    9.662879][    T1] ata1: SATA max UDMA/133 irq 33
[    9.667757][    T1] ata2: SATA max UDMA/133 irq 33
[    9.673605][    T1] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[    9.680786][    T1] nand: Samsung NAND 128MiB 3,3V 8-bit
[    9.686158][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    9.694493][    T1] Scanning device for bad blocks
[    9.706557][    T1] Bad eraseblock 75 at 0x000000960000
[    9.774920][    T1] Bad eraseblock 733 at 0x000005ba0000
[    9.780597][    T1] Bad eraseblock 737 at 0x000005c20000
[    9.788594][    T1] Bad eraseblock 765 at 0x000005fa0000
[    9.800905][    T1] Bad eraseblock 838 at 0x0000068c0000
[    9.811779][    T1] Bad eraseblock 896 at 0x000007000000
[    9.829404][    T1] 9 fixed-partitions partitions found on MTD device orion_nand
[    9.836857][    T1] Creating 9 MTD partitions on "orion_nand":
[    9.842727][    T1] 0x000000000000-0x000000100000 : "uboot"
[    9.849661][    T1] 0x000000100000-0x000000180000 : "uboot_env"
[    9.856884][    T1] 0x000000180000-0x000000200000 : "key_store"
[    9.864107][    T1] 0x000000200000-0x000000280000 : "info"
[    9.870859][    T1] 0x000000280000-0x000000c80000 : "etc"
[    9.877606][    T1] 0x000000c80000-0x000001680000 : "kernel_1"
[    9.884784][    T1] 0x000001680000-0x000004640000 : "rootfs1"
[    9.891960][    T1] 0x000004640000-0x000005040000 : "kernel_2"
[    9.899168][    T1] 0x000005040000-0x000008000000 : "rootfs2"
[    9.907642][    T1] libphy: Fixed MDIO Bus: probed
[    9.913341][    T1] libphy: orion_mdio_bus: probed
[    9.919410][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    9.927505][    T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[    9.935163][    T1] mv643xx_eth: Set the PHY to fix link down
[    9.935785][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 50:67:f0:a3:1b:54
[    9.951237][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    9.958590][    T1] ehci-pci: EHCI PCI platform driver
[    9.963873][    T1] ehci-orion: EHCI orion driver
[    9.968789][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
[    9.975105][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    9.983704][    T1] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[   10.005614][  T112] ata1: SATA link down (SStatus 0 SControl F300)
[   10.013302][    T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[   10.020326][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
[   10.029482][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.037486][    T1] usb usb1: Product: EHCI Host Controller
[   10.043092][    T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-1 ehci_hcd
[   10.050456][    T1] usb usb1: SerialNumber: f1050000.ehci
[   10.056517][    T1] hub 1-0:1.0: USB hub found
[   10.061023][    T1] hub 1-0:1.0: 1 port detected
[   10.066430][    T1] usbcore: registered new interface driver usb-storage
[   10.073575][    T1] mousedev: PS/2 mouse device common for all mice
[   10.080427][    T1] rtc-mv f1010300.rtc: registered as rtc0
[   10.086348][    T1] i2c /dev entries driver
[   10.093339][    T1] rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable.
[   10.101647][    T1] rtc-pcf8563 0-0051: registered as rtc1
[   10.108888][    T1] device-mapper: uevent: version 1.0.3
[   10.114562][    T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
[   10.124184][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[   10.131441][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[   10.138853][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[   10.146303][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[   10.153129][    T1] device-mapper: raid: Loading target version 1.14.0
[   10.161729][    T1] hidraw: raw HID events driver (C) Jiri Kosina
[   10.168209][    T1] drop_monitor: Initializing network drop monitor service
[   10.175665][    T1] NET: Registered protocol family 17
[   10.181080][    T1] Key type dns_resolver registered
[   10.186826][    T1] registered taskstats version 1
[   10.191642][    T1] Loading compiled-in X.509 certificates
[   10.197268][    T1] zswap: loaded using pool lzo/zbud
[   10.217477][    T1] Key type big_key registered
[   10.225470][    T1] Key type encrypted registered
[   10.364803][  T114] ata2: SATA link down (SStatus 0 SControl F300)
[   10.381191][    T1] md: Waiting for all devices to be available before autodetect
[   10.388768][    T1] md: If you don't use raid, use raid=noautodetect
[   10.395885][    T1] md: Autodetecting RAID arrays.
[   10.400705][    T1] md: autorun ...
[   10.404273][    T1] md: ... autorun DONE.
[   10.408501][    T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[   10.416769][    T1] Please append a correct "root=" boot option; here are the available partitions:
[   10.425939][    T1] 1f00            1024 mtdblock0 
[   10.425943][    T1]  (driver?)
[   10.433956][   T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   10.441444][    T1] 1f01             512 mtdblock1 
[   10.441448][    T1]  (driver?)
[   10.449528][    T1] 1f02             512 mtdblock2 
[   10.449532][    T1]  (driver?)
[   10.457567][    T1] 1f03             512 mtdblock3 
[   10.457571][    T1]  (driver?)
[   10.465558][    T1] 1f04           10240 mtdblock4 
[   10.465561][    T1]  (driver?)
[   10.473552][    T1] 1f05           10240 mtdblock5 
[   10.473555][    T1]  (driver?)
[   10.481518][    T1] 1f06           48896 mtdblock6 
[   10.481520][    T1]  (driver?)
[   10.489506][    T1] 1f07           10240 mtdblock7 
[   10.489509][    T1]  (driver?)
[   10.497494][    T1] 1f08           48896 mtdblock8 
[   10.497497][    T1]  (driver?)
[   10.505514][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   10.514515][    T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.9-kirkwood-tld-1 #1
[   10.522200][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   10.529220][    T1] [<c010f6ac>] (unwind_backtrace) from [<c010bb00>] (show_stack+0x10/0x14)
[   10.537712][    T1] [<c010bb00>] (show_stack) from [<c0119fa0>] (panic+0xe0/0x30c)
[   10.545333][    T1] [<c0119fa0>] (panic) from [<c0e01628>] (mount_block_root+0x1bc/0x2a4)
[   10.553557][    T1] [<c0e01628>] (mount_block_root) from [<c0e017f8>] (mount_root+0xe8/0x154)
[   10.562130][    T1] [<c0e017f8>] (mount_root) from [<c0e019b0>] (prepare_namespace+0x14c/0x18c)
[   10.570875][    T1] [<c0e019b0>] (prepare_namespace) from [<c0e011c8>] (kernel_init_freeable+0x270/0x2dc)
[   10.580497][    T1] [<c0e011c8>] (kernel_init_freeable) from [<c09dcee0>] (kernel_init+0x8/0x10c)
[   10.589414][    T1] [<c09dcee0>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
[   10.597717][    T1] Exception stack(0xdf48bfb0 to 0xdf48bff8)
[   10.603492][    T1] bfa0:                                     00000000 00000000 00000000 00000000
[   10.612405][    T1] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   10.621315][    T1] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   10.628667][    T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

pls help :-((

p.s.: Sorry for the poor english..

====

Moderator edit: Add code tag. Please use code tag to post log.

↧

Nsa320 boot from hdd (6 replies)

February 13, 2020, 7:21 am

≫ Next: Unbrick Pogoplug (1 reply)

≪ Previous: Nsa320 Kernelpanic (2 replies)

hi,

i would like to boot my nas320 from sata.
formated a drive (3 TB. one partition) in ext3 and labeld "rootfs"..extracted Debian... fw_setenv bootdev=ide...
The nas load uboot 2017.07 and then only orange led blinking...
what else must done for booting sata ??

fw_printenv
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=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootdelay=10
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
partition=nand0,2
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
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_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
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3956
ethaddr=50:67:f0:a3:1b:54
dtb_file=/boot/dts/kirkwood-nsa320.dtb
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ipaddr=192.168.0.128
serverip=192.168.0.1
mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3
bootdev=ide

↧

Unbrick Pogoplug (1 reply)

February 16, 2020, 9:25 am

≫ Next: NSA325V2 with OMV or ubuntu (1 reply)

≪ Previous: Nsa320 boot from hdd (6 replies)

A few years ago... I followed this blog http://blog.qnology.com/2015/04/hacking-pogoplug-v3oxnas-proclassic.html that details your uBoot install on pogoplugs and had it all setup.

Time went by and dust gathered... And now I have a need again - but I can't find the USB that I made for this setup.

So now it doesn't exactly boot. I am a newbie or at least only know what I know... Anyway - I am in Manjaro linux and trying to SSH into the plug and... nothing. Here are some things I have tried.

Mangrove ~]$ ssh root:Password@192.168.1.13 #(No my Password is not Password but I used the CORRECT one)
ssh: connect to host 192.168.1.13 port 22: Connection timed out
Mangrove ~]$ ssh root@192.168.1.13
ssh: connect to host 192.168.1.13 port 22: Connection timed out
Mangrove ~]$ ssh 192.168.1.13
ssh: connect to host 192.168.1.13 port 22: Connection timed out

Found some mention of a default password so I tried...
Mangrove ~]$ ssh root:ceadmin@192.168.1.13
ssh: connect to host 192.168.1.13 port 22: Connection timed out

I also found some other post that discusses some method of enabling SSH -

Mangrove ~]$ curl -k "https://root:ceadmin@192.168.1.13/sqdiag/HBPlug?action=command&command=dropbear%20start"
curl: (28) Failed to connect to 192.168.1.13 port 443: Connection timed out

And for kicks I tried :
Mangrove ~]$ curl -k "https://root:Password@192.168.1.13/sqdiag/HBPlug?action=command&command=dropbear%20start"
curl: (28) Failed to connect to 192.168.1.13 port 443: Connection timed out

By the way - the front light on power up gives a green blinking light followed by green solid and then amber blinking... then blank - and then that starts over again. Maybe I have to SSH in at a certain timing? Any thoughts?

Thanks in advance for any help!

TC

↧

NSA325V2 with OMV or ubuntu (1 reply)

February 22, 2020, 6:40 am

≫ Next: U-Boot Kirkwood - NSA310 - nandump segfault (1 reply)

≪ Previous: Unbrick Pogoplug (1 reply)

Hello, i am newbie in coding boxes and my english is very bad. that's why i write my problem in german.

Ich habe ein NSA325v2 NAS mit dem

SoC: Kirkwood 88F6282_A1

und

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)

Darauf habe ich openwrt installiert.

Da ich leider mit openwrt nicht zurechtkommen würde ich gerne Ubuntu oder/und OMV darauf installieren.

Wie soll ich damit anfangen?

Ich habe Putty und ein usb to RS adapter.

↧

U-Boot Kirkwood - NSA310 - nandump segfault (1 reply)

March 1, 2020, 3:15 pm

≫ Next: Inaccessible Seagate GoFlex Home (no replies)

≪ Previous: NSA325V2 with OMV or ubuntu (1 reply)

Hi,

I am trying to flash a Zyxel NSA310 that is branded as a "TDC HomeDisk" (Denmark).

I uart-booted a new uboot and tried out the first commands if the 2017.07 U-Boot Kirkwood-Thread.

/mnt/testmount/tools # cat /etc/fw_env.config 
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
# NAND example
/dev/mtd1		0x0000		0x20000		0x20000			4

The guide says this line should be different (mtd0 instead of mtd0), can I continue with this?

The partitions are different, but according to the guide this is to be expected of NSA3xx devices:

/mnt/testmount/tools # cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"

But what's an immediate showstopper was this segfault I got while running nandump from my USB stick.

/mnt/testmount/tools # ./nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0Segmentation fault

This is from the boot of the original uboot:

20:37:30.619 ->         |  \/  | __ _ _ ____   _____| | |
20:37:30.619 ->         | |\/| |/ _` | '__\ \ / / _ \ | |
20:37:30.619 ->         | |  | | (_| | |   \ V /  __/ | |
20:37:30.619 ->         |_|  |_|\__,_|_|    \_/ \___|_|_|
20:37:30.619 ->  _   _     ____              _
20:37:30.619 -> | | | |   | __ )  ___   ___ | |_ 
20:37:30.619 -> | | | |___|  _ \ / _ \ / _ \| __| 
20:37:30.619 -> | |_| |___| |_) | (_) | (_) | |_ 
20:37:30.619 ->  \___/    |____/ \___/ \___/ \__| 
20:37:30.619 ->  ** MARVELL BOARD: RD-88F6281A LE 
20:37:30.619 -> 
20:37:30.619 -> U-Boot 1.1.4 (Feb 22 2011 - 10:31:35) Marvell version: 3.4.19
20:37:30.619 -> 
20:37:30.619 -> U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFEE0
20:37:30.685 -> 
20:37:30.685 -> Soc: 88F6281 A1 (DDR2)
20:37:30.685 -> CPU running @ 1200Mhz L2 running @ 400Mhz
20:37:30.685 -> SysClock = 400Mhz , TClock = 200Mhz 
20:37:30.685 -> 
20:37:30.685 -> DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
20:37:30.685 -> DRAM CS[0] base 0x00000000   size 256MB 
20:37:30.685 -> DRAM Total size 256MB  16bit width
20:37:30.685 -> Addresses 10M - 0M are saved for the U-Boot usage.
20:37:30.685 -> Mem malloc Initialization (10M - 7M): Done
20:37:30.738 -> NAND:128 MB
20:37:31.781 -> Flash:  0 kB
20:37:31.814 -> 
20:37:31.814 -> CPU : Marvell Feroceon (Rev 1)
20:37:32.379 -> Kernel address is 0xc80000.
20:37:32.379 -> 
20:37:32.379 -> Streaming disabled 
20:37:32.379 -> Write allocate disabled
20:37:32.379 -> 
20:37:32.379 -> Module 0 is RGMII
20:37:32.379 -> Module 1 is TDM
20:37:32.379 -> 
20:37:32.379 -> USB 0: host mode
20:37:32.911 -> PEX 0: PCI Express Root Complex Interface
20:37:32.911 -> PEX interface detected Link X1
20:37:32.944 -> Net:   egiga0, egiga1 [PRIME]
20:37:32.977 -> Hit any key to stop autoboot:  2 ??? 1 ??? 0 
20:37:34.969 -> 
20:37:34.969 -> NAND read: device 0 offset 0xc80000, size 0xa00000
20:37:35.002 -> 
20:37:35.002 -> 
Reading data from 0xc80000 --   0% complete.
[...]
Reading data from 0x167f800 -- 100% complete.
20:37:41.976 ->  10485760 bytes read: OK
20:37:41.976 -> ## Booting image at 02000000 ...
20:37:41.976 ->    Image Name:   Linux-2.6.22.18
20:37:41.976 ->    Created:      2011-02-22   3:33:51 UTC
20:37:41.976 ->    Image Type:   ARM Linux Kernel Image (uncompressed)
20:37:41.976 ->    Data Size:    5701144 Bytes =  5.4 MB
20:37:41.976 ->    Load Address: 00008000
20:37:41.976 ->    Entry Point:  00008000
20:37:41.976 ->    Verifying Checksum ... OK
20:37:43.304 -> OK
20:37:43.304 -> 
20:37:43.304 -> Starting kernel ...

Can I flash this box at all?

All internal partitions are mounted as ro, is that normal? I couldn't copy the tools folder to the internal disk to ditch the USB-drive:

/mnt/testmount/tools # mount
rootfs on / type rootfs (rw)
/proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)
/dev/mtdblock6 on /zyxel/mnt/nand type yaffs2 (ro)
/dev/sda1 on /zyxel/mnt/sysdisk type ext3 (ro,data=ordered)
/dev/loop0 on /ram_bin type ext2 (ro)
/dev/loop0 on /usr type ext2 (ro)
/dev/loop0 on /lib/security type ext2 (ro)
/dev/loop0 on /lib/modules type ext2 (ro)
/dev/ram0 on /tmp/tmpfs type tmpfs (rw)
/dev/ram0 on /usr/local/etc type tmpfs (rw)
/dev/ram0 on /usr/local/var type tmpfs (rw)
/dev/mtdblock4 on /etc/zyxel type yaffs2 (rw)
/dev/md0 on /i-data/3c7e9e7c type xfs (rw,usrquota,nouuid)
/dev/md0 on /i-data/3c7e9e7c/.media/mbvideo/Musik type xfs (rw,usrquota,nouuid)
/dev/md0 on /i-data/3c7e9e7c/.media/mbvideo/Billeder type xfs (rw,usrquota,nouuid)
/dev/md0 on /i-data/3c7e9e7c/.media/mbvideo/Videoer type xfs (rw,usrquota,nouuid)
/dev/md0 on /i-data/3c7e9e7c/.media/mbvideo/Dokumenter type xfs (rw,usrquota,nouuid)
/dev/md0 on /usr/local/apache/web_framework/data/cache type xfs (rw,usrquota,nouuid)
/dev/mtdblock4 on /usr/local/apache/web_framework/data/config type yaffs2 (rw)
/dev/md0 on /usr/local/zy-pkgs type xfs (rw,usrquota,nouuid)
/dev/md0 on /etc/zyxel/zy-pkgs type xfs (rw,usrquota,nouuid)
/dev/md0 on /usr/local/apache/htdocs/zyxel/pkg type xfs (rw,usrquota,nouuid)
/dev/sdb1 on /mnt/testmount type ext3 (rw,data=ordered)
/mnt/testmount/tools #

I am happy about any help! Thanks!

↧

Inaccessible Seagate GoFlex Home (no replies)

March 11, 2020, 3:54 am

≫ Next: GoFlex Home failed install (no replies)

≪ Previous: U-Boot Kirkwood - NSA310 - nandump segfault (1 reply)

Not been here for some time, but it's nice to see that the site is still active and bodhi is still sharing his great knowledge...

I'm trying to recover a Seagate GoFlex Home unit which I messed up some time ago. The problem was that I mixed up two units, one which accesible by a serial cable and one which wasn't, and I made a mistake with my envars and now it doesn't boot and I don't know of any way of accessing it.

Yesterday I did discover that the system would boot with a Debian USB stick inserted.... Without the stick it would go though a boot cycle with the Green LED flashing for 13 secs before switching off for 3 secs before resuming the cycle. With the Debian USB stick the Green LED flashes for 21 secs before changing to a steady Orange for 11 secs before changing to a steady Green where it stays. My DHCP server does not seem to assign an IP address so I am unable to access it, although the LEDs on the NIC are constantly flashing. To me, it looks as though the system has actually booted, and i was wondering if there was anything I could do with the Debian installation to add a start up routine which would output some msg to a flle which I could examine on another device. I'm not familiar with Debian and don't how uBoot invokes Debian and whether I can run a script to assign a static IP address which I could subsequently ping.

Any guidance would be appreciated.

↧

GoFlex Home failed install (no replies)

March 12, 2020, 8:12 am

≫ Next: unbrick uboot for iomega ix2-200 (1 reply)

≪ Previous: Inaccessible Seagate GoFlex Home (no replies)

Hi! I am new here and new at hacking my Goflex home. I tried to update to ArchLinux but at the end I did the reboot and only got a green flashing light. I have done some other things so I don't really know where I am at. I have a serial connection and am attaching a log. I have tried to Uart boot through the serial connection but I immediately get an +xmodem protocol error. Any assistance would be appreciated!

↧

unbrick uboot for iomega ix2-200 (1 reply)

March 19, 2020, 5:09 pm

≫ Next: goflexhome stop working after archlinux (3 replies)

≪ Previous: GoFlex Home failed install (no replies)

Please help with unbrick iomega ix2-200.

When trying to install Debian, it cleared the NAND.

I installed JTAG and connected to ix-200 using OpenOCD (using configuration files from iomega iconnect)

It turned out according to the instructions for installing openWRT on iconnect loaded in RAM uboot from iomega iconnect (uboot.kwb to the address 0x0600000, start from 0x0600000, then on the serial port I see a response from the NAS, there I tried to load an different backup\image to the address 0x0, but the NAS still does not load after resetting.

how do I restore the NAS? Thanks

↧

goflexhome stop working after archlinux (3 replies)

March 19, 2020, 9:00 pm

≫ Next: install u-boot on Pogoplug Pro from OpenWrt (3 replies)

≪ Previous: unbrick uboot for iomega ix2-200 (1 reply)

Guys, need help!!

... a long time ago (about 2 years ago), I was trying to Boost my GoFlexHome (2TB) NAS. Due the problems with dlna, poor network transfers speeds, lack of redundance... . And last.. I was looking for to Rsync solution.

So I followed the tutorial below:

https://archlinuxarm.org/platforms/armv5/seagate-goflex-home

step by step!!

Everything seems to be ok... until ...reboot. My GoFlex wont came back. The Green light constantly blinks. No IP address from my router. No access from any kind.

So I REALLY need your help!!

I dont even know where to start...

↧

install u-boot on Pogoplug Pro from OpenWrt (3 replies)

March 29, 2020, 5:25 am

≫ Next: Need help with creating USB for the new uBoot (1 reply)

≪ Previous: goflexhome stop working after archlinux (3 replies)

Hi,

I bought a pogoplug pro on ebay recently and decided to install OpenWrt on it. I played around with it for a bit but quickly realised that the current release of OpenWrt does not expose the internal sata port and I also had problems using different wifi cards in the pcie slot. So I decided to look into updating uboot to bohdi's version as released on the forum here to be able to run Debian on it. This was a bit more difficult than expected so I'll outline the process below which may be useful to others. This has worked for me but everything you do is at your own risk so please read the whole post and only continue if you understand the process. Messing up your uboot install will probably result in a brick so you have been warned.

The starting point is a pogoplug pro with OpenWrt 19.07.2 installed, a working serial connection and a 64 bit linux machine / VM.

OpenWrt on the Pogoplug Pro uses the following layout of the mtd:

0x000000000000-0x000000040000 : "stage1"
0x000000040000-0x0000003c0000 : "u-boot"
0x0000003c0000-0x000000440000 : "u-boot-env"
0x000000440000-0x000000e00000 : "kernel"
0x000000e00000-0x000008000000 : "ubi"

        hex           bytes           eraseblocks
mtd0    40000       262144         2          
mtd1    380000     3670016       28
mtd2    80000       524288         4
mtd3    9c0000     10223616     78
mtd4    7200000   119537664   912

To be able to flash bohdi's uboot and environment to nand you will need write access to mtd0 and mtd1. Unfortunately OpenWrt has mtd0 and mtd1 set to 'read only' by default which means it is not possible to flash uboot from the default OpenWrt install. So the first thing you need to do is to build a custom OpenWrt image which does not set mtd0 and mtd1 to 'read only'.

The following guides give a good description how to build your own custom OpenWrt image:

https://openwrt.org/docs/guide-developer/quickstart-build-images

https://openwrt.org/docs/guide-user/additional-software/beginners-build-guide

Follow these guides to setup your 64 bit linux build system / VM, download the sources and checkout branch 19.07.2

One thing to remember is that a manual / custom build of OpenWrt does not allow you to download the different prebuilt packages due to difference in 'vermagic'. The following page gives a good description how to compile a custom version of OpenWrt which still allows you to use the official openwrt package repository:

https://hamy.io/post/0015/how-to-compile-openwrt-and-still-use-the-official-repository/

It is important to do this since some additional packages are needed to be able to write uboot to nand.

Once you have setup the OpenWrt build environment and created the correct configuration a change in the OpenWrt dts file is needed to make sure mtd0 and mtd1 are writable. Open the dts file in the following folder and remove the 'read only' settings of mtd0 and mtd1 in the dts file. openwrt/target/linux/oxnas/files/arch/arm/boot/dts/ox820-cloudengines-pogoplugpro.dts Once that has been done save the dts file and continue with building your custom OpenWrt image. This may take a while depending on the speed of your build PC.

The build should complete OK and you will have a custom sysupgrade image for the pogoplug pro with the same 'vermagic' as the official builds. Now log into the luci webinterface or use ssh to connect to the device and run sysupgrade using your custom image. Once this finishes the device will reboot and you can connect via ssh / serial port again. (You may have to pull the power plug to force a reboot)

Use ssh or serial to connect to your custom OpenWrt on the pogoplug. Run the following commands to to update the openwrt package list and install the nand-utils package.

opkg update
opkg install nand-utils

Check the output of the following commands which should say that mtd0 and mtd1 are now writable.

mtdinfo /dev/mtd0
mtdinfo /dev/mtd1

Copy bodhi's pogoplug pro uboot archive to the /tmp directory (RAM) on the pogoplug. Change to the /tmp directory and extract the archive:

cd /tmp
tar xvf uboot.2015.10-tld-2.ox820.bodhi.tar

Now it is time to erase part of the nand flash and write the new uboot files there. It is important that you do not switch off the device until you have done all the steps below or you will probably end up with a brick.

Erase 2 blocks on mtd0 and write spl file to it:

flash_erase /dev/mtd0 0x0 2
nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img

Erase 8 blocks on mtd1 and write uboot and the environment to it:

flash_erase /dev/mtd1 0x0 8
nandwrite /dev/mtd1 uboot.2015.10-tld-2.ox820.mtd0.img
nandwrite -s 786432 /dev/mtd1 uboot.2015.10-tld-2.ox820.environment.img

Assuming you dont get any erors the new uboot and environment have been written to nand. When you reboot the device the serial console output should show it is now running bohdi's uboot:

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
  Boot device: NAND
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set

U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)
OXNAS OX820

Now you can connect your USB or sata drive with the Debian rootfs and it should boot into debian. You can also boot back into your custom OpenWrt in nand (as a sort of rescue system) by using the following command:

nboot 60500000 0 440000; bootm

Koen

↧

Need help with creating USB for the new uBoot (1 reply)

April 5, 2020, 8:30 am

≫ Next: Restore uboot for Synology DS414 (1 reply)

≪ Previous: install u-boot on Pogoplug Pro from OpenWrt (3 replies)

It has been many years ago that I installed debian on a dockstar using Jeff's instruction. I am familiar much with the unix command and only followed several step-by-step instruction to get things to work.

I have an old Pogo-B01 that I never used and want to put a new system into it. I have followed the steps to install new U-Boot but I did not do anything in step 11 because I did not understand how to do it. So I rebooted the box.

Quote

11. Required setup for default envs

This default envs image supports booting with multiple disk drives (and hubs) attached. The disk drives could be type (usb or sata). The scanning logic and default envs were set to automatically boot the box with the following required configuration:

r1. There must be only one partition among all partitions from all drives that contains the kernel files. The 2 kernel files are /boot/uImage and /boot/uInitrd.
r2. The partition that contains the 2 kernel files must be partition 1 in a disk drive
r3. The partition that contains the rootfs must be labeled rootfs
r4. The rootfs partition is recommended to be type Ext3 (this is not a hard requirement, ext4 should boot OK, but Ext3 will ensure no problem).

Now I am stuck as I don't have a working usb to boot it and it keeps rebooting itself. And if I stop autoboot, I would get the OX820> prompt.

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
  Boot device: NAND
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)
OXNAS OX820

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.40400000
Hit any key to stop autoboot:  0
OX820>

Can someone please guide me to the right place what I should do next or how do I create a USB stick for it?

I am accessing the box using a serial cable.

↧