Welcome! Log In Create A New Profile

Advanced

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

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

rescue login:



(Status : Test on 4 Mach-Types, awaiting tests on others )Kirkwood/*Plug*/Dockstar Rescue V2.8.2 : GPT support & many other enhancements + full kernel support for GoFlexNet/Home, Zyxel NSA3x0 and many others...

All of the features from Jeff'sV2, plus:
  • Well-tested and tuned Linux 3.3.2 kernel w/ lots of modules
  • GPT/EFI support in kernel and with the "gdisk" utility
  • Bonjour/Zeroconf/Avahi advertising of services: ( use ssh root@rescue.local to log in w/o hunting for the IP address)
  • fixes for the "Too Many Bad Blocks" NAND driver problem on GoFlex Net/Home
  • tweaks to udev so that SATA devices are handled more nicely, plus proper function in 3.x kernels
  • lm-sensors for the Zyxel NSA320 and any other supported Kirkwood device that has sensor on board
  • p910nd print server : very lightweight and easy to set up
  • fixed an intermittent problem w/ ntpd so that the time sync is more positive
This is a modest nudge upward in terms of function, but it should work on many more machines-. I've tested it out on Dockstar, Pogoplug E02, GoFlex Home and my Zyxel NSA320... it works very well... as always, respect the standard, mandatory boilerplate-language disclaimer: you accept all responsibility for using these files and the commands shown below. It works great for me, but I don't know what your level of expertise is... use at your own risk.

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

Download Link: RescueV2.8.1-05282012.tar.gz

(or for V2.8.2 use this link : https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz == but change commands for flashing accordingly !)



INSTALLATION:
Right now it is just manual installation - make sure you use the instructions for _your_ machine, not another:

***Newer U-Boot w/ L2 cache bug-fix required***http://forum.doozan.com/read.php?3,6965,6965#msg-6965

On PogoplugV1/V2, GoFlex Net/Home and Dockstar:
# make sure your **arcNumber** is correctly set, and check your console/netconsole connectivity in case of problems

#  Pogoplug E02    3542 if you have a kernel that supports it, or you can use 2097 (sheevaplug) if you have a truly vanilla mainline kernel that has no PogoE02-specific support in it
#
# Dockstar and PogoplugV1/E01    2998
#
# GoFlex Net and GoFlex Home    3089 if you have a kernel that supports it, or you can use 2678 (sheevaplug-eSATA) if you have a vanilla mainline kernel (but you'll likely experience the bad-blocks-NAND-mtd problem)
#   [ ! yes, you can use the same arcNumber for both of these GoFlex devices ! ]

# boot into Debian or something _other_ than the "rescue system" 
# download it to your Kirkwood device/Dockstar/Pogoplug/GoFlex
# untar it after downloading
tar zxvf RescueV2.8.1-05282012.tar.gz

# using tools from mtd-utils 

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


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


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



For the Zyxel NSA320:
# make sure your arcNumber is correctly set, and check your console/netconsole connectivity in case of problems
#  Zyxel NSA320    3956  for arcNumber


# boot into Debian or something _other_ than the "rescue system" 
# download it to your Zyxel NSA320
# untar it after downloading
tar zxvf RescueRescueV2.8.1-05282012.tar.gz


# using tools from mtd-utils 


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


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

fw_setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x4640000 0xa00000; bootm 0x800000'
fw_setenv set_bootargs_rescue 'setenv bootargs console=$console ubi.mtd=8 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts'

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

USAGE NOTES:
0. Booting into the Rescue System: from within netconsole or serial, execute the following:
run bootcmd_rescue


1. ssh login is easy - you probably won't need the ip address of your box anymore (username root ; password root):
ssh root@rescue.local
This should work on any Bonjour/Zeroconf/Avahi-enabled machine, and perhaps on some others.


2. Changes to the Read-Only rootfs: temporarily make it read-write...
You can make changes to the system, but be careful as there is little margin for error.
mount -o remount,rw /
#  make whatever changes you want to, such as adding modprobe commands to /etc/init.d/rcS
#  then revert to ro
mount -o remount,ro /
One important change to consider is to set your own password!


3. For special hardware, e.g. sensors Make selected kernel modules load at boot time.
The kernel has much of the in-common hardware support built-in, not as modules. Since some machines have extra capabilities or non-common hardware, modules supporting this must be loaded by hand, or added to the /etc/init.d/rcS startup script. For example:

#hardware monitoring on the Zyxel NSA320:
modprobe nsa3xx-hwmon

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

BUILDING IT:
(We will assume you already have the normal build-essential components that one would have: normal Buildroot dependencies...)

Go to somewhere in your own home directory, and as a normal user (not as root):
mkdir rescuebuilddir
cd rescuebuilddir
wget http://buildroot.uclibc.org/downloads/buildroot-2010.08.tar.gz
tar zxf buildroot-2010.08.tar.gz
wget http://dl.dropbox.com/u/1015928/Kirkwood/rescue/rescue-V2.8-applyto-buildroot2010.08.patch
cd buildroot-2010.08
patch -p1 < ../rescue-V2.8-applyto-buildroot2010.08.patch
wget http://dl.dropbox.com/u/1015928/Kirkwood/rescue/custom-RescueV2.8.1.tar.gz
tar zxf custom-RescueV2.8.tar.gz
cp custom/buildroot-config .config
make


After anywhere from about a half hour to two hours, your build should finish. In Jeff's original setup, multiple processors were not enabled. It is currently set for 6 processors (my build box is a 3.6GHz Quad Core : a full run took about 35 minutes on my desktop machine- YMMV).

Once the run is finished:

cd output/images

cat <<END >rootfs.cfg
[ubifs]
mode=ubi
image=rootfs.ubifs
vol_id=0
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
END

ubinize -o rootfs-mtd2.img -m 2048 -p 128KiB -s 512 rootfs.cfg
dd if=uImage of=uImage-mtd1.img bs=512K conv=sync


Your completed uImage-mtd1.img and rootfs-mtd2.img image files should now be ready.

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





Edited 40 time(s). Last edit at 10/30/2012 05:20PM by davygravy.
Looks great! :)

I tried it on my GoFlex Home and it boots fine, but whichever USB drive I connect it doesn't get loaded completely ie the sda1 sda2 devices are not created.

Quote

[ 158.330214] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 158.486007] usb 1-1: New USB device found, idVendor=0718, idProduct=04a2
[ 158.492760] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 158.499932] usb 1-1: Product: Nano
[ 158.503366] usb 1-1: Manufacturer: Imation
[ 158.507483] usb 1-1: SerialNumber: 07A11E03C895CE92
[ 158.518073] scsi0 : usb-storage 1-1:1.0
[ 159.551098] scsi 0:0:0:0: Direct-Access Imation Nano PMAP PQ: 0 ANSI: 0 CCS

Nothing happens after this. I tried with 2-3 different drives and its all the same.

btw what is the correct arcNumber for the GoFlex Home?
That is odd. My goflex home is running the same image.

I use the GoFlex Net machid for the Home...
root@GoFlexHome:~# fw_printenv arcNumber
arcNumber=3089

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


I'm wondering if a scsi module of some sort has to be loaded manually... ???

Jeff kept the kernel w/ builtin support as small as possible (correct thinking).

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


varkey: please try this: boot into rescue mode, wait a moment, and then insert a USB drive and mount it
mount /dev/sda1 /mnt

For me, it seems to autoload the module needed for sdX devices, once issue a mount command. There is some basic udev infrastructure built in IIUC.

To me it looks like the _insertion_ (or presence) of the device doesn't create node, but rather the accessing of it (via mount).



davygravy@bitbaker64:~$ ssh root@rescue.local
Warning: the RSA host key for 'rescue.local' differs from the key for the IP address '192.168.11.173'
Offending key for IP in /home/davygravy/.ssh/known_hosts:71
Matching host key in /home/davygravy/.ssh/known_hosts:75
root@rescue.local's password: 
rescue:~# mount /dev/sda1 /mnt
rescue:~# lsmod
Module                  Size  Used by    Not tainted
sd_mod                 32868  2 
crc_t10dif              1110  1 sd_mod
rescue:~# mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,noatime)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/sda1 on /mnt type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
rescue:~#


Note below at timestamp 47 seconds... when I issued the mount command.
    7.538935] VFS: Mounted root (ubifs filesystem) readonly on device 0:15.
[    7.546251] Freeing init memory: 160K
[    7.610506] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    7.774709] usb 1-1: New USB device found, idVendor=0930, idProduct=6545
[    7.781483] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    7.788652] usb 1-1: Product: DataTraveler 109
[    7.793135] usb 1-1: Manufacturer: Kingston
[    7.797337] usb 1-1: SerialNumber: 0060E049DF77EBB0B00002F2
[    7.823449] scsi0 : usb-storage 1-1:1.0
[    8.822404] scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 109 PMAP PQ: 0 ANSI: 0 CCS
[   10.109787] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   47.370238] sd 0:0:0:0: [sda] 15240576 512-byte logical blocks: (7.80 GB/7.26 GiB)
[   47.381350] sd 0:0:0:0: [sda] Write Protect is off
[   47.386167] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[   47.386581] sd 0:0:0:0: [sda] No Caching mode page present
[   47.392118] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   47.402342] sd 0:0:0:0: [sda] No Caching mode page present
[   47.407861] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   47.415468]  sda: sda1
[   47.423220] sd 0:0:0:0: [sda] No Caching mode page present
[   47.428736] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   47.434889] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   47.448169] kjournald starting.  Commit interval 5 seconds
[   47.456358] EXT3-fs (sda1): using internal journal
[   47.461201] EXT3-fs (sda1): mounted filesystem with ordered data mode


Can you confirm this on your machine? I see this behavior on all of my machines (PPlug, Dockstr, GoFlex, Zyxel).

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


Yep, you are right. I was able to successfully mount it.

[   27.430261] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   27.586122] usb 1-1: New USB device found, idVendor=0718, idProduct=04a2
[   27.592879] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   27.600051] usb 1-1: Product: Nano
[   27.603485] usb 1-1: Manufacturer: Imation
[   27.607602] usb 1-1: SerialNumber: 07A11E03C895CE92
[   27.618528] scsi0 : usb-storage 1-1:1.0
[   28.651213] scsi 0:0:0:0: Direct-Access     Imation  Nano             PMAP PQ: 0 ANSI: 0 CCS
[   40.398285] sd 0:0:0:0: [sda] 7827456 512-byte logical blocks: (4.00 GB/3.73 GiB)
[   40.406524] sd 0:0:0:0: [sda] Write Protect is off
[   40.411369] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[   40.412020] sd 0:0:0:0: [sda] No Caching mode page present
[   40.417536] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   40.427770] sd 0:0:0:0: [sda] No Caching mode page present
[   40.433310] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   40.461775]  sda: sda1 sda2
[   40.471655] sd 0:0:0:0: [sda] No Caching mode page present
[   40.477172] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   40.483323] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   40.500470] kjournald starting.  Commit interval 5 seconds
[   41.438809] EXT3-fs (sda1): using internal journal
[   41.443655] EXT3-fs (sda1): mounted filesystem with ordered data mode

Although in Jeff's Rescue v2, it would automatically create the sdx1 etc

@davygravy : On the GoFlex Home, there are two LEDs on the front right? Only the upper one works, how do I enable the lower one?



Edited 2 time(s). Last edit at 05/14/2012 12:17AM by varkey.
No idea. Never saw it come on.

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





Edited 1 time(s). Last edit at 05/14/2012 03:15PM by davygravy.
Working on a V2.5 or 3 ... moved to Buildroot 2012.02, have uclibc reconfigured to work with newer source, and now re--re-rebuilding....

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


Do we need support for partitions of size > 2TB? What kind of priority is that for users?

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


Goetz
Sources/Patches for Rescue V2.1
May 19, 2012 02:56PM
Hi Davygravy,
thanks for the updates Rescuesystem. I've installed on my dockstart to replace an outdated OpenWRT and it works fine
Could you please publish your build root changes, as I would like to build an complete system, not just a rescue one.

BTW: I had a hard time getting it installed, but in the end was rescued by my broken debian on an usb-stick. Somehow the RAM based rescue-systems did not boot on my dockstar. And all the working kernels were unable to mount root from the ramdisks ...

thanks,
Goetz.
need help flashing this.

rescue-v5-machs_all-hwmon-avahi.tar.gz rootfs-mtd2.img uImage-mtd1.img
bash-3.2# flash_eraseall /dev/mtd1
Erasing 128 Kibyte @ 600000 -- 100 % complete.
bash-3.2# nandwrite /dev/mtd1 uImage-mtd1.img
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
Writing data to block 18 at offset 0x240000
Writing data to block 19 at offset 0x260000
Writing data to block 20 at offset 0x280000
Writing data to block 21 at offset 0x2a0000
Writing data to block 22 at offset 0x2c0000
Writing data to block 23 at offset 0x2e0000
Writing data to block 24 at offset 0x300000
Writing data to block 25 at offset 0x320000
Writing data to block 26 at offset 0x340000
Writing data to block 27 at offset 0x360000
bash-3.2# flash_eraseall /dev/mtd2
Erasing 128 Kibyte @ f900000 -- 100 % complete.
bash-3.2# ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y
bash: ubiformat: command not found
bash-3.2# apt-get install mtd-utils
bash: apt-get: command not found
bash-3.2# ls /usr/bin
ls: reading directory /usr/bin: Invalid argument
bash-3.2# cd
bash-3.2# cd /
bash-3.2# ls
bin boot dev etc fsckoptions home lib links locale media mnt opt proc root sbin selinux srv sys tmp usr var
bash-3.2# cd usr
bash-3.2# ls
ls: reading directory .: Invalid argument
bash-3.2# cd /usr
bash-3.2# ls
ls: reading directory .: Invalid argument
bash-3.2# ls /bin
ls: reading directory /bin: Invalid argument
bash-3.2# cd
bash-3.2# ls /bin
ls: reading directory /bin: Invalid argument
bash-3.2# cd /
bash-3.2# ubiformat /dev/mtd2 -s 512 -f /mnt/temp/rootfs-mtd2.img -y
bash: ubiformat: command not found
@dheerajjotwani

I'm sorry, but you either need a RAM or an USB-stick based system to rescue your box. (And most likely access to the serial console, unless you've enabled netconsole in uboot).

bash-3.2# flash_eraseall /dev/mtd2 
Erasing 128 Kibyte @ f900000 -- 100 % complete.

This command erased all data on /dev/mtd2. Including ubiformat.

(I'm a little irritated, as mtd2 is 32M an not just 128k, but I think your flash is gone)
thanks

i dont have a serial cable. i am trying to setup the goflex home. i updated the uboot succesfully. then set arcnumber as 3089 and setup nc. and now trying to setup rescue. the deal is that if i try rebooting from the debian pendrive, no ip is resolved to the device. here is the dmesg from the boot with a pendrive

[ 0.000000] Linux version 2.6.37.6-goflex (root@debian) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #2 PREEMPT Fri May 13 21:06:35 IST 2011
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Seagate GoFlex Net
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 32768
[ 0.000000] free_area_init_node: node 0, pgdat c0594e20, node_mem_map c0668000
[ 0.000000] Normal zone: 256 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 32512 pages, LIFO batch:7
[ 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: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 121240k/121240k available, 9832k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xc8800000 - 0xfe800000 ( 864 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0031000 ( 164 kB)
[ 0.000000] .text : 0xc0031000 - 0xc0567d54 (5340 kB)
[ 0.000000] .data : 0xc0568000 - 0xc059afa0 ( 204 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Preemptable hierarchical RCU implementation.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:114
[ 0.000000] Console: colour dummy device 80x30
[ 21.474963] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[ 21.714890] pid_max: default: 32768 minimum: 301
[ 21.714990] Mount-cache hash table entries: 512
[ 21.715287] CPU: Testing write buffer coherency: ok
[ 21.717373] NET: Registered protocol family 16
[ 21.718778] Kirkwood: MV88F6281-A1, TCLK=200000000.
[ 21.718793] Feroceon L2: Cache support initialised.
[ 21.720339] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[ 21.720369] final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[ 21.736683] bio: create slab <bio-0> at 0
[ 21.737307] vgaarb: loaded
[ 21.737842] SCSI subsystem initialized
[ 21.738260] libata version 3.00 loaded.
[ 21.738939] usbcore: registered new interface driver usbfs
[ 21.739218] usbcore: registered new interface driver hub
[ 21.739404] usbcore: registered new device driver usb
[ 21.740991] Switching to clocksource orion_clocksource
[ 21.747488] FS-Cache: Loaded
[ 21.765740] NET: Registered protocol family 2
[ 21.765958] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 21.766689] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 21.766790] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 21.766850] TCP: Hash tables configured (established 4096 bind 4096)
[ 21.766860] TCP reno registered
[ 21.766870] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 21.766896] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 21.767092] NET: Registered protocol family 1
[ 21.767392] RPC: Registered udp transport module.
[ 21.767403] RPC: Registered tcp transport module.
[ 21.767412] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 21.767426] PCI: CLS 0 bytes, default 32
[ 21.767576] Trying to unpack rootfs image as initramfs...
[ 21.927431] Freeing initrd memory: 2108K
[ 22.017998] FS-Cache: Netfs 'nfs' registered for caching
[ 22.019107] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 22.020478] JFS: nTxBlock = 963, nTxLock = 7709
[ 22.020975] msgmni has been set to 240
[ 22.022481] io scheduler noop registered
[ 22.022492] io scheduler deadline registered
[ 22.022590] io scheduler cfq registered (default)
[ 22.031177] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 22.121382] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 22.487128] console [ttyS0] enabled
[ 22.530767] brd: module loaded
[ 22.538707] loop: module loaded
[ 22.543000] sata_mv sata_mv.0: version 1.28
[ 22.547324] sata_mv sata_mv.0: slots 32 ports 2
[ 22.554636] scsi0 : sata_mv
[ 22.558076] scsi1 : sata_mv
[ 22.561406] ata1: SATA max UDMA/133 irq 21
[ 22.565524] ata2: SATA max UDMA/133 irq 21
[ 22.571460] ONFI flash detected
[ 22.574711] ONFI param page 0 valid
[ 22.578218] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[ 22.586895] Scanning device for bad blocks
[ 22.743969] 4 cmdlinepart partitions found on MTD device orion_nand
[ 22.750266] Creating 4 MTD partitions on "orion_nand":
[ 22.755450] 0x000000000000-0x000000100000 : "u-boot"
[ 22.761769] 0x000000100000-0x000000500000 : "uImage"
[ 22.768033] 0x000000500000-0x000002500000 : "rootfs"
[ 22.774418] 0x000002500000-0x000010000000 : "data"
[ 22.782996] MV-643xx 10/100/1000 ethernet driver version 1.4
[ 22.788935] mv643xx_eth smi: probed
[ 22.799062] net eth0: port 0 with MAC address 00:10:75:26:7a:10
[ 22.805375] console [netcon0] enabled
[ 22.809055] netconsole: network logging started
[ 22.813726] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 22.820336] orion-ehci orion-ehci.0: Marvell Orion EHCI
[ 22.825689] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 22.881045] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 22.901032] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 22.907740] hub 1-0:1.0: USB hub found
[ 22.911560] ata1: SATA link down (SStatus 0 SControl F300)
[ 22.917142] hub 1-0:1.0: 1 port detected
[ 22.921909] Initializing USB Mass Storage driver...
[ 22.927024] usbcore: registered new interface driver usb-storage
[ 22.933196] USB Mass Storage support registered.
[ 22.937984] usbcore: registered new interface driver ums-datafab
[ 22.944222] usbcore: registered new interface driver ums-freecom
[ 22.950413] usbcore: registered new interface driver ums-jumpshot
[ 22.956717] usbcore: registered new interface driver ums-sddr09
[ 22.962862] usbcore: registered new interface driver ums-sddr55
[ 22.969289] mice: PS/2 mouse device common for all mice
[ 23.241043] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 23.281042] ata2: SATA link down (SStatus 0 SControl F300)
[ 23.392454] hub 1-1:1.0: USB hub found
[ 23.396312] hub 1-1:1.0: 4 ports detected
[ 23.681206] usb 1-1.1: new high speed USB device using orion-ehci and address 3
[ 23.871214] usb 1-1.2: new high speed USB device using orion-ehci and address 4
[ 23.981028] rtc-mv rtc-mv: internal RTC not ticking
[ 23.986483] i2c /dev entries driver
[ 23.991766] cpuidle: using governor ladder
[ 23.996075] scsi2 : usb-storage 1-1.2:1.0
[ 24.001599] cpuidle: using governor menu
[ 24.005578] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[ 24.012326] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[ 24.051076] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 24.091071] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[ 24.131073] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[ 24.171070] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[ 24.177215] sdhci: Secure Digital Host Controller Interface driver
[ 24.183537] sdhci: Copyright(c) Pierre Ossman
[ 24.188557] Registered led device: status:green:health
[ 24.188785] Registered led device: status:orange:fault
[ 24.189008] Registered led device: sata0:white:bar0
[ 24.189241] Registered led device: sata0:white:bar1
[ 24.189465] Registered led device: sata0:white:bar2
[ 24.189692] Registered led device: sata0:white:bar3
[ 24.189923] Registered led device: sata1:white:bar0
[ 24.190164] Registered led device: sata1:white:bar1
[ 24.190397] Registered led device: sata1:white:bar2
[ 24.190637] Registered led device: sata1:white:bar3
[ 24.195334] usbcore: registered new interface driver usbhid
[ 24.200933] usbhid: USB HID core driver
[ 24.204942] oprofile: hardware counters not available
[ 24.210019] oprofile: using timer interrupt.
[ 24.215715] TCP cubic registered
[ 24.218960] NET: Registered protocol family 17
[ 24.223688] lib80211: common routines for IEEE802.11 drivers
[ 24.229379] lib80211_crypt: registered algorithm 'NULL'
[ 24.229389] Registering the dns_resolver key type
[ 24.234192] Gating clock of unused units
[ 24.234202] before: 0x00dfc3fd
[ 24.234209] after: 0x00c7c1c9
[ 24.235046] registered taskstats version 1
[ 24.240031] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 24.246619] Freeing init memory: 164K
[ 25.001912] scsi 2:0:0:0: Direct-Access SanDisk Cruzer Blade 8.02 PQ: 0 ANSI: 0 CCS
[ 25.013877] sd 2:0:0:0: [sda] 7856127 512-byte logical blocks: (4.02 GB/3.74 GiB)
[ 25.021462] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 25.036549] sd 2:0:0:0: [sda] Write Protect is off
[ 25.042308] sd 2:0:0:0: [sda] Mode Sense: 45 00 00 08
[ 25.042322] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 25.052711] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 25.060029] sda: sda1
[ 25.066726] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 25.081251] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 34.855278] EXT3-fs: barriers not enabled
[ 34.860204] EXT3-fs (sda1): mounted filesystem with writeback data mode
[ 34.868579] kjournald starting. Commit interval 5 seconds
[ 35.556304] udev[764]: starting version 164
[ 36.236036] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[ 36.396952] r8712u: DriverVersion: v7_0.20100831
[ 36.406415] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 36.412892] r8712u: USB_SPEED_HIGH with 4 endpoints
[ 36.418906] r8712u: Boot from EFUSE: Autoload OK
[ 37.161814] r8712u: CustomerID = 0x0010
[ 37.165671] r8712u: MAC Address from efuse = 54:04:a6:9f:bc:ce
[ 37.173630] usbcore: registered new interface driver r8712u
[ 37.726086] EXT3-fs (sda1): using internal journal
[ 40.488571] NET: Registered protocol family 10
[ 41.221441] r8712u: 1 RCR=0x153f00e
[ 41.225687] r8712u: 2 RCR=0x553f00e
[ 41.343807] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 41.349864] ADDRCONF(NETDEV_UP): wlan0: link is not ready
@ all : I'm reworking something w/ the 2.1 ... and will (hopefully) post later this or next week w/ an improvement.
Being able to Debootstrap or run Jeff's installer from here is a requirement, and apparently it fails on at least one of those two.

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

@ dheerajjotwani : we want you to get help w/ your installation or issue, but you should really move this particular question to the Debian section. It appears from the boot messages that what you are booting is not a rescue image, but rather some other type, Debian, perhaps.

Are you using some sort of network/USB device? This is odd (and related to networking clearly):
[ 36.236036] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[ 36.396952] r8712u: DriverVersion: v7_0.20100831
[ 36.406415] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 36.412892] r8712u: USB_SPEED_HIGH with 4 endpoints
[ 36.418906] r8712u: Boot from EFUSE: Autoload OK
[ 37.161814] r8712u: CustomerID = 0x0010
[ 37.165671] r8712u: MAC Address from efuse = 54:04:a6:9f:bc:ce
[ 37.173630] usbcore: registered new interface driver r8712u
[ 37.726086] EXT3-fs (sda1): using internal journal
[ 40.488571] NET: Registered protocol family 10
[ 41.221441] r8712u: 1 RCR=0x153f00e
[ 41.225687] r8712u: 2 RCR=0x553f00e
[ 41.343807] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 41.349864] ADDRCONF(NETDEV_UP): wlan0: link is not ready

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


thanks davygravy

yes i am trying to boot with debian usb stick. but the goflex home is not getting an ip so cant ssh either... i have a goflex net running debian successfully. bought two goflex home and tried setting them up by first installing uboot, changing arc number to 3089 and setting up nc. then using the goflexnet rootfs usb stick, i tried booting the goflexhome but no ip is resolved for the device and the led on the front after blinking initially, stabalizes to solid green. the indicators on the lan port remain lit and flicker showing lan activity, however the device doesnt show up in my routers dhcp list.

i then removed the usb disk and copy pasted the dmesg log here for help. can you please help... me requesting mods to please move this to the debian section of the forum

EDIT:
got it working. the debian image i was booting from was corrupt. tried a new copy and all worked like a charm. rescue v2.1 installed and tested and boot enabled from sata port.

big thumbs up !!



Edited 1 time(s). Last edit at 05/20/2012 04:58PM by dheerajjotwani.
KK, sounds great. BTW, a newer updated version of the rescue that (truly) parallels the behavior of Jeff's V2 + wider-kernel-support+avahi+gdisk is just a few days away now...

You'll want to upgrade from that previous "testing" version, as it has some shortcomings...

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


Re: Sources/Patches for Rescue V2.1
May 20, 2012 08:13PM
Goetz Wrote:
-------------------------------------------------------
> Hi Davygravy,
> thanks for the updates Rescuesystem. I've
> installed on my dockstart to replace an outdated
> OpenWRT and it works fine
> Could you please publish your build root changes,
> as I would like to build an complete system, not
> just a rescue one.
> thanks,
> Goetz.

Yes, I'm just finishing a rework of what I had started last week... the new stuff will parallel Jeff'sV2 completely, plus have avahi+gdisk+lmsensors+WiderKernelSupport+aFixOr2...

I made sure I really stuck to the exact base profile that Jeff had used... so it should be transparent+feature_additions.

And, yes, I'll post a patch to apply to buildroot so folks can go off on their own missions. ;^)

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





Edited 1 time(s). Last edit at 05/20/2012 08:54PM by davygravy.
@davygravy : Please check http://forum.doozan.com/read.php?2,6550,8029#msg-8029

Might be the reason why the /dev/sdx etc are not created automaticaly.
I'm not sure that is it. It might be peripherally related, but I don't think it is the cause of what _we_ are seeing.
(here is an interesting snippet: http://www.spinics.net/lists/linux-usb/msg60204.html )

On the 3.3.2 kernel:
rescue:/# cat config | grep EHCI
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_EHCI_MV is not set
rescue:/#

On Jeff'sV2 Rescue kernel:
davygravy@bitbaker64:~/RescueV2.1-redux/buildroot-2010.08/output/build/linux-2.6.32.18$  cat .config | grep EHCI
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
The option CONFIG_USB_EHCI_MV didn't exist in older kernels, it appears.

I 've been very, very, very careful with this latest (today's) version that I've just finished rolling. I'm inclined to think that there may have been some change in udev, or between udev and kernel interaction.

I'll keep looking at it, agreed, we'd all like the "old" behavior.

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

OK, I found the problem. It looks like udevd was not starting properly. In the startup script there is a test that "prevented udev from running w/ 2.4 kernels". Well, it looked for 2.6* kernels and, you guessed it, 2.7* kernels. A minor adjustment (3.*) and its back in business.

Now we get:

          Jeff Doozan's
Dockstar/Pogoplug Recovery System

rescue login: root
Password: 
May 22 03:41:52 login[134]: root login on 'ttyS0'
rescue:~# lsmod
Module                  Size  Used by    Not tainted
rescue:~# [   44.002889] usb 1-1.1: new full-speed USB device number 3 using orion-ehci
[   44.114488] usb 1-1.1: New USB device found, idVendor=05e3, idProduct=0606
[   44.121396] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   44.128750] usb 1-1.1: Product: USB Hub 2.0
[   44.132977] usb 1-1.1: Manufacturer: ALCOR
[   44.139496] hub 1-1.1:1.0: USB hub found
[   44.153213] hub 1-1.1:1.0: 4 ports detected
[   44.442768] usb 1-1.1.2: new full-speed USB device number 4 using orion-ehci
[   44.562988] usb 1-1.1.2: not running at top speed; connect to a high speed hub
[   44.572744] usb 1-1.1.2: New USB device found, idVendor=0781, idProduct=5530
[   44.579825] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   44.587354] usb 1-1.1.2: Product: Cruzer
[   44.591289] usb 1-1.1.2: Manufacturer: SanDisk
[   44.595784] usb 1-1.1.2: SerialNumber: 20060775101D8B336814
[   44.612616] scsi0 : usb-storage 1-1.1.2:1.0
[   44.692774] usb 1-1.1.4: new full-speed USB device number 5 using orion-ehci
[   44.743993] usbcore: registered new interface driver uas
[   44.822989] usb 1-1.1.4: not running at top speed; connect to a high speed hub
[   44.831737] usb 1-1.1.4: New USB device found, idVendor=0846, idProduct=9030
[   44.838831] usb 1-1.1.4: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[   44.846636] usb 1-1.1.4: Product: WNA1100
[   44.850665] usb 1-1.1.4: Manufacturer: NETGEAR WNA
[   44.855489] usb 1-1.1.4: SerialNumber: 12345
[   45.037078] cfg80211: Calling CRDA to update world regulatory domain
[   45.614085] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer           1.26 PQ: 0 ANSI: 5
[   45.654669] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[   45.664795] sd 0:0:0:0: [sda] Write Protect is off
[   45.670517] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   45.701519]  sda: sda1 sda2 sda3
[   45.710636] sd 0:0:0:0: [sda] Attached SCSI removable disk

rescue:~# lsmod
Module                  Size  Used by    Not tainted
sd_mod                 32868  0 
crc_t10dif              1110  1 sd_mod
ath9k_htc              67430  1 
mac80211              329588  1 ath9k_htc
ath9k_common            1938  1 ath9k_htc
ath9k_hw              345253  2 ath9k_htc,ath9k_common
ath                    14177  3 ath9k_htc,ath9k_common,ath9k_hw
cfg80211              158416  3 ath9k_htc,mac80211,ath
rfkill                 14649  1 cfg80211
uas                     6619  0 
rescue:~#

Q.E.D. ... worky-worky, as they say...

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





Edited 4 time(s). Last edit at 05/21/2012 09:43PM by davygravy.
^ Great work! :) Will test it right away! :P
OK, no more features... I'm stopping with stuff here, removing (for the time) the USB/IP drivers and I'll try then to move it to the most recent buildroot toolchain. The new toolchain isn't really necessary, but it would make the patches more minimal and a tad cleaner.


I'll provide usage notes for avahi customization/integration and a quick p910nd HowTo, this weekend.

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





Edited 1 time(s). Last edit at 05/25/2012 03:59PM by davygravy.
davidgravy, why are you using pogoplug v2 with sheevaplug arcnumber???
Hi pazos ... thank you for asking ... the first two answers are "because it works" and "because it works well", though it is clear that the LED will never function _perfectly_ (ie., getting it to turn green...) without the patches you made for proper LED support on the E02. Otherwise it works just fine.

Honestly, if you have a truly "ready-to-go-and-well-tested" 3.3.x patch for the E01, E02 and the PogoV4Series that you can point me to, I would be happy (ie. enthusiastic and very grateful!) to reroll it w/ an upgraded kernel, and issue a V2.8.1. A few users have asked me to stay w/ kernel 3.3.3 and go no further as they've seen some oddness in certain key functions (beginning w/ 3.3.5, IIRC) that they wanted/needed. { been really busy lately, I should have emailed you about this before, actually }

There is very little extra room left over now in the rootfs ... in fact I had to remove some modules (some archaic and/or PCI stuff) to free up room for gdisk. If ALARM folks have a burning need for a package or two that are smallish and essential though, I could try to free up a bit more space and add that in for you all. On the other hand, adding kernel support for CloudEngines stuff to enable the LEDs in E01/E02, and proper support for mtd and LED in Series4/Mobile would only make the uImage a tiny bit larger... and there _is_ room for that.

As it is, though, the current V2.8 (kernel-wise; down to mtd partitions and harware profile) supports all of the following machines/machids :
Marvell DB-88F6281-BP Development Board                                             
Marvell RD-88F6192-NAS Reference Board                                            
Marvell RD-88F6281 Reference Board                                                  
Marvell 88F6281 GTW GE Board                                                        
Marvell SheevaPlug Reference Board                                                  
Marvell eSATA SheevaPlug Reference Board                                        
Marvell GuruPlug Reference Board                                                   
QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P and TS-219P+ Turbo NAS         
QNAP TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U Turbo NAS                         
Seagate FreeAgent DockStar                                                         
Seagate GoFlex Net/Home   (using the same arcNumber/machid)                                                                                                                    
Marvell OpenRD Base Board                                                         
Marvell OpenRD Client Board                                                          
Marvell OpenRD Ultimate Board                                                       
LaCie Network Space v2 NAS Board                                                  
LaCie Internet Space v2 NAS Board                                             
LaCie Network Space Max v2 NAS Board                                                 
LaCie d2 Network v2 NAS Board                                                      
LaCie 2Big Network v2 NAS Board                                                   
LaCie 5Big Network v2 NAS Board                                                    
HP t5325 Thin Client                                                               
ZyXEL NSA310 1-Bay Power Media Server                                          
ZyXEL NSA320 2-Bay Power Media Server

Using another machines machid (mtd access still works, just not perfect LEDs):
CloudEngines PogoplugE01/V1
CloudEngines PogoplugE02/V2

I've tested it on all of the underlined ones. I don't have any of the other machines to test it on... maybe someone at ALARM has some of these others?

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





Edited 2 time(s). Last edit at 05/27/2012 11:07AM by davygravy.
Some people at archlinuxarm are asking why rescue system doesn't boot with arcnumber=3542 (pogo_e02). creating a patch for it is rather simple and the machine will work with both arcnumbers.

I don't have any pogo devices right now, but change led definitions and mtd partitions is really easy, I will make a little patch when I have some more time :)
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.

I haven't tested it w/ pogov4 yet. I'll have to check it in all my boxes before I post it, though.

Also, I've finished the U-Boot stuff... final images are posted, so in a week or two I'll give Jeff the go-ahead to let these deprecate the old ones.

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





Edited 1 time(s). Last edit at 05/28/2012 11:37AM by davygravy.
Bah, wrong thread, sorry...



Edited 1 time(s). Last edit at 05/29/2012 06:07PM by Kurlon.
I'm working on latest stable from Buildroot 2012.05 and I've got it pretty close to bashed into shaped, I think.

I had to mess around with the with ifplugd & scripts in /etc/init.d/ in order to get udhcpc to does its stuff before ntpdate/ntpd kicked in... but that part is done now.

I think that some udev-ish tidying up is all that is needed. This will probably be a 3.3.3 kernel will run on nearly any Kirkwood box, (and on some toasters and electric toothbrushes).

---------------------------------------------------------------

Correction(s): 2012.05 seems to have some odd behavior that allows it to skip/reject part of the kernel patch, so I've fallen back to 2012.02 BR stuff. ... also, although the networking portion works fine, I've not been able to get udev and sysvinit working perfectly, so I'm going to concentrate on adding _rescue_ or _install_ features, not on adding more and more capability. To do this, I'll have to cut back on bloat and unneeded kernel stuff. If it is really/primarily the intent for it to be a Rescue System, then sysfs can handle the devices that would be normally used in an install or repair, and udev&sysvinit wouldn't be necessary then.

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





Edited 2 time(s). Last edit at 06/10/2012 02:40PM by davygravy.
Hi All,

I just ran the uboot updater here

So that I could install this rescue system, I havn't rebooted yet because when I checked to see if the necessary commands where available, i found that I can't access things like fw_printenv or fw_setenv, they aren't in /usr/sbin.

I am running a Seagate Goflex Home, it's running ArchArm from USB and it has an old (broken) version of plugapps on the internal NAND. I want to flash the rescue system to NAND instead.

What am I doing wrong and why don't I have access to those fw_* commands?

Like I said, I'm now running the uboot from the above link, although havn't rebooted yet as I am awaiting replies and imagine it likely won't come back up after a reboot at the moment.

Thanks.
If your still running uboot, either the old uboot ("Marvell>>" prompt) or the new uboot (don't recall what the prompt is) , the correct commands are printenv and setenv, not the ones starting with fw_

Anyway, it shouldn't be a problem if you successfully installed the uboot. Did you get through this instruction ok?
Quote

NAND erase: device 0 offset 0x0, size 0x80000
Erasing at 0x60000 -- 100% complete.
OK
Marvell>> nand write.e 0x800000 0x0 0x80000
nand write.e 0x800000 0x0 0x80000

NAND write: device 0 offset 0x0, size 0x80000
524288 bytes written: OK
If so then it's ok to continue to follow the remaining instructions.
laprjns Wrote:
-------------------------------------------------------
> If your still running uboot, either the old uboot
> ("Marvell>>" prompt) or the new uboot (don't
> recall what the prompt is) , the correct commands
> are printenv and setenv, not the ones starting
> with fw_
>
> Anyway, it shouldn't be a problem if you
> successfully installed the uboot. Did you get
> through this instruction ok?
>
Quote

NAND erase: device 0 offset 0x0, size
> 0x80000
> Erasing at 0x60000 -- 100% complete.
> OK
> Marvell>> nand write.e 0x800000 0x0 0x80000
> nand write.e 0x800000 0x0 0x80000
>
> NAND write: device 0 offset 0x0, size 0x80000
> 524288 bytes written: OK
> If so then it's ok to continue to follow the
> remaining instructions.

I got through the instructions and installed it, but then I could only boot into rescue, the system refused to boot from my usb drive. I tried manually booting the drive, it would load the ramdisk and kernel from usb but still end up in rescue mode.

Eventually I downgraded uboot back to the v0.7 one on the arch arm page (http://archlinuxarm.org/platforms/armv5/seagate-goflex-home) and my arch linux pen drive started booting again, but now rescue doesn't boot.

I tried manually booting rescue from the uboot prompt but it would just stop and not boot.

Is there any way I can get the new uboot to work so I can boot arch off my pen drive and rescue from the NAND?
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: