Rescue V2.8.2 : many enhancements + full kernel support for GoFlexNet/Home, Zyxel NSA3x0 and many others

I tried to update my old rescue system on my DockStar, but i get these errors:

...
rescue:/tmp# flash_eraseall /dev/mtd2
Erasing 128 Kibyte @ 2000000 -- 100 % complete.
rescue:/tmp# ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y
[  641.322528] UBIFS error (pid 95): ubifs_read_node: bad node type (255 but expected 9)
[  641.330405] UBIFS error (pid 95): ubifs_read_node: bad node at LEB 217:92928
[  641.337507] UBIFS error (pid 95): ubifs_iget: failed to read inode 2124, error -22
[  641.345137] UBIFS error (pid 95): ubifs_lookup: dead directory entry 'ubiformat', error -22
[  641.353542] UBIFS warning (pid 95): ubifs_ro_mode: switched to read-only mode, error -22
-sh: ubiformat: Invalid argument
rescue:/tmp#

After reboot i get:

...
[   14.024824] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[   14.031901] Please append a correct "root=" boot option; here are the available partitions:
[   14.040313] 1f00            1024 mtdblock0  (driver?)
[   14.045421] 1f01            4096 mtdblock1  (driver?)
[   14.050505] 1f02           32768 mtdblock2  (driver?)
[   14.055600] 1f03          224256 mtdblock3  (driver?)
[   14.060681] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

EDIT: I have made a USB Stick with http://archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz and can boot it ;)

btw. in the instruction above is missing where i can get "flash_eraseall"... There is a note: using tools from mtd-utils But where can i get them?

From https://github.com/doozan/uBoot/blob/master/install_uboot_mtd0.sh i see that this is possible:

wget http://download.doozan.com/uboot/flash_erase
wget http://download.doozan.com/uboot/nandwrite

But where can i download "ubiformat" ?



Edited 4 time(s). Last edit at 09/02/2012 11:40AM by jedie.

jedie Wrote:
-------------------------------------------------------
> I tried to update my old rescue system on my
> DockStar, but i get these errors:
>

> ...
> rescue:/tmp# flash_eraseall /dev/mtd2
> Erasing 128 Kibyte @ 2000000 -- 100 % complete.
> rescue:/tmp# ubiformat /dev/mtd2 -s 512 -f
> rootfs-mtd2.img -y
> [  641.322528] UBIFS error (pid 95):
> ubifs_read_node: bad node type (255 but expected
> 9)
> [  641.330405] UBIFS error (pid 95):
> ubifs_read_node: bad node at LEB 217:92928
> [  641.337507] UBIFS error (pid 95): ubifs_iget:
> failed to read inode 2124, error -22
> [  641.345137] UBIFS error (pid 95): ubifs_lookup:
> dead directory entry 'ubiformat', error -22
> [  641.353542] UBIFS warning (pid 95):
> ubifs_ro_mode: switched to read-only mode, error
> -22
> -sh: ubiformat: Invalid argument
> rescue:/tmp# 
>

Your host that you were booted into is called "rescue". Is this a NAND rescue that you were booted into, or a USB rescue? (flashing your NAND while booted from NAND usually doesn't work)


> After reboot i get:
>

> ...
> [   14.024824] VFS: Cannot open root device
> "ubi0:rootfs" or unknown-block(0,0)
> [   14.031901] Please append a correct "root="
> boot option; here are the available partitions:
> [   14.040313] 1f00            1024 mtdblock0 
> (driver?)
> [   14.045421] 1f01            4096 mtdblock1 
> (driver?)
> [   14.050505] 1f02           32768 mtdblock2 
> (driver?)
> [   14.055600] 1f03          224256 mtdblock3 
> (driver?)
> [   14.060681] Kernel panic - not syncing: VFS:
> Unable to mount root fs on unknown-block(0,0)
>

>
> EDIT: I have made a USB Stick with
> http://archlinuxarm.org/os/ArchLinuxARM-armv5te-la
> test.tar.gz and can boot it ;)
>
> btw. in the instruction above is missing where i
> can get "flash_eraseall"... There is a note:
> using tools from mtd-utils But where can i
> get them?
>
> From
> https://github.com/doozan/uBoot/blob/master/instal
> l_uboot_mtd0.sh i see that this is possible:
>

wget
> http://download.doozan.com/uboot/flash_erase
> wget
> http://download.doozan.com/uboot/nandwrite

>
> But where can i download "ubiformat" ?

Some of the commands have changed with updates to MTD utils.

The best alternative may be to boot from one of my USB rescue images.

=====================================================

• davy's Github Repo's rescue-dg

davygravy Wrote:
> Your host that you were booted into is called
> "rescue". Is this a NAND rescue that you were
> booted into, or a USB rescue? (flashing your NAND
> while booted from NAND usually doesn't work)

Ah! Yes, that's it: I was in the old installed NAND rescure system.

I flash now with a debian on USB and it works.

Thank you!

I have a serial cable... But is it right that the rescue system doesn't use dhcp ? The rescue system doesn't get a IP.

It uses DHCP, and the dhcp client does work. I've tested it against 5 or 6 different routers.

Have you tried using a network scanner (angry ip scanner, for instance) to find it?

=====================================================

• davy's Github Repo's rescue-dg

Hello from France.

Thx for your good work all.

I have a question about reinstall debian with Jeff's scripts on a fresh usb stick.

Both squeeze and wheezy install scripts failed. could you help me?

Thx

Resolved :

1. mount / -rw -o remount
2. removed or rename the /usr/bin/perl symlink of the rescue system
3. mount / -r -o remount
4. cd /tmp
5. wget http://projects.doozan.com/debian/dockstar.debian-squeeze.sh
6. edit dockstar.debian-squeeze.sh and remove '--no-check-gpg ' of the following line : /usr/sbin/debootstrap --verbose --no-check-gpg --arch=$ARCH --variant=$VARIANT --include=$EXTRA_PACKAGES $RELEASE $ROOT $DEB_MIRROR
7. chmod +x dockstar.debian-squeeze.sh
8. export PATH=$PATH:/usr/sbin:/sbin
9. ./dockstar.debian-squeeze.sh

And it's OK.

I don't know if it's the right way but i have now a working usb stick.



Edited 1 time(s). Last edit at 10/11/2012 02:57AM by thunder.

Hi, is there any possibility to add udhcpd applet to busybox there?

I'm not sure whether it would interact poorly w/ what is already there in terms of daemons and udhcp* stuff.

I'll take a peek at what is there right now & post back.

=====================================================

• davy's Github Repo's rescue-dg

Thanks for the great job.

And is it possible for you to upload that environment, where you've compiled all that stuff (openvpn, busybox, e.t.c.), because I've tried to copy some programs from USB with debian, it seems to be OK if I will copy some libraries as well, but libraries on USB debian installation are newer and bigger, therefore it takes much more space, so I would like to compile some programs myself but I would need the same libraries you have used for rescue image.

How did you make udhcpc do its stuff before ntpdate? I'm having a hard time figuring out how to make ntpd run before udhcpc? I tried adding delay but the kernel always waits for ntpd to come up before executing udhcpc. Any ideas?

Are you talking about rc.d script booting process? If yes - just comment ntp related script, or paste "exit" as a second string...

Have a couple of questions:
1. Can it be installed from u-boot with tftp? I'm having problem starting Debian on USB.
2. Once inside the rescue system, is it possible to install Debian on USB using http://projects.doozan.com/debian/?

Thanks

Quote
davygravy
kk, thank you for the offer for the patch... actually, 30 minutes and some testing seems to have done it (just took the ALARM support patch and pulled out the two Pogo sections, added/modified two lines or so in each)... I now have a version 2.8.1 that extends arcNumber support for the Pogo_e02 and pogoplugv4 by their given arcNumbers...

I tested it in the PogoE02 and it works fine - setting arcNumber to 3542 enables proper LED behavior. I haven't tested it on the mtd function w/ this patch, but it shouldn't have changed anything wrt mtd.

hi all,
I successfully installed rescue system v2.8.1 on my PogoE02 (pink), and also Debian Wheezy on USB device.
They both work, but LED configuration is not fine.
In fact, in

/sys/class/leds

I only have:

plug:green:health

and

plug:red:misc

I can just switching on/off the led with orange color changing (echo..) trigger value of plug:green:health to default-on/none.
This behaviour both occur on rescue system (installed from archive at first post RescueV2.8.1-05282012.tar.gz), whose kernel is:

Linux rescue 3.3.2-kirkwide #1 Mon May 28 13:23:17 CDT 2012 armv5tel GNU/Linux

and Debian Wheezy, whose kernel is:

Linux debian 3.2.0-3-kirkwood #1 Mon Jul 23 22:36:47 UTC 2012 armv5tel GNU/Linux

The arcNumber is set to 3542, here is the output of the fw_printenv command:

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:00:8C:09
serverip=192.168.0.100
ipaddr=192.168.0.104
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
arcNumber=3542

Do you have any clue on how could I configure the led to green?

Thanks

hi all,
here are further steps I made, about issue of LED not properly set on Pogoplug E02, using rescue.

Please consider I'm quite a noob at these things, so forgive me if what I write here is not correct.

Having a look at content of rescue source file referenced at first post (custom-RescueV2.8.1.tar.gz), whitin the config file of buildroot (buildroot-config) it's also se the kernel config to be used:

#
# Kernel
#
BR2_LINUX_KERNEL=y
# BR2_LINUX_KERNEL_2_6_34 is not set
# BR2_LINUX_KERNEL_SAME_AS_HEADERS is not set
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
# BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.3.2"
BR2_LINUX_KERNEL_VERSION="3.3.2"
BR2_LINUX_KERNEL_PATCH="custom/linux-3.3.2-wide"
# BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="custom/linux-3.3.2-config"
BR2_LINUX_KERNEL_UIMAGE=y
# BR2_LINUX_KERNEL_BZIMAGE is not set
# BR2_LINUX_KERNEL_ZIMAGE is not set
# BR2_LINUX_KERNEL_VMLINUX is not set

In turn, having a look in the kernel config file refernced there (custom/linux-3.3.2-config), I see that the POGO E02 arch (CONFIG_MACH_POGO_E02) is missing:

#
# Marvell Kirkwood Implementations
#
CONFIG_MACH_DB88F6281_BP=y
CONFIG_MACH_RD88F6192_NAS=y
CONFIG_MACH_RD88F6281=y
CONFIG_MACH_MV88F6281GTW_GE=y
CONFIG_MACH_SHEEVAPLUG=y
CONFIG_MACH_ESATA_SHEEVAPLUG=y
CONFIG_MACH_GURUPLUG=y
CONFIG_MACH_TS219=y
CONFIG_MACH_TS41X=y
CONFIG_MACH_DOCKSTAR=y
CONFIG_MACH_GOFLEXNET=y
CONFIG_MACH_GOFLEXHOME=y
CONFIG_MACH_OPENRD=y
CONFIG_MACH_OPENRD_BASE=y
CONFIG_MACH_OPENRD_CLIENT=y
CONFIG_MACH_OPENRD_ULTIMATE=y
CONFIG_MACH_NETSPACE_V2=y
CONFIG_MACH_INETSPACE_V2=y
CONFIG_MACH_NETSPACE_MAX_V2=y
CONFIG_MACH_D2NET_V2=y
CONFIG_MACH_NET2BIG_V2=y
CONFIG_MACH_NET5BIG_V2=y
CONFIG_MACH_T5325=y
CONFIG_MACH_NSA310=y
CONFIG_MACH_NSA320=y

#
# System MMU
#

Anyway, after discovering this, I tried to recompile the 3.3.2 kernel, using instructions found in the kernle 3.3.2 thread (I resumed the procedure I followed in the file attached to this post). Of course, during the menuconfig I enabled the POGO_E02 machine, in this case. The compilation and the install of the kernel was ok, and I was able to start the pogo with my kernel (confirmed by output of "uname -a").

But, apparently the machine arch is not recognized correctly, and the led configuration is the Sheevaplug one (arc=2097).

My fw_env seems to be setted correctly, infact:

root@debian:/var/log# fw_printenv | grep arc
arcNumber=3542

(on the previous post, there is the compite fw_printev output)
But, in my dmseg output, running my custom build kernel, it seems that the wrong machine number is taken into account:

[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.3.2-goflex-kirkwide-sdm (root@debian-cc) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #1 Sat Oct 27 00:20:18 CEST 2012
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c07027a4, node_mem_map c0777000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65024 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

(you can see in red the kernel string, that confirm I'm using my custom built kernel; the reference to goflex is just because I didn't rename correctly the default string used in the .config I used).

I also attach here the kernel config used to build the kernel.

Do you have any clue on what is wrong, and how could possibly fix it?

Thanks very much.

have you tried setting the machid instead of arcNumber?

I will take a second look at my UBoot.

=====================================================

• davy's Github Repo's rescue-dg

how could I set the machid?
for arcNumber, I just execute:

/usr/sbin/fw_setenv arcNumber 3542

Is it just a question of setting another param with fw_setenv like this?

/usr/sbin/fw_setenv machid 3542

I will try as possible (I suppose no harm in doing this)

It worked!

Setting the "machid" variable makes the led behave correctly, both on rescue system (i.e. with the kernel provided by you in the first post) and on my debian install on usb hdd (i.e. with the kernel I rebuilt).
Therefore, the led support was already there, but for some reasons I don't know setting the variable "arcNumber" in uBoot is not effective: the variable that is indeed considered is "machid". The only caveat is that "machid" wants the hex value of the architecture number. In my case (POGO_E02), the corresponding value for arcNumber=3542 is machid=dd6.
Therefore, the only thing to do to enable correct led behaviour was:

/usr/sbin/fw_setenv machid dd6

Maybe this may help also in other cases.

Thanks for your help.

PS: as a side note, while trying setting "machid", the first try I did was to set value 3542, and of course the kernel didn't boot. So I needed to access netconsole to change the value of machid. Being on a windows box, I downloaded the windows port of nc suggested in the netconsole tutorial by Jeff (link), and in fact as explained it worked only in read-only mode. But I found another port of nc that worked interactively even on windows (link; actually not a great discover, being the first result on google for "netcat on windows"!). Maybe this info could be useful to others, too.



Edited 2 time(s). Last edit at 10/28/2012 03:37AM by traycold.

Yes, I've found the problem.

The UBoot that I uploaded for Jeff to distribute to the community is a completely functional/tested/working kwb image - save for one detail : the arcNumber setup is not correctly implemented (this is my oversight, not Jeff's).

I have a newer one that does correctly implement it here : https://dl.dropbox.com/u/1015928/Kirkwood/uboot/newer-uboots-nonEFI_GPT-TESTED/uboot.mtd0.kwb-pogoE02-L2Coff-arcNumberworks.tar.gz

(NOTE: UNTAR/GUNZIP it first, before tftp-transfering it to your Pogo E02! Flash at your own risk-it worked great for me-YMMV-in any case, be careful.)



Flashing command sequence and output here :

pogoE02>                                                                        
pogoE02> set serverip 192.168.x.x   
pogoE02> set ipaddr 192.168.x.x                                           
pogoE02> tftpboot 0x800000 uboot.mtd0.kwb-pogoE02-L2Coff-arcNumberworks         
Using egiga0 device                                                             
TFTP from server 192.168.x.x; our IP address is 192.168.x.x               
Filename 'uboot.mtd0.kwb-pogoE02-L2Coff-arcNumberworks'.                        
Load address: 0x800000                                                          
Loading: ####################################                                   
done                                                                            
Bytes transferred = 524288 (80000 hex)                                          
pogoE02> nand erase 0x0 0x80000                                                 
                                                                                
NAND erase: device 0 offset 0x0, size 0x80000                                   
Erasing at 0x60000 -- 100% complete.                                            
OK                                                                              
pogoE02> nand write.e 0x800000 0x0 0x80000                                      
                                                                                
NAND write: device 0 offset 0x0, size 0x80000                                   
 524288 bytes written: OK                                                       
pogoE02> reset                                                                  
resetting ...                                                                   
                                                                                
                                                                                
U-Boot 2011.12 (Jun 08 2012 - 11:41:39)                                         
Pogoplug E02                                                                    
                                                                                
SoC:   Kirkwood 88F6281_A0                                                      
DRAM:  256 MiB                                                                  
WARNING: Caches not enabled                                                     
NAND:  128 MiB                                                                  
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   
Net:   egiga0                                                                   
88E1116 Initialized on egiga0                                                   
Hit any key to stop autoboot:  0                                                
(Re)start USB...                                                                
USB:   Register 10011 NbrPorts 1                                                
USB EHCI 1.00                                                                   
scanning bus for devices... 2 USB Device(s) found                               
       scanning bus for storage devices... 0 Storage Device(s) found            
** Block device usb 0 not supported                                             
                                                                                
** Invalid boot device **                                                       
Creating 1 MTD partitions on "nand0":                                           
0x000002500000-0x000008000000 : "mtd=3"                                         
UBI: attaching mtd1 to ubi0                                                     
UBI: physical eraseblock size:   131072 bytes (128 KiB)                         
UBI: logical eraseblock size:    129024 bytes                                   
UBI: smallest flash I/O unit:    2048                                           
UBI: sub-page size:              512                                            
UBI: VID header offset:          512 (aligned 512)                              
UBI: data offset:                2048                                           
UBI error: ubi_read_volume_table: the layout volume was not found               
UBI error: ubi_init: cannot attach mtd1                                         
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22                
UBI init error 22                                                               
...                                         
Wrong Image Format for bootm command                                            
ERROR: can't get kernel image!                                                  
stopping USB..                                                                  
                                                                                
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                                           
   Image Type:   ARM Linux Kernel Image (uncompressed)                          
   Data Size:    3038888 Bytes = 2.9 MiB                                        
   Load Address: 00008000                                                       
   Entry Point:  00008000                                                       
   Verifying Checksum ... OK                                                    
   Loading Kernel Image ... OK                                                  
OK                                                                              
                                                                                
Starting kernel ...                                                             
                                                                                
Uncompressing Linux... done, booting the kernel.                                
[    0.000000] Booting Linux on physical CPU 0                                  
[    0.000000] Initializing cgroup subsys cpuset                                
[    0.000000] Initializing cgroup subsys cpu                                   
[    0.000000] Linux version 3.3.2-kirkwide (davygravy@bitbaker64) (gcc version2
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397
[    0.000000] CPU: VIVT data cache, VIVT instruction cache                     
[    0.000000] Machine: Pogoplug E02                                            
[    0.000000] Memory policy: ECC disabled, Data cache writeback                
...            
[   13.066319] Kirkwood: MV88F6281-A0, TCLK=200000000.                          
[   13.066337] Feroceon L2: Enabling L2                                         
[   13.066377] Feroceon L2: Cache support initialised.                          
[   13.070047] bio: create slab <bio-0> at 0                                    
...
[   13.262228] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled         
[   13.282697] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A    
[   13.738837] console [ttyS0] enabled                                          
[   13.743452] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND )
[   13.752145] Scanning device for bad blocks                                   
[   13.832184] 4 cmdlinepart partitions found on MTD device orion_nand          
[   13.838481] Creating 4 MTD partitions on "orion_nand":                       
[   13.843661] 0x000000000000-0x000000100000 : "u-boot"                         
[   13.849469] 0x000000100000-0x000000500000 : "uImage"                         
[   13.855239] 0x000000500000-0x000002500000 : "rootfs"                         
[   13.861018] 0x000002500000-0x000008000000 : "data"                           
...
...
[   14.692189] hub 1-1:1.0: USB hub found                                       
[   14.696354] hub 1-1:1.0: 4 ports detected                                    
Initializing random number generator... done.                                   
Starting system message bus: done                                               
Starting network...                                                             
Starting Network Interface Plugging Daemon: eth0.                               
Starting Netatalk services (this will take a while): Starting afpd              
 afpd cnid_metad.                                                               
Starting sshd: OK                                                               
starting p910nd with options -b -f /dev/usb/lp0 on port 0 with pid-file p9100d.d
                                                                                
...                                                                                                                             
                                                                                
                                                                                
                                                                                
          MacPlug for Kirkwood Devices                                          
        File/Print Sharing Suite for Mac                                        
                 Doozan Forum                                                   
            http://forum.doozan.com                                             
                                                                                
                                                                                
             MacPlug developed by                                               
                  davygravy                                                     
            david.c.purdy@gmail.com                                             
                                                                                
                                                                                
                                                                                
                                                                                
MacPlug login: root                                                             
Password:                                                                       
MacPlug:~#                                                                      
MacPlug:~# ls /sys/class/leds/                                                  
status:green:health  status:orange:fault

My LED on the Pogo E02 now works as it should, and arcNumber is honored and recognized as it should be. The machid variable in flash env can be unset.

=====================================================

• davy's Github Repo's rescue-dg

I have rerolled it as 2.8.2 and reissued it w/ the Pogo E02 enabled, as I had supposed/believed it was.

Thanks for your attention to detail and patience.

MacPro:~ davygravy$ ssh root@192.168.X.X

         Doozan Forum
Kirkwood/*Plug* Recovery System
     V2.8.2 : Oct 29 2012

root@192.168.11.188's password: 
rescue:~# dmesg | grep Machine
[    0.000000] Machine: Pogoplug E02
rescue:~#

=====================================================

• davy's Github Repo's rescue-dg

Edited 1 time(s). Last edit at 11/01/2012 09:50PM by davygravy.

Edit2: Docstar revived after trying various things, especially those specified in this thread (http://forum.doozan.com/read.php?2,9256) .

Hi everyone,

I did something very bad: I erase my Dockstar memory while trying to install rescue 2.8.2 (Trying the Whizzy install script but got error, and the various reading lead me here).

I should Not have run these commands while booting with the Dockstar boot itself but with some USB-boot (but I didn't have any other thing to boot with) :

flash_eraseall /dev/mtd7
nandwrite /dev/mtd7 uImage-mtd1.img
flash_eraseall /dev/mtd8
ubiformat /dev/mtd8 -s 512 -f rootfs-mtd2.img -y
=> ERROR: ubiformat not found...

I thought I could do it :( so sad.

Edited: I found a USB disk which has ext2+swap partitions on it. I plugged it in the Dockstar, and it booted up with 3.3.3-dockstar-shyd. The USB must have been a backup disk I made more than a year ago.

What should I do now to "Reverse" these commands that I did while booting with the Dockstar's internal boot partition please ?
flash_eraseall /dev/mtd7
nandwrite /dev/mtd7 uImage-mtd1.img
flash_eraseall /dev/mtd8

Thank you everyone for helping me ressucitate my Dockstar .

(I do see it gets assigned IP from the router. But other than that, I can't even ssh/winScp to it if booting with a blank ext2+swap usb key). :( :(



Edited 6 time(s). Last edit at 02/28/2013 09:14PM by sint.

how can is set the right timezone on this rescue system? i need Europe/Berlin.

@ Basti

dpkg-reconfigure tzdata einfach ausführen ;-)

Hi Folks,

i wanna say thanks your your work, but i had a lot of questions. I have got a Pogo E02 with the Rescue System v2 on it, latest uboot installed trough the sh script and Debian on a USB Stick. Now i want to update to the latest 2.8.2 Rescue System but im not sure if i am right and before i brick my Pogo i want to her if my steps were ok.

1. I had set my Pogo with this command the Arch Number 3542

/usr/sbin/fw_setenv arcNumber 3542

2. After that i download the Arch Rescue System 2.8.2

wget https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz

untar it

tar zxvf RescueV2.8.2-10292012.tar.gz

3. Whe i got both files i should download flash_erase and nandwrite:

wget http://download.doozan.com/uboot/flash_erase
wget http://download.doozan.com/uboot/nandwrite

4. And flash mtd0 and mtd1 with these commands:

flash_eraseall /dev/mtd1
nandwrite /dev/mtd1 uImage-mtd1.img


flash_eraseall /dev/mtd2
ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y

and set this values:

fw_setenv set_bootargs_rescue 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts'
fw_setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
fw_setenv bootcmd_pogo 'run bootcmd_rescue'
fw_setenv rescue_installed 1

I think this is right?!

Ok, but on the instrutions on the first page tehere also stands Pogoplug E02 3542 if you have a kernel that supports it

Did my default Armel Kernel from Debian boot up again?


So the next steps, after flashing those both images i boot into Rescue Mode and enter

run bootcmd_rescue

And the last problem, i got on my pc ubuntu as os, but i didnt found anything about the netconsole how to use it on thos forum. whalt should i exactly do to use it?

I know, a lot of quesions, ive rtfm but i want to be on the right side.

thx

Ok,

i did it and also set the machid to dd6. But before i reboot i wait for feedback ;) I hope my Debian on stick will boot up,

Thx

Der Freibeuter Wrote:
-------------------------------------------------------
... snip ...
> 3. Whe i got both files i should download
> flash_erase and nandwrite:
>
> wget
> http://download.doozan.com/uboot/flash_erase
> wget
> http://download.doozan.com/uboot/nandwrite

No, this is not necessary, since flash_erase and nandwrite are already available
>
... snip ...
>
> So the next steps, after flashing those both
> images i boot into Rescue Mode and enter
>
> run bootcmd_rescue

No, you are way past this point once the rescue system is booted up ...
>
> And the last problem, i got on my pc ubuntu as os,
> but i didnt found anything about the netconsole
> how to use it on thos forum. whalt should i
> exactly do to use it?

Look here and maybe here also
>
> I know, a lot of quesions, ive rtfm but i want to
> be on the right side.
>
> thx

Hope this helps!

Cheers,

chessplayer

---
Standart ist der Standardfehler

Hi guys,

unbelievable, but in spite of the red alert text in the first post, i managed to erase mtd1 and mtd2 on one of my Zyxel NSA320s when trying to install the rescue system (wanted to do everything quickly, since I need to go out for a while in a minute and copy and pasted the wrong commands ...).

Now the machine is still running and I have others with which I could try to remedy the situation if I only knew enough to do so. Therefore, here is what I believe to be the case:

a) mtd1 = uboot_env and mtd2 = key_store (from looking at fw_printenv)
b) uBoot is still there as it is in mtd0

fw_printenv still gives me the values I expect to see, but maybe it does not read directly from /dev/mtd1? What is/dev/mtd2 used for (key_store)? Can I reboot with it overwritten?

If not, will the following help:

1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 (will be a challenge, but google will be my friend ...)
2. Flash those images to the one currently under re-construction

Any help would be greatly appreciated, as always ...

---
Standart ist der Standardfehler

Sounds to me like a nanddump is in order.

WarheadsSE,

ok, thanks, but: this means ???

What I have done meanwhile is create images of mtd0 - mtd8 (using dd) from the second NSA320 I am currently fiddling with. Is that about the same you were suggesting?

---
Standart ist der Standardfehler

Just for the sake of completeness: the answer is "recoverable".

The idea I had in my original post actually did work. So, if anybody else is interested, this is what can be done, if need be:

1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 via

dd if=/dev/mtdx of=nsa320_mtdx.img

2. Flash those images to the one needing re-construction via

flash_eraseall /dev/mtdx
nandwrite /dev/mtdx nsa320_mtdx.img

Maybe other noobs apart from myself will profit from this.

---
Standart ist der Standardfehler

Hi~~
I can't boot from usb stick.
My uboot is "U-Boot 2011.12 (Apr 18 2012 - 23:08:20) "
I need to install rescue system.
Netconsole is working.
I'v setup tftpd also.
Could you tell me install method of rescue system via tftp?
Step by step Please~~~~