Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault This is posted on my blog, but thought it would be useful here too. Here's the link on my blog - http://doncharisma.org/2013/09/22/build-your-own-pro-nas-seagate-goflex-net-with-debian-linux-raid1-and-openmediavault/ Thanks to all the guys here for maintaining the forum and all of the invaluable information posted here, without it, I wouldn't have been able to do this:) Cheers, Don Charisma, http://DonCharisma.com FROM MY BLOG 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. [b]WHY?[/b] 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. [b]HOW?[/b] 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, www.doozan.com . 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. [b]But it's never as straightforward in real life is it ?[/b] 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, doncharisma.com Toolbox Tools Mandatory 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. Optional 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 - http://morschi.com/2012/10/05/seagate-goflex-net-debian/ Basically, you'll probably need to go to pogoplug website (https://goflexnet.pogoplug.com/) , 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 - http://download.pogoplug.com/dev/linux.html) In order to connect to GoFlex Net command line on ssh you'll need to either install an ssh client such as BitVise SSH (http://www.bitvise.com/ssh-client-download 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. [b]STEP 2 - Make a bootable "rootfs" on USB drive[/b] 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 (http://projects.doozan.com/debian/) from Doozan.com 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 doozan.com (http://forum.doozan.com/read.php?2,7806,7806,quote=1) download his package here - http://dl.dropbox.com/u/1015928/Kirkwood/rootfs_images/NSA320quickstart.tar.gz. You only need the "kirkwood-debian_rootfs.img" file, ignore the other files. [code] # to extract the archive in Ubuntu (or use WinRAR in Windows) tar -xvzf NSA320quickstart.tar.gz [/code] 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. [code] # 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 /media/debian cp -a /media/debian/* /mnt/umount /mnt umount /media/debian [/code] 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. [b]STEP 3 - Update the GoFlex Net inbuilt bootloader to boot from USB[/b] 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 [code] # Procedure from "http://projects.doozan.com/uboot/ cd /tmp wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh [/code] 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. [code] # Restore original uBoot wget http://download.doozan.com/uboot/files/uboot/uboot.mtd0.goflexnet.original.kwb flash_erase /dev/mtd0 0 4 nandwrite /dev/mtd0 uboot.mtd0.goflexnet.original.kwb [/code] [b]STEP 4 - First boot from USB[/b] 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 : [code] root@debian-kirkwood-wide:/# [/code] Do a: [code] uname -a [/code] 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 forum.doozan.com, 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. [b]STEP 5 - Install rescue system (optional but HIGHLY recommended)[/b] 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 : [code] cd /tmp wget http://jeff.doozan.com/debian/rescue/install_rescue.sh chmod +x install_rescue.sh ./install_rescue.sh [/code] 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. [b]STEP 6 - Install netconsole (optional but HIGHLY recommended)[/b] 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 - http://forum.doozan.com/read.php?3,14,14 Netconsole 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: [code] # 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 10.10.10.203 and my GoFlex Net is 10.10.10.231 fw_setenv serverip 10.10.10.203 fw_setenv ipaddr 10.10.10.231 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' [/code] On the desktop machine (Ubuntu - 10.10.10.203) [code] nc -u -l 6666 & nc -u 10.10.10.231 [/code] You'll need to reboot in order for these settings to take effect. I've got into the habit of doing this : [code] # for some linux installations sync shutdown -h now # or on some other linux installations sync halt [/code] Reason for doing this is to make sure any cached data is written to disk and propertly shutdown the operating system. [b]STEP 7 - Install OpenMediaVault to USB[/b] OpenMediaVault installation was fairly straightforward, although had to do some digging around on forums ! This thread - http://forums.openmediavault.org/viewtopic.php?f=12&t=514 on OMV forum is now out of date, but forms that basis of how to do it. [b]Update sources.list file[/b] 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. [code] vi /etc/apt/sources.list [/code] This is what yours will look like: [code] root@debian-kirkwood-wide:/# cat /etc/apt/sources.list deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free deb http://ftp.debian.org/debian/ squeeze main contrib non-free deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free [/code] As I'm based in Asia, this is what mine looks like after editing: [code] deb http://ftp.th.debian.org/debian-security/ squeeze/updates main contrib non-free deb-src http://ftp.th.debian.org/debian-security/ squeeze/updates main contrib non-free deb http://ftp.th.debian.org/debian/ squeeze main contrib non-free deb-src http://ftp.th.debian.org/debian/ squeeze main contrib non-free [/code] 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. [code] apt-get update apt-get upgrade apt-get install xmlstarlet [/code] Get xmlstarlet 1.5.0-1 and install it: [code] wget http://ftp.us.debian.org/debian/pool/main/x/xmlstarlet/xmlstarlet_1.5.0-1_armel.deb dpkg -i xmlstarlet_1.5.0-1_armel.deb [/code] Now do a HARD reboot, sync, shutdown and then power cycle. [code] sync shutdown -h now [/code] 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. [code] root@debian-kirkwood-wide:~# cat /etc/hostname debian-kirkwood-wide root@debian-kirkwood-wide:~# echo "GoFlexNet1" > /etc/hostname root@debian-kirkwood-wide:~# cat /etc/hostname GoFlexNet1 [/code] 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. [code] root@debian-kirkwood-wide:~# cat /etc/hosts 127.0.0.1 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 127.0.0.1 localhost 10.10.10.231 GoFlexNet1 ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters [/code] Now do a HARD reboot, sync, shutdown and then power cycle. [code] sync shutdown -h now [/code] 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 [code] echo "deb http://packages.openmediavault.org/public 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 [/code] 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 http://10.10.10.231 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 : [code] # USE CAUTION, updates internal flash fw_setenv usb_bootcmd 'run usb_init; setenv usb_root LABEL=rootfs; run usb_set_bootargs; run usb_boot' [/code] 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. [b]STEP 8 - Migrate your rootfs to SATA hard drive (optional)[/b] 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 [code] # 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 [/code] 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. [code] 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' [/code] Now that you've done that you can try to boot from the hard disk and it should work. [b]STEP 9 - Setup RAID1 (optional)[/b] 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 <a href="http://linuxconfig.org/linux-software-raid-1-setup">this guide</a> 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. [code] # list all partitions on disks sfdisk -l # check mounts, where rootfs is mounted mount -l [/code] 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. [code] #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 [/code] 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. [code] # create raid device (consider using --assume-clean) # mdadm --create md1 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3 [/code] 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 --metadata=0.90 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" [code] ls /dev #basic details of raid mdadm /dev/md127 #detailed details of raid # http://www.ducea.com/2009/03/08/mdadm-cheat-sheet/ mdadm --detail /dev/md127 #or cat /proc/mdstat [/code] Next we need to make the filesystem on the array [code] #make the file system ext3 mkfs.ext3 /dev/md127 [/code] Lastly as described here , label your array, I've called mine "raid1" [code] #label the raid 1 array # tune2fs -L raid1_data /dev/md127 [/code] 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 : [code] #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} [/code] 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. [b]STEP 10 - Do some cool stuff with the LEDS (optional)[/b] 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 -http://forum.doozan.com/read.php?2,13561. 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 : [code] # for iostat apt-get install sysstat [/code] Now we need to edit the /etc/rc.local file like so : [code] #!/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"; sda_prev="none"; sdb="none"; sdb_prev="none"; md1="none"; md1_prev="none"; cpu20="none"; cpu20_prev="none"; cpu40="none"; cpu40_prev="none"; cpu60="none"; cpu60_prev="none"; cpu80="none"; cpu80_prev="none"; cpu_utilise=0 } # 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" ); } sda_prev=sda; sda="none"; sdb_prev=sdb; sdb="none"; md1_prev=md1; md1="none"; cpu20_prev=cpu20; cpu20="none"; cpu40_prev=cpu40; cpu40="none"; cpu60_prev=cpu60; cpu60="none"; cpu80_prev=cpu80; cpu80="none"; } END { print "The end"; } ' & exit 0 [/code] 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 : [code] # Make it possible to not shut down network interfaces, # needed to use wake-on-lan netdown="-i" if [ "$NETDOWN" = "no" ]; then netdown="" fi # 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 } [/code] That's it your done, enjoy:) [b]APPENDIX - for reference, chrooting for kernel upgrade/change or troubleshooting[/b] This procedure was posted by tuxuser in doozan.com forums here - http://forum.doozan.com/read.php?2,9256,9957#msg-9957. 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. [code] # 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 https://dl.dropbox.com/sh/nwt2kbvetvgvroo/661x9b5PLg/Kirkwood/kernel/linux-image-3.3.2-kirkwood-dg_1.1_armel.deb?dl=1 -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 exit # Unmount chroot-environment umount /tmp/wheezy/dev/pts umount /tmp/wheezy/dev umount /tmp/wheezy/sys umount /tmp/wheezy/proc cd / umount /tmp/wheezy #Reboot init 6 [/code] [b]TO DO[/b] I'd like to get LEDs to respond to network traffic. I saw a post here - http://forum.doozan.com/read.php?2,4638,4645 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 - https://raid.wiki.kernel.org/index.php/Preventing_against_a_failing_disk. 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 - http://forum.doozan.com/read.php?2,9522,11046. I think I will try and add this as difficult to debug boot problems without it. [b]Confusion and Conclusion[/b] 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 doozan.com 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 doozan.com 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:) [url=http://DonCharisma.com]by Don Charisma[/url] [b]Resources and Sources[/b] DonCharisma, LEDs on GoFlex Net - http://forum.doozan.com/read.php?2,13561 Davygravy's rootfs, (Zyxel NSA320 : basic support for Debian installation) - http://forum.doozan.com/read.php?2,7806 How to extract a .tar.gz file - http://askubuntu.com/questions/25347/what-command-do-i-need-to-unzip-extract-a-tar-gz-file Gr3yh0und on Debian/GoFlex Net - http://morschi.com/2012/10/05/seagate-goflex-net-debian/ Rescue System v2 - http://forum.doozan.com/read.php?4,3896 Dockstar Rescue Linux - http://www.rudiswiki.de/wiki9/DockStarRescue OMV on Pogoplug - http://forums.openmediavault.org/viewtopic.php?f=12&t=514 Debian Sources Mirrors Worlwide - http://www.debian.org/mirror/list-full (In German) OMV on GoFlex - http://forums.openmediavault.org/viewtopic.php?f=12&t=2552 USB when hard drives attached boot issue, http://forum.doozan.com/read.php?3,9398 Varkey on booting Debian from SATA GoFlex Net - http://www.varkey.in/2011/06/boot-debian-from-sata-seagate-goflex-net/ A post about setting up linux RAID1 - http://linuxconfig.org/linux-software-raid-1-setup A post about Inital Array Creation - https://raid.wiki.kernel.org/index.php/Initial_Array_Creation Preventing against a failing disk, RAID 10,f2 - https://raid.wiki.kernel.org/index.php/Preventing_against_a_failing_disk How to label linux partitions - http://www.cyberciti.biz/faq/linux-partition-howto-set-labels/ Chrooting - http://forum.doozan.com/read.php?2,9256,9957#msg-9957 Howto: Getting network LED working with firewall - http://forum.doozan.com/read.php?2,4638,4645 Howto: Create Debian rootfs image for your GoFlex/Dockstar via debootstrap on a Ubuntu/Debian PC - http://forum.doozan.com/read.php?2,5986,6221 GoFlex Net: Boot from USB while SATA disks connected - http://forum.doozan.com/read.php?3,9398 Full System Backup with rsync - https://wiki.archlinux.org/index.php/Full_System_Backup_with_rsync DockstarDebianSqueeze (In German) - http://www.mikrocontroller.net/articles/DockstarDebianSqueeze Front LED (In German) - http://www.mikrocontroller.net/articles/Dockstar#Front_LED_ansprechen Newer uBoot as workaround to 3.2 kernel problem - http://forum.doozan.com/read.php?3,6965 OBIHOERNCHEN'S BLOG, Posts tagged GoFlex (see for LED info) - http://obihoernchen.net/wordpress/tag/goflex/ Redirect stdin stdout to multiple files - http://www.unix.com/unix-dummies-questions-answers/124609-redirect-stdin-stdout-multiple-files.html How can I send stdout to multiple commands? - http://unix.stackexchange.com/questions/28503/how-can-i-send-stdout-to-multiple-commands want leds to change to hard drive activity - http://archlinuxarm.org/forum/viewtopic.php?t=2899 Ten(ish) steps to set up a dockstar - http://archlinuxarm.org/forum/viewtopic.php?f=18&t=289 Pogoplug root password (Linux Developers) - http://download.pogoplug.com/dev/linux.html Review Seagate FreeAgent GoFlex Net Media Sharing Device - http://www.notebookcheck.net/Review-Seagate-FreeAgent-GoFlex-Net-Media-Sharing-Device.37033.0.html Linux Kernel 3.10.4 Kirkwood package and rootfs (Non Flattened Device Tree) - http://forum.doozan.com/read.php?2,12096 Use netconsole to troubleshoot uBoot without a serial cable - http://forum.doozan.com/read.php?3,14,14 Kernel install fails with Wheezy script - http://forum.doozan.com/read.php?2,9256 Howto: Getting network LED working with firewall - http://forum.doozan.com/read.php?2,4638 [How To] Use netconsole to troubleshoot Debian kernel booting - http://forum.doozan.com/read.php?2,9522 Proper LED Setup - http://dev.shyd.de/2012/01/kernel-3-1-10-ready-to-use/ https://forum.doozan.com/read.php?2,13630,13630#msg-13630 Thu, 05 Mar 2026 20:55:49 -0600 Phorum 5.2.23 https://forum.doozan.com/read.php?2,13630,72144#msg-72144 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,72144#msg-72144
- Samba for making attached USB HDD accessible from our home net
- Radicale for the family calendars https://radicale.org/
- smartmontools for periodic hdd health checks

Up to now rights management is nearly not existing (everyone in our home net can access hdd, and calendars ...) That's one point I want to take care of.
Thats something I expected advantages using OMV ...]]> Martin aus Dortmund Debian Sun, 04 Nov 2018 07:34:09 -0600 https://forum.doozan.com/read.php?2,13630,72139#msg-72139 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,72139#msg-72139
If you would like to install OMV on armv5 the easiest way is via softy script https://github.com/armbian/config. The script is optimised for armv7, however, some of the software installations work on armv5 out of the box, others do after some changes in the script.

I have tested OMV. It did install and was running fine, but most of the extra plugins would not work on armv5. Most of the management and tasks on the NAS I do via ssh anyway, so I have removed OMV as it was interfering with the apt install as well for some reason.

I have used the softy script to install TV headend, Syncthing, Transmission and MiniDLNA. Currently, all running nicely. The other software in the script I did not try. Docker and newer nodejs do not work on armv5. Back up your system before you use the script, uninstalling the software is not as straightforward.]]> garagoyun Debian Sun, 04 Nov 2018 04:41:19 -0600 https://forum.doozan.com/read.php?2,13630,71944#msg-71944 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,71944#msg-71944
EDIT: Second try with a cleaned up USB Stick and newly installed Debian 4.18-4 (I have made some backups of several stages of created USB sticks according to https://forum.doozan.com/read.php?2,12096,24034#msg-24034, that makes this an easy and fast job...)

Now I tried it without any changes.... no success.

Perhaps the "xmlstartlet" problem is not fixed, and the procedure mentioned here is necessary ....

Quote

Get xmlstarlet 1.5.0-1 and install it: 


wget http://ftp.us.debian.org/debian/pool/main/x/xmlstarlet/xmlstarlet_1.5.0-1_armel.deb
dpkg -i xmlstarlet_1.5.0-1_armel.deb

EDIT 2 Now I used serial console to shutdown dockstar

after 
shutdown -h now
on serial console, the setup on ssh console resumed 

[ ok ] Starting ftp server: proftpd.
here the setup was freezed, and continues after shutdown command ... 
Setting up php-xml (1:7.0+49) ...
Setting up xmlstarlet (1.6.1-2) ...
Setting up libpython-stdlib:armel (2.7.13-2) ...
Setting up libtevent0:armel (0.9.31-1) ...
Setting up collectd-core (5.7.1-1.1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/collectd.service -> /lib/systemd/system/collectd.service.

XMLStartlet seems to be quite ok ... concerning the version number ...


That seems to be a similar problem.
I dont think, that it is the correct solution to use elder versions.
I think I will drop my plan to use OMV on Dockstar, perhaps it is really too memory demanding ...

https://forum.doozan.com/read.php?2,61959,page=2]]> Martin aus Dortmund Debian Fri, 02 Nov 2018 04:15:44 -0500 https://forum.doozan.com/read.php?2,13630,71939#msg-71939 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,71939#msg-71939 https://forum.openmediavault.org/index.php/Thread/21234-Install-OMV4-on-Debian-9-Stretch/

erasmus is for debian 8 and arrakis for debian 9.

I didnt try arrakis for the moment, but i got running erasmus on debian 8 (Jessie) on the GFN some month ago.
I think it was Jessie:
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with kernel 4.11.3]]> joerg_999 Debian Fri, 02 Nov 2018 03:15:51 -0500 https://forum.doozan.com/read.php?2,13630,71934#msg-71934 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,71934#msg-71934
https://openmediavault.readthedocs.io/en/latest/installation/on_debian.html


/etc/apt/sources.list.d/openmediavault.list looks like that 

deb http://packages.openmediavault.org/public arrakis main
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis main
## Uncomment the following line to add software from the proposed repository.
deb http://packages.openmediavault.org/public arrakis-proposed main
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis-proposed main
## This software is not part of OpenMediaVault, but is offered by third-party
## developers as a service to OpenMediaVault users.
deb http://packages.openmediavault.org/public arrakis partner
# deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis partner

afterwards invoked 

export LANG=C
export DEBIAN_FRONTEND=noninteractive
export APT_LISTCHANGES_FRONTEND=none
apt-get update
apt-get --allow-unauthenticated install openmediavault-keyring
apt-get update

... then 

apt-get --yes --auto-remove --show-upgraded \
    --allow-downgrades --allow-change-held-packages \
    --no-install-recommends \
    --option Dpkg::Options::="--force-confdef" \
    --option DPkg::Options::="--force-confold" \
    install postfix openmediavault

At that step the download-and-install-magic should take place, but there are two points with problems, the last one freezes the installation

First one does not freeze the installation process 

...
systemd/system/smartd.service.
[....] Not starting S.M.A.R.T. daemon smartd, disabled via /etc/default/smartmontoo[warn. (warning).
Setting up mdadm (3.4-4+b1) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
...

But this here does 

Warning: The home dir /run/proftpd you specified can't be accessed: No such file or directory
Adding system user `proftpd' (UID 111) ...
Adding new user `proftpd' (UID 111) with group `nogroup' ...update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
...kGPPwU1V
Not creating home directory `/run/proftpd'.
Adding system user `ftp' (UID 112) ...
Adding new user `ftp' (UID 112) with group `nogroup' ...
Creating home directory `/srv/ftp' ...
'/usr/share/proftpd/templates/welcome.msg' -> '/srv/ftp/welcome.msg.proftpd-new'
[ ok ] Starting ftp server: proftpd.
...
At that point the installation freezes



A check done by opening a second ssh console shows that /run/proftpd is existing ...

After "shutdown -h now" and cycling power, the system is not longer accessible by ssh, serial console reports... 

root@debian:~# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 20  bytes 1320 (1.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 1320 (1.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

no more network connections ...]]> Martin aus Dortmund Debian Fri, 02 Nov 2018 02:53:21 -0500 https://forum.doozan.com/read.php?2,13630,56539#msg-56539 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56539#msg-56539
> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:17:19-0700)
> Seagate GoFlex Net

You've installed u-boot but did not flash the default envs image.

Quote

8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8).

As described in step 1, u-boot envs must be defined in /etc/fw_env.config as

# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

This default envs image supports booting with multiple disk drives (and hubs) attached. The disk drives could be any type (usb, sata, sd card). The scanning logic and default envs were set to automatically boot the box with the following required configuration:

For whatever reason, if you can't set up your configuration to satisfy the following 4 requirements, then don't flash this defaut envs image. It might not boot properly. In this case, section C below can be used to tailor the envs to your specific configuration.

r1. There must be only one partition among all partitions from all drives that contains the kernel files. The 2 kernel files are /boot/uImage and /boot/uInitrd.
r2. The partition that contains the 2 kernel files must be partition 1 in a disk drive
r3. The partition that contains the rootfs must be labeled rootfs
r4. The rootfs partition is recommended to be type Ext3 (this is not a hard requirement, ext4 should boot OK, but Ext3 will ensure no problem).

So the bottom line is if you have only one rootfs in a single Ext3 partition, which is labeled as rootfs, then you're all set.

a. Download the default u-boot envs at Dropbox:

uboot.2016.05-tld-1.environment.bodhi.tar
md5:
3823eef10011b864859d31a76470e0e3
sha256:
c8db95a4225e8d78bdaaaa372bd5a87e4b98f3448dd9c62fc96c72b2df1a997c

.....

So to set the envs to correct default values, see this post:
https://forum.doozan.com/read.php?3,33935,33992#msg-33992

Since you are running GoFlex Net these 2 variables are different, modify those in the uEnv.txt. 
devices=usb ide
dtb_file=/boot/dts/kirkwood-goflexnet.dtb

After you've booted into Debian, you can flash the default envs image, and adjust the envs according to your box (as instructed).]]> bodhi Debian Mon, 09 Apr 2018 15:34:42 -0500 https://forum.doozan.com/read.php?2,13630,56529#msg-56529 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56529#msg-56529 - reinstalled 3.3.2 -> all OK (serial and ssh)
- from there updated u-boot to 2017.07 -> Ok
- rebooted 3.3.2 all working
- Tried rootfs Debian-4.12.1 but stopped with this log:

============ 
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:17:19 -0700)
Seagate GoFlex Net

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  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... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=3", size 219 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1743, bad PEBs: 9, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 1708, total reserved PEBs: 35, PEBs reserved for bad PEB handling: 31
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 691 ms (0 Bytes/s)
Found bootable drive on usb 0:1
3821592 bytes read in 941 ms (3.9 MiB/s)
7245696 bytes read in 969 ms (7.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 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
   Loading Kernel Image ... OK
   Loading Ramdisk to 07424000, end 07b0cf40 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


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


Available machine support:


ID (hex)	NAME

ffffffff	Generic DT based system

ffffffff	Marvell Kirkwood (Flattened Device Tree)


Please check your kernel config and/or bootloader.

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

printenv produce: 

GoFlexNet> printenv
arcNumber=3089
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:26:73:39
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2342/131068 bytes
GoFlexNet>

===========
Have I omitted something ?
Thanks for help

-----
moderator: please use code tags (formatted code button) to post logs.]]> Oscar Debian Mon, 09 Apr 2018 08:58:04 -0500 https://forum.doozan.com/read.php?2,13630,56484#msg-56484 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56484#msg-56484 -------------------------------------------------------
> 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.
>
I supposed that will be a 20 MBps write to the RAID on a Seagate GoFLEX NET unit. In that case, I reckon that will be the bottleneck on the GoFLEX NET unit.

I recently setup my Seagate GoFLEX Home using a Seagate 3 TB SATA HDD as a local NAS with NFS and am only able to get up to 45/18 MBps R/W, respectively, to my NAS on my Gigabit LAN. My 3 TB SATA HDD is capable of 45+ MBps write and am hoping to get at least 40 MBps write. I tried to increase the wsize to 32678 on my Linux desktop computer, but mount on my Linux desktop computer always shows wsize=16384. Unfortunately, I am aware of if there is something I can tweak on my Seagate GoFLEX Home unit to increase the write throughput. I just hope some of you who manage to get a 40+ MBps write throughput on your NAS will be able to chime in. So far, this is rather disappointing.]]> habibie Debian Sun, 08 Apr 2018 11:06:43 -0500 https://forum.doozan.com/read.php?2,13630,56464#msg-56464 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56464#msg-56464
> After installed netconsole (point 6) I have lost
> my SSH. On serial I see my GFN but I cant reach
> it. Nmap say my host is down. Any suggestion to
> resolve this.

With serial console attached, power up, let it try to boot. And post the entire serial console log here.]]> bodhi Debian Sun, 08 Apr 2018 03:07:54 -0500 https://forum.doozan.com/read.php?2,13630,56449#msg-56449 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56449#msg-56449 many thanks.
After installed netconsole (point 6) I have lost my SSH. On serial I see my GFN but I cant reach it. Nmap say my host is down. Any suggestion to resolve this.
Thanks. Ciao
P.S. I started my installation with "kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.goflexnet.mtd0.kwb -p" and all goes well (tried also rescue system) .... until netconsole installation]]> Oscar Debian Sun, 08 Apr 2018 02:39:37 -0500 https://forum.doozan.com/read.php?2,13630,56439#msg-56439 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56439#msg-56439
You could also use a newer jessie rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and install OpenMediavault.
https://forum.doozan.com/read.php?2,12096

Also try stretch rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 in that release thread to see if OpenMediavault can be run on it.]]> bodhi Debian Sat, 07 Apr 2018 16:14:19 -0500 https://forum.doozan.com/read.php?2,13630,56294#msg-56294 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56294#msg-56294 davygravy Dropbox public folder

Perhaps may help someone
Ciao]]> Oscar Debian Fri, 06 Apr 2018 05:58:38 -0500 https://forum.doozan.com/read.php?2,13630,56289#msg-56289 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,56289#msg-56289 want to try this hack but link to rootfs from davygravy's is died and I'm not able to found the "kirkwood-debian_rootfs.img" file that was in the package.
Someone could help me ?
Many thanks]]> Oscar Debian Fri, 06 Apr 2018 05:11:09 -0500 https://forum.doozan.com/read.php?2,13630,38964#msg-38964 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38964#msg-38964
> i search every packages as deb armel and installed
> it with dpkg - now i' m able to login

When you have the error above, you should reconfigure dpkg, clean, and do apt-get update. And install.

Basically, forcing install packages like you did will work, but it is not the right way.]]> bodhi Debian Sun, 15 Oct 2017 15:44:53 -0500 https://forum.doozan.com/read.php?2,13630,38954#msg-38954 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38954#msg-38954 lexa Debian Sun, 15 Oct 2017 13:09:13 -0500 https://forum.doozan.com/read.php?2,13630,38949#msg-38949 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38949#msg-38949
The following packages have unmet dependencies:
openmediavault : Depends: php5-pam but it is not going to be installed
Depends: scponly but it is not installable
E: Unable to correct problems, you have held broken packages.]]> lexa Debian Sun, 15 Oct 2017 11:27:21 -0500 https://forum.doozan.com/read.php?2,13630,38419#msg-38419 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38419#msg-38419 -------------------------------------------------------
> I search for wheezy, i online found 3.17 the
> 3.18.5 is already jessie.

Right! I remember incorrectly.]]> bodhi Debian Wed, 11 Oct 2017 16:16:04 -0500 https://forum.doozan.com/read.php?2,13630,38409#msg-38409 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38409#msg-38409 lexa Debian Wed, 11 Oct 2017 12:26:00 -0500 https://forum.doozan.com/read.php?2,13630,38334#msg-38334 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38334#msg-38334 lexa Debian Mon, 09 Oct 2017 13:42:14 -0500 https://forum.doozan.com/read.php?2,13630,38269#msg-38269 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38269#msg-38269
OMV works well only in wheezy, not even jessie, IIRC.

Are you running the stretch rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 ? you might want to try older rootfs:

jessie:
Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

wheezy:
Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2


The errors you saw could be that some OMV packages are not in stretch yet.]]> bodhi Debian Sun, 08 Oct 2017 15:19:48 -0500 https://forum.doozan.com/read.php?2,13630,38264#msg-38264 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,38264#msg-38264
I made a new system and got a Error by openmediavault. 

root@debian:~# 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-fpm but it is not installable
                  Depends: php5-cgi but it is not installable
                  Depends: php5-cli but it is not installable
                  Depends: php5-pam but it is not going to be installed
                  Depends: openssh-blacklist-extra but it is not installable
                  Depends: php5-proctitle but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

can you help me]]> lexa Debian Sun, 08 Oct 2017 15:13:08 -0500 https://forum.doozan.com/read.php?2,13630,26900#msg-26900 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,26900#msg-26900 Luigi Debian Wed, 23 Mar 2016 10:13:29 -0500 https://forum.doozan.com/read.php?2,13630,24707#msg-24707 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,24707#msg-24707
Quote
rmleonard
Do you have an updated openmediavault install posting?

(Your original spoke of version 0.4 and iirc 2.xx is the current)

The current version seems to be in the apt sources...
(But will that work correctly?)

I've been gifted a goflex net (not sure if it works)...
So I need to find out why it doesn't have a web page, and then.. omv seems to be where i'd like its destiny to lie...(or maybe Amahi, or Tonido, or the like)

In the past 2 years, any new thoughts on the workings of the little pogoplug?

@rmleonard PM'ed me this, and I felt the answers where relevant publicly, so have answered so ...

1. "Do you have an updated openmediavault install posting? "

No, it was never my intention to maintain this, nor do I have the resources. I'd of course welcome anyone who wanted to take it over into a github, etc ... offers ?

2. "The current version seems to be in the apt sources"

If it's in apt-sources, then great, Debian repo is often very well maintained, so that may work better than trying to do it yourself ...

3. "In the past 2 years, any new thoughts on the workings of the little pogoplug?"

I think "little" is the operative word. 128MB memory is pretty small ... however the GoFlexNet/Pogoplug do run for years without crashing, and all drawing virtually no power, running virtually on fresh air ! So for the right application(s), which is still a large area, GoFlexNet and Pogoplug etc, still great fun and totally useable.

Since learning more about Linux, and Debian, I've tended to do more of my stuff on command line, so OMV I'm not using anymore. Not because it's "not great", but just that my personal usage evolved, to where I don't need a NAS type interface. I can build RAID arrays on command line or create NFS shares, etc ...

I bought a couple of Odroid devices, which has been my progression in ARM. They have faster CPUs, more cores and more memory, and the hardware is more accessible. They do also have their drawbacks, I've had some major issues getting enough power to peripherals, which I seem to have resolved now.

Overall, anything I've done on ARM/embedded takes more time, and is more challenging than anything on Intel/PC platform. The advantage of ARM is cost, low power consumption and arguably long term stability as CPUs often run without coolers ...

Another recent purchase was two Asrock mini-itx motherboards with Intel CPUs, which I find a lot easier to get software working on than ARM based devices. Also Intel now have the compute stick, and some small form factor PCs, which are more expensive than ARM gear, but probably save a lot of time ...

Lastly, I think the main "value" in doing anything with any of these devices in not in what you achieve, but in what you learn along the way.

Cheers

Don Charisma]]> DonCharisma Debian Sun, 29 Nov 2015 04:04:11 -0600 https://forum.doozan.com/read.php?2,13630,23971#msg-23971 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,23971#msg-23971
http://doncharisma.org/2013/09/22/build-your-own-pro-nas-seagate-goflex-net-with-debian-linux-raid1-and-openmediavault/

cheers]]> DonCharisma Debian Mon, 28 Sep 2015 16:35:19 -0500 https://forum.doozan.com/read.php?2,13630,22809#msg-22809 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,22809#msg-22809 Saverio Debian Mon, 20 Jul 2015 06:57:30 -0500 https://forum.doozan.com/read.php?2,13630,21507#msg-21507 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,21507#msg-21507 -------------------------------------------------------
> I've got OMV running on my Pogoplug Pro / V3 with
> bodhi's 3.18.5. rootfs. I posted a brief demo on
> Youtube here:
> https://www.youtube.com/watch?v=v4VHeI43yGI . It
> works surprisingly well IMO.

Wow THANKS for that.]]> JoeyPogoPlugE02 Debian Sun, 26 Apr 2015 17:06:59 -0500 https://forum.doozan.com/read.php?2,13630,21456#msg-21456 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,21456#msg-21456 https://www.youtube.com/watch?v=v4VHeI43yGI . It works surprisingly well IMO.]]> LeggoMyEggo Debian Fri, 24 Apr 2015 07:45:53 -0500 https://forum.doozan.com/read.php?2,13630,20190#msg-20190 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,20190#msg-20190
Cheers]]> DonCharisma Debian Wed, 04 Mar 2015 22:50:46 -0600 https://forum.doozan.com/read.php?2,13630,20189#msg-20189 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,20189#msg-20189
One thing I forgot to do when I set mine up was to add in the swap partitions. With mdadm, at boot, an fsck on a RAID array can fail due to not having enough memory. So it's *essential* to create the swap if you're using RAID, and these do need adding to /etc/fstab ... This was my solution to a similar issue I was having.

If you're booting off a flash device it's possible there's an issue with the flash drive your using. So might be worth trying a different flash device. Or even SATA booting.

And lastly, (or maybe firstly actually !) have a dig around in the logs, setup the netconsole or even better serial cable - that way you might find out actually what the problem is. Simply saying "it doesn't boot" isn't enough information to provide accurate solutions ...

PS always do a "sync" before your do a reboot ... or indeed unmount or eject a flash drive ... that way you're sure data has been written to the device.

Cheers]]> DonCharisma Debian Wed, 04 Mar 2015 22:42:27 -0600 https://forum.doozan.com/read.php?2,13630,20147#msg-20147 Re: Build your own Pro NAS – Seagate Goflex Net with Debian Linux, RAID1 and OpenMediaVault https://forum.doozan.com/read.php?2,13630,20147#msg-20147
I have managed it to do the same.
Runs absolutely stable.
With 2x 3,5 inch harddrives as Raid1. (With extra Wires for supplying the Disks with 12 Volt too)
I have approx. 35 MB/s Read and 35 MB/s Write performance.

The only problem is, when i want to reboot this thing.

If i am doing it via "reboot" -> The system hangs
"shutdown -r 0" -> Sometimes works, but sometimes hangs too. (50% ?!?)

Is there a newer Image for the USB Stick, i can try ?
(Propably one, that can be upgraded "in Place")

Br,]]> hollari Debian Mon, 02 Mar 2015 07:40:35 -0600