Short Report about GoFlex Home

Hi!

Here I want to write down a short report about debian incl. rescue system on GoFlex Home.

I took my brandnew GoFlex Home and connected it like this howto.

Second step is to install Jeff's UBoot with the --no-uboot-check switch.
When you where asked you have to select GoFlexNet.

The next step is to install debian squeeze like here. You only need the second step and Reboot.

Then install a new kernel with GoFlex support, look here.

Now you have to change the arcnumber: setenv arcNumber 3089
From this point your GoFlex Home is able to boot from Sata.

Then it's a good idea to install the rescue system.
How this works you can find here.

I want to say Thanx to all the guy's, that i linked here. Because they made it possible to run debian with booting from sata and also have a working rescue system!!!

My Idea to write this here down is only to have all in one post....

cya
major

Great initiative. Change the GoFlex kernel link to http://dev.shyd.de/2012/01/kernel-3-1-10-ready-to-use/

Mr M: How about GoFlex & Others Kernel 3.3.2 here : http://forum.doozan.com/read.php?2,7676

It is newer and has the fix for the NAND problem that many people saw while booted in Linux.

=====================================================

• davy's Github Repo's rescue-dg

Hi,

I have new Goflex Home with original OS (version 2.7.1-391). I want to install Debian. Should i follow installation directions from first post, or use this link http://projects.doozan.com/debian/ for Debian installation instruction?

Thank You.

Hi!

I tried it that way its shown in Post one with GoFlexHome.
All went fine, till Debian reboot. I recieve EHCI Timeouts:

** Unable to read "/rescueme.txt" from usb 0:1 **
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
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
EHCI timed out on TD - token=0x800d8d80
EHCI timed out on TD - token=0x800d8d80
EHCI timed out on TD - token=0x800d8d80
 ** ext2fs_devread read error - block
** Unable to read "/boot/uImage" from usb 0:1 **
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
EHCI timed out on TD - token=0x800d8d80
EHCI timed out on TD - token=0x800d8d80
EHCI timed out on TD - token=0x800d8d80
 ** ext2fs_devread read error - block
** Unable to read "/boot/uInitrd" from usb 0:1 **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435344 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

I tried it two times. With serial/tftp i can restore to stock uboot androotfs etc.
For 2 Times i startet over, same result. Help is verry welcome!

derdigge

This Issue was caused by that usbstick.
Ther fourth one i have tried worked!
Its a no name - total cheap ;)

But now i ran into the next :

## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435344 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4529842 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x00000c11).

This in first order means That the steps dont work as shown here out of the box.
So if you havent a ttl / serial do not do this ;)

Is there a way to fix my issue? I think i have to install a new Kernel.
But how can i do so from serial? Pls someone help me out!

derdigge

Hi,

it looks like you forgot to set the right arcNumber in your uBoot environment. Boot the GFH with the rescue system and say

fw_setenv arcNumber 3338

Try again then.

Cheers,

chessplayer

---
Standart ist der Standardfehler

lighning fast reply, Thank you!

Thats not the case:

GoFlexNet> printenv
arcNumber=3338

But maybe my machine was identified wrong by that mtd0 installer script?

The uboot promts me with GoFlexNet but i am on GoFlexHome
What will be the right uboot for me then? i will flash it with tftp.

archnumber 2097 worked ;)

Hi,

all I can tell you is that I used Jeff's standard uBoot install. In addition, I installed the updated rescue system and then made modifications to allow booting from HDD.

For me, this worked for for both the GoFlex Net (which will become my VDR) and the GoFlex Home 3TB (which is my NAS and will be used for backup as well) and also the Dockstar.

---
Standart ist der Standardfehler

So, in fact, you have a SheevaPlug ;-))

---
Standart ist der Standardfehler



Edited 1 time(s). Last edit at 01/22/2013 11:44AM by chessplayer.

hehe theese Device are meaning so much fun ;)

vdr is also my plan ;))
i will stay on booting fom usb so i can carry the Harddisk arround then.

But this really is an GoFlex Home.

derdigge Wrote:
-------------------------------------------------------
> hehe theese Device are meaning so much fun ;)
>
> vdr is also my plan ;))
> i will stay on booting fom usb so i can carry the
> Harddisk arround then.
>
> But this really is an GoFlex Home.

We are getting off topic. If you want to discuss the VDR-Option further (mine has been up and running on the Dockstar for one and a half years now ...), send a PM (since I cannot send you one ...)

---
Standart ist der Standardfehler