GoFlex home died after the Archlinux upgrade

[SloppyPenguin]

Hi Everyone,

I have a GoFlex Home device, and went ahead with a full ARchlinux update (which is known to create problems with filesystem update after Archlinux's decision to keep everything in /usr/bin, as described here: http://bit.ly/17RaSGM). Unfortunately, my system never came back online. I am getting a kernel panic at boot. I read everything I could find online and still don't know how I can resolve this. Your help will be greatly appreciated.

Here are the details:

I am seeing these messages on the kernel log (obtained by netconsole)

$this->bbcode_second_pass_code('', '[ 12.909347] Kernel panic - not syncing: Attempted to kill init!
[ 12.915363] [<c000d290>] (unwind_backtrace+0x0/0xe0) from [<c03d2b34>] (panic+0x58/0x198)
[ 12.923647] [<c03d2b34>] (panic+0x58/0x198) from [<c0021afc>] (do_exit+0x88/0x7a0)
[ 12.931306] [<c0021afc>] (do_exit+0x88/0x7a0) from [<c00224a4>] (do_group_exit+0x0/0xf8)
[ 12.939476] [<c00224a4>] (do_group_exit+0x0/0xf8) from [<40289000>] (0x40289000)
')

And the boot messages are as follows:

$this->bbcode_second_pass_code('', 'U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(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
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 1 not supported
** Block device usb 1 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 2 not supported
** Block device usb 2 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 3 not supported
** Block device usb 3 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ST2000DL001-9VT156 Firm: CC98 Ser#: 5YDA2RL2
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2889400 bytes read
Loading file "/uInitrd" from ide device 0:1 (hda1)
** File not found /uInitrd
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
2643758 bytes read
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-3.1.10-22-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2889336 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: UBIT-2010.11-00125-ga21bcca
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2643694 Bytes = 2.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...')

[WarheadsSE]

Uhm..

Yeah, Arch kernel & UBIT uInitrd? problemo, right there.

[SloppyPenguin]

Actually, I am all ears for *any* suggestions to 'un-brick' the device. Not necessarily trying to repair Archlinux. When I configured this NAS almost a year ago, UBIT & Archlinux seemed like the best way to go At this point, does it seem possible to save the device without wiping all the personal data in it, or did I just end up with an expensive internal hard drive?

[WarheadsSE]

Lol.. Yeah, you're fine. It isn't a brick.

You just need to figure out why it is loading the UBIT initrd, and stop that.

$this->bbcode_second_pass_quote('', 'L')ol.. Yeah, you're fine. It isn't a brick.

[WarheadsSE]

If you can get it booted into *anything* you can flash the uboot again, and probably be fine.

[SloppyPenguin]

$this->bbcode_second_pass_quote('', 'I')f you can get it booted into *anything* you can flash the uboot again, and probably be fine.

[moonman]

Ubuntu doesnt support armv5. Either create a bootable usb stic or connect your drive to a pc and remove all uinitrds that you can find (look in the root of the drive and under /boot)

[SloppyPenguin]

Yea, I think I bricked it this time I attempted to erase nand and write the original FW, which failed. I can no longer see any messages on the console, and also no blinking lights... It was fun while it lasted

[moonman]

Get a $2 usb to ttl adapter and unbrick it then.