power off and on - DockStar boots falsely into Pogoplug

Hi,

at first, thanks for this great software and documentation!

Today I installed debian squeeze into an usb-stick and the new uboot into mtd0. And it works great.

But when I do a halt and power the device off, on the next start it boots always into Pogoplug. I'll post the uboot log/recording as soon as I installed netconsole. By the way - will the network in squeeze still work when netconsole is activated in uboot?


Thanks
-- crunshy

----------------------------------------------------------------------
reboot:
----------------------------------------------------------------------
U-Boot 2010.03-01266-g42f7128-dirty (Aug 22 2010 - 13:33:06)
Marvell-Sheevaplug
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1432436 bytes read
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1432436 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4703837 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1432372 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  0000800
   Verifying Checksum ... OK                                                                                  
## Loading init Ramdisk from Legacy Image at 01100000 ...                                                     
   Image Name:   initramfs                                                                                    
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)                                                    
   Data Size:    4703773 Bytes =  4.5 MB                                                                      
   Load Address: 00000000                                                                                     
   Entry Point:  00000000                                                                                     
   Verifying Checksum ... OK                                                                                  
   Loading Kernel Image ... OK                                                                                
OK                                                                                                            
                                                                                                              
Starting kernel ...

so far so good, but after power off and on:

                                                                                                              
----------------------------------------------------------------------                                        
after halt (power off/on)                                                                                     
----------------------------------------------------------------------                                        
U-Boot 2010.03-01266-g42f7128-dirty (Aug 22 2010 - 13:33:06)                                                  
Marvell-Sheevaplug                                                                                            
Hit any key to stop autoboot:  0                                                                              
(Re)start USB...                                                                                              
USB:   Register 10011 NbrPorts 1                                                                              
USB EHCI 1.00                                                                                                 
scanning bus for devices... 3 USB Device(s) found                                                             
       scanning bus for storage devices... Device NOT ready                                                   
   Request Sense returned 00 00 00                                                                            
1 Storage Device(s) found                                                                                     
** Bad partition 1 **                                                                                         
** Block device usb 1 not supported                                                                           
** Block device usb 2 not supported                                                                           
** Block device usb 3 not supported                                                                           
** Bad partition 1 **                                                                                         
** Bad partition 1 **                                                                                         
Wrong Image Format for bootm command                                                                          
ERROR: can't get kernel image!                                                                                
stopping USB..                                                                                                
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000                                                       
Scanning JFFS2 FS: ......... done.                                                                            
### JFFS2 load complete: 524288 bytes loaded to 0x800000                                                      
## Starting application at 0x00800200 ...  

Quote

scanning bus for storage devices... Device NOT ready

Your USB device isn't getting reset, or isn't properly responding to the reset commands. I've seen this before when I reset uBoot at some very strange points, but I've never seen it when just restarting the machine.

I'd try a different USB device, or look for some linux utility that you could run at shutdown to force a reset of your device. I don't know of any such utilities, but I've never looked, either. If you do figure something out, please let the rest of us know!

-- Jeff

The problem is, USB-boot works (after warm-reset) and (after power fault could-start) it does not. You can see this in my post above.

So I thought about alternatives to get the device to boot always into debian:

1. I thought about not using the usb-stick at all as root-"partition". But 256 MB is a bit small, even without the 32MB plugbox-"rescue"-partition, 256MB+32MB is still too small.
2. Do an automatic restart in pogoplug after 1 minute so that it can boot from an usb-stick.
3. load the kernel from mtd3 and use the root-system from the usb-stick on 0:1 (maybe /dev/sda1 with uuid or something like that because on the bus there will be some external harddisks too).

Option 1 is thanks to Jeff explained in detail in this post. But due to the lak of having a rescue-system and only 32MB more space I reconsiddered this intent.

Option 2 could also not work because if there is more than one usb-device plugged I get this:

U-Boot 2010.03-01266-g42f7128-dirty (Aug 22 2010 - 13:33:06)
Marvell-Sheevaplug
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 5 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 00 00 00
2 Storage Device(s) found
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
** Bad partition 1 **
** Block device usb 2 not supported
** Block device usb 3 not supported
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1976384 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

Option 2 isn't described anywhere and I think I'll have to learn a bit more about uboot and embedded systems in general before I get my hands dirty. Or maybe Jeff is also interested in this way and can be motivated ;-)



So far, thanks Jeff and all the others ;-)
-- crunshy

U-Boot 2010.03-01266-g42f7128-dirty (Aug 22 2010 - 13:33:06)
Marvell-Sheevaplug
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 5 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 00 00 00
error in inquiry
2 Storage Device(s) found
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
** Bad partition 1 **
** Block device usb 2 not supported
** Block device usb 3 not supported
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
Device NOT ready
   Request Sense returned 00 00 00
** Can't read partition table on 0:0 **
** Bad partition 1 **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1976384 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

Jeff, did you used the master branch from git.denx.de/?p=u-boot.git for the new u-boot image?
Because from the log above it's 2010.03...

There are at minimum two Bugs which I suppose concern my problems with usb-detection:

Bug 1: USB storage probe

Bug 2: disk/part.c: 'usb storage' avoiding overflow when output capacity

Will there be an updated version from your side or is this my start in getting hands dirty and trying to compile my own u-boot?

Jeff rocks ;-)

Thanks to him I updated the mtd0 with a new u-boot test-version and it worked flawlessly.
It boots fast, without any errors and all kinds of usb-devices plugged in.

Thanks,
-- crunshy

jeff, are you making this update to uboot mainline? I have the same issue...

Never mind Jeff - I found the other thread you had: http://forum.doozan.com/read.php?3,291

Thanks. Good stuff and thanks again :)

I've had some tempermental USB behavior. After installing debian, I did some minor config changes rebooted, and went to pogoplug environment. Continued reboots gave me continued entry into pogoplug instead of debian, so I thought I had borked the debian somehow. Well I was actually getting behavior similar to this thread where it would sometimes boot into debian and sometimes into pogoplug. See netconsole log below.

I have two dockstars, and several usb drives (all flash and powered by USB). I do have setups that correctly boot into debian every time, so this is mostly to try to help track down whatever is causing the detection issues. I know when I first hit this issue, I thought the problem was debian and not uBoot or the thumb drives themselves.

First the failed boot attempt that results in the pogoplug environment:

nema@phobos:~$ ./netconsole 192.168.2.15 6666
NOTE: the interrupt signal (normally ^C) has been remapped to ^T

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... error in inquiry
0 Storage Device(s) found
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1430120 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4703913 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1430056 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4703849 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

There were no hardware or software changes between these logs, and they are actually a single netconsole session.

@Nematocyst

I have a flash drive (PNY 4GB Micro Swivel Attaché) that produces the same results:
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... error in inquiry
0 Storage Device(s) found

I experimented with the usb commands and was able to get around it by resetting the usb first. At least my device worked when I did this.
At the u-boot prompt do the following:
setenv usb_init "usb reset; usb start"
saveenv

Hi,

I'm getting a similar issue to the issue that crunshy was getting.. I'm using the most recent uBoot and I'm still getting these issues with booting off of a USB drive. The difference between mine and crunshy's situation is that I almost always log into pogoplug instead of debian; maybe once in 10 times I'll load into debian. I've tried on a number of different flash drives with the same result:

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 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... 3 USB Device(s) found
scanning bus for storage devices... Device NOT ready
Request Sense returned 06 28 00
1 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

One other note about my situation: there's no rhyme or reason for when it works correctly, either. I can perform either /sbin/poweroff or /sbin/reboot... both will randomly work correctly to boot into debian instead of pogoplug.

hmmm I threw one of my usb drives into a linux box and ran e2fsck, which cleared some errors, but the startup sequence is still having troubles finding my usb drive. I can mount it fine manually, but the start sequence just isn't able to see it. I've tried with two different USB drives, which I've seen work fine before on this dockstar. I'm running out of ideas as to what to try next.

Well it is a good sign that the device is at least seen.
I have a 2GB PNY Attaché that on cold start the device is not even found.
Now if I stop autoboot then plug it in then is is found.

Here is what I see

Marvell>> usb reset
(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




If you have a serial cable then try the following.

Power on Dockstar
Stop Autoboot
usb reset <--- Your device should be found but not ready
usb start <--- See if you device is now found and ready

If your device does come up correctly you can do the trick I mentioned to Nematocyst.

ygator Wrote:
-------------------------------------------------------
> If you have a serial cable then try the
> following.
>
> Power on Dockstar
> Stop Autoboot
> usb reset <--- Your device should be found but
> not ready
> usb start <--- See if you device is now found
> and ready
>
> If your device does come up correctly you can do
> the trick I mentioned to Nematocyst.

I already tried that; the dockstar will go through a time-consuming process for each step, waiting for 2-3 minutes before it times out and moves on to the next step. So usb reset waits for about 2-3 minutes, says it's not ready, and then usb start waits for 2 minutes, and says it's not ready.

One other thing to note for the Win7 x64 people out there - the Nokia CA-42 cable I bought causes my Win7 x64 system to randomly crash; however, while running a virtual linux box, the cable works completely fine. So I guess this is my warning to Win7 x64 users that if you want to try this cable, make sure you save anything that you're working on before trying it out, unless you decide to use a virtual box instead.

ygator Wrote:
> At the u-boot prompt do the following:
> setenv usb_init "usb reset; usb start"
> saveenv


I tried that. Unfortunately, it didn't work on the USB device(s) I had trouble with.

It's interesting in that if I 'reboot' from the pogo environment, it *always* goes into debian. And if I 'reboot' from debian, it *always* goes into the pogo environment. It's like the pogo environ deactivates USB differently so that uBoot can recognize the drive, but debian doesn't.

Again, this occurs only with certain USB drives I have. The situation is really bizarre because I have two drives that are identical to the best of my knowledge. One works every time, the other, uBoot doesn't always recognize it and so boots pogo.

As I said earlier, I have setups that reliably boot into debian each time. It would be nice to track down what's going on, and I'll assist in any way I can. It's unclear to me if it's a hardware or software problem. Even though my remedy was finding a suitable USB drive, I"m not convinced it's really the drive(s) that are the problem.



Edited 1 time(s). Last edit at 09/19/2010 06:34PM by Nematocyst.

I thought that would have worked since it did on two drives that gave the inquiry error for me.
Though I am using my own compiled u-boot.


Here is a run down of the usb flash drives that I have tested.

Recognized from cold start
Sandisk Cruzer Micro's 512MB, 1GB, 4GB, 16GB
Microcenter Store Brand 8GB

Recognized from cold start, but with error in inquiry. Works if USB is reset first.
Lexar JumpDrive TwistTurn 4GB
PNY Micro Swivel Attaché 4GB

Not Recognized from cold start
PNY Attaché 2GB

I also believe there has to be a software solution for this.

I will also add to list of 'Not Recognized from cold start':

USB Flash Memory Kingston DT100 8GB

Nematocyst Wrote:
-------------------------------------------------------
> ygator Wrote:
> > At the u-boot prompt do the following:
> > setenv usb_init "usb reset; usb start"
> > saveenv
>
>
> I tried that. Unfortunately, it didn't work on
> the USB device(s) I had trouble with.


I've been messing with this issue a bit and have a solution that works for me. It seems that issuing a reset (or stop+start cycle) alone isn't enough. Cycling each time didn't give any benefit. But what did was cycling after the error really occurred.

Here are the relevant changes I made to my environment to get it booting every time. [I'm not going to claim 100% correct USB booting, because I still don't understand the problem, and one issue this solution addresses, I was unable to duplicate after applying the "fix"]

Problem 1: usb start doesn't work. This is the one I couldn't duplicate after applying the fix. However, this solution did work when I entered it manually from netconsole, so I believe it will work when needed. One note, when 'usb start' fails, causing this fix to kick in, there is a substantial delay caused by whatever makes it fail.

The fix was to stop usb, and then start it again.
original usb_init:

setenv usb_init usb start

becomes:

setenv usb_init 'if usb start; then version; else usb stop; usb start;fi;'

Problem 2: ext2load failed
The fix was to stop+start usb, and try loading again.

original usb_load_uimage:

setenv usb_load_uimage 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage'

becomes:

setenv usb_load_uimage 'mw 0x800000 0 1; run usb_ext2load_uimage'
setenv usb_ext2load_uimage 'if ext2load usb $usb_device 0x800000 /boot/uImage; then version; else usb stop; run usb_init; ext2load usb $usb_device 0x800000 /boot/uImage;fi;'

I have 2 dockstars, and on the 2nd one, the fix for problem 2 was slightly different, but both worked. eg:

setenv usb_ext2load_uimage ext2load usb $usb_device 0x800000 /boot/uImage
setenv usb_load_uimage 'mw 0x800000 0 1; if run usb_ext2load_uimage; then version; else usb stop; run usb_init; run usb_ext2load_uimage;fi;'

The same approach could be used for loading uInitrd. I originally did that also, but my testing revealed that it wasn't necessary after the above fixes were applied.



Edited 1 time(s). Last edit at 10/15/2010 02:00PM by Nematocyst.

I have a PNY Attache 2Gb USB stick that's so old and beat up that I can't identify it further (it has a silver plastic shell with translucent orange highlights). It is very similar to this one. I was able to install and bot from this stick without any issues at all. However, its 2Mb/sec read/write speed really drags down the Dockstar, and I was sure to run out of usable space on the stick.

I also have a Mushkin enhanced 16Gb USB stick recently purchased from NewEgg:
http://www.newegg.com/Product/Product.aspx?Item=N82E16820226079
It has wonderful read and write speed and capacity for a modern USB stick. BUT I'd not been able to get it to boot from the Dockstar all by itself.

I *was* able to boot this stick if I (a) waited long enough for the Mushkin boot to fail allowing the Dockstar firmware to boot, then (b) issue a "reboot" command. I hypothesize that the first boot failure plus the reboot issues the appropriate "reset" on the Mushkin stick, but I have nothing to show for proof.

However, working off the hypothesis provided by this thread, I discovered the "start-stop-start" solution did work for me:

$ /usr/sbin/fw_printenv | grep ^bootcmd
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

$ /usr/sbin/fw_setenv bootcmd "usb start; usb stop; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset"

$ /usr/sbin/fw_printenv | grep ^bootcmd
bootcmd=usb start; usb stop; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

I'm about to try the further finessed command above that leverages the "if" statement, to ensure my Dockstar continues to boot both the Mushkin 16Gb as well as the old PNY 4Gb sticks (you know, for backup).

Hello all; pardon some total noob questions. My background is hardware and this is my first foray into embedded linux. I have (apparently) disabled my dock from phoning home and installed the most recent uboot. However, the dock always boots to the Pogoplug:~$ prompt and continues to respond to the stxadmin password. I have now tried 3 different USB sticks with this same result.
4g Kingston
1g Kingston
2g no-name trade show give-away
I have experimented with various partition sizes on the sticks. The current one is sda1 as 500M and sda2 as 500M swap. I have also tried toggling the bootable flag on sda1 to no avail. I don't know if this is important; prior to installing uboot my dock would show a bash command prompt now it goes to Pogoplug. Thanks for any thoughts.

Chris Z

thank you, Fred, you "start-stop-start" solution does work for me.

just to add to this i have a PNY attache 4gb, brand new purchase (sept 2011). when i turn on my dockstar, uboot goes to the recovery distro of jeff's that i installed over top of the pogo linux. on reboot it will boot to debian that i installed on the PNY drive.

works normal and as expected with an old 2gb sandisk cruzer. its probably 3 years old.

of note with the PNY, it also misbehaves in an xbox 360. if i put a user profile on it and turn on the 360, the console will not see the user profile. if i pull the thumb drive out and reinsert it, the profile will appear. i suspect some kind of dumb initialization issue with the drive. so pretty much it doesn't work for either of the purposes i picked it up for. so i'll be looking around ebay for old sandisk cruzers, since they work fine with the dockstar and the xbox.

i didn't mess too much with environment settings other than this, which didn't help:

setenv usb_init "usb reset; usb start"
saveenv

Thanks a lot for your hints bohdi!
I have fixed the environment as following:

-sh-3.2# fw_printenv
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_installed=0
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_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:50:43:00:02:02
arcNumber=2097
ipaddr=192.168.1.100
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
usb_set_bootargs=setenv bootargs console=$console root=UUID=$usb_root_uuid rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_root_uuid=afe306a5-db03-4b36-98d0-d7531c1f53a7

However it still does not boot into debian. :-(
I will post you here the boot log maybe you or someone can point me in the right direction.
Thanks a lot.

-sh-3.2# reboot
The system is going down NOW!
Sending SIGTERM to all processes
Requesting system reboot
[  454.350000] md: stopping all md devices.
[  455.350000] Restarting system.
[  455.350000] Reseting !!


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 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... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "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: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...


U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (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 128MB
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: REDSTONE:0.1

Streaming disabled
Write allocate disabled


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

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-10-14  20:23:19 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1978544 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.
[    0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #63 Wed Oct 14 13:23:16 PDT 2009
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Console: colour dummy device 80x30
[    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 0MB 0MB 0MB = 128MB total
[    0.000000] Memory: 125824KB available (3592K code, 253K data, 124K init)
[    0.240000] Mount-cache hash table entries: 512
[    0.240000] CPU: Testing write buffer coherency: ok
[    0.240000] NET: Registered protocol family 16
[    0.240000]
[    0.240000] CPU Interface
[    0.240000] -------------
[    0.240000] SDRAM_CS0 ....base 00000000, size 128MB
[    0.240000] SDRAM_CS1 ....disable
[    0.240000] SDRAM_CS2 ....disable
[    0.240000] SDRAM_CS3 ....disable
[    0.240000] PEX0_MEM ....base e8000000, size 128MB
[    0.240000] PEX0_IO ....base f2000000, size   1MB
[    0.240000] INTER_REGS ....base f1000000, size   1MB
[    0.240000] NFLASH_CS ....base fa000000, size   2MB
[    0.240000] SPI_CS ....base f4000000, size  16MB
[    0.240000] BOOT_ROM_CS ....no such
[    0.240000] DEV_BOOTCS ....no such
[    0.240000] CRYPT_ENG ....base f0000000, size   2MB
[    0.240000]
[    0.240000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.240000]
[    0.240000]  Detected Tclk 200000000 and SysClk 400000000
[    0.240000] MV Buttons Device Load
[    0.240000] Marvell USB EHCI Host controller #0: c0539600
[    0.740000] PEX0 interface detected no Link.
[    0.740000] PCI: bus0: Fast back to back transfers enabled
[    0.740000] SCSI subsystem initialized
[    0.740000] usbcore: registered new interface driver usbfs
[    0.740000] usbcore: registered new interface driver hub
[    0.740000] usbcore: registered new device driver usb
[    0.740000] NET: Registered protocol family 2
[    0.750000] Time: kw_clocksource clocksource has been installed.
[    0.840000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.840000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.840000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.840000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.840000] TCP reno registered
[    0.870000] RTC has been updated!!!
[    0.870000] RTC registered
[    0.870000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.870000]   o RAID 5 Xor calculation
[    0.870000]   o kernel memcpy
[    0.870000]   o kenrel memzero
[    0.870000] Number of XOR engines to use: 4
[    0.870000] cesadev_init(c00116f0)
[    0.870000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.870000] MV Buttons Driver Load
[    0.870000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.870000] squashfs: LZMA suppport for slax.org by jro
[    0.870000] JFFS2 version 2.2. (NAND) é 2001-2006 Red Hat, Inc.
[    0.870000] io scheduler noop registered
[    0.870000] io scheduler anticipatory registered (default)
[    0.890000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.890000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.900000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.910000] Loading Marvell Ethernet Driver:
[    0.910000]   o Cached descriptors in DRAM
[    0.910000]   o DRAM SW cache-coherency
[    0.920000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.920000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.930000]   o TCP segmentation offload enabled
[    0.930000]   o Receive checksum offload enabled
[    0.940000]   o Transmit checksum offload enabled
[    0.940000]   o Network Fast Processing (Routing) supported
[    0.950000]   o Driver ERROR statistics enabled
[    0.950000]   o Driver INFO statistics enabled
[    0.960000]   o Proc tool API enabled
[    0.960000]   o Rx descripors: q0=128
[    0.960000]   o Tx descripors: q0=532
[    0.970000]   o Loading network interface(s):
[    0.970000]     o eth0, ifindex = 1, GbE port = 0
[    0.980000]     o eth1, ifindex = 2, GbE port = 1
[    0.990000]
[    0.990000] mvFpRuleDb (c7ed4000): 1024 entries, 4096 bytes
[    0.990000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.000000] Copyright (c) 1999-2006 Intel Corporation.
[    1.010000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.010000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.020000]
[    1.020000] Warning Sata is Powered Off
[    1.020000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.030000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    1.040000] Scanning device for bad blocks
[    1.140000] Using static partition definition
[    1.150000] Creating 4 MTD partitions on "nand_mtd":
[    1.150000] 0x00000000-0x00100000 : "u-boot"
[    1.160000] 0x00100000-0x00500000 : "uImage"
[    1.160000] 0x00500000-0x02500000 : "root"
[    1.170000] 0x02500000-0x10000000 : "data"
[    1.170000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.180000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.210000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.230000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.230000] usb usb1: configuration #1 chosen from 1 choice
[    1.240000] hub 1-0:1.0: USB hub found
[    1.240000] hub 1-0:1.0: 1 port detected
[    1.360000] USB Universal Host Controller Interface driver v3.0
[    1.640000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.790000] usb 1-1: configuration #1 chosen from 1 choice
[    1.790000] hub 1-1:1.0: USB hub found
[    1.800000] hub 1-1:1.0: 4 ports detected
[    2.150000] usb 1-1.2: new high speed USB device using ehci_marvell and address 3
[    2.250000] usb 1-1.2: configuration #1 chosen from 1 choice
[    2.250000] usbcore: registered new interface driver usblp
[    2.260000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    2.270000] Initializing USB Mass Storage driver...
[    2.270000] scsi0 : SCSI emulation for USB Mass Storage devices
[    2.280000] usbcore: registered new interface driver usb-storage
[    2.280000] USB Mass Storage support registered.
[    2.290000] mice: PS/2 mouse device common for all mice
[    2.290000] i2c /dev entries driver
[    2.300000] Linux telephony interface: v1.00
[    2.300000] md: linear personality registered for level -1
[    2.310000] md: raid0 personality registered for level 0
[    2.310000] md: raid1 personality registered for level 1
[    2.490000] raid6: int32x1     97 MB/s
[    2.660000] raid6: int32x2    114 MB/s
[    2.830000] raid6: int32x4    122 MB/s
[    3.000000] raid6: int32x8    110 MB/s
[    3.000000] raid6: using algorithm int32x4 (122 MB/s)
[    3.000000] md: raid6 personality registered for level 6
[    3.010000] md: raid5 personality registered for level 5
[    3.010000] md: raid4 personality registered for level 4
[    3.020000] raid5: measuring checksumming speed
[    3.070000]    arm4regs  :  1084.000 MB/sec
[    3.120000]    8regs     :   754.800 MB/sec
[    3.170000]    32regs    :   899.600 MB/sec
[    3.170000] raid5: using function: arm4regs (1084.000 MB/sec)
[    3.180000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    3.180000] dm_crypt using the OCF package.
[    3.190000] sdhci: Secure Digital Host Controller Interface driver
[    3.190000] sdhci: Copyright(c) Pierre Ossman
[    3.200000] usbcore: registered new interface driver usbhid
[    3.200000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    3.210000] TCP cubic registered
[    3.210000] NET: Registered protocol family 1
[    3.220000] NET: Registered protocol family 17
[    3.220000] md: Autodetecting RAID arrays.
[    3.230000] md: autorun ...
[    3.230000] md: ... autorun DONE.
[    6.450000] Empty flash at 0x009ac208 ends at 0x009ac800
[    7.580000] VFS: Mounted root (jffs2 filesystem) readonly.
[    7.580000] Freeing init memory: 124K
[    7.600000] scsi 0:0:0:0: Direct-Access              USB Reader       0001 PQ: 0 ANSI: 0 CCS
[    8.390000] sd 0:0:0:0: [sda] 15564800 512-byte hardware sectors (7969 MB)
[    8.410000] sd 0:0:0:0: [sda] Write Protect is off
[    8.410000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    8.460000] sd 0:0:0:0: [sda] 15564800 512-byte hardware sectors (7969 MB)
[    8.480000] sd 0:0:0:0: [sda] Write Protect is off
[    8.480000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    8.490000]  sda: sda1 sda2
[    8.500000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    8.500000] sd 0:0:0:0: Attached scsi generic sg0 type 0
init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)
starting pid 284, tty '': '/etc/init.d/rcS'
[    9.790000] eth0: started
udhcpc (v1.7.0) started
HWADDR 00 0x50 0x43 0x00 0x02 0x02
PIP0 2
PIP1 2
Sending discover...
Sending discover...
Sending discover...
HWADDR 00 0x50 0x43 0x00 0x02 0x02
PIP0 2
PIP1 2
Unexpected Argument: leasefail
interface=eth0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PWD=/
SHLVL=1
HOME=/
_=/bin/printenv
No lease, forking to background
starting pid 329, tty '': '/bin/sh'
-sh-3.2# mount /dev/sda1 /mnt
[   25.090000] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
-sh-3.2# cat /mnt/etc/debian_version
6.0.9
-sh-3.2#