Goflex Home - Installed uBoot and Debian but now stuck

Hello and huge thanks for all your work.

I have an old GoFlex Home that was hacked and I decided to install alternative fw which eventually led me to this forum.

I followed the two main tutorials:

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

and

https://forum.doozan.com/read.php?2,12096 (followed the instructions under 25 Aug 2019 as indicated)

Initially, all went relatively well, netconsole was working and I was able to ssh to the new debian installation!
My old HDD could not be mount though. netconsole reported:

Failed to mount ext2 filesystem...
** Unrecognized filesystem type **

So I started researching what I could do.

In the meantime I decided to do:

sudo apt-get upgrade

During that I got:

update-initramfs: Generating /boot/initrd.img-5.2.9-kirkwood-tld-1

So I issued:

cd /boot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.2.9-kirkwood-tld-1 -d initrd.img-5.2.9-kirkwood-tld-1 uInitrd

on another terminal which I already had open (and without yet rebooting), I also tried installing testdisk to try and figure out what was wrong with the HDD.
I again got:

update-initramfs: Generating /boot/initrd.img-5.2.9-kirkwood-tld-1

So I figured I would again need to regenerate the uInitrd boot file::

cd /boot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.2.9-kirkwood-tld-1 -d initrd.img-5.2.9-kirkwood-tld-1 uInitrd

then I rebooted... The usb stick was somehow corrupt(?) and on netconsole I saw that the usb could not be recognised.
I took the usb stick to another linux machine and there it couldn't be mounted and fdisk was reporting a readonly fs and 1TB space!

Anyway then I got a fresh usb stick and followed the 25 Aug 2019 instructions of https://forum.doozan.com/read.php?2,12096
Now on netconsole I see:

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:  0
Initializing devices...
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: ST3000DM001-9YN166 Firm: CC9F Ser#: S1F13FQH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
Unknown command 'mmc' - try 'help'
Loading envs from usb 0...
** File not found /boot/uEnv.txt **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** Bad device mmc 0 **
Loading envs from mmc 1...
** Bad device mmc 1 **
Loading envs from mmc 2...
** Bad device mmc 2 **
Loading envs from mmc 3...
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
loading 1 bytes read in 723 ms (0 Bytes/s)
Found bootable drive on usb 0
uImage ...
4973929 bytes read in 1013 ms (4.7 MiB/s)
loading uInitrd ...
9713936 bytes read in 930 ms (10 MiB/s)
loading DTB /boot/dts/kirkwood-goflexhome.dtb ...
10249 bytes read in 3260 ms (2.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-11-21  15:02:53 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973865 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
Starting kernel ...

But the goflex does not answer to ping or to ssh.

Here is my printenv from netconsole:

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_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
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:B0:52
if_netconsole=ping $serverip
ipaddr=192.168.2.243
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.2.116
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_netconsole; fi
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 test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.2.116
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=echo Initializing 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 $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
usb_ready_retry=15

Environment size: 3039/131068 bytes

Sorry for the long post but I thought it would help to report all the details to help you guys help me :)

ador,

The kernel has booted, but with netconsole, the output stops after this:

> Starting kernel ...

So there is no way to tell if it has completed booting in to Debian (i.e. mounted rootfs).

> But the goflex does not answer to ping or to ssh.

Wait for a while and see if you can find a new IP address in the network (in your router). For use IOS Fing, or Linux nmap to find it.

Another option is

ping debian.local

=====

If you still cannot find the GF Home in the network, and without serial console, the best next step is to revisit how you created the rootfs. You can recreate it again and post the session here.

One thing to pay attention to is with the new 2017.07 u-boot, you must skip Step 4 in the rootfs creation:

Quote


4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Do not do this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-5.2.9-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.2.9-kirkwood-tld-1 -d zImage.fdt uImage
sync

If your Linux box does not have mkimage, then install it

apt-get install u-boot-tools

So if Step 4 was done, then now you need to reverse it:

cp -a uImage.orig uImage

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

Hello bodhi, thank you for taking the time to reply.

I just now tried booting without the HDD on the board and I was able to ssh to debian...
So it seems that the failure to mount the HDD was preventing the proper boot to debian... ?
Does that make sense?

So now on to my next problem, which is why does the hdd appear as "Unrecognized filesystem type"?

printenv reports:

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: ST3000DM001-9YN166 Firm: CC9F Ser#: S1F13FQH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 2861588.4 MB = 2794.5 GB (5860533168 x 512)
Unknown command 'mmc' - try 'help'

and then:

Loading envs from ide 0...
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **

Is there any way to mount this drive on the newly updated goflexhome?
Should I take it on another pc and try to see if it is detected/mounted?

ador,


> Failed to mount ext2 filesystem...
> ** Unrecognized filesystem type **

> Is there any way to mount this drive on the newly
> updated goflexhome?
> Should I take it on another pc and try to see if
> it is detected/mounted?

Since you can boot with USB rootfs, you can fix this in the GF Homew after the system has booted and is running. You can plug it into the slot (but do this at your own risk, I did this many times before, but YMMV). The safest approach of course is mounting the HDD on this box using USB-HDD connector.

If you plug in the HDD on the GF Home. List the mount points and list storage devices and see which drive letter the HDD was assigned to

mount
fdisk -l

You have 1 USB rootfs and 1 HDD, but insert the HDD later so most likely root is /dev/sda1 and the HDD is /dev/sdb1.

Now you can mount it, or running e2fsck to check for errors. Or repartition it. Remember to assign a label to the HDD partition (good practice).

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

It took a while before I go a chance to work on the goflex...

I am at a loss. Except that one time where I was able to boot into debian without the HDD on, I have not been able to ssh.
After the "Starting kernel ..." the goflex stops responding to ping, the LED turns orange and then turns back to green...

I tried recreating my usb but alas.

Can you please help by walking me through the steps to prepare the usb?
In you instructions you mention: "... 1. Format a new USB drive with a single Ext3 partition, and label it rootfs. "
I suspect I might be doing something wrong there.

If it helps when I mount the usb to a linux I get:

$ lsblk -f 
NAME        FSTYPE LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1      ext3   rootfs 129dad2f-d4aa-4dd7-82be-48a08497fb75   12.8G     5% /media/deb

$ lsblk -l
NAME      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda         8:0    1 14.5G  0 disk
sda1        8:1    1 14.5G  0 part /media/deb

ador,

> I am at a loss. Except that one time where I was
> able to boot into debian without the HDD on, I
> have not been able to ssh.
> After the "Starting kernel ..." the goflex stops
> responding to ping, the LED turns orange and then
> turns back to green...

That is how it should be. When you connect netconsole, the output stops at "Starting kernel ...". After you've booted into Debian, you can do more set up in Debian to get more output during boot.

The LED behavior is also good. This device always turn orange and then green after the kernel has booted.

Now the part where the kernel mounts the rootfs is where the problem is.

Quote

$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1 ext3 rootfs 129dad2f-d4aa-4dd7-82be-48a08497fb75 12.8G 5% /media/deb

The above looks good. So we need to look for other info

====

Mount the USB rootfs on another Linux box. Assuming it is mounted at /media/sdb1.

mount
fdisk -l 
df -h
e2label /dev/sdb1
cd /media/sdb1
ls -lart ./boot

and please post the entire log for this here.

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

Hey bodhi,

here's the output (the usb is mounted at /media/deb):

$ fdisk -l

Disk /dev/sda: 14.5 GiB, 15597568000 bytes, 30464000 sectors
Disk model: Ultra
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe12d4f1b

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1  *     2048 30463999 30461952 14.5G 83 Linux

$ df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        59G   20G   37G  35% /
devtmpfs        1.8G     0  1.8G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           1.9G   17M  1.9G   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/mmcblk0p1  253M   55M  198M  22% /boot
tmpfs           383M     0  383M   0% /run/user/1000
/dev/loop0       15G  773M   13G   6% /media/pi
/dev/sda1        15G  764M   13G   6% /media/deb

$ e2label /dev/sda1
rootfs

$ cd /media/deb
$ ls -lart ./boot

total 46244
drwxr-xr-x 21 root root    4096 Feb 17  2015 ..
drwxr-xr-x  2 root root    4096 Aug 16  2019 dts
-rwxr-xr-x  1 root root 4963616 Aug 18  2019 zImage-5.2.9-kirkwood-tld-1
-rw-r--r--  1 root root  165790 Aug 18  2019 config-5.2.9-kirkwood-tld-1
-rw-------  1 root root 4963616 Aug 18  2019 vmlinuz-5.2.9-kirkwood-tld-1
-rw-------  1 root root 3101889 Aug 18  2019 System.map-5.2.9-kirkwood-tld-1
-rw-r--r--  1 root root 9649570 Aug 18  2019 linux-headers-5.2.9-kirkwood-tld-1_1.0_armel.deb
-rw-r--r--  1 root root 9713872 Aug 25  2019 initrd.img-5.2.9-kirkwood-tld-1
-rw-r--r--  1 root root 4963680 Aug 25  2019 uImage
-rw-r--r--  1 root root 9713936 Aug 25  2019 uInitrd
drwxr-xr-x  3 root root    4096 Aug 25  2019 .

Finally, can you please tell me to how set up Debian to get more output during boot (for future reference).

Thanks again for your help!

ardor,

The Wiki thread, Netconsole section, 2nd post, shows you how to set up netconsole output in Debian:

Quote
https://forum.doozan.com/read.php?2,23630

Netconsole

Use netconsole to troubleshoot uBoot without a serial cable
Use netconsole to troubleshoot Debian kernel booting

Your log showed the rootfs boot files look good. So the only remaining things to check and do:


1. Check the USB rootfs for error

umount /media/deb
e2fsck /dev/sda1

If there was file system errors, then it is most likely the reason. Sometime if the error is too significant the kernel kicks it out to the initramfs prompt and stops booting. Or course you cannot see it stop without serial console.

2. After checking rootfs errors, remove the HDD from the GF Home. Only this USB rootfs plugged in. Power up.

And on another Linux box (if you have another Linux box, if not then control-C to exit the netconsole server and use this box), wait for about 2 minutes and start pinging the GF Home

Note that for the first time, it might take a very long time for debian.local to be advertised (by avahi) to other boxes.

ping debian.local

And also check for a new IP address in the router (this will appear quicker).

========

If you still cannot find its dynamic IP in the router, then on another LInux box, setup the static IP in the rootfs to 192.168.2.243. With the static IP address hopefully you can find it easier.

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

Success! Thank you!

e2fsck reported:

e2fsck 1.44.5 (15-Dec-2018)
rootfs contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 15076/952848 files (6.9% non-contiguous), 271556/3807744 blocks

After that I was able to ssh to the GoFlex.
I also setup netconsole for kernel boot logging, so if something similar happens hopefully I will have more details.

I will now try to see if I can mount the existing HDD without losing its data.



Edited 1 time(s). Last edit at 11/29/2020 06:44AM by ador.

ok there is something really fishy going on, possibly with the usb of the goflex.

I was doing an ap-get upgrade and at some point got:

$ apt-get upgrade

....
[ ok ] Stopping NTP server: ntpd.
[ ok ] Starting NTP server: ntpd.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.2.9-kirkwood-tld-1
cpio: Read error at byte 20480 in file ./usr/lib/modules/5.2.9-kirkwood-tld-1/kernel/drivers/net/ethernet/atheros/atl1e/atl1e.ko, padding with zeros
cpio: Read error at byte 4096 in file ./usr/lib/modules/5.2.9-kirkwood-tld-1/kernel/drivers/net/ethernet/broadcom/bnx2.ko, padding with zeros

in the netconsole I saw:

[   37.077077][ T1164] Segment Routing with IPv6
[  408.913420][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  409.114492][    C0] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  409.123583][    C0] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 fc db 28 00 00 38 00
[  409.131667][    C0] print_req_error: I/O error, dev sda, sector 16571176 flags 80700
[  409.283415][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  409.673410][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  410.063410][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  410.453411][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  410.843411][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  411.233411][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  411.434470][    C0] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  411.443540][    C0] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 fc db 28 00 00 08 00
[  411.451623][    C0] print_req_error: I/O error, dev sda, sector 16571176 flags 0
[  411.613415][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  411.814480][    C0] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[  411.823552][    C0] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 fc d7 50 00 00 20 00
[  411.831631][    C0] print_req_error: I/O error, dev sda, sector 16570192 flags 80700
[  411.983410][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  412.373411][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  412.763408][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  413.153409][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  413.543410][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  413.933409][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  414.143562][    C0] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 fc d7 50 00 00 08 00
[  414.151641][    C0] print_req_error: I/O error, dev sda, sector 16570192 flags 0
[  414.513415][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[  530.003414][  T168] usb 1-1: reset high-speed USB device number 2 using orion-ehci

When taking the usb to another linux box and doing e2fsck:

e2fsck /dev/sda1                                                           
e2fsck 1.44.5 (15-Dec-2018)
rootfs: recovering journal
Clearing orphaned inode 496944 (uid=0, gid=0, mode=0100644, size=1986292)
Clearing orphaned inode 496954 (uid=0, gid=0, mode=0100644, size=395844)
Clearing orphaned inode 515192 (uid=0, gid=0, mode=0100755, size=723796)
Clearing orphaned inode 496960 (uid=0, gid=0, mode=0100644, size=198192)
Clearing orphaned inode 497066 (uid=0, gid=0, mode=0100644, size=267724)
Clearing orphaned inode 539084 (uid=0, gid=0, mode=0100755, size=198576)
Clearing orphaned inode 539214 (uid=0, gid=0, mode=0100644, size=190320)
Clearing orphaned inode 539256 (uid=0, gid=0, mode=0100644, size=38920)
Clearing orphaned inode 539272 (uid=0, gid=0, mode=0100644, size=703312)
Clearing orphaned inode 539226 (uid=0, gid=0, mode=0100644, size=241872)
Clearing orphaned inode 497077 (uid=0, gid=0, mode=0100644, size=9520)
Clearing orphaned inode 539340 (uid=0, gid=0, mode=0100644, size=2097564)
Clearing orphaned inode 497109 (uid=0, gid=0, mode=0100644, size=133212)
Clearing orphaned inode 497046 (uid=0, gid=0, mode=0100644, size=580456)
Setting free inodes count to 937685 (was 937784)
Setting free blocks count to 3512359 (was 3538094)
rootfs: clean, 15163/952848 files, 295385/3807744 blocks

I have tried it with another usb stick and still get the same behavior.
I am starting to think that the goflex usb has some HW problem.
What do you think?



Edited 2 time(s). Last edit at 11/29/2020 07:20AM by ador.

Ok I picked up a really old usb flash I had laying around that was actually given to me as an advertising gimmick...
And it worked perfectly.

I no longer get errors in netconsole (at least not yet).
I have done apt-get upgrade and also installed a couple of tools I needed (ntfs-3g, samba, etc.).

For the time being everything works as expected.

So I assume that GoFlex had an issue with "high-speed USB device" USB sticks.

ardor,

I don't recall you said what type of USB flash drives you were using! "high-speed USB device" sounds suspect. There are USB 3.0 flash drives that don't work properly with these old Kirkwood boxes. Example: Sandisk 32GB USB 3.0 should be avoided.

Glad to hear it is working well now.

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

Yes indeed, I never mentioned the type of USB.
I wrongly assumed it would be backwards compatible...

Anyway, all is well now. Thank you for all your help bodhi!