Advice Please: Wheezy script failed at debootstrap and now NAND won't boot

I made the mistake of rebooting after the Wheezy script failed at debootstrap.

Now my GoFlex Net won't boot from NAND properly. Luckily it looks like U-Boot installed correctly, I can boot rescue disk from USB drive, and therefore managed to grab a U-Boot log using nc.

I'd like to try and continue with the installation, but not sure how to go about this...

Some advice please: Would it be better to

a) try and restore original Go-Flex U-Boot and use the reset switch to restore back to factory settings
...I'm guessing this is risky since the original U-Boot doesn't have the functionality of the old one and if it doesn't work it could be completely bricked.

b) leave new U-Boot in place and try and restore just the original firmware, and start again with the install
...Unfortunately I didn't take a backup of the firmware so I'll have to find it somewhere else.

c) boot from the rescue disk and try and complete the install from there
...The problem here is that with the rescue disk in the only usb port, where do I install Wheezy to? I guess I could try and install it to one of the sata drives and configure U-boot to look there for the install

d) wipe some of the original firmware and add a rescue partition on the NAND.
... This would make it easier to install Wheezy to external USB flash drive

It would be great to get optinions on best way to go.

Enclosed is log of failed NAND boot. Not sure what's going on here or whether it can be fixed easily.

Thanks,

Felix

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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:        1748
UBI: number of bad PEBs:         4
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:             1727
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: .......  read_nand_cached: error reading nand off 0xa56200 size 8192 bytes
.  read_nand_cached: error reading nand off 0x1b00000 size 8192 bytes
 done.
read_nand_cached: error reading nand off 0xa55a00 size 8192 bytes
off = 0xa54ee0 magic 0x1985 type 0xe002 node.totlen = 3051
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

anyone?

Go with option c, but boot from the RAM based rescue: http://forum.doozan.com/read.php?4,1871 It shouldn't be a problem to swap the USB drive at that point.

Hi Jeff,

Thanks for the advice, and great forum by the way. I would have never have thought of using RAM based rescue option.

It all went well and I managed to get Debian installed correctly.

I still have no idea why the orginal pogoplug firmware got corrupted. I couldn't see anything in the script that could have caused it. However, I don't need it now, so it's all good.

Many thanks,

Felix