Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault 50

The result of spending copious hours and days, knee deep in Linux IS – a working and stable 2TB NAS with Debian Linux based on Seagate GoFlex NET. Persistence and Charisma eventually paid off, ended up being a labour of love, but it was WORTH IT. This is a guide on how to do the same the EASY WAY., don charisma, Seagate GoFlex Net Seagate GoFlex Net

This is a fairly hardcore and long geeky guide (6000 words), I realise it’s a niche audience that will be interested in hacking cheap bits of hardware off of Amazon, so if not for you then don’t read it:)


I like saving money and being green at the same time is a bonus.

Seagate GoFlex Net has two SATA ports for portable hard drives, it has a 1.2GHz processor and runs on just a few watts of electricity. For it’s size it’s powerful, expandable and green. Free market prices vary obviously, at the time of writing it’s not expensive around £29 in UK, I guess that’s $40 in USA. Total of around £130 for a two disk RAID1 NAS with a web based GUI for administration, off the shelf alternatives are maybe £200-£250. Ability to install any of the 25000 debian packages, priceless.

Seagate package this device with built in software from Pogoplug. Seagate in my experience are THE BEST hard drive manufacturer. However they tend to suck big style on the software they include with their hardware. Pogoplug on GoFlex Net is like putting a lawnmower engine in a Ferrari. It’s OK for some consumers who don’t want to know anything about the technical side, but really it’s not much use for anyone serious. Also it poses some security issues, such as sharing data on Windows network without any password, meaning anyone who has access to your local network has access to your shared files.

I wanted a semi-portable NAS. Seagate GoFlex Net weighs only a few hundred grammes, hand luggage for travelling.

I didn’t want to mess around too much with circuit boards, a finished device in a nice case fits the bill. GoFlex Net has a nice moulded plastic case.

I wanted the device to be a NAS, that is accessible on the Network so I don’t have to mess around plugging and unplugging USB cables. GoFlex Net has gigabit ethernet port.

As I don’t want to spend all my time knee deep in Linux commands, I wanted some kind of easy-to-use management interface. OpenMediaVault fits the bill, everything in one place.

I wanted RAID1 for integrity of my data. GoFlex Net has 2 SATA ports, so RAID 0 and 1 and also spanning possible.


Looking around on the internet, I looked at various different devices. Perhaps a Raspberry PI, but doesn’t have case or SATA interface for drives. Pogoplug? expensive and cheaper models don’t have SATA.

Seagate GoFlex Net was the best I could find on a miser’s budget and having the possibility of doing what I want it to do. I like the way the hard drives hot plug into the top of the device. Just a great design.

Stock software on GoFlex Net is Pogoplug, basically it’s Pogoplug with a Seagate label on it. Searching internet revealed that other’s had installed Arch Linux and Debian Linux on the device, and personally I have a preference for Debian Linux as I use Ubuntu and that’s based on Debian.

Enter Jeff Doozan’s website, . They have posts and pages about specifically what I wanted to do, Debian on GoFlex Net and other ARM devices such as Pogoplug and Zyxel NSA320. It all sounded oh so simple in my research.

But it’s never as straightforward in real life is it ?

It’s taken me a lot of hours, weeks in fact to get to the point of having stable GoFlex Net with Debian Linux, OpenMediaVault and RAID1. And many many failed attempts !

This is a guide for how to do it, and sharing what I learn’t along the way. If you want to build a similar device, then you’ll be able to using this guide, the EASY WAY, avoiding the mistakes I made, saving time and stress.

Obviously if you follow this guide you do so at your own risk, and it’s your responsibility to make sure that you’re doing things correctly, not mine. GoFlex Net can be broken (aka bricked, foobared, door-stopper) if you don’t use care and caution, ESPECIALLY when doing anything to do with the inbuilt NAND flash memory. Take care in what you’re doing and you won’t have a problem. Check everything carefully and check the references I’ve given to external sites.

What you’ll need to do this

Don Charisma, Toolbox



Seagate GoFlex Net

USB Flash Drive (not camera card eg SD), I use Sandisk Cruzer and Cruzer Fit

Ubuntu or other flavour of Linux, either running direct on a PC/Laptop or in a Virtual Machine

An SSH client program, Ubuntu has one or on Windows I use BitVise SSH Client.

Some time and patience and willingness to learn. A little bit of Linux knowledge extremely beneficial.


gparted GUI partion editor on Ubuntu

Portable/2.5″ Hard Drive(s) – Seagate Hard Drives recommended, Backup Plus 1TB are a good fit and cheap at around £50 each

This is how we do it

  • STEP 1 – Get ssh access to GoFlex Net
  • STEP 2 – Make a bootable “rootfs” on USB drive
  • STEP 3 – Update the GoFlex Net inbuilt bootloader to boot from USB
  • STEP 4 – First boot from USB
  • STEP 5 – Install rescue system (optional but HIGHLY recommended)
  • STEP 6 – Install netconsole (optional but HIGHLY recommended)
  • STEP 7 – Install OpenMediaVault to USB
  • STEP 8 – Migrate your rootfs to SATA hard drive (optional)
  • STEP 9 – Setup RAID1 (optional)
  • STEP 10 – Do some cool stuff with the LEDS (optional)
  • APPENDIX – for reference, chrooting for kernel upgrade/change or troubleshooting

STEP 1 – Get ssh access to GoFlex Net

In order to do anything with your GoFlex Net you’ll need to get command line access via ssh to the “root” user.

See GR3YH0UND’S BLOG on Prepare SSH Connection

Basically, you’ll probably need to go to  pogoplug website , register yourself and your device and switch ssh access on in the “Security Settings” page. You could try connecting via ssh on your GoFlex Net fresh out of the box, would save you a step.

The login for your GoFlex Net is either “root/stxadmin” or “root/ceadmin” (pogoplug website)

In order to connect to GoFlex Net command line on ssh you’ll need to either install an ssh client such as BitVise SSH (on Windows) or use ssh from a terminal window on Ubuntu (or however you want to do it !)

You’ll need to IP address for your GoFlex Net, it will get one automatically from your router. You might see this if you explore the network in Windows (will have a name like “FADS265D34″, or in your router’s list of DHCP clients with an IP address on. For mine I have my router setup so it issues the same IP address to my GoFlex Net.

Once you’ve got ssh access, you can move to next step.

STEP 2 – Make a bootable “rootfs” on USB drive

First thing to note is that GoFlex Net is NOT supported with standard Debian kernel, in my experience it just won’t boot. Also using either the Debian Squeeze or Wheezy install scripts from don’t work and/or are broken, so just don’t waste the hours trying, I did, and all I got was tired, frustrated and annoyed.

The MOST RELIABLE way I found of creating a bootable USB drive is to use rootfs from davygravy’s post on download his package here. You only need the “kirkwood-debian_rootfs.img” file, ignore the other files.

# to extract the archive in Ubuntu (or use WinRAR in Windows)
tar -xvzf NSA320quickstart.tar.gz

Next we need to prepare the USB Flash drive. Personally I reckon ext2 partition format is the best to use for flash drive. I think because of it’s age it’s the simplest and least likely to cause problems.

To do this I used gparted GUI on Ubuntu, you’ll need to :

1. locate your USB drive in dropdown menu, will probably be /dev/sdb or /dev/sdc, be sure you’ve selected the correct drive !

2. delete existing paritions

3. create new partitions, I’d suggest first partition ext2 around 1GB (min 256MB) label “rootfs”, second parition linux swap 256MB label “swap”. You can move and resize these later if you so wish.

Now we need to put the rootfs onto the flash drive.

# On your Ubuntu/Linux machine , suppose your drive's partion1 /dev/sdb1 is mounted at /mntmount /dev/sdb1 /mnt
sudo -s
mkdir /media/debian
mount -o loop <path-to-kirkwood-debian-image_debian.img> /media/debian
cp -a /media/debian/* /mnt
umount /mnt
umount /media/debian
# where /mnt is the mounted USB drive

That’s the USB drive created, with *working* rootfs, debian 3.3.2 kernel, Debian Squeeze distibution.

SIDE NOTE: It’s possible to upgrade squeeze to wheezy on this installation with the 3.3.2 kernel. And I’ve also managed to install the 3.10.4 kernel by bodhi here. PLEASE DON’T UPGRADE KERNEL OR SQUEEZE TO WHEEZY IF YOU WANT TO INSTALL OPENMEDIAVAULT, Debian squeeze is needed by OpenMediaVault and the 3.3.2 kernel works fine.

STEP 3 – Update the GoFlex Net inbuilt bootloader to boot from USB

We need to do this so that we can boot from a USB flash drive, instead of being locked into Pogoplug software.

Update uboot

Be sure that you’re ready and prepared for this stage as will actuall *WRITE* to the flash memory in the GoFlex Net. If you don’t do it right you could brick your device here. So make sure power is on and will stay on during the procedure

# Procedure from "
cd /tmp
chmod +x

Restore old uBoot

This step is only for reference, DON’T ACTUALLY RUN IT NOW. Should you wish to revert to the original GoFlex Net/Pogoplug software, then you can use this procedure.

# Restore original uBoot
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot.mtd0.goflexnet.original.kwb

STEP 4 – First boot from USB

Take the USB Stick you’ve made and put into the USB port of the GoFlex Net. You’ll need to power cycle the device.

If all’s well you should see the GoFlex get an IP address from your router. In my router I have the IP address of the GoFlex Net mapped to a static IP address via the MAC address.

With the IP address you can see from router (or you’ve mapped against MAC address), connect via SSH client, login with “root/root”.

Once your in you should see a prompt :


Do a:

uname -a

this will show you the kernel version which should be davygravy’s 3.3.2

You now have a working Debian Squeeze installtion, 3.3.2 kirkwood kernel.

If you’re NOT ABLE TO BOOT, then it’s possible BUT unlikely that you’ve bricked the device in STEP 3, if this is the case you’ll need to get more involved with fixing this, and may involved UART or serial booting. I don’t have any experience with this, so you’ll need to sort this out, help can be found at, either post a question or look at other’s questions.

More likely other reason why you’re not able to boot are that your flash drive just doesn’t work for whatever reason. I’ve had nothing but headache trying to boot from SD memory cards in generic reader, so not a good idea. From what I understand SD cards expect to be used with FAT16/FAT32 format and don’t like working with any other filesystem, which seems to explain the problems I’ve had. I mentioned earlier that best results I’ve had from Sandisk Cruzer or Cruzer fit. These aren’t the fastest devices but they do boot and seem to hold a Debian installation.

Another reason is that you’ve not created the rootfs properly. So I’d suggest try another flash drive and repeat the procedure for creating the rootfs on your USB drive.

STEP 5 – Install rescue system (optional but HIGHLY recommended)

If you don’t install the rescue system, then you’ll be forced to boot from the USB drive all the time. If the USB drive fails to boot then you will have to make another one to get into the device.  My experience is that the USB drive installations will break after you’ve spent hours and hours configuring and installing. If you want any chance of repairing then booting into debian without a bootable USB drive would be a good idea. So this and a lot of frustrating hours are why I recommend you install the rescue system. For my purposes V2 rescue work fine. The procedure is described here by Jeff Doozan.

IMPORTANT, this procedure will write to the Flash in your GoFlex Net, so have everything ready advance and make sure power won’t go off.

So either you’re in your ssh from USB drive that’s booted your davygravy’s rootfs or you need to boot into it, then :

cd /tmp
chmod +x

Reboot without the USB stick attached and you should boot into the rescue system. Then reboot with the USB attached and you should boot into davygravy’s rootfs.

STEP 6 – Install netconsole (optional but HIGHLY recommended)

Without netconsole, you can’t monitor the boot process (well at least the bits up until Kernel is loaded). It’s a bit of extra effort, but it will help you debug if the USB stick is not booting. Netconsole procedure is described by Jeff Doozan here –,14,14


On the Goflex NET, you’ll need to setup some environment variables for the uBoot loader. These are written into the internal flash, so be VERY VERY careful you get this right. CHECK, DOUBLE CHECK and TRIPLE CHECK anytime you are flashing internal flash or doing anything with it.

On the GoFlex Net:

# serverip is the machine that you will monitor on, ipaddres is the address of your GoFlex Net
# my Ubuntu machine I use to monitor is and my GoFlex Net is

fw_setenv serverip
fw_setenv ipaddr
fw_setenv if_netconsole 'ping $serverip'
fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
fw_setenv preboot 'run if_netconsole start_netconsole'

On the desktop machine (Ubuntu –

nc -u -l 6666 &
nc -u

You’ll need to reboot in order for these settings to take effect. I’ve got into the habit of doing this :

# for some linux installations
shutdown -h now

# or on some other linux installations

Reason for doing this is to make sure any cached data is written to disk and propertly shutdown the operating system.

STEP 7 – Install OpenMediaVault to USB

OpenMediaVault installation was fairly straightforward, although had to do some digging around on forums ! This thread on OMV forum is now out of date, but forms that basis of how to do it.

Update sources.list file

It’s good practice to do this on any installation of Debian, and will speed up any installations and updates because hopefully you’ll find mirrors that are close to you. Please refer to Debian worldwide mirrors full list to get yours.

vi /etc/apt/sources.list

This is what yours will look like:

root@debian-kirkwood-wide:/# cat /etc/apt/sources.list
deb squeeze/updates main contrib non-free
deb-src squeeze/updates main contrib non-free
deb squeeze main contrib non-free
deb-src squeeze main contrib non-free

As I’m based in Asia, this is what mine looks like after editing:

deb squeeze/updates main contrib non-free
deb-src squeeze/updates main contrib non-free
deb squeeze main contrib non-free
deb-src squeeze main contrib non-free

Now we need to update the out Debian installation to latest version of Squeeze, and install xmlstartlet. For some reason the xmlstarlet used by OMV comes from debian Wheezy (but OMV isn’t stable on Wheezy), so we also need to install xmlstarlet, then upgrade it to a later version manually.

apt-get update
apt-get upgrade
apt-get install xmlstarlet

Get xmlstarlet 1.5.0-1 and install it:

dpkg -i xmlstarlet_1.5.0-1_armel.deb

Now do a HARD reboot, sync, shutdown and then power cycle.

shutdown -h now

You should have rebooted and be back at your ssh prompt.

Now I change the hostname, my GoFlex Net is called “GoFlexNet1″, you can call yours what you want.

root@debian-kirkwood-wide:~# cat /etc/hostname
root@debian-kirkwood-wide:~# echo "GoFlexNet1" > /etc/hostname
root@debian-kirkwood-wide:~# cat /etc/hostname

Now we update our hosts file and tell it what out IP address is. I’d recommend setting this in your router as mentioned earlier. If you want a static IP address then you’ll need to configure your /etc/network/interfaces or do it via the OMV interface.

root@debian-kirkwood-wide:~# cat /etc/hosts localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

root@debian-kirkwood-wide:~# vi /etc/hosts
root@debian-kirkwood-wide:~# cat /etc/hosts localhost GoFlexNet1
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Now do a HARD reboot, sync, shutdown and then power cycle.

shutdown -h now

Now we need to setup /etc/apt/sources.list.d/openmediavault.list so that OMV knows where to look for it’s files, install the OMV keys, install OMV and restart the Apache server.

OMV installer will ask questions, so don’t stray too far:

  • about mail server (I didn’t bother will setup later)
  • RAID arrays, I don’t think GoFlex can boot from RAID so no point starting the RAID early, if you are planning to use RAID then you’ll need to start the arrays, OMV will do this for you
echo "deb fedaykin main" > /etc/apt/sources.list.d/openmediavault.list

# the first apt-get update will throw an error, thats why we install the openmediavault-keyring

apt-get update
apt-get install openmediavault-keyring
apt-get update
apt-get install openmediavault
service apache2 restart

DO NOT REBOOT, YET ! First we need to setup a couple of things, especially re-enabling the now disabled ssh.

First go to your internet browser firefox chrome etc, my page is

Login to the OMV web interface using “admin/openmediavault”, and setup the following :

  • enable ssh /permit root
  • general settings – session timeout 0 (nothing more annoying than having to re-login every 5 minutes)
  • date & time

*Shutdown using OMV web interface and power cycle.*

Go to browser and again login to OMV web interface and do:

  • update manager – update to 0.4.37

*Shutdown using OMV web interface and power cycle.*

At this stage I attached an SATA hard disc and tried to boot from USB. No joy, doesn’t boot. This problem is described here reply here. Basically uBoot and the kernel loaded from USB disagree on where the rootfs is. The solution provided by bodhi is to force uBoot and the Kernel to boot from a partition called “rootfs”.

So remove the SATA drive and reboot, then do this :

# USE CAUTION, updates internal flash
fw_setenv usb_bootcmd 'run usb_init; setenv usb_root LABEL=rootfs; run usb_set_bootargs; run usb_boot'

Now insert SATA drive again

*Shutdown using OMV web interface and power cycle.*

You should now have a working OpenMediaVault on your USB Flash Drive, that you can boot with SATA drives attached.

You may wish to leave configuration like this and continue booting off the USB flash drive, that’s fine if you trust the USB flash drive and do regular backups of the USB drive. Advantage of booting from USB flash drive is that you can use the whole of your SATA drives for data and setting up RAID is slightly simpler, because you can RAID the whole drives. Disadvantage is that I’m not convinced of the longevity of a USB flash drive for linux installations, so it’s possible it will break at some point. Also your USB port is now tied up, so attaching anything else to USB port is more complicated.

One solution to make this more reliable would be to boot off a USB hard disc, and you’d still be RAID the whole drives, but USB port still occupied.

My solution is to boot off of one of the SATA attached drives, which is what I’m not going on to describe next. Downside is that RAID has to be manually setup and so do the partitions.

STEP 8 – Migrate your rootfs to SATA hard drive (optional)

I’ve already given my reasons for wanting to do this, basically I believe that this is more stable and reliable.

First we need to partition the drive(s), I used gParted GUI in Ubuntu, but Linux heads feel free to command line it. I’ve made my rootfs just a bit smaller than a 4GB flash drive so that I could just copy it onto flash drive for backup, and also allows for logs to grow and any updates that may happen later. So here’s my layout

Partition1 -> size=3800MiB -> format to ext3 -> label = “rootfs_hd”

Partition2 -> size=512MiB -> format to linux-swap -> label=”swap”

Partition3 -> size=The rest of the disk -> unformatted -> label=””

Do the same for both disks if you have two, partition1 on second disk I labeled “backup_rootfs_hd”. Also make a mental note of which disk is “master” (the one to boot from) and which is “backup”

Now you need to copy the rootfs that you’ve created on your USB flash drive to your “master” hard disk. Ubuntu is quite helpful in mounting drives so they may already be mounted, otherwise you’ll need to do it manually

# assuming "master" hard disk rootfs is /dev/sdc1 and usb flash drive rootfs is /dev/sdd1
mkdir /media/hd_rootfs
mkdir /media/usb_rootfs
mount /dev/sdc1 /media/hd_rootfs
mount /dev/sdd1 /media/usb_rootfs
cp -a /media/usb_rootfs/* /media/hd_rootfs

So you should now in theory have a bootable hard drive. BUT there is one step left, your uBoot isn’t yet configured for SATA booting. How to set this up was described by varkey here. Basically we need to set some variables for uBoot, so again be careful doing this.

fw_setenv sata_boot 'ide reset; mw 0x800000 0 1; ext2load ide 0:1 0x800000 /boot/uImage; if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
fw_setenv sata_bootcmd 'run usb_set_bootargs; run sata_boot'
fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset'

Now that you’ve done that you can try to boot from the hard disk and it should work.

STEP 9 – Setup RAID1 (optional)

If you’ve got this far then well done !

My discs where mounted /dev/sda /dev/sdb. The partitions I wished to RAID1 where around 950GB each /dev/sda3 /dev/sdb3. I used &lt;a href=””&gt;this guide&lt;/a&gt; here loosely as a reference for this, but note his is quite a different setup.

First of all find out what your partitions are labeled, and have a look where rootfs_hd is mounted which well tell you which is master and which is backup.

# list all partitions on disks
sfdisk -l

# check mounts, where rootfs is mounted
mount -l

Now the unformatted rest-of-disk partitions we created earlier need to have their partition type switched to “linux raid autodetect”, and then list all partitions again so we know they’ve been updated.

#change partition type of partition 3 to fd (linux raid autodetect)
sfdisk -c /dev/sdb 3 fd

#change partition type of partition 3 to fd (linux raid autodetect)
sfdisk -c /dev/sda 3 fd

# list all partitions on disks
sfdisk -l

Now you’re going to create the array. Once created it will immediately do a resync, and this will take 3-4 hours. I didn’t think about it ahead of time so I had no choice but to wait, and I reckon it’s not a bad idea to let the RAID system check the disks, as I don’t want a bad disk in my array. If you know what you’re doing and are confident about it, consider using the –assume-clean flag, which avoids doing a resync and saves time. The downside I reckon is that you don’t get your disks checked. Up to you, see here for more details.

# create raid device (consider using --assume-clean)
mdadm --create md1 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3

mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/md1 started.

RESYNC will take around 3-4 hours for 1TB drives, so be patient, montior and don’t reboot or poweroff whilst it’s being done. You can continue doing things, but anything you do on the drives will temporaily pause the resync and it will take longer. You can continue setting up filesystem etc, just don’t copy a bunch of data in until the resync has finished.

As you can see my array is called /dev/md/md1 and also it seems /dev/md127 (not quite what I was expecting !). It seems that these device iditifiers are interchangable, OMV will use the md127 one.

These commands will tell you about the array and you’ll be able to find your md127 device in “ls /dev”

ls /dev

#basic details of raid
mdadm /dev/md127

#detailed details of raid
mdadm --detail /dev/md127
cat /proc/mdstat

Next we need to make the filesystem on the array

#make the file system ext3

mkfs.ext3 /dev/md127

Lastly as described here , label your array, I’ve called mine “raid1″

#label the raid 1 array
tune2fs -L raid1_data /dev/md127

Your RAID1 array should now be configured and “seeable” in OMV web interface. Obviously once it’s finished resyncing power down using OMV and power cycle. Then you can start using it:)

Optional Bonus !

If you want to manually backup your live rootfs from one master to backup, you already have partitions in place for this. Use this procudure :

#backup rootfs
mkdir /tmp/backup
mount /dev/sdb1 /tmp/backup
cd /tmp/backup
mkdir rootfs_backup
rsync -aAXv /* /tmp/backup/rootfs_backup --exclude={/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/lost+found}

This means that in the event that your master disk dies then you have a backup that you can boot into on the “backup” disc. I don’t know how best to automate this, and whether wise to automate. Probably best to run prior to any updates, and maybe once a week or so.

STEP 10 – Do some cool stuff with the LEDS (optional)

Getting the LEDs giving some feedback about what’s going on, seemed to be a nice-to-have, but since implimenting this I’ve found that it’s invaluable. So I’d suggest strongly consider doing this. There’s several things I wanted to get feedback on :

1. Disk and CPU activity

2. When is it “safe” to disconnect the power at shutdown

3. Network activity

I wasn’t able to get network activity working, I think it may be possible with the “sar” command that comes with iostat. The method with iptables didn’t work, I’m assuming because the davygravy kernel I’m using isn’t setup for it. Happy for any readers to report back how to do this.

For Disk and CPU, the iostat command is perfect. I did a post on Doozan forum here -“by Don Charisma – LEDs on GoFlex Net”. I use an awk command to process the output of iostat, and then feed this to the LEDs. You could change the position of the LEDs to suit your own particular scenario.

Here’s what the LEDs are assigned to :

doncharisma, don charisma, Seagate GoFlex Net LEDs

Seagate GoFlex Net LEDs

Here’s how we do it:

You’ll need to install the systat package :

# for iostat
apt-get install sysstat

Now we need to edit the /etc/rc.local file like so :

#!/bin/sh -e
# rc.local
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
# In order to enable or disable this script just change the execution
# bits.
# By default this script does nothing.

# For LED control on Seagate GoFlex Net that's been Debianised
# (c) Don Charisma 2013

iostat -z 1 | awk -W interactive '
BEGIN { sda="none";
# if hard drives or RAID active, set flag for LED
/sda/ {	sda="timer"; }
/sdb/ {	sdb="timer"; }
/md1/ { md1="default-on"; }
# Find the line with CPU info, pick the last number = percentage idle
# subtract it from 100 to give CPU utilisation
/..*..*..*..*..*..*/  { cpu_utilise = 100 - $6;
				if (cpu_utilise >= 20.0) { cpu20="default-on"; }
				if (cpu_utilise >= 40.0) { cpu40="default-on"; }
				if (cpu_utilise >= 60.0) { cpu60="default-on"; }
				if (cpu_utilise >= 80.0) { cpu80="default-on"; }
/Device:/ { if (sda != sda_prev)
				{ print sda > "/sys/class/leds/status:white:left0/trigger";
			      fflush( "/sys/class/leds/status:white:left0/trigger" );

			if (sdb != sdb_prev)
				{ print sdb > "/sys/class/leds/status:white:left1/trigger";
				  fflush( "/sys/class/leds/status:white:left1/trigger" );

			if (md1 != md1_prev)
				{ print md1 > "/sys/class/leds/status:white:left2/trigger";
				  fflush( "/sys/class/leds/status:white:left2/trigger" );
				  print md1 > "/sys/class/leds/status:white:left3/trigger";
				  fflush( "/sys/class/leds/status:white:left3/trigger" );

			if (cpu20 != cpu20_prev)
				{ print cpu20 > "/sys/class/leds/status:white:right0/trigger";
				  fflush( "/sys/class/leds/status:white:right0/trigger" );

			if (cpu40 != cpu40_prev)
				{ print cpu40 > "/sys/class/leds/status:white:right1/trigger";
				  fflush( "/sys/class/leds/status:white:right1/trigger" );

			if (cpu60 != cpu60_prev)
				{ print cpu60 > "/sys/class/leds/status:white:right2/trigger";
				  fflush( "/sys/class/leds/status:white:right2/trigger" );

			if (cpu80 != cpu80_prev)
				{ print cpu80 > "/sys/class/leds/status:white:right3/trigger";
				  fflush( "/sys/class/leds/status:white:right3/trigger" );


END { print "The end"; }
' &

exit 0

Now for shutdown/halt LEDs, to make green LED go off and the white LEDs to blink, we need to make a change to the /etc/init.d/halt file, here’s how the section of mine that I changed looks :

# Make it possible to not shut down network interfaces,
# needed to use wake-on-lan
     if [ "$NETDOWN" = "no" ]; then

# for goflex green led
     echo none > /sys/class/leds/status:green:health/trigger

# for goflex white leds
     echo timer | tee /sys/class/leds/status:white:*/trigger > /dev/null

log_action_msg "Will now halt"
     halt -d -f $netdown $poweroff $hddown


That’s it your done, enjoy:)

APPENDIX – for reference, chrooting for kernel upgrade/change or troubleshooting

This procedure was posted by tuxuser in forums here. I’ve made some slight edits.

In the event that your USB flash drive won’t boot, you should still be able to get your GoFlex Net running via the rescue system. You can then chroot into the rootfs on your USB drive, and perhaps make repairs, look at logs, maybe fix the problem.

Also if you want to change kernel, it has to be done via chroot, you can’t change a live kernel. The procedure here is for changing kernel, if you just want to chroot into your installation, stop once you’re chroot’ed.

Once you’ve booted into the rescue system, this would be “a” procedure to change the kernel.

# Mount roofs
mkdir /tmp/wheezy
mount /dev/sda1 /tmp/wheezy
cd /tmp/wheezy
# Prepare chroot-environment
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount -t devpts pts dev/pts/
chroot /tmp/wheezy /bin/bash

# Now here we go with the kernel install
#Dependencies for a https wget
apt-get update apt-get install dialog ca-certificates openssl
wget -O linux-image-3.3.2-kirkwood-dg_1.1_armel.deb

# Safety
cp -r /boot /boot-backup

# flash-kernel never installed for me successfully for me -> removing postinstall-script, otherways update-initramfs will bug around
rm /etc/kernel/postinst.d/zz-flash-kernel

# Install Kernel
dpkg -i linux-image-3.3.2-kirkwood-dg_1.1_armel.deb

# Build proper uboot images (neccessary because uBoot has to boot from images)
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.3.2 -d vmlinuz-3.3.2-kirkwood-dg uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.3.2-kirkwood-dg -d initrd.img-3.3.2-kirkwood-dg uInitrd

# Exit chroot
# Unmount chroot-environment
umount /tmp/wheezy/dev/pts
umount /tmp/wheezy/dev
umount /tmp/wheezy/sys
umount /tmp/wheezy/proc cd /
umount /tmp/wheezy

init 6


I’d like to get LEDs to respond to network traffic. I saw  a post here relating to this, well I couldn’t get the iptables thing to work, not sure why as yet. Wasn’t able to think of another Linux tool to use to detect network traffic or not, since the iptables command gives an error. Perhaps the sar tool would do.

I think I will also try changing the RAID system to RAID10,f2 as described here. I wasn’t aware when I started this of RAID10,f2, which is why I used RAID1. RAID1 has the possibility of being faster than a single disk for reads but in practice for a single client connection, you’re reading off a single disk, probably the master. RAID10,f2 however can be setup on just 2 discs, and the data is organised in such a way that data can be read off of both disks at the same time to serve a single client.

Also like to get the swap partitions RAID’ed, maybe the rootfs, although there are reasons for not RAIDing the rootfs.

I might build my second unit the same, but use NTFS drives mirrored using rsync, for flexibility in plugging them into my Windows machines.

The netconsole is great up until the kernel starts booting, but then I’m not getting any messages from the booting system. It’s possible to get these boot messages sent via netconsole, but requires fiddling with the kernel as described here. I think I will try and add this as difficult to debug boot problems without it.

Confusion and Conclusion

In total I must have spent a month working on this, it looks easy but isn’t. Hopefully this guide has taken out a lot of the donkey work and hair pulling, and you may be able to do it in a day:)

Building a NAS that’s on a par with devices costing far more is entirely possible. Just a case of persistence and willingness to learn.

My GoFlex NET has now been running a couple of weeks and seems stable enough with OpenMediaVault and my two 1TB RAID1 disks. Performance wise I’m happy enough, only bottleneck I’ve found so far is the Samba daemon which is using a lot of CPU when I copy files over the network onto the RAID array. But still I’m getting around 20MB/s which is OK.

Thank you to all the guys at forum, Jeff, vlad, davygravy, bohi, varkey, Gr3yh0und and others, your forum and blogs have been invaluable resources. Also a big thanks to the developers of OpenMediaVault, I really hope that their project is going to continue and get better and better, amazing work.

I’m happy to answer any questions, if I can, but best place to ask really is register at forum and ask there, other people may have same problem and be looking on Jeff’s forum.

If anyone from Seagate reads this, then yes I’d be happy to work as a consultant, build for you some decent software for your products.

Let me know of any feedback or errors, so that I can update this post.

Happy Debian’ing and NAS’ing:)

Resources and Sources

DonCharisma, LEDs on GoFlex Net –,13561

Davygravy’s rootfs, (Zyxel NSA320 : basic support for Debian installation) –,7806

How to extract a .tar.gz file -

Gr3yh0und on Debian/GoFlex Net –

Rescue System v2 –,3896

Dockstar Rescue Linux –

OMV on Pogoplug –

Debian Sources Mirrors Worlwide –

(In German) OMV on GoFlex –

USB when hard drives attached boot issue,,9398

Varkey on booting Debian from SATA GoFlex Net –

A post about setting up linux RAID1 –

A post about Inital Array Creation –

Preventing against a failing disk, RAID 10,f2 –

How to label linux partitions –

Chrooting –,9256,9957#msg-9957

Howto: Getting network LED working with firewall –,4638,4645

Howto: Create Debian rootfs image for your GoFlex/Dockstar via debootstrap on a Ubuntu/Debian PC –,5986,6221

GoFlex Net: Boot from USB while SATA disks connected –,9398

Full System Backup with rsync –

DockstarDebianSqueeze (In German) –

Front LED (In German) –

Newer uBoot as workaround to 3.2 kernel problem –,6965

OBIHOERNCHEN’S BLOG, Posts tagged GoFlex (see for LED info) –

Redirect stdin stdout to multiple files –

How can I send stdout to multiple commands? –

want leds to change to hard drive activity –

Ten(ish) steps to set up a dockstar –

Pogoplug root password (Linux Developers) –

Review Seagate FreeAgent GoFlex Net Media Sharing Device –

Linux Kernel 3.10.4 Kirkwood package and rootfs (Non Flattened Device Tree) –,12096

Use netconsole to troubleshoot uBoot without a serial cable –,14,14

Kernel install fails with Wheezy script –,9256

Howto: Getting network LED working with firewall –,4638

[How To] Use netconsole to troubleshoot Debian kernel booting –,9522

Proper LED Setup –

Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

50 thoughts on “Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault

  • maihoaomv

    i posted this exact same reply on the debian “Linux Device Hacking” forum so this is kinda sorta a duplicate. i hope it’s ok that i ask these questions here also. i may post this over on the omv forum also to see if i get toasted for asking. they may have just overlooked the armel stuff.

    i’ve had 0.4 running on the goflex home for a while. i like the new 0.5 version and am trying to install it to run on the gfh. i worked my way through the procedure an get as far as installing omv but it fails for unmet dependencies: php5-proctitle

    the php5-proctitle deb package is available for x64 and i386 but not armel. i found what I think is the source code for php5-proctitle on the omv site.

    any ideas how to get it to work with omv 0.5?
    is it possible to compile and package php5-proctitle on the goflex without having to cross-compile?
    any suggestions?
    any ideals?
    any help with compiling php5-proctitle?

    and i suspect php5-proctitle won’t be the only package that is missing for armel.

    root@GoFlexHome:~# apt-get install openmediavault
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:
    The following packages have unmet dependencies:
     openmediavault : Depends: php5-proctitle but it is not installable
    E: Broken packages
    • Don Charisma Post author

      Hey maihoaomv,

      Don’t worry about posting in multiple places, the info for this is very much distributed anyway and no one would blame:)

      Interestingly I had the *exact* same problem with OMV 0.5 in my attempt to install. In short the conclusion I came to was that it isn’t at this moment compatible with armel. ie I gave in, in favour of a working solution, against a distant perhaps possible solution.

      Solutions :

      1. Wait until Debian make php5-proctitle available for armel. You could pester them, maybe it’s almost done ?
      2. Ask OMV guys if they know a work around, or whether OMV would use a different package, or be hacked not to use php5-proctitle
      3. Compile to package yourself for armel … sorry I don’t know how to do this, but I suspect it’s possible, don’t know how hard or how long it would take. Only experience I have with Linux compilation is the reg.db for wireless, which wasn’t too difficult with a tutorial. There are guides I know on for recompile kernel, but don’t know if compiling the php5-proctitle package would be similar procedure. Best source of help with this probably

      Very hard to say at this stage whether php5-proctitle is the only obstacle, it was probably 5-6am when I gave in and didn’t plan on re-exploring !

      I will repost this and OMV forums, hopefully someone who knows more than me will chip in:)


      Don Charisma

  • maihoaomv

    Yea!!! I got openmediavault 0.5 sardaukar to work on the GoFlex Home. For some reason the /etc/collectd/collectd.conf file is not being correctly configured during installation of omv. I cheated and copied the contents of collectd.conf from the virtual machine into the collectd.conf on the GoFlex and the installation completed successfully.

    Once I had the WebGUI up and logged in I was able to do the minimum configuration. Samba, NFS, and SSH is working. I couldn’t get Plugins to work though. I get a communication error. Still don’t know why collectd isn’t configured correctly. Maybe someone on the omv forum can tell me.

    Thanks for your help and encouragement.

    • Don Charisma Post author

      My pleasure, glad you got it working. I’m sticking with my “stable” system for now!

      I had problems in the past with collectd on OMV 0.4, (however I think it was wheezy rather than squeeze) I had to abandon the install as it rendered it unbootable – did you check for reboot working yet?

      Communication error sounds resolvable, internet/network issue?

      Don Charisma

      • maihoaomv

        Reboots ok.

        FYI. I did a fresh install a second time. I noticed in the /etc/collected/collected.conf file that nearly all the config stuff was commented out including the hostname. I uncommented the hostname, restarted the install and it completed without further errors. I wonder if maybe there is a bug.

        Anyway I wasn’t able to get plugins to work. That’s a totally different problem. I noticed on the OMV forum someone else was having the exact same problem with not being able to see the plugins. Keeping my eye on that one. Maybe they will come up with a solution.

        • Don Charisma Post author

          So do you think it’s OMV or the deb package that are commenting out the hostname in /etc/collected/collected.conf (why I mentioned it was on wheezy I had the problem)

          For plugins I remember there being an extra repository to add (in sources), to get for instance mini-dlna to work (because I think plugins were “beta” versions). Have you checked this ?


          Don Charisma

          • maihoaomv

            Right now I’m thinking there may be something different between the ISO install and the package install in that the iso may be preconfigured. Whereas the way we did it doesn’t have the the advantage of of a preconfigured os already in place. Maybe somethig that was overlooked. Just a thought. I didn’t have any problem installing the iso in a VM. Was hoping someone on the OMV team might see a possible connection.

            I could never get minidlna to work with 0.4. Works beautifully with 0.5. I didn’t know about the extra repository. Didn’t put a lot of effort into trying to get it to work because I was using Logitech media server anyway for both squeeze box and DLNA music playback.


      • maihoaomv

        ok i tried it in a i386 vm. i chose debian-6.0.7-i386-netinst.iso (squeeze) as the base install os without installing graphics. I then installed openmediavault and with the exception of having to manually install postfix it ran all the way through to completion without failure. and as far as i got through the configuration it, omv working perfectly.

        well so much for that theory.

        however i did in the process find out why the arm version of squeeze fails for collectd configuration. the problem is the hostname as i suspected but the real reason it fails is there is an extra line in the /etc/hosts file that appears to be added during the installation of squeeze onto the hard drive (in the vm).

        i tried adding this extra line to the /etc/hosts on the goflex and it installed omv without failure (with the exception of php5 and php5-proctitle on course which can be preinstalled).

        in your instructions you talk about the /etc/hosts file as follows:

        root@debian-kirkwood-wide:~# cat /etc/hosts localhost
        ::1 localhost ip6-localhost ip6-loopback
        fe00::0 ip6-localnet
        ff00::0 ip6-mcastprefix
        ff02::1 ip6-allnodes
        ff02::2 ip6-allrouters

        on the goflex the following line needs to be added to the /etc/hosts file: GoFlexHome.localdomain GoFlexHome

        adding the line fixed the problem.

        root@GoFlexHome:~# cat /etc/hosts
        # This configuration file is auto-generated.
        # WARNING: Do not edit this file, your changes will be lost. localhost GoFlexHome.localdomain GoFlexHome

        # The following lines are desirable for IPv6 capable hosts
        ::1 ip6-localhost ip6-loopback
        fe00::0 ip6-localnet
        ff00::0 ip6-mcastprefix
        ff02::1 ip6-allnodes
        ff02::2 ip6-allrouters
        ff02::3 ip6-allhosts

        also note there is an extra line at the end of /etc/hosts that i presume was added during omv install.

        so in conclusion the difference between the i386 and the arm is that the i386 installer takes care of the /etc/hosts setup but in the arm version there probably is no installer as such so as a result /etc/hosts doesn’t get updated with the hostname.

        how is the arm os installed in the beginning? this might be a good question to ask on the doozan forum.

        it’s been fun (when i’m making progress) and frustrating at the same time but i learned a lot. now i need to tackle the problem with being unable to see the plugins and communication failure in the omv web gui.

        slowly but surely we are making progress with omv on arm but in the future if omv is to support all platforms then somewhere along the way the omv team needs to address these problems.


        • Don Charisma Post author

          Hey maihoaomv,

          Your experiences mirror mine, it’s frustrating at times, but rewarding in the end.

          I think the /etc/hosts line is missing because that needs to be set by you the user (davygravy didn’t know the name of your machine or what domain you’ll be in when he built the rootfs). So I think the answer will probably be something like, do you’re own fresh install then add a compatible kernel or compile the kernel yourself.

          For now I have a stable device, which took me a long time to get here, so I’m not making any changes. Possible that once OMV goes 0.6 stable then it might be worth trying with a wheezy install.


          Don Charisma

          • maihoaomv

            for me it’s a hobby. i was just wanting to see if i could get 0.5 to run on armel. and it does, mostly, very nicely. i’m sitting on pins and needles waiting for 0.6 omv to be released. wheezy at last, yea!!!!

            hopefully somewhere along the way volker will support armel. they are relatively inexpensive machines (with other advantages also), and since the release of raspberry pi, arm is starting to become quite popular.

            i bought the goflex to use on my home lan not realizing just how badly stock seagate sucked. cracking it was fun and made it much more versatile. arm is well supported in debian. it’s fairly easy to use, and with omv installed, makes samba and nfs a breeze to setup.

            over the years as the jobs changed i had been forced to move away from unix. when i retired i figured it was a good time to get back into it. in my opinion linux is so much more fun than windows. because there is more openness it’s easier to find answers on the internet. besides it gives the brain cells a challenge and helps to slow the creep of the cobwebs (i hope).

          • Don Charisma Post author

            About the same with the Seagate net, I was aware of stock firmware and possibility to change to debian before I bought TWO seagate goflex nets. I just like the lower power consumption, the two SATA ports and portability aspect most.

            I spent really a lot of time getting it up and running and have had multiple builds work then mysteriously fail, so I don’t want to experiment anymore, well at least not until there’s a good reason (and there’s time factors for me at present also). I can appreciate this is different for other people.

            Seagate software side of things generally sucks, I have Seagate Satellite also, and there’s been quite a few issues with it. For their hardware, it’s way better than the competition. I’ve had failed seagate hard drives but they have lasted way way longer than Western Digital, Samsung etc, the only other one that was any good was Toshiba, and I think they sold their hard drive business to seagate, or at least Tosh laptops seem to have Tosh branded seagate drives.

            Like you I’ve been around a bit in different jobs and used a variety of OS’es. Linux is much improved with commercial support on Ubuntu, and debian seems very stable now. For some mainstream things Microsoft seems better. But I reckon with all these copyright clampdowns they keep on having, Linux really has a massive opportunity to go much more mainstream. Reason I say this, is that if pirates can’t pirate software anymore, they aren’t suddenly going to magic money out of thin air, they will turn to open source alternatives. GIMP vs Photoshop, Ubuntu vs Windows … god knows how this will affect Apple, but they seem to have a little niche anyway.

            Good to chat, as and when I convert GoFlexNet2 to debian, I may update this post or write an additional one.

            Best regards

            Don Charisma

    • Don Charisma Post author

      Have to confess, I’ve never had yellow led …

      Please don’t panic and think about what you’re doing next. Every time I wasn’t able to boot from USB stick, I was able to use this procedure to revert to factory.

      The code looks fine for restoring the original uboot, which return it to the factory uboot. Did you get any error messages ? what were you trying to do before reverting to factory ? why did you want to revert to factory ?


      Don Charisma

  • Artur

    when start led blinking green ~10s, switch to amber. No ip adress no ssh router not view, no respond to pings

    when return it to the factory uboot: no erorr messages
    no logs :(

    Sorry poor english

    • Don Charisma Post author

      No worries for English, I know you’re doing your best.

      But please can you answer my questions, otherwise it’s difficult to help …

      * what were you trying to do before reverting to factory ?

      * why did you want/need to revert to factory ?


      Don Charisma

  • Artur

    why did you want/need to revert to factory:
    I not replalce usb stick when installing rescue system to original usb and on the rescue disk contiune install
    installing xmlstarlet_1.5.0-1 shutdown and not booting

    why did you want/need to revert to factory ?:
    i’m panic when no boot from usb. I thought I have to start over again

    • Don Charisma Post author

      Panic’ing them flashing not a good idea, I explained this early on and repeated the warnings in my post…before flashing you need to be 100% sure you’re doing the right thing.

      Rescue system allows you to boot without the USB stick attached and you can ssh into the GoFlex Net.

      If you’ve done a restore factory uBoot, then it should boot without USB stick attached.

      Have you tried all of these. Have you tried to create a new USB stick with davygravy’s rootfs on it (on a Ubuntu machine) ?

      The only way we can decide if it’s bricked is to try all the things we can think of first. Even if it’s not possible to boot, may be possible to get into it via serial cable or UART.


      Don Charisma

    • Don Charisma Post author

      No worries, my pleasure.

      I haven’t done anything with the serial cable, so can’t help with that. Hopefully you can get it sorted out.

      As I said to other people, once you get the GoFlex stable and how you want it, leave it that way !


      Don Charisma

  • maihoaomv

    Sounds like to me it may actually be running uboot but not finding any thing to boot from it hangs with the orange led blinking. I have my GoFLexHome set up to boot from either usb or hard drive. It starts out with the green led blinking then switches to blinking orange led for about 20+ seconds while it is trying to find something to boot from.

    If you have access to a linux machine why don’t you try putting a rescue rootfs on a usb flash and try booting it from that. Not sure what the name is but you should be able to find it on the doozan forum. Ask on the forum if you have to. Generally someone will be willing to help you. If that works and you can get ssh access then you should be able to fix it.

    Net console is ok if you don’t run into any problems. But if you, like me, were having problems after the kernel starts, the serial console is the only way you are going to be able to see what is going on. Getting it open without breaking it is the hard part. There are several guides on the internet that may help with installation of the serial cable.

    Hope it helps.


    • Don Charisma Post author

      Hope this can help Artur.

      What worries me is if the flashing to factory failed with the flash left in an inconsistent state.

      Hopefully it’ll be possible to unbrick it.



  • maihoaomv


    this may be what you can try to get it booted. there is no guarantee this will work so you do it at your own risk.
    i generally don’t use netconsole. it didn’t work that well for me. i prefer the serial console instead. with the serial you can see every step of the boot process. so i won’t be able to help you with netconsole.

    if you are interested in giving it a try, you can find the rescue rootfs here:

    not sure which one is which but start with this one first:

    you will need to be on a linux machine to do this. alternately you could boot your pc from a ubuntu or linux mint, doesn’t matter, install cd.

    plug the flash into a usb port. you will need at least a 512MB flash.
    open a terminal. at the command line type
    sudo blkid
    to find the flash. it most likely will be /dev/sdb1

    in the following i’m assuming that the flash is /dev/sdb1. be absolutely sure. otherwise you could ruin a partition on your hard drive. once you know which dev the flash is on type
    mkfs.ext3 /dev/sdb1
    that is assuming your flash is on /dev/sdb1. change sdb1 if needed.

    it will take a few seconds depending on the size to write the ext3 file system. once it completes add the rootfs label. type
    tune2fs -L rootfs /dev/sdb1

    mount the flash.
    mount /dev/sdb1 /mnt

    cd /mnt

    verify the label is rootfs. type
    sudo blkid

    you should see something similar to the following
    /dev/sdb1: LABEL=”rootfs” UUID=”8e266dda-027c-42fb-a439-69016b40f8e6″ TYPE=”ext3″

    NOTE: the label must be rootfs

    check to see if the file system was made. type

    you should see lost+found and nothing else

    download the tarball from the dropbox site onto the flash drive

    it’s a large file (58MB) so it will take a while to download

    now untar the file system onto the flash.
    tar -xvpf rootfs-br2012.02_06082012.tar .

    Don’t forget the period at the end. once tar has completed its job it should dump you back into the command line. type
    rm rootfs-br2012.02_06082012.tar
    NOTE: cache buffering can cause data not to be written to the flash. so sync’ing the cache is important to ensure all the data is written to flash before unmounting the flash.

    wait for the command line.
    verify file system was written to flash. type

    you should see the following

    bin dev home linuxrc mnt proc sbin tmp var
    boot etc lib lost+found opt root sys usr

    at the command line type
    sudo umount /mnt

    remove flash and plug it into the usb of the goflex. turn on the power and hopefully it will boot. you might try ping’ing it to see if you have network connectivity. if you can get ssh (or netconsole) access then you should be able to fix the problem.

    beyond that i’m lost.
    good luck

  • Artur

    Can you help me, I got the following message and UART boot:

    U-Boot 1.1.4 Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0

    U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00691750

    Soc: 88F6281 A1 (DDR2)
    CPU running @ 1200Mhz L2 running @ 400Mhz
    SysClock = 400Mhz , TClock = 200Mhz

    DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
    DRAM CS[0] base 0x00000000 size 128MB
    DRAM Total size 128MB 16bit width
    Addresses 8M – 0M are saved for the U-Boot usage.
    Mem malloc Initialization (8M – 7M): Done
    NAND:256 MB
    Flash: 0 kB

    CPU : Marvell Feroceon (Rev 1)

    Streaming disabled
    Write allocate disabled

    USB 0: host mode
    PEX 0: interface detected no Link.
    Net: egiga0 [PRIME]
    Hit any key to stop autoboot: 3 2 1 0

    NAND read: device 0 offset 0x100000, size 0x300000
    Reading data from 0x3ff800 — 100% complete.
    3145728 bytes read: OK
    ## Booting image at 00800000 …
    Image Name: Linux-
    Created: 2011-02-17 8:10:10 UTC
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 3236180 Bytes = 3.1 MB
    Load Address: 00008000
    Entry Point: 00008000
    Verifying Checksum … Bad Data CRC

  • artur

    Hi Don Charisma, Maihoaomv,

    Problem solved :D

    I booting from UART. After reinstall uboot, booting correctly from usb.

    I installed OMV :)

    Thank you for helpfulness

  • artur

    I do not know, uBoot reinstall solved problem.

    There is another problem:

    do not go to boot from hdd. when attached hdd, does not seem to

  • Robert


    Don ! Great Great work. Helped very much. THANK You!

    Only one line missing from your description:

    fw_setenv arcNumber 3089

    Without it no sata was recognised in dmesg either.


  • robert

    Hi Don!

    You a re amazing. (Can’t read as fast as you answer :)

    Sequence should be in step 7, when you write:
    “At this stage I attached an SATA hard disc and tried to boot from USB. No joy, doesn’t boot. ”
    Extend this to mention SATA not even appears in dmesg without that line.
    Probably you changed the kernel and as a part of that process, made this step, that’s why you forgot…
    Never mind…
    Thanks to keep document living!

    I have one question:
    How did you upgraded to wheeze?
    I tried distupgrade but stayed at Debian 6.0

    Regards Robert

  • Sammy

    Thanks for the excellent guide. Your time knee deep saved the rest of us :)
    I had trouble getting my stat recognized. Turns out I also was missing
    fw_setenv arcNumber 3089
    I think it should be added towards the end of step 7 after updating OMV before attaching sata drive.
    Thanks again!

  • Paul

    Hi Don,

    Great blog. I’m a complete newbie with Linux etc but willing to invest the time and give this a try as the Goflex Net fell just short of what I’m after (NAS that can work with time machine for Mac but can also act as a DLNA box for my Samsung Smart TV blue ray player).

    A couple of Q’s before I get started:
    1. Does your process leave the Pogoplug web interface intact? (Not the end of the world if it doesn’t, but I’ve seen a Pogoplug device hack that seems to leave the basic functionality intact.)
    2. Is it possible to setup the Goflex Net to act as a DLNA Server? If so what add-on would you recommend?

    Thanks for sharing your efforts and advice.

    • Don Charisma Post author

      You are welcome :)

      1. To my knowledge it’s revertible using the script to “Restore old uBoot” … but please do your own due diligence on before ploughing in !

      2. I installed mini-DLNA on a prior build, however the build broke before I tested it (due to SD card problems). It’s possible to install mini-DLNA via OMV but you need to add a special repository. This is explained on OMV forums. Otherwise it’s command line deb. So bottom line is that it’s possible, but I can’t tell you exactly how to do it as I’m not using it.

      Also check the links at the bottom, there are many useful blogs/sites from guys that are doing “stuff” with GoFlex Net and Dockstar.

      My system is and has been running without failure since prior to writing the article. I would recommend ditching the Flash drive at your earliest opportunity, they do fail. I have kept my Flash drive as it was when I built my build, so I can revert if necessary.

      RAID 1 works well although it does a weekly or monthly rebuild by default which isn’t really necessary. If you have the time and interest I would look at the RAID suggestion in my TODO list, it’s possible that you’d get a performance gain. My system gives around 20Mb/s which is OK for what I’m doing with it.

      Warm regards


  • BKrueger

    massive thanks for your work!

    I Just want to give a short feedback – since i had some trouble using the LEDs =).

    1. as some guys said already, there is one command missing:
    fw_setenv arcNumber 3089
    I set this var in the very end (before trying to install a sata drive) but i guess, you are not able to use sata/LEDs (you can control only the green one) before setting this variable correctly!

    2. The script which is used to show the cpu usage is not working properly. I just fixed the little awk bug, so that now only the real cpu idle value is taken into account.

    Just replace this part
    # Find the line with CPU info, pick the last number = percentage idle
    # subtract it from 100 to give CPU utilisation
    /..*..*..*..*..*..*/ { cpu_utilise = 100 – $6;
    if (cpu_utilise >= 20.0) { cpu20=”default-on”; }
    if (cpu_utilise >= 40.0) { cpu40=”default-on”; }
    if (cpu_utilise >= 60.0) { cpu60=”default-on”; }
    if (cpu_utilise >= 80.0) { cpu80=”default-on”; }
    # Find the line with CPU info, pick the last number = percentage idle
    # subtract it from 100 to give CPU utilisation
    /avg-cpu:/ {
    cpu_utilise = 100 – $6;
    if (cpu_utilise >= 20.0) { cpu20=”default-on”; }
    if (cpu_utilise >= 40.0) { cpu40=”default-on”; }
    if (cpu_utilise >= 60.0) { cpu60=”default-on”; }
    if (cpu_utilise >= 80.0) { cpu80=”default-on”; }

    cheerio and massive thx !!!