Help me to unbrick GFH

Hi! After five hours of mindblowing tries, I come here to ask for help, guys.

I have GoFlex Home 2TB with ArchLinux onboard (if it still there, huh). I want to reinstall it (don't ask me 'why', please) with this manual and after partitioning drive power in my house suddenly goes off... after it recovering I found that my GFH just blinking with green LED and I can't even make SSH to it. It seems his drive was totally cleared. But GFH has not only drive, huh? ;)

So I opened terminal in my MacOS and start listening to 'nc -luk 10.10.10.5 6666'. Hmmm... at least it resolving so now I can load ArchLinux from USB, push old uboot so my reset button start working again, restore GFH to original firmware via this guide and then install Arch again. Let's go!

At first I've installed Ubunti with Parallels Desktop (MacOS and Linux have a 'bit' difference with terminal commands, you know). Then, in Ubuntu I completed this guide with my 2GB USB stick to be able to load from it and then flash default uboot with working reset button. Put it in GFH, restart it and... nothing. Tried to re-format it and put files manually (not via terminal). Nothing. Tried to put files not in root of partitions but in folders 'boot' and 'root'. Nothing! I even tries to do this all but with formatting second (largest) partition not in ext4 but in ext2 - nothing! Of course I followed file copying order and make all changes under root, not just sudo.

Here is some log from nc:

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... 2 USB Device(s) found
       scanning bus for storage devices... 1 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!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
Loading file "/uInitrd" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
reading /boot/uImage

** Unable to read "/boot/uImage" from usb 0:1 **
reading /uInitrd

** Unable to read "/uInitrd" from usb 0:1 **
** 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: ST32000542AS Firm: CC95 Ser#: 5XW1S88L
            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)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
Loading file "/uInitrd" from ide device 0:1 (hda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
reading /boot/uImage

** Unable to read "/boot/uImage" from ide 0:1 **
reading /uInitrd

** Unable to read "/uInitrd" from ide 0:1 **
** Bad partition 1 **
** Bad partition 1 **
No Powersaving mode 7F
Error (no IRQ) dev 1 blk 0: status 0x7f
** Can't read from device 1 **

** Unable to use ide 1:1 for fatload **
No Powersaving mode 7F
Error (no IRQ) dev 1 blk 0: status 0x7f
** Can't read from device 1 **

** Unable to use ide 1:1 for fatload **
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:ramdisk", error -19
Error reading superblock on volume 'ubi:ramdisk'!
UBIFS not mounted, use ubifs mount to mount volume first!
Marvell>>

But there is boot img on my USB stick:

Marvell>> usb tree
usb tree

Device Tree:
  1  Hub (480 Mb/s, 0mA)
  |  u-boot EHCI Host Controller 
  |
  +-2  Mass Storage (480 Mb/s, 100mA)
       Generic Mass Storage BCF3FE91
     
Marvell>> fatls usb 0:1
fatls usb 0:1
            
            ./
   104212   mlo 
   361488   u-boot.img 
      603   uenv.txt 

3 file(s), 2 dir(s)

Manual reading and usbboot doesn't help me...

Marvell>> fatload usb 0:1 0x0000000 boot/u-boot.img
fatload usb 0:1 0x0000000 boot/u-boot.img
reading boot/u-boot.img

361488 bytes read

Marvell>> usbboot
usbboot

** No boot device **

So... now I'm totally stacked. What's wrong? Why it wont to load from USB? And if it totally can't do it because of some unknown reason - how I can restore my original firmware or re-install Acrh if I cant even SSH my device?

Will be much appreciated for any assistance and especially for detailed instruction because I am newbie in all of this. :)

P.S: Also I've registered at this board but can't log in with my login/password. 'That username/password was not found or is inactive. Please try again.' I even tried to reset my password and log in with new combination - no success.

Not my day, may be :(

As I can understood - now my GFH is just totally cleared HDD with dock station with strange u-boot and inactive 'reset' button. What I must do to scream "it's alive!" ?

Veniq,

Looks like neither your USB or HDD rootfs is fit for booting. uBoot can't find the kernel images to load. Do these things:

1. Interrupt netconsole again and print out uBoot envs and post here.
printenv

2. Shutdown and unplug both the HDD and USB drives. Use a different USB stick if you can (or use the same one if you are OK with erasing the content completely). On a differrent Linux box, put this Debian 3.11.1 rootfs on the USB stick and boot with it.
http://forum.doozan.com/read.php?2,12096
whether it will work depending on how your uBoot envs are defined currently. But it's worth a try.

Finally, you are running an old version of uBIT. You should upgrade uBoot with Jeff's installation script install_uboot_mtd0.sh (see http://projects.doozan.com/uboot). This will make things easier later on. After you've installed new uBoot you can run either Arch or Debian.

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

Here is my printenv:

Marvell>> printenv 
printenv
bootcmd=run fast_boot; run usb_boot; run hd_boot; run ubi_boot
bootdelay=3
baudrate=115200
ide_start=ide reset
ubi_start=ubi part root
usb_start=usb start
nc_test=ping $ncip
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
silent_boot=run silent_rd ubi_args ubi_fallback
fast_boot=run fast_rd ubi_args ubi_fallback
usb_boot=for scan in 0 1 2 3; do run usb_args_$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback;done
usb_args_0=boot_dev='usb 0:1'; dev_args='root=/dev/sda1 rootdelay=10'
usb_args_1=boot_dev='usb 1:1'; dev_args='root=/dev/sdb1 rootdelay=10'
usb_args_2=boot_dev='usb 2:1'; dev_args='root=/dev/sdc1 rootdelay=10'
usb_args_3=boot_dev='usb 3:1'; dev_args='root=/dev/sdd1 rootdelay=10'
hd_boot=run ide_start; for scan in 0 1; do run hd_args_$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback; done
hd_args_0=boot_dev='ide 0:1'; dev_args='root=/dev/sda1'
hd_args_1=boot_dev='ide 1:1'; dev_args='root=/dev/sdb1'
ubi_boot=run ubi_rd ubi_args ubi_fallback
ubi_args=dev_args='ubi.mtd=root'
rescue=dev_args='ubi.mtd=root rootfstype=preboot'; boot_dev='usb 0:1'; run ext2_kern ext2_auto boot_rd; boot_dev='ide 0:1'; run ide_start ext2_kern ext2_auto boot_rd; run silent_rd ubi_fallback; run fast_rd ubi_fallback; run ubi_rd ubi_fallback
chain=nand read.e 0x800000 0x480000 0x80000; go 0x800200
ethact=egiga0
console=ttyS0,115200
mtdids=nand0=orion_nand
set_bootargs=setenv bootargs console=$console $mtdparts $dev_args $rd_args netconsole=@$ipaddr/eth0,@$ncipk/
ext2_kern=ext2load $boot_dev $addr_kern /boot/uImage
ext2_auto=ext2load $boot_dev $addr_rd /boot/uInitrd
ext2_rd=ext2load $boot_dev $addr_rd /uInitrd
ext2_boot=run ext2_rd boot_rd; run ext2_auto boot_auto; run boot_kern
fat_kern=fatload $boot_dev $addr_kern /boot/uImage
fat_rd=fatload $boot_dev $addr_rd /uInitrd
fat_boot=run fat_rd boot_rd
ubi_kern=ubifsmount boot; ubifsload $addr_kern /boot/uImage
ubi_rd=ubifsmount ramdisk; ubifsload $addr_rd /uInitrd
ubi_fallback=run ubi_kern boot_rd
silent_rd=ubifsmount silent; ubifsload $addr_rd /uInitrd
fast_rd=ubifsmount fast; ubifsload $addr_rd /uInitrd
boot_kern=run set_bootargs; bootm $addr_kern
boot_rd=run set_bootargs; bootm $addr_kern $addr_rd
boot_auto=rd_args='rootfstype=auto'; run boot_rd
addr_kern=0x680000
addr_rd=0x1100000
ipaddr=10.10.10.6
ncip=10.10.10.5
ncipk=10.10.10.4
serverip=10.10.10.3
led_init=green blinking
led_exit=green off
led_error=orange blinking
ethaddr=02:50:43:36:21:57
preboot=run ubi_start silent_boot; run nc_test nc_start; run usb_start
mtdparts=mtdparts=orion_nand:1M(u-boot),6M(uImage),-(root)
partition=nand0,0
mtddevnum=0
mtddevname=u-boot
stdin=nc
stdout=nc
stderr=nc

Environment size: 2742/131068 bytes

As you can see, this guide by updating uboot

http://projects.doozan.com/uboot

is one of my steps to unbricking GFH at all (after that my reset button will be active again so I can flash stock firmware). But I can't complete that guide at least because of I can't SSH to my device. So, depending on your message, my last chance is try to made another USB stick. Hope, this will work or Jeff will advice some other pretty way to make everything work...

Veniq Wrote:
-------------------------------------------------------
> As you can see, this guide by updating uboot
>
> http://projects.doozan.com/uboot
>
> is one of my steps to unbricking GFH at all (after
> that my reset button will be active again so I can
> flash stock firmware). But I can't complete that
> guide at least because of I can't SSH to my
> device. So, depending on your message, my last
> chance is try to made another USB stick. Hope,
> this will work or Jeff will advice some other
> pretty way to make everything work...

Right! your boot log showed you are still running uBIT:

U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael

This is will cause problem booting later with kernel 3.2.x+.

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

About old uBIT/uBoot (I can't understand difference between these terms, sorry) - I just followed this manual:

http://archlinuxarm.org/platforms/armv5/seagate-goflex-home (installation tab, from step 14)

So after that I got what I got :)

U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael

I don't know can I replace suggested in manual uBoot with newest (and if can - how?) or just skip those steps because I gonna update it after making USB stick anyway. Any advice will appreciated.

---

You said 'right' - so, new USB stick will really help in my situation or it still just 'worth a try'?

Veniq,

> You said 'right' - so, new USB stick will really
> help in my situation or it still just 'worth a
> try'?

Try it and see if it works.

Or better yet, if you intent to run Arch, then get the Arch rootfs tarball from:
http://archlinuxarm.org/platforms/armv5/seagate-goflex-home
(see installation step 12), and try booting with it.

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

I doesn't understood nothing in Debian topic so I follow yours advice and made bootable USB with Arch onboard via last link that you posted here, connected it to GoFlex dock, rebooted device and it successfully start kernel.

So I pushed new UBOOT via Jeff's guide:

# Setting arcNumber to 2097 (SheevaPlug)
# Note: if you have a kernel that supports your platform, you should use the proper arcNumber.
# You can set the correct arcNumber by running the following command:
/usr/sbin/fw_setenv arcNumber 3089

# uBoot installation has completed successfully.

...and (SIC!!! I'm dumbass...) rebooted device. Now it just blinking red. If I plug SATA drive or USB it blinking green then any LED disappears. Can't SSH to it. NC also show nothing... only after this I found new guide:

http://archlinuxarm.org/forum/search.php?st=0&sk=t&sd=d&sr=posts&keywords=reboot&t=3355&sf=msgonly&ch=-1&start=10

which says that I must NOT reboot before set correct arcNubmer, NC and ethaddr. Yeah, and reset button still inactive.

Thats all, I can go to shop for new GoFlex?

Veniq Wrote:
-------------------------------------------------------
> I doesn't understood nothing in Debian topic so I
> follow yours advice and made bootable USB with
> Arch onboard via last link that you posted here,
> connected it to GoFlex dock, rebooted device and
> it successfully start kernel.
>
> So I pushed new UBOOT via Jeff's guide:
>
>

> # Setting arcNumber to 2097 (SheevaPlug)
> # Note: if you have a kernel that supports your
> platform, you should use the proper arcNumber.
> # You can set the correct arcNumber by running the
> following command:
> /usr/sbin/fw_setenv arcNumber 3089
> 
> # uBoot installation has completed successfully.
>

>
> ...and (SIC!!! I'm dumbass...) rebooted device.
> Now it just blinking red. If I plug SATA drive or
> USB it blinking green then any LED disappears.
> Can't SSH to it. NC also show nothing... only
> after this I found new guide:
>
> http://archlinuxarm.org/forum/search.php?st=0&sk=t
> &sd=d&sr=posts&keywords=reboot&t=3355&sf=msgonly&c
> h=-1&start=10
>
> which says that I must NOT reboot before set
> correct arcNubmer, NC and ethaddr. Yeah, and reset
> button still inactive.
>
> Thats all, I can go to shop for new GoFlex?

arcNumber is not a problem, since you have the latest rootfs with kernel that can handle it. The reason was the ethaddr. When the LED is red, it meant the boot process was aborted because some value was not set, which in this case it most likely the ethaddr. Sometime updating uBoot to a much newer version will wipe out the currrent ethaddr.

To unbrick the box, you need serial console. Buy a serial module converter like I recommended in this thread:
http://forum.doozan.com/read.php?8,13263,13264#msg-13264

Or get a Nokia CA-42 cable and modify it.

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

Both of them or only USB 2.0 to TTL UART?

Only the serial module converter, the header might not be applicable (depending on whether the header was pre-installed or not).

First, open the GF Home first to check if the header is installed or just holes on the board. Pics from Arch site:
http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3397

If there is already serial header then you can use wire testing clips to connect them. As varkey recommended:
http://www.varkey.in/2011/06/seagate-goflex-net-serial-connection/

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

How I can disassemble GFH cradle? I put out two screw that was under rubber legs so I can open only that side of cradle... opposite side seems closed. :(

Veniq Wrote:
-------------------------------------------------------
> How I can disassemble GFH cradle? I put out two
> screw that was under rubber legs so I can open
> only that side of cradle... opposite side seems
> closed. :(

No, it is not. It only looks that way. The bottom plate has several hinges that hold it snugly fit to the case. After taken off the 2 screws, use a thin plastic tool/knife (or even a steak knife would work) to get into the groove and pry it opened, very slowly and gently. In the process, you would break some hinges, but that's OK, there are many to keep the case closed.

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