GoFlex Home gone AWOL

I have a GoFlex Home unit which I messed about with about a year ago and must have installed a new uBoot. Unfortunately I can no longer access it.

When I switch on with no disk, the green light blinks for a while and then changes to a blinking orange.

When a particula disk is inserted the green light blinks for around 30 secs, then changes to a steady orange for 5 secs and the turns to a steady green

If I use any other disk the results are the same as no disk.

I've also noticed I can ping the device until the green light goes steady.

Unfortunately I get no response when attaching a serial cable.

How do I found out what's going on? I have probably configured nc as part of the boot process, and it would have worked fine at one point, but I can't remember how nc is supposed to work. Is there something I can run to see what the device is waiting for?

> When a particula disk is inserted the green light
> blinks for around 30 secs, then changes to a
> steady orange for 5 secs and the turns to a steady
> green

What is "particular disk"? is that a Debian rootfs? or any other Linux rootfs?

> I've also noticed I can ping the device until the
> green light goes steady.

That's u-boot responding to the ping.

>
> Unfortunately I get no response when attaching a
> serial cable.
>
> How do I found out what's going on?

Your best approach is to get the serial console working. It will solve the problem easily.

Describe your serial console set up: what type of system you're running the serial console server, what program is running (minicom/picocom/putty/screen....), post the command you used to start, how do you connect the wires (did you try swaping TX/RX)? did you try this setup with a different box to see if the serial converter is actually working?.

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

bodhi Wrote:
-------------------------------------------------------
> > When a particula disk is inserted the green
> light
> > blinks for around 30 secs, then changes to a
> > steady orange for 5 secs and the turns to a
> steady
> > green
>
> What is "particular disk"? is that a Debian
> rootfs? or any other Linux rootfs?

It's Arch Linux. I noticed that some work was done around August last year so that if I could find any msgs here from me around that time I might find an example of how I set it up. I believe I tried to use nc to display the uBoot msgs because I couldn't get serial access working.

> > I've also noticed I can ping the device until
> the
> > green light goes steady.
>
> That's u-boot responding to the ping.

If I get nc set up properly on my PC, assuming u-boot uses nc, should I then see the boot proces?

> > Unfortunately I get no response when attaching
> a
> > serial cable.
> >
> > How do I found out what's going on?
>
> Your best approach is to get the serial console
> working. It will solve the problem easily.

Yes, I'm sure it would.

> Describe your serial console set up: what type of
> system you're running the serial console server,
> what program is running
> (minicom/picocom/putty/screen....), post the
> command you used to start, how do you connect the
> wires (did you try swaping TX/RX)? did you try
> this setup with a different box to see if the
> serial converter is actually working?.

I have the serial connector working fine on another GoFlex Home unit, but I just can't achieve any connection with this one. I don't know why that would be, but I may have broken something when trying to hook it up originally.

I can try it again, but don't feel hopeful.

> If I get nc set up properly on my PC, assuming
> u-boot uses nc, should I then see the boot proces?

Yes.

Assuming the IP address of the GF Home (u-boot env ipaddr) is 192.168.0.100, run nc on the Linux PC like this

nc -lup 6666 192.168.0.100 6666

Note that if the PC is Ubuntu, netcat traditional is needed to run nc successfully.

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

I found the post which set up my u-Boot:-

https://forum.doozan.com/read.php?3,48529,49034

So your netconsole was set up properly.

preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ipaddr=192.168.1.22
serverip=192.168.1.43

From another Linux box terminal, make sure that its IP address is 192.168.1.43, and then run netconsole:

nc -lup 6666 192.168.1.22 6666

Power up the GoFlex Home. It should start pinging the 192.168.1.43 box. And when there is a successful return, it will start output the u-boot boot log to the netconsole server on 192.168.1.43.

When you see the count down, interrupt netconsole to see if the input mode is working. And then go ahead executing

boot

See how far you get into the Linux kernel booting process.

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

bodhi Wrote:
-------------------------------------------------------
> So your netconsole was set up properly.

Yes!

>

> preboot_nc=setenv nc_ready 0; for pingstat in 1 2
> 3 4 5; do; sleep 1; if run if_netconsole; then
> setenv nc_ready 1; fi; done; if test $nc_ready -eq
> 1; then run start_netconsole; fi
> preboot=run preboot_nc
> ipaddr=192.168.1.22
> serverip=192.168.1.43
>

ethaddr=00:10:75:2e:ae:0f
if_netconsole=ping $serverip
ipaddr=192.168.1.22

nc_ready=1
ncip=192.168.1.43

preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_net
console; fi

serverip=192.168.1.43
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc

> From another Linux box terminal, make sure that
> its IP address is 192.168.1.43, and then run
> netconsole:
>
>

> nc -lup 6666 192.168.1.22 6666
>

>
> Power up the GoFlex Home. It should start pinging
> the 192.168.1.43 box. And when there is a
> successful return, it will start output the u-boot
> boot log to the netconsole server on
> 192.168.1.43.
>
> When you see the count down, interrupt netconsole
> to see if the input mode is working. And then go
> ahead executing
>
>

> boot
>

> See how far you get into the Linux kernel booting
> process.

It looks as though the system expects to boot from USB and I can't find the required files. Would I be able to create a stick from which to boot?

My intension is to install OpenWrt on this device so it will boot independently of any media present. Will I be able to do that now or should I create a bootable USB stick first?

> My intension is to install OpenWrt on this device
> so it will boot independently of any media
> present. Will I be able to do that now or should I
> create a bootable USB stick first?

Run netconsole again, interrupt the countdown and execute:

printenv
mtdpars

Please post the entire netconsole log here.

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

bodhi Wrote:
-------------------------------------------------------
> > My intension is to install OpenWrt on this
> device
> > so it will boot independently of any media
> > present. Will I be able to do that now or should
> I
> > create a bootable USB stick first?
>
> Run netconsole again, interrupt the countdown and
> execute:
>
>

> printenv
> mtdpars
>

>
> Please post the entire netconsole log here.

I've attempted to re-create the USB stick based on Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 but without a /boot/uEnv.txt

Here is the boot log:-

root@MultiBoot:/mnt/projects/gfh/gfh/gfh-2 # nc -up 6666 192.168.1.22 6666


U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 10 ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ... 0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: WDC WD3200AAJS-00L7A0  Firm: 01.03E01 Ser#:  WD-WMAV2HZ97868
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Unknown command 'mmc' - try 'help'

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

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            4135936         b6db02a0-01     83

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

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

Part    Start Sector    Num Sectors     UUID            Type
  1     63              39086082        00000000-01     83
  2     39086145        586051200       00000000-02     83
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 723 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3833487 bytes read in 1121 ms (3.3 MiB/s)
loading uInitrd ...
7245696 bytes read in 1292 ms (5.3 MiB/s)
loading DTB /boot/dts/kirkwood-goflexhome.dtb ...
10603 bytes read in 3214 ms (2.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2019-02-16  20:53:13 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3833423 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   

Starting kernel ...

and it stops at this point...

Here is the environment:-

GoFlexHome> printenv
printenv
arcNumber=3338
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-goflexhome.dtb
ethact=egiga0
ethaddr=00:10:75:2e:ae:0f
if_netconsole=ping $serverip
ipaddr=192.168.1.22
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.1.43
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_net
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if t
serverip=192.168.1.43
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  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 $uenv_addr /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_ready_retry=15

Environment size: 3026/131068 bytes
GoFlexHome> mtdparts
mtdparts

device nand0 <orion_nand>, # parts = 4
 #: name                size            offset          mask_flags
 0: u-boot              0x00100000      0x00000000      0
 1: uImage              0x00400000      0x00100000      0
 2: rootfs              0x02000000      0x00500000      0
 3: data                0x0db00000      0x02500000      0

active partition: nand0,2 - (rootfs) 0x02000000 @ 0x00500000

defaults:
mtdids  : none
mtdparts: none
GoFlexHome> ^C

Edited 1 time(s). Last edit at 02/16/2019 03:17PM by balanga.

balanga,

>    Image Name:   Linux-4.12.1-kirkwood-tld-1
>    Created:      2019-02-16  20:53:13 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    3833423 Bytes = 3.7 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
>    Image Name:   initramfs-4.12.1-kirkwood-tld-1
>    Created:      2017-07-24   0:18:23 UTC
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    7245632 Bytes = 6.9 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 01c00000
>    Booting using the fdt blob at 0x1c00000
>    
> 
> Starting kernel ...

So far so good! netconsole does not print any more info after this (you need further setup inside Debian to see more).

At this point, assuming the rootfs was created correctly, the kernel should have mounted the rootfs, and the box should be running and you can ping it from another box:

ping debian.local

Also observe the LED behavior, is it solid green?

If you can ping it, then you can try to login

ssh root@debian.local

Note that this basic rootfs use DHCP by default (192.168.1.22 is only up during u-boot booting), so look for a new IP address assigned by the router at this point. If you see a brand new IP address, then it is probably the GoFlex Home. Try that too

ssh root@192.168.1.xx

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



Edited 1 time(s). Last edit at 02/16/2019 08:35PM by bodhi.

Many thanks bodhi,

You are a genius!

I didn't realise that a new IP address was re-assigned. Everything works just like you said.

root@debian:~# uname -a
Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 armv5tel GNU/Linux
root@debian:~# 

balanga Wrote:
-------------------------------------------------------
> Many thanks bodhi,
>
> You are a genius!
>
> I didn't realise that a new IP address was
> re-assigned. Everything works just like you said.
>
>

> root@debian:~# uname -a
> Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat
> Jul 15 21:40:50 PDT 2017 armv5tel GNU/Linux
> root@debian:~# 
>

Cool! Now you have a running system. You can follow the OpenWRT instruction to flash that system to NAND. As long as you keep the current u-boot envs intact, you can boot back to Debian.

But OpenWrt will installation require you to modify the envs. So you could tweak the final envs so that when you plug in the USB rootfs, it will boot to Debian automatically, and skip OpenWRT.

However, if you don't think you need to fall back to Debian, then no need to tweak envs.

In any case, in Debian, save it for safe keeping:

fw_printenv > /boot/uEnv.Debian.text

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

bodhi Wrote:
-------------------------------------------------------
> balanga Wrote:
> -------------------------------------------------------
> > Many thanks bodhi,
> >
> > You are a genius!
> >
> > I didn't realise that a new IP address was
> > re-assigned. Everything works just like you
> said.
> >
> >

> > root@debian:~# uname -a
> > Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT
> Sat
> > Jul 15 21:40:50 PDT 2017 armv5tel GNU/Linux
> > root@debian:~# 
> >

>
> Cool! Now you have a running system. You can
> follow the OpenWRT instruction to flash that
> system to NAND. As long as you keep the current
> u-boot envs intact, you can boot back to Debian.
>
> But OpenWrt will installation require you to
> modify the envs. So you could tweak the final envs
> so that when you plug in the USB rootfs, it will
> boot to Debian automatically, and skip OpenWRT.
>
> However, if you don't think you need to fall back
> to Debian, then no need to tweak envs.
>
> In any case, in Debian, save it for safe keeping:
>

> fw_printenv > /boot/uEnv.Debian.text
>

This sounds like something i would like to have, ie a system which would boot OpenWrt normally from NAND unless it found a USB stick with a Debian rootfs. Are saying that I could do that if I include a /boot/uEnv.txt on the USB stick with the correct magic words? And this is without needing to update the existing uBoot?

balanga,

> This sounds like something i would like to have,
> ie a system which would boot OpenWrt normally from
> NAND unless it found a USB stick with a Debian
> rootfs. Are saying that I could do that if I
> include a /boot/uEnv.txt on the USB stick with the
> correct magic words?

> And this is without needing
> to update the existing uBoot?

Some envs must be changed to accomodate booting LEDE/OpenWrt. See the Wiki thread for example installing OpenWrt on Pogo E02. It should be very similar to the GoFlex Home.

Quote


Rescue Systems

Rescue System V2 (Original)
MacPlug & SMBPLug
Rescue System Pogo V3
Rescue System V4, using a custom LEDE firmware (BETA)
Rescue System for Pogo E02 using LEDE

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



Edited 1 time(s). Last edit at 02/17/2019 05:17PM by bodhi.