Creating bootable USB for Seagate GoFlex Home

I have a Seagate GoFlex Home. I'd like to leave the internals mostly alone (just because), with that as a starting point.
I'd like to create a bootable USB with the latest supported debian build so that I can run a small fileserver with NFS exported directories.

Simple - right?.... <sigh>

at some point last night.. late.. (remember - never hack hardware after midnight... or feed gremlins... bad things happen....)

I had the system boot the thumbdrive ... once-ish... it had debian lenny,
I had started off with the load "wheezy" script, it failed (some kind of error about firmware too old or somesuch),
then I tried the dockstar squeeze script... it too failed - (same error)
then the lenny script... Success - - - However, I could not find a repo to add to the sources.list file that wouldn't generate errors...
so the system never updated.. I successfully booted several times, so I know that the internal pointers know about a bootable usb.
I then tried to re-run the wheezy script... and that messed up the thumb drive...

so back to square one...

so my main question is (I think) - how can I create the bootable USB on (for instance) my laptop (ubuntu 15.xx) ?
What source repos do I put into the sources.list file for the ARMEL foundation?

one tutorial says download the boot.img file from http://http.us.debian.org/debian/dists/stable/main/ and start from there...
there is no boot.img.gz file in the armel directory.... (or am I missing it?)

I think I have seen a tutorial on this topic - but I can't find it again...

Thoughts? Help? Directions?

Rich

Rich,

So are you running stock software on GF Home? You can take a look at the following threads:

Latest kernel/rootfs:
http://forum.doozan.com/read.php?2,12096

Latest u-boot:
http://forum.doozan.com/read.php?3,12381

And then tell us what is your goal? are you willing to connect serial console to do more hacking? or just want to run the latest Debian kernel on your USB/HDD drive?

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

I was originally inside the box to set up the serial monitor to revive the beastie and reload stock firmware (I think I had 2.71 loaded.. from this site: http://support.goflexhome.hipserv.com/en/reflash/ )

I have a second unit that I'll have to open and unbrick at a later time, when I last tried it would not take the 2.71 file... so I need to check to make sure that my cable isn't tweaked out...

Right now - I need the server set up...

if I need to get the serial line set up to get Debian on it - I will.....
I'm about 3hrs from getting home.... so I'll read up and try the above links at that time...

EDIT:::::
After reading the two articles... it looks like it would be best to reset things back to stock 2.71 just in case and then begin from that point
first doing the update of the uboot .... then replacing rootfs...
HOWEVER - - - what I think I really want would be to leave the internals alone, and create a bootable USB stick and having debian there. if this is my goal.... what changes do I need to make to the Uboot and/or rootfs ?

Rich



Edited 1 time(s). Last edit at 10/22/2015 04:59PM by rmleonard.

Rich,

> HOWEVER - - - what I think I really want would be
> to leave the internals alone, and create a
> bootable USB stick and having debian there. if
> this is my goal.... what changes do I need to make
> to the Uboot and/or rootfs ?

The Debian rootfs on USB can be booted with stock u-boot. But the stock u-boot envs will need to change so that it will boot USB first, and then if it fails, will boot stock OS from NAND. This can be done inside stock OS using blparam command.

So the bottom line is it must be modified a little in the envs area.

Another option is to install newer u-boot, and then adjust the new u-boot envs to boot USB, and then stock OS if USB fails.

What I would recommend is to back up your NAND mtds first before doing anything. So that you can restore them and go back to stock if you want to. And then install new u-boot and rootfs. Once you starts using a latest Linux kernel, you might never want to go back to stock.

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

attached is the boot sequence followed by "printenv"

this is my "backup" goflex home... it was given to me by a buddy - he believes he bricked it.. but can't remember what he was doing at the time...

I'd like to note several things...
if the env var for the ethernet address is what the machine thinks the ethernet address is...
there is something VERY wrong...
on the bottom of the box is says:
MAC:0010752B5F90

the env var:
ethaddr=00:50:43:00:02:02

some of the other values look 'odd'...

so - for this unit.... what should my next step be?
I tried http://cyanlabs.net/Thread-Seagate-GoFlex-Home-recovery-via-serial
twice - - - - both times the boot fails...
(the resulting boot is what is in the attached file)

I have no USB or Drive attached... this is the bare bones boxen...

is there a "special reset" for the ENV variables?
something that will either properly zero them out or initialize them to factory settings?

I'll crack open my other unit (this one should be fine as far as its internals go..) and reset it to factory tomorrow...

more to follow

rmleonard,

Yes, it was messed up!

1. You could either reset to factory first, and then follow the 2 links I posted above to create rootfs and install new u-boot:
http://forum.doozan.com/read.php?2,24172,24177#msg-24177

2. If you can't reset to factory then, connect serial console, boot up and interrupt it. List the available commands and post here:

help

3. The GF Home is almost impossible to brick. The worst case is you will be able boot with UART using serial console. See the instruction in the u-boot thread

Latest u-boot: 
http://forum.doozan.com/read.php?3,12381

about how we should always try booting with UART before flashing new u-boot.

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

Confusion:
Your step 1 above - refers to this thread?!

Steps 2-3: reloading / loading uboot..

If I only have access to system via the serial port..
I think (I could be wrong).. tftpboot is the only way to get data into the GFH...

And for that I think i need more info ...

the 'Fw_....' commands are part of something in the upgrade, not in the stock system correct?

I feel like I'm missing a step..

rmleonard,

> I feel like I'm missing a step..

Please try these first:

- Reset to factory, if not successful then
- Connect serial console

Then we'll go from there.

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

okay - I have the first unit re-flashed back to factory settings.. it is ready to be "fixed" properly....

the unit that I thought would be easier and whatnot.. the unit that had been running, and all that... just threw me for a loop... it is the same size/shape/color/smell as the other... BUT... upon boot it says it is a GoFlexNET not home... and the whole boot start sequence is different.... the bottom plate says GoFlexHome....

see attached file:
I booted it then "pressed the any key" to abort the autoboot.. (which loops - see second file)
the first file - after the abort - i did a printenv....

The second log file shows a full boot sequence up to the self-reset it does

I tried getting it to boot off of the same thumb drive that I used to reset the other unit...
the sequence of events is as follows....
with power off: press/hold reset button... power on
hold reset button until WHITE led flashes - - - it never does.. and the boot log never shows any indication that the reset button is being pressed...

so....
I tried the re-flash trick described on this page:
http://cyanlabs.net/Thread-Seagate-GoFlex-Home-recovery-via-serial

even though I can (from the laptop) ping the GoFlex..
the GoFlex cannot ping the laptop... (not worried at the moment.. that could mean just about anything)
BUT - the tftpboot never finds the server (PUMPKIN running on winders..) - the other unit fired up immediately..
(gateway? maybe?)

so - I have 1 GoFlex ready for "Step 2" (updating the uBoot? IIRC), and am wondering what to do with Unit 2

Thoughts?

Rich
(had migraine earlier, took meds, can't sleep.. its 4:30AM)

rmleonard,

> okay - I have the first unit re-flashed back to
> factory settings.. it is ready to be "fixed"
> properly....

Do this:

- Create the Debian 3.16 rootfs
- Log in to the stock OS and mount the new rootfs
- Install new u-boot

> > boot it says it is a GoFlexNET not home... and the
> whole boot start sequence is different.... the
> bottom plate says GoFlexHome....

It is a GoFex Home, running GoFlex Net u-boot, which is compatible and can be used on both boxes.

> so....
> I tried the re-flash trick described on this
> page:
> http://cyanlabs.net/Thread-Seagate-GoFlex-Home-rec
> overy-via-serial

Bad move. You've found this site, so you don't need to follow other procedure. Doing that only makes it more difficult for me to help you :) Note that I did not mean to say the link provided bad info, just that when you trying various things you tend to make it worse.

> and am wondering what to do with
> Unit 2

Use another USB stick, create the Debian 3.16 rootfs like for the 1st unit. And try booting with it. No need to change anything yet, because the installed u-boot is an execellent older version from davygravy.

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

Follow-on -- - -
BAD weekend with flu bug.. ick!

I have one GoFlex reflashed back to Factory base load, and then I have replaced its internal Factory SSHD with an updated version that allows more "proper" root access.

The second unit - it just won't hunt.. nothing seems to be able to get it to boot the USB with the factory 2.7.1 firmware.
I have both semi-dismembered and a serial console ready to go...
I've been unable to get a netconsole working... (this might be my shortcomings - not the GoFlex's)

the hardware is different
Unit 1 (The one that won't load ) - shows an internal sticker w/ 2.0.010 JAA
Unit 2 (Factory freshed) Shows same sticker with 2.0.012 JAA on it..
Both appear to be REV.01 boards, Unit 1 has a connector riser for the JTAG, Unit 2 just has holes in the board. different vendors on the Caps and some of the chips.. The Unit 1 has a LARGEish #1 just above the 2 LEDs, same spot on Unit 2 has a squarish #3

More Follow-on::::
Following the 2014.07 U-Boot instructions - - I almost got it...
but it's late and I am not sure where I farkled it up...

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home

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
Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Unknown command 'mmc' - try 'help'

Reset IDE: ide_preinit failed

no USB devices available
Unknown command 'mmc' - try 'help'

no IDE devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'mmc' - try 'help'
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

at that point it loops ...
this is a GoFlexHome -
I am guessing that I somehow forgot to finish the boot image on the internals... (but Shouldn't they have been unchanged from the factory settings?)

and here are the current environment settings
(which don't seem to be what I remember saving via the fw_setenv commands before the reboot)

GoFlexHome> printenv
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2827/131068 bytes

so I am guessing that if I knew what to key in - it might work...

help?

rmleonard,

> (Re)start USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 1 USB Device(s)
> found
> scanning usb for storage devices... 0
> Storage Device(s) found

You need to plug in the USB rootfs to boot into Debian.

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

More Info::::
okay - I prepared the external USB drive - - -
I have the USB thumb drive formatted as a single EXT3 partition
(I would have preferred adding swap, but if I get it working I can do that later)

I set the Label to "rootfs" (all lower case"
I set the flag to boot

as root (not using the SUDO command)
I ran - - - -
cd /media/rml/mnt-point/
(I am now at the root of the thumb drive)
tar -xvf /home/rml/Downloads/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar .
this put all of the files at the root of the thumb drive

I created a /boot/uEnv.txt file. - - - - - this file is on the thumb drive in /boot

mmc_root=LABEL=mmcrootfs
sata_root=LABEL=satarootfs
usb_root=LABEL=usbrootfs
load_dtb=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb

then I booted the beastie...

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home

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
Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'mmc' - try 'help'

Reset IDE: ide_preinit failed

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	30279680  	00087895-01	83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'mmc' - try 'help'

no IDE devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2865664 bytes read in 429 ms (6.4 MiB/s)
6535284 bytes read in 615 ms (10.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2015-02-08   9:02:01 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2865600 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


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


Available machine support:


ID (hex)	NAME

ffffffff	Generic DT based system

ffffffff	Marvell Kirkwood (Flattened Device Tree)


Please check your kernel config and/or bootloader.

then 'poot' - - - nothing

so it looks like the uEnv.txt file needs to be on the internal /boot ?

how can I boot to the internal (it just loops) get a prompt and then tinker/edit the "missing" files?

Look at this post above, and other posts following that:

http://forum.doozan.com/read.php?2,24172,24207#msg-24207

Quote

Do this:

- Create the Debian 3.16 rootfs
- Log in to the stock OS and mount the new rootfs
- Install new u-boot

The default envs boot with 3.16 rootfs, unchanged. To boot with 3.18.5 rootfs, you need to perform step 4b. That's why I recommend the 3.16 rootfs.

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

AwesomeSauce - - - We have Life!

arcNumber=2097
machid=0x831
ethaddr=b6:d0:5e:0f:a1:17
ipaddr=192.168.0.231
serverip=192.168.0.220
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi

I tried to use fw_setenv to change the ethaddr to the address on the bottom of the unit....
it doesn't let me...
is there a way to boot in some kind of "safe mode" where I have an OS and can reset these things?
if I create a /boot/uEnv.txt on the USB stick and add ethaddr to that.... will that work?

But - I have Control of the Boxen - - - WhaaHoo!!
apt-get update/upgrade worked....

The Second Unit - - -
(the one that the boot up shows GoFlex Net instead of GoFlex home....)
I created a second USB identically to the first - using Debian 3.16 (like the first)
it still DOES NOT boot...
and I broke a wire on my usb serial cable - - I'll rewire that tomorrow morning, and try to get the boot environment again...

Thank You Bodhi!

rmleonard,

> if I create a /boot/uEnv.txt on the USB stick and
> add ethaddr to that.... will that work?

It should work in the uEnv.txt.

>
> But - I have Control of the Boxen - - - WhaaHoo!!
> apt-get update/upgrade worked....
>

Cool!

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

AWESOME Sauce II !!!!!


On the second unit....
I could NOT get it to boot from any USB Stick...
I read somewhere that the USB stick had to be partitioned as MBR, and on top of that put the EXT3 or EXT2 formatted block...

and what do you know... it worked!!!!

and I got the netconsole working too....!!

TA DA!!!!!

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
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
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2756040 bytes read in 431 ms (6.1 MiB/s)
6032465 bytes read in 587 ms (9.8 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2755976 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:48 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6032401 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

Drat and Fnark!
boot order demons turn the Awesome Sauce to muck!

When I snapped the 2GB HD into the port and hooked it all up to boot....
it stopped at "starting kernel ..."

so I am guessing that I need to change something on the boot command something or another...

More Reading!!!

Any thoughts on this one?
it is definitely loading the uImage and whatnot... and getting stuck on the ramfs stuff....
here is the whole of the boot sequence:

(the good parts are around 18.60 - - - where it defines the hard drive as sdaXX and the USB Stick as sdbXX - - )

so I'll go digging in the USB stuff to see about making it respond to sdb .... or seeing if there is a boot order that I can affect to make sure that the SATA stuff goes second, making it sdb and leaving the USB stuff as sda...

More as I find it....

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home

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
host 192.168.1.53 is alive
Using egiga0 device
host 192.168.1.53 is alive
Using egiga0 device
host 192.168.1.53 is alive
Using egiga0 device
host 192.168.1.53 is alive
Using egiga0 device
host 192.168.1.53 is alive
Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate GoFlex Home
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 115744K/131072K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 15328K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07248b0   (7283 kB)
[    0.000000]       .init : 0xc0725000 - 0xc0765444   ( 258 kB)
[    0.000000]       .data : 0xc0766000 - 0xc07c975c   ( 398 kB)
[    0.000000]        .bss : 0xc07c975c - 0xc08144dc   ( 300 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000011] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[   14.806946] Console: colour dummy device 80x30
[   14.806975] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   14.896732] pid_max: default: 32768 minimum: 301
[   14.896850] Security Framework initialized
[   14.896919] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   14.896937] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   14.897814] Initializing cgroup subsys devices
[   14.897875] Initializing cgroup subsys freezer
[   14.897905] Initializing cgroup subsys net_cls
[   14.897952] Initializing cgroup subsys blkio
[   14.898049] CPU: Testing write buffer coherency: ok
[   14.898519] Setting up static identity map for 0x5273f0 - 0x527448
[   14.900891] devtmpfs: initialized
[   14.904869] prandom: seed boundary self test passed
[   14.908934] prandom: 100 self tests passed
[   14.908965] pinctrl core: initialized pinctrl subsystem
[   14.909478] regulator-dummy: no parameters
[   14.909943] NET: Registered protocol family 16
[   14.910399] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   14.911649] cpuidle: using governor ladder
[   14.911676] cpuidle: using governor menu
[   14.911816] Kirkwood: MV88F6281-A1, TCLK=200000000.
[   14.911840] Feroceon L2: Enabling L2
[   14.911880] Feroceon L2: Cache support initialised.
[   14.948257] vgaarb: loaded
[   14.948615] usbcore: registered new interface driver usbfs
[   14.948692] usbcore: registered new interface driver hub
[   14.948816] usbcore: registered new device driver usb
[   14.949812] Switched to clocksource orion_clocksource
[   14.988589] NET: Registered protocol family 2
[   14.989577] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[   14.989603] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[   14.989622] TCP: Hash tables configured (established 1024 bind 1024)
[   14.989694] TCP: reno registered
[   14.989708] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   14.989730] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   14.989994] NET: Registered protocol family 1
[   14.990333] RPC: Registered named UNIX socket transport module.
[   14.990344] RPC: Registered udp transport module.
[   14.990352] RPC: Registered tcp transport module.
[   14.990359] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   14.990667] Unpacking initramfs...
[   15.493014] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[   15.493154] NetWinder Floating Point Emulator V0.97 (double precision)
[   15.494315] futex hash table entries: 256 (order: -1, 3072 bytes)
[   15.494384] audit: initializing netlink subsys (disabled)
[   15.494440] audit: type=2000 audit(0.680:1): initialized
[   15.495262] zbud: loaded
[   15.495539] VFS: Disk quotas dquot_6.5.2
[   15.495592] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   15.496158] NFS: Registering the id_resolver key type
[   15.496217] Key type id_resolver registered
[   15.496227] Key type id_legacy registered
[   15.496253] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   15.496268] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   15.496437] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   15.496750] msgmni has been set to 237
[   15.496904] Key type big_key registered
[   15.499260] alg: No test for stdrng (krng)
[   15.499377] bounce: pool size: 64 pages
[   15.499443] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   15.499463] io scheduler noop registered
[   15.499477] io scheduler deadline registered
[   15.499645] io scheduler cfq registered (default)
[   15.500157] mv_xor mv_xor.0: Marvell shared XOR driver
[   15.539891] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   15.579879] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   15.580054] mv_xor mv_xor.1: Marvell shared XOR driver
[   15.619877] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   15.659876] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   15.660312] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   15.661315] console [ttyS0] disabled
[   15.681415] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[   16.228760] console [ttyS0] enabled
[   16.233691] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[   16.240103] nand: Micron MT29F2G08AAD
[   16.243780] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[   16.249474] Scanning device for bad blocks
[   16.472289] 4 cmdlinepart partitions found on MTD device orion_nand
[   16.478583] Creating 4 MTD partitions on "orion_nand":
[   16.483768] 0x000000000000-0x000000100000 : "u-boot"
[   16.489150] 0x000000100000-0x000000500000 : "uImage"
[   16.494531] 0x000000500000-0x000002500000 : "rootfs"
[   16.499915] 0x000002500000-0x000010000000 : "data"
[   16.506043] libphy: Fixed MDIO Bus: probed
[   16.522757] libphy: orion_mdio_bus: probed
[   16.526988] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   17.610961] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:28:59:e4
[   17.619955] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   17.626514] ehci-pci: EHCI PCI platform driver
[   17.631061] ehci-orion: EHCI orion driver
[   17.635167] orion-ehci orion-ehci.0: EHCI Host Controller
[   17.640639] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   17.648366] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   17.669848] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   17.675986] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   17.682831] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   17.690106] usb usb1: Product: EHCI Host Controller
[   17.695008] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[   17.701754] usb usb1: SerialNumber: orion-ehci.0
[   17.707139] hub 1-0:1.0: USB hub found
[   17.710992] hub 1-0:1.0: 1 port detected
[   17.715812] mousedev: PS/2 mouse device common for all mice
[   17.721962] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[   17.727973] i2c /dev entries driver
[   17.732477] hidraw: raw HID events driver (C) Jiri Kosina
[   17.738237] drop_monitor: Initializing network drop monitor service
[   17.744813] TCP: cubic registered
[   17.748154] NET: Registered protocol family 17
[   17.752799] Key type dns_resolver registered
[   17.757821] registered taskstats version 1
[   17.762966] rtc-mv rtc-mv: setting system clock to 2015-11-02 02:33:57 UTC (1446431637)
[   17.772973] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[   17.850798] udevd[55]: starting version 175
[   18.007365] SCSI subsystem initialized
[   18.029985] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   18.091932] sata_mv sata_mv.0: cannot get optional clkdev
[   18.097453] sata_mv sata_mv.0: slots 32 ports 1
[   18.149977] scsi0 : sata_mv
[   18.153158] ata1: SATA max UDMA/133 irq 21
[   18.204261] usb 1-1: New USB device found, idVendor=18a5, idProduct=0300
[   18.211026] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   18.218213] usb 1-1: Product: STORE N GO
[   18.222175] usb 1-1: Manufacturer: Verbatim
[   18.226378] usb 1-1: SerialNumber: C70055FB1C5C9655
[   18.249569] usb-storage 1-1:1.0: USB Mass Storage device detected
[   18.256127] scsi1 : usb-storage 1-1:1.0
[   18.261835] usbcore: registered new interface driver usb-storage
[   18.271082] usbcore: registered new interface driver uas
[   18.659864] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   18.699887] ata1.00: ATA-8: ST2000DL003-9VT166, CC98, max UDMA/133
[   18.706101] ata1.00: 3907029168 sectors, multi 0: LBA48 
[   18.769889] ata1.00: configured for UDMA/133
[   18.790221] scsi 0:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC98 PQ: 0 ANSI: 5
[   18.833357] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[   18.842285] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   18.847849] sd 0:0:0:0: [sda] Write Protect is off
[   18.853015] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   18.879968]  sda: sda1
[   18.884092] sd 0:0:0:0: [sda] Attached SCSI disk
[   18.900317] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   19.262109] scsi 1:0:0:0: Direct-Access     Verbatim STORE N GO       5.00 PQ: 0 ANSI: 6
[   19.281003] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   19.286559] sd 1:0:0:0: [sdb] 3782639 512-byte logical blocks: (1.93 GB/1.80 GiB)
[   19.302442] sd 1:0:0:0: [sdb] Write Protect is off
[   19.309047] sd 1:0:0:0: [sdb] No Caching mode page found
[   19.314461] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[   19.337901]  sdb: sdb1
[   19.353822] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/sda1 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[   29.349125] uhci_hcd: USB Universal Host Controller Interface driver
[   29.363402] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   29.378237] usbcore: registered new interface driver usbhid
[   29.383971] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

rmleonard,

See this:
http://forum.doozan.com/read.php?3,19093

And this:
http://forum.doozan.com/read.php?3,24212

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

I hope to get a few hours of concentrated hacking time this weekend (my honeydoo list is mostly up to date, and neither of the kids has said they need to be anywhere, so - - - My Time!)

I did the install of the environment img from work - ssh'ing in - - and it didn't come back up...
thinking about it...
The ETHADDR was reset, and unchangeable - so it may not have gotten a DHCP --
I used fixed leases almost across the board - keeps the kids from bringing up "new toys" without letting dad know first....
and keeps the neighbor from readily using my connection - - - I have a neighbor who keeps "trying" to get into my connection....
so far - - my 'net foo' is better than his....

as I scroll through the notes on http://forum.doozan.com/read.php?3,24212 - it looks like I just need to make sure that
ETHADDR, MACHID, ARCNUMBER, MTDPARTS, ROOTFSTYPE, and probably IPADDR, SERVERIP

I should be able to set those from the "paused/interupt" prompt...

thoughts?
is that about where things are?

When I am done - - - I'll write up a step/by/step summary type - how to....

and now - - - - off to start a new thread.... (I had an idea)

Awesome Sauce!!!
To the Max!

THANK YOU to everyone who pitched in their 2cents
(and those who tossed in a few dollars worth too)

Thank You Bodhi!!!!!
(you were very patient with me.... thank you very much!)


Both Seagate GoFlex Home boxen are up and running!!!!

a few follow on questions...

On the Seagate site - the 2.7.1 firmware archive contains a file :
hipserv2-seagateplug-2012-0508.ubi

how is this different/the same as - a *.kwb file as used here?

when the GoFlexHome boxen are configured with the factory firmware.. paperclipping the little reset button causes a unique reaction on boot, namely - going into a reset mode and loading from the USB stick, reloading firmware, using the white LED, etc....

at the moment, running things with the 3.16 firmware - holding in the reset button - does nothing...
how would one go about creating a baseline 3.16 or later "oh drats - blew it up again USB stick" that would reload the boxen to "this" firmware rather than "that" one? (with all of the environment variables and all that....)

with the resource limitations of the boxen hardware - is it practical/worthwile to update to Debian Jessie?


[ducking head]
[girding loins w/ lead and asbestos]
[prepping for possible flameage]

anyone thought of running ISCSI targets with these things?
(and then maybe a Raspberry Pi as the initiator and loading something like open media vault )

I have open media vault running on one of the boxen already (just to play)
the hard drive is 4TG and is running fine... (someone told me 3 was the limit... but it formatted out just fine.. ... ... well, to 3.6TB, but at that point - it may be a rounding error)



...[[[ topic shift ]]]...

I have a Seagate Central - I have root access to it...
any way of getting more control over it?
it has a version of opkg on it, but I've tried several attempts to add more/different sources to it's sources file and get nowhere...
it would be nice to add 'screen' and maybe a full os to it...
here is its printenv and uname -a

bootdelay=2
baudrate=38400
ethaddr=00:11:22:4F:54:54
ipaddr=192.168.1.2
serverip=192.168.1.100
port=0
netboot_cmd=tftp 0x4000000 bootpImage; go 0x4000000
boardtest_state_memory=none
cpu_clock=700
netmask=255.255.0.0
bootfile="/tftpboot/uImage"
tftp_bsize=512
udp_frag_size=512
whitney_state=saved
serialNo=NA6SAARB
ethaddr0=00:10:75:40:95:F2
bootargs=console=ttyS0,38400 mem=256M root=/dev/sda3 rw
mfgtest_state=final_tested_ok
bootcmd=scsi init;ext2load scsi 0:1 0x4000000 uImage;bootm
netboot=0
mfgmodel=Seagate Central
model_name=cirrus_v1
current_kernel=kernel2
rtclog=522d077b
stdin=serial
stdout=serial
stderr=serial
verify=n
num_boot_tries=0



uname -a
Linux NAS-T1 2.6.35.13-cavm1.whitney-econa.whitney-econa #1 Wed Sep 16 15:47:59 PDT 2015 armv6l GNU/Linux

I read somewhere that the CPU on this boxen has 2 cores, but one is disabled via software...
is that updateable/upgradeable?

is the Seagate Central the same unit as the Seagate Business Storage NAS ?


Again - - - Thank All of you for helping out!

rmleonard,

> On the Seagate site - the 2.7.1 firmware archive
> contains a file :
> hipserv2-seagateplug-2012-0508.ubi
>
> how is this different/the same as - a *.kwb file
> as used here?

That ubi looks like what was flashed to the stock rootfs in NAND. UBIFS is the format ususally used for NAND rootfs. The kwb is the format of Kirkwood u-boot NAND image. So they are not related in any way.

>
> when the GoFlexHome boxen are configured with the
> factory firmware.. paperclipping the little reset
> button causes a unique reaction on boot, namely -
> going into a reset mode and loading from the USB
> stick, reloading firmware, using the white LED,
> etc....
>
> at the moment, running things with the 3.16
> firmware - holding in the reset button - does
> nothing...

It is normal. The reset button is specially programed by Seagate so that you could reflash stock FW in NAND. When you run with a modern kernel such as our Linux 3.16 here, the reset button does nothing, until you explicitly program it. Usually done with tool such as esekeyd to respond to the button with a script, which can do anything you want it to do when the reset button is pressed. My customized patch for kernel 3.6 and later already enabled the button, you just need to install a tool such as esekeyd:

- See esekeyd man page.
- Or see davidedg esekeyd setup.

> with the resource limitations of the boxen
> hardware - is it practical/worthwile to update to
> Debian Jessie?

Yes

> anyone thought of running ISCSI targets with these
> things?

Yes it is possible, and also desirable, if you have a usage for it.

And BTW,

Quote

[prepping for possible flameage]

No worry, flaming is not allowed in this forum :))

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



Edited 2 time(s). Last edit at 11/16/2015 03:31AM by bodhi.