Recovery System ready for use

Thanks for your answer!

So you think it is not a good advice to install the recovery (as a replacement for the - in my case - useless) pogoplug software? In my understanding it is and so I installed it.

Already flashed the recovery again but with no success. It does not boot really. After blinking orange (or yellow?) the led turns off.

After posting yesterday I unset arcNumber but that was not a good idea because now it does not boot from hdd, too. By now I have a bricked dockstar. Just ordered a serial cable to see what exactly fails. Can last a few days. Does the rescue system (with the newest uboot) support debugging by serial?

I have another dockstar here in original delivery state and will experiment with it. Maybe I can see what I am doing wrong.

//edit:

After installing the second dockstar having debian on usb stick and booting I had another try with the rescue system. Symptom is exactly the same: With usb stick it boots and gets an ip from my router (uDCHPd running) and without it fails totally. After flashing green then orange the led turns off and nothing more happens.

With all respect to Jeffs work at this device its a fatal rescue system where the rescue itself fails to boot?!

//edit2:

According to netconsole the system says it starts the kernel (with all checksums ok), but then noting more happens.



Edited 2 time(s). Last edit at 11/07/2010 10:06AM by Riffer.

Hi Riffer,
set the arcNumber -Value to 2097, then the Dockstar boots normally.
DHCP fails for me too, but Lothar post a workaround that works for me:

Since i didnt get zcip to work at all and dont wanted to depend on a working dhcp i added an alias to /etc/init.d/rcS:

ifconfig eth0:2 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255 up

regards
Stefan

> set the arcNumber -Value to 2097, then the
> Dockstar boots normally.

Many thanks to you. I will give it a try (tomorrow, because I am away from my dockstars atm).
But why 2097? In http://forum.doozan.com/read.php?3,1893 Jeff tells 2998 is the right number?

ifconfig eth0:2 192.168.1.2 netmask 255.255.255.0
broadcast 192.168.1.255 up

then

ifconfig eth0:2 192.168.0.2 netmask 255.255.255.0
broadcast 192.168.0.255 up

would work for my 192.168.0.xxx network?

best regards,
Riffer



Edited 1 time(s). Last edit at 11/08/2010 05:02AM by Riffer.

Hi,

Quote

But why 2097? In http://forum.doozan.com/read.php?3,1893 Jeff tells 2998 is the right number?

2097 ist the original value from the Dockstar. With 2997 my dockstar didn't boot the rescue-system (all ok with debian on hd). Then I'm connect a serial-cable und change the value to the original value. After that, the dockstar boots also the rescue-system.

Quote

would work for my 192.168.0.xxx network?

Yes, change the values to your subnet. In your example your dockstar ist available under the IP-Adress 192.168.0.2

regards
Stefan

Stefan Wrote:
-------------------------------------------------------
> 2097 ist the original value from the Dockstar.
> With 2997 my dockstar didn't boot the
> rescue-system (all ok with debian on hd). Then I'm
> connect a serial-cable und change the value to the
> original value. After that, the dockstar boots
> also the rescue-system.

Great! Sounds like the rescue of my now semi broken first dockstar is an easy task. The second one still boots so I can set the arcNumber from running debian.

I thank you very much! (and apologies for my rough english but I am a guy from germany and beside my school grade in english was not the very best school time is over a long time ago. But life and job teached me more english then any school lession could do).

Works great but a few nagging issues.

I'd like the dockstar to boot from usb (flash) first and fallback to the rescue image only if that fails.

Currently if I'm running debian off usb and if I do a reboot/shutdown it will comeback with the rescue image.
I have to pull the plug to go back to usb instead. Kinda makes it a pain to do remote administration via ajaxterm or webmin if a physical reboot is required.

Is there a workaround for this? Maybe a script that can reload the root filesystem from usb that I can run as a watchdog on the rescue disk or somesuch ?

I remember seeing a similar script for reloading the dns-323 from usb ...
Would a hack like the one used in setup.sh in the linked procedure work ? http://bfg100k.blogspot.com/2008/11/upgrading-ffp-05-and-moving-it-to-usb.html

Or is there a cleaner solution I can use to avoid having to physically power cycle the device to get it to recover properly?

Just feels like it's missing some option in uboot to give the USB time to pick up the slack or something...

Fixed it myself.

I used Jeff's uBoot usb polling script and that fixed my issue. Didn't know the side port was the last one on the list.

Hello Jeff,
I did every as instructed and it seem ok. The problem is that my nand has some bad block, now it won't boot to rescue or popoplug which is gone. Can you show me how to fix this. And also, why do I have bad block in the first place. I only had this unit for less than 2 weeks. reinstall uboot few times(less than 10). Last, is it possible to restore to factory popoplug if you have mdt0,mdt1,mdt2 backup?
Thanks.



Edited 1 time(s). Last edit at 11/10/2010 11:14PM by guest01.

RobM Wrote:

> I used Jeff's uBoot usb polling script and that

Could you please leave a link here? I can not find that one.

thanks,

Just got a dockstar today - love it!

I installed Debian on a flash drive (and cp -a it to a USB hard drive as well) - both work great.

I also installed the rescue system. - which works fine. When I try and plug in flash drivers and USB hard drive when running the rescue system - I see the devices detected in dmesg:

44.068220] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5408
[ 44.075133] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 44.082493] usb 1-1.2: Product: U3 Titanium
[ 44.086693] usb 1-1.2: Manufacturer: SanDisk
[ 44.091023] usb 1-1.2: SerialNumber: 3551920EACD1C080
[ 44.097339] usb 1-1.2: configuration #1 chosen from 1 choice
[ 44.106911] scsi0 : SCSI emulation for USB Mass Storage devices
[ 44.117154] usb-storage: device found at 3
[ 44.117164] usb-storage: waiting for device to settle before scanning
[ 49.107558] usb-storage: device scan complete
[ 49.108183] scsi 0:0:0:0: Direct-Access SanDisk Cruzer 8.01 PQ: 0 ANSI: 0 CCS
[ 51.297629] usb 1-1.4: new high speed USB device using orion-ehci and address 4
[ 51.408720] usb 1-1.4: New USB device found, idVendor=1058, idProduct=1021
[ 51.415629] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 51.422988] usb 1-1.4: Product: Ext HDD 1021
[ 51.427276] usb 1-1.4: Manufacturer: Western Digital
[ 51.432302] usb 1-1.4: SerialNumber: 574D41563532333536363538
[ 51.439173] usb 1-1.4: configuration #1 chosen from 1 choice
[ 51.448880] scsi1 : SCSI emulation for USB Mass Storage devices
[ 51.458898] usb-storage: device found at 4
[ 51.458908] usb-storage: waiting for device to settle before scanning
[ 56.457569] usb-storage: device scan complete
[ 56.458557] scsi 1:0:0:0: Direct-Access WD Ext HDD 1021 2002 PQ: 0 ANSI: 4


BUT - I don't see the partitions:

rescue:/tmp# cat /proc/partitions
major minor #blocks name

31 0 1024 mtdblock0
31 1 4096 mtdblock1
31 2 32768 mtdblock2
31 3 486400 mtdblock3



Is this normal? - when I inserted both disks in stock pogo - they appeared in /proc/partitions

How can I tell what partitions the external devices are are to mount them?

thanks,

PHT

Hi,

I have installed the rescue system on a GoFlex Net, but it will not boot.
All I get is:

U-Boot 2010.09 (Oct 23 2010 - 11:53:10)
Marvell-GoflexNet by Jeff Doozan, Peter Carmichael

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... 1 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-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:        1751
UBI: number of bad PEBs:         1
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:             1730
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'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** 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..

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

LED keeps blinking orange...

Any suggestions?

Well - please disregard.

Even though the USB drives DON'T appear in /proc/partition - they are still mountable.

mount /dev/sda1 /tmp/sda1 worked fine.

Thanks,

PHT


Peter Hope-Tindall Wrote:
-------------------------------------------------------
> thanks,
>
> Just got a dockstar today - love it!
>
> I installed Debian on a flash drive (and cp -a it
> to a USB hard drive as well) - both work great.
>
> I also installed the rescue system. - which works
> fine. When I try and plug in flash drivers and
> USB hard drive when running the rescue system - I
> see the devices detected in dmesg:
>
> 44.068220] usb 1-1.2: New USB device found,
> idVendor=0781, idProduct=5408
> [ 44.075133] usb 1-1.2: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> [ 44.082493] usb 1-1.2: Product: U3 Titanium
> [ 44.086693] usb 1-1.2: Manufacturer: SanDisk
> [ 44.091023] usb 1-1.2: SerialNumber:
> 3551920EACD1C080
> [ 44.097339] usb 1-1.2: configuration #1 chosen
> from 1 choice
> [ 44.106911] scsi0 : SCSI emulation for USB Mass
> Storage devices
> [ 44.117154] usb-storage: device found at 3
> [ 44.117164] usb-storage: waiting for device to
> settle before scanning
> [ 49.107558] usb-storage: device scan complete
> [ 49.108183] scsi 0:0:0:0: Direct-Access
> SanDisk Cruzer 8.01 PQ: 0 ANSI: 0 CCS
> [ 51.297629] usb 1-1.4: new high speed USB
> device using orion-ehci and address 4
> [ 51.408720] usb 1-1.4: New USB device found,
> idVendor=1058, idProduct=1021
> [ 51.415629] usb 1-1.4: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> [ 51.422988] usb 1-1.4: Product: Ext HDD 1021
> [ 51.427276] usb 1-1.4: Manufacturer: Western
> Digital
> [ 51.432302] usb 1-1.4: SerialNumber:
> 574D41563532333536363538
> [ 51.439173] usb 1-1.4: configuration #1 chosen
> from 1 choice
> [ 51.448880] scsi1 : SCSI emulation for USB Mass
> Storage devices
> [ 51.458898] usb-storage: device found at 4
> [ 51.458908] usb-storage: waiting for device to
> settle before scanning
> [ 56.457569] usb-storage: device scan complete
> [ 56.458557] scsi 1:0:0:0: Direct-Access WD
> Ext HDD 1021 2002 PQ: 0 ANSI: 4
>
>
> BUT - I don't see the partitions:
>
> rescue:/tmp# cat /proc/partitions
> major minor #blocks name
>
> 31 0 1024 mtdblock0
> 31 1 4096 mtdblock1
> 31 2 32768 mtdblock2
> 31 3 486400 mtdblock3
>
>
>
> Is this normal? - when I inserted both disks in
> stock pogo - they appeared in /proc/partitions
>
> How can I tell what partitions the external
> devices are are to mount them?
>
> thanks,
>
> PHT

Interesting LED weirdness.

Debian (USB) boot will work find with arcNumber=2097 or arcNumber=2998 - if set to 2998 - the kernel allows control of the LED.

But - the recovery system will ONLY boot if arcNumber=2097 - although it supports the LED with a heartbeat. (will not boot with arcNumber=2998).

PHT

Take that back. After a cold boot - neither the recovery system or the USB debian boot work boot with arcnumber=2998.

I needed to reset the uboot.environment using nc to make it come back to life.

I think I'll forego the LED flashing correctly for now - a working dockstar is better to have!!!

;-)

PHT

Peter Hope-Tindall Wrote:
-------------------------------------------------------
> Debian (USB) boot will work find with
> arcNumber=2097 or arcNumber=2998 - if set to 2998
> - the kernel allows control of the LED.
>
> But - the recovery system will ONLY boot if
> arcNumber=2097 - although it supports the LED with
> a heartbeat. (will not boot with arcNumber=2998).


I had exactly the same problem and at the end I decided to NOT set the arcNumber to another value then 2097 because only with this the rescue is able to startup - and what else is a rescue system that does not boot then nonsense?

But why have you Jeff done it this way?

Why using 2097 for the rescue system where the standard kirkwood kernel only does right led support with 2998?

Jeff? Could you please update the rescue system to use 2998?

Finally I had success!

Now the dockstar starts up with LED working under kernel 2.6.35.9 with arcNumber 2998.

For others who want to build their own rescue image I post a short description and a new build-dockstar-archive for buildroot-2010.11 maybe tomorrow after having some tests. There have been some changes to the files Jeff supported but my job is completly based on his work. Hope all works fine for you!

//edit:

Here is my archive for kernel 2.6.35.9.

Buildroot-Dockstar.tgz

cd /usr/src
wget http://buildroot.uclibc.org/downloads/buildroot-2010.11.tar.gz
tar -xzvf buildroot-2010.11.tar.gz
cd buildroot-2010.11
wget http://www.meineneue.de/wp-content/buildroot-dockstar.tgz
tar -xzvf buildroot-dockstar.tgz
cp custom/buildroot-config .config
make

after that you must follow the original notes by Jeff in start posting!

To install the self compiled image you have to chance Jeffs install script.
When I have time I will post an adapted version for your convenience.

Any reports are welcome!



Edited 4 time(s). Last edit at 02/17/2011 09:30AM by Riffer.

Hi all,

During some tests I lost the feature booting into pogoplug or into usb debian system.

I have only the Marvell prompt. ( thanks to netcat system )
Now I have downloaded and started the rescue system from usb.
I was able to login into the RAM Running Rescue System.

But now the rescue install install_rescue.sh doesn't work.


The Question is: how to install an new Rescue System on the dockstar system.
Cause the pogoplug doesn't work anymore.

Thanks in advance...



Edited 2 time(s). Last edit at 01/02/2011 02:37AM by htreede.

Hi!
I have just installed the rescue system, but it failed:

Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete  
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 203 -- 100 % complete  
ubiformat: formatting eraseblock 255 -- 100 % complete  
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
# Rescue System installation has completed successfully.

When I reboot, u-boot says:

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-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'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** 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.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:  done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...

Any idea?
Thanks!

I have solved my problem. The file /etc/fw_env.config was already present but with the wrong contents. As the install_recue.sh script did not overwrite it, the fw_printenv and fw_setenv commands did not work.

After fixing this, it is now OK.

Hi Riffer,

which steps i have to perform after make?

Regards

Is there any way to get the rescue boot with arcNumber=2998 ? Or maybe a way to restore the pogoplug system, because this rescue system is not really useful as a rescue as it can't boot...

Can't install the rescue system after installing openwrt because the flash (/dev/mtd) layout has changed. mtd1 and mtd2 are now too small to hold rescue images. The changes are shown at the openwrt website:

http://wiki.openwrt.org/toh/seagate/dockstar#flashlayout

I can't figure out how to change the mtd partition sizes from openwrt. Is it using the mtd_utils? I can erase and write to mtd but can't seem to delete and resize partitions. Can they be deleted and resized when booted into openwrt without crashing the Dockstar?

If the mtd partion sizes are set from uboot (I have the Jeff's modified uboot already written to mtd0), can the rescue system be installed using tftp in uboot?

bohwaz Wrote:
-------------------------------------------------------
> Is there any way to get the rescue boot with
> arcNumber=2998 ? Or maybe a way to restore the
> pogoplug system, because this rescue system is not
> really useful as a rescue as it can't boot...

I have the same problem too.

Until it gets fixed...I have clone my USB boot stick in case my primary boot stick fails.

Patiently waiting....
S9

I got the recovery system installed over my openwrt install. Afterwards I was able to get debian installed on a flash drive. This was a trial and error process, especially writing mtd2. For some reason the write never completed-- the dockstar hung during the nand write.e step. I waited a few minutes the first couple of times and then I waited about half an hour but it never finished. None the less, the write appears to have been successful as I have a working recovery system. I was then able to write debian to an external flash drive. In case anyone is in the same boat, here are the steps I used:

Boot into uboot-- I had already installed Jeff's modified uboot but I don't see why this shouldn't work with the pre-installed uboot. Although you will probably want to upgrade when you have a working recovery system.

First, repartition the flash/mtd device:

mtdparts del uImage
mtdparts del rootfs
mtdparts del data

mtdparts add nand0 0x400000@0x100000 uImage
mtdparts add nand0 0x2000000@0x500000 root
mtdparts add nand0 0xdb00000@0x2500000 data

saveenv

Next, write mtd1 and mtd2. If the write for mtd2 hangs, let it go for a while (10s of minutes I would think should be sufficient).

mw.b 0x6400000 0xff 0x400000
tftpboot 0x6400000 uImage-mtd1.img
nand erase 0x00100000 0x00400000
nand write.e 0x6400000 0x00100000 0x400000

mw.b 0x6400000 0xff 0x2000000
tftpboot 0x6400000 rootfs-mtd2.img
nand erase 0x00500000 0x02000000
nand write.e 0x6400000 0x500000 0x2000000

saveenv

Then it was a matter of setting env variables until the thing worked. This was a somewhat tedious process-- I am sure there is an easier way to do it than how I did it. I 'setenv'ed variables to match a post on the first page of this thread until it booted properly. I then installed debian to a flash drive. More twiddling with saveenv to get usb booting properly. But everything now works.

For an explanation of uboot commands, I found http://www.denx.de/wiki/U-Boot/Documentation to be helpful.

> which steps i have to perform after make?

Please have a look at the start post of Doozan: http://forum.doozan.com/read.php?4,831,831#msg-831

To install the image you will must have a look into the install file of Doozan and change it to not download from his site but from your ftp or copy it manually by scp and to use your self compiled image.

Maybe I will have time to release a special version of it.

Hello!

Today i was trying to install a rescue system and got a following error:

Quote
# Installing Rescue System

Erasing 128 Kibyte @ 400000 -- 100 % complete.
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
Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: error!: file "/tmp/rootfs-mtd2.img" (size 4570273 bytes) is not multiple of eraseblock size (131072 bytes)
error 0 (Success)
Installation failed.

Somebody knows what was going wrong here?

I have the same error as harrim4n.
using /usr/sbin/ubiformat /dev/mtd2 -s 512 -f /tmp/rootfs-mtd2.img -y
produces the same output.
Is it safe to reboot or what should I do?
Thanks


Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 13 -- 6 % complete libmtd: error!: cannot write 131072 bytes to mtd2 (eraseblock 13, offset 0)
error 12 (Cannot allocate memory)

ubiformat: error!: cannot write eraseblock 13
error 12 (Cannot allocate memory)
Installation failed.

like rfanch3r in the other thread I removed the two image files, rerun the installer and all went fine.
Isn't it strange that it fails in the same spot (6%)?

Hi !

I have a little problem here on my Goflex Home.

I tried to install the recovery system and it's not booting, even on my USB key ...

The only thing i have done (and shoudn't have done I think) is "setenv arcNumber 3089"

Is the recovery system not booting with this arcNumber ?

What con I do ? I don't have a netconsole set ... I think I will use a serial cable. (Is there a tutorial on how to use and solder the serial cable ?)