I semi-bricked my GoFlex Home a while ago by trying out a new u-boot. It appears that it knocked out the ethernet connectivity & killed the ability to boot properly. I do realize that I tried the GoFlex Net u-boot & I believe that I jacked up the process for using it with a GoFlex Home. What's the best way to go about fixing this?

It is currently connected via serial, which is where I copied the log from.

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Using egiga0 device
ping failed; host 10.10.10.5 is not alive
Hit any key to stop autoboot:  0

Reset IDE: ide_preinit failed
** Bad partition 1 **
** Bad partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
(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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** 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:

Edit: I am able to gain access to the command prompt. U-Boot checks as 1.21.



Edited 2 time(s). Last edit at 05/06/2013 04:42PM by CrimsonKnight13.

As you've discovered, you have not bricked it! it's the same Goflex Net uBoot that allow booting both GoFlex Net and GoFlex Home. You just did not have a USB with rootfs plugged in.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

That's great news then. =)

Are there any tutorials to make a rootfs USB with Arch Linux ARM or Debian ARM? *found the good one by Vlad*

Edit: I have great success! =D

Debian Wheezy now works from a USB drive w/ 3.6.11 kernel
Rescue v2.8.2 installed to NAND
Full network connectivity outside of serial connection

I'm quite pleased with the progress & look forward to tinkering with it again.



Edited 1 time(s). Last edit at 05/08/2013 10:28PM by CrimsonKnight13.