Upgrading GoFlexHome from ubit

[lauri4n]

Hi,

I tried to upgrade my old archlinux-arm install, but I did something in wrong order and my goflex didn't boot anymore. I guess that I didn't update uboot and I just created a new usb from http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz. And now, my ubit is too old to boot using the new kernel.

I've now followed these instructions:
viewtopic.php?f=53&t=762#p4447

I can now ssh into goflex, and I got this:
$this->bbcode_second_pass_code('', '
root@host-001's password:
/etc/ubit/images:
/etc/ubit/ubimounts:
/etc/ubit/extramounts:

U-Boot ethaddr value is: 02:50:43:48:7f:a9
There was no current cached ethaddr value.
No change has been made
UBIT v0.6 by peaslaker 2010.11-00125-ga21bcca
ubit0-6:~# fw_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
stdin=serial
stdout=serial
stderr=serial
ethaddr=02:50:43:48:7f:a9
preboot=run ubi_start silent_boot; run nc_test nc_start; run usb_start
mtdparts=mtdparts=orion_nand:1M(u-boot),6M(uImage),-(root)
ubit0-6:~#
ubit0-6:~#
ubit0-6:~# mkdir usb
ubit0-6:~# mount /dev/sda1 usb
ubit0-6:~# ls usb
2.6.37-ubit-01715-g1e5cda0 home proc tmp
bin lib root uImage
boot lost+found run uInitrd
dev mnt sbin usr
etc oldboot srv var
goflexhome.sh opt sys
')

What to do next? Can I update uboot/ubit from my current ubit and then continue with the latest.tar.gz usb? Or can I boot to archlinux and then update uboot/ubit from there?

Thanks in advance,

Lauri

[moonman]

Use this tarball instead: http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz

Follow instructions in my signature to reinstall from scratch, but instead wget the tarball I mentioned above. Make sure the drive you were using previously is not connected to GFH at the time you try to boot.

When your system boots up, I would suggest updating uboot right away.
$this->bbcode_second_pass_code('', 'pacman -Sy uboot-goflexhome')
After that you may do a full system update and then install the latest kernel that's available with linux-kirkwood-dt package.

[lauri4n]

Hi again,

And thanks for your advice. I followed your instructions using the alternative tarball, but GFH still didn't boot up properly.

I got frustrated after trying a few different variations, and I decided to try to flash mtd0 directly using nandwrite etc. Well, of course it was a very bad decision, especially without detailed instructions. And now my GFH is a brick (= no lights at all).

So, I went on and ordered a Raspberry Pi and SATA-USB-cable.

Anyway, I appreciate your help and quick responses. Thanks.

[moonman]

Oh boy. You can still recover it with a serial. If you are going to be using RpI as a NAS, you will be disappointed in performance compared to GFH.