Install Debian on Seagate GoFlex's hard drive

Ok. So I am a noob when it comes to uboot/netconsole, etc. However, I can follow instructions if I can find them! I previously had installed Arch Linux on my GoFlex following the instructions over at their forums. So, on the hard disk that comes with the device, I had 2 partitions. One that held the Arch OS and the other that held my data. However, one fine day, the GoFlex base unit decided to conk. I managed to get a new base unit from ebay. What I plan to do now, is to install Debian on the partition that holds the Arch OS. I am looking at this script. As far as I can tell this will install Debian on a USB flash drive. But I'd be much happier running it off the hard disk instead.



Edited 1 time(s). Last edit at 06/05/2015 12:08AM by dips0502.

dips0502,

What you can do to run Debian is to create Debian rootfs on a USB stick. And then install my released u-boot.

So with the new GoFlex (is this GF Home or GF Net?), you will need to boot into the stock Pogo OS and install u-boot from there.

In summary:

- Create Debian rootfs on USB stick (worry about the hard disk installation later). Use a different Linux box to do this, as root.
- Login to Pogo OS. And install new u-boot from there
- Plug in the new Debian USB rootfs.
- Boot

After successfully running Debian, then transfer the rootfs from USB to the HDD partition where Arch rootfs is (it is simple: erase Arch files and cp -aR from the USB Debian rootfs).

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

Installing new u-boot from there seems a bit daunting. Is it alright if I do it from the uBoot install script here

And it is the GoFlex Home



Edited 1 time(s). Last edit at 06/05/2015 11:16AM by dips0502.

dips0502,

> Installing new u-boot from there seems a bit
> daunting. Is it alright if I do it from the uBoot
> install script
> here
>
> And it is the GoFlex Home

It is OK to run install_uboot_mtd0.sh to install older u-boot. It should work fine for the GF Home. However, be aware that it is older so it lacks some modern features. And you will need to select GoFlex Net version (there is no older version of GoFlex Home u-boot). It is almost the same, but the LED control is different, therefore it will not work correctly on Goflex Home.

You can follow the same steps I've laid out above, and run this script to install u-boot in lieu of using the manual procedure to install new u-boot.

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

I am at the step that says:

2. Make sure ethaddr is set in uBoot env. It must be set before rebooting the system. This version will look for the ethaddr, and will not bring up the network if it can't find it.
fw_printenv ethaddr
If you don't have fw_printenv/fw_setenv, then you are running either stock Pogo OS, or earlier version of Arch Linux ARM. The correct tool to use in this case is blparam in your system.

So, I do:
./blparam ethaddr

And it gives me this:

MTD: /dev/mtd0
type: 4
flags: 0x400
size: 1048576
erase size: 131072
write size: 2048
oob size: 64
-- Writing parameter 'baudrate=115200'
-- Writing parameter 'loads_echo=0'
-- Writing parameter 'ipaddr=169.254.254.253'
-- Writing parameter 'serverip=169.254.254.254'
-- Writing parameter 'rootpath=/mnt/ARM_FS/'
-- Writing parameter 'netmask=255.255.0.0'
-- Writing parameter 'run_diag=yes'
-- Writing parameter 'CASset=min'
-- Writing parameter 'MALLOC_len=1'
-- Writing parameter 'ethprime=egiga0'
-- Writing parameter 'bootargs_end=:::DB88FXX81:eth0:none'
-- Writing parameter 'image_name=uImage'
-- Writing parameter 'standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end)

$(mvPhoneConfig); bootm 0x2000000;'
-- Writing parameter 'ethmtu=1500'
-- Writing parameter 'usb0Mode=host'
-- Writing parameter 'nandEcc=1bit'
-- Writing parameter 'netretry=no'
-- Writing parameter 'rcvrip=169.254.100.100'
-- Writing parameter 'loadaddr=0x02000000'
-- Writing parameter 'autoload=no'
-- Writing parameter 'ethact=egiga0'
-- Writing parameter 'rtc_mode=active'
-- Writing parameter 'vm_ver_smt=2.0.0'
-- Writing parameter 'explrpk=PGRT-BNCP-EXDA-ZPGA'
-- Writing parameter 'explrsn=NA1Y80F9'
-- Writing parameter 'asm1_tag=10:11:09:02:04:35:21'
-- Writing parameter 'stdin=serial'
-- Writing parameter 'stdout=serial'
-- Writing parameter 'stderr=serial'
-- Writing parameter 'mainlineLinux=no'
-- Writing parameter 'enaMonExt=no'
-- Writing parameter 'enaCpuStream=no'
-- Writing parameter 'enaWrAllo=no'
-- Writing parameter 'pexMode=RC'
-- Writing parameter 'disL2Cache=no'
-- Writing parameter 'setL2CacheWT=yes'
-- Writing parameter 'disL2Prefetch=yes'
-- Writing parameter 'enaICPref=yes'
-- Writing parameter 'enaDCPref=yes'
-- Writing parameter 'sata_dma_mode=yes'
-- Writing parameter 'netbsd_en=no'
-- Writing parameter 'vxworks_en=no'
-- Writing parameter 'bootdelay=3'
-- Writing parameter 'disaMvPnp=no'
-- Writing parameter 'pcieTune=no'
-- Writing parameter 'bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs'
-- Writing parameter 'console=console=ttyS0,115200'
-- Writing parameter 'bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000'
-- Writing parameter 'enaAutoRecovery=no'
-- Writing parameter 'rtc_tz=PST'
-- Writing parameter 'ntp_default=pool.ntp.org'
-- Writing parameter 'smt_tag=10:11:09:02:04:36:56'
Erasing 128 kb @ 0xa0000
Writing 2048 kb @ 0xbf800
***
*** BOOT LOADER PARAMETERS CHANGED -- REBOOT NECESSARY TO TAKE EFFECT!

Should I reboot? Am not sure how to proceed from here.

dips0502,

No. Don't reboot. To list the envs, blparam must be run with no parameter.

This command

./blparam ethaddr

has erased the ethaddr. So find your MAC address either in old log or bottom of the Pogo and re-enter it:

./blparam ethaddr xx:xx:xx:xx:xx > /dev/null

After that, list all envs:

./blparam

or list ethaddr

./blparam | grep ethaddr

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



Edited 1 time(s). Last edit at 06/06/2015 03:56AM by bodhi.

Ran this with my MAC address -

/blparam ethaddr xx:xx:xx:xx:xx:xx > /dev/null

There was no error returned.

However,

./blparam | grep ethaddr

returns nothing.

dips0502 Wrote:
-------------------------------------------------------
> Ran this with my MAC address -
>

/blparam ethaddr xx:xx:xx:xx:xx:xx >
> /dev/null

>
> There was no error returned.
>
> However,

./blparam | grep ethaddr

> returns nothing.

Try running without redirecting to /dev/null. This time use the single quotes, to see if there was error:

./blparam ethaddr 'xx:xx:xx:xx:xx:xx'

But don't worry abou this, you can enter it later after flashing default set of u-boot envs during installation steps.

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



Edited 1 time(s). Last edit at 06/06/2015 04:30AM by bodhi.

Ok. Finally! Turns out, this is what I needed -

blparam ethaddr=00:10:75:29:a7:1b

Quick question - Do I flash the default set of u-boot envs after flashing uboot or before?

dips0502 Wrote:
-------------------------------------------------------
> Ok. Finally! Turns out, this is what I needed -
>

blparam ethaddr=00:10:75:29:a7:1b

>
> Quick question - Do I flash the default set of
> u-boot envs after flashing uboot or before?

Ah. I've mixed up the syntax. Flash it after or before does not matter. But all the steps must be followed sequentially, so it would be after.

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

Ok. So I have flashed uboot and the default environment variables. fw_printenv prints the variables without any errors. The last thing to do is to modify certain u-boot variables using fw_setenv. But I cant seem to find this binary.

wget http://download.doozan.com/uboot/fw_setenv

returns not found

Got it.

cp fw_printenv fw_setenv

Edited 2 time(s). Last edit at 06/06/2015 08:24AM by dips0502.

I am almost done. I am at the step which asks to restore the 3 envs using the saved envs

fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv rootfstype 'xxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

But since I am flashing from a stock GoFlex Home, when I saved the environment variables with the blparam binary, there was no mtdparts defined and rootfstype was 'ubifs'.

The current value for these variables are:

rootfstype=ext3
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

I guess I should be keeping these. Just need a confirmation.

dips0502,

> The current value for these variables are:
>

> rootfstype=ext3
> mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage)
> ,32M(rootfs),-(data)
>

>
> I guess I should be keeping these. Just need a
> confirmation.

Yes, it looks good. That's the correct mtdparts. And remmeber when you created the rootfs on USB stick, the instruction said use Ext3. So if you did that then this env rootfstype is correct. Also make sure the ethaddr was set to your MAC address.

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



Edited 1 time(s). Last edit at 06/06/2015 11:29AM by bodhi.

bodhi,

Thanks for all the help. Here is my netconsole output. I was able to boot into Debian and login. Does this look all correct?
Now all I need is to transfer the rootfs onto the GoFlex drive.

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'mmc' - try 'help'

Reset IDE: ide_preinit failed

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

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

no IDE devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2876051 bytes read in 392 ms (7 MiB/s)
6535284 bytes read in 496 ms (12.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2015-06-05  14:26:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2875987 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

dips0502,

Cool! everything looks great. The warning messages were expected, since you only have USB drive (no HDD or SD).

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



Edited 1 time(s). Last edit at 06/06/2015 01:38PM by bodhi.

I connected my hard disk to the SATA slot and attempted to boot the device. It boots, the green light is constant. However, it doesnt get an IP address from my router. After a network scan for the device on the network, it doesnt show up. However, if I remove the hard disk and boot only with the usb, it become available on the network. Here are the netconsole outputs for the 2 cases:

With only usb pen drive attached:

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'mmc' - try 'help'

Reset IDE: ide_preinit failed

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

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

no IDE devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2876051 bytes read in 393 ms (7 MiB/s)
6535284 bytes read in 495 ms (12.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2015-06-05  14:26:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2875987 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

With the hard disk in the SATA slot:

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:04:12)
Seagate GoFlex Home
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'mmc' - try 'help'

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: ST2000DL001-9VT156 Firm: CC96 Ser#: 5YD0QP8P
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)

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

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

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

Part    Start Sector    Num Sectors     UUID            Type
  1     62              39082258        cab70c80-01     83
  2     39082320        -427034986      cab70c80-02     83
loading envs from ide 0 ...
** File not found /boot/uEnv.txt **
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2876051 bytes read in 392 ms (7 MiB/s)
6535284 bytes read in 496 ms (12.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2015-06-05  14:26:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2875987 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

dips0502,

Take a look at this post. I explained the booting process with multiple drives:
http://forum.doozan.com/read.php?3,19093

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

I tried to read this and understand, but its going over my head.
I copied the rootfs from the usb drive to the hard disk exactly like you said. And then attempted to boot from only the hard disk. (Removed the USB). However, it doesn't boot. Only a soild green light and then no network activity. Is there a way to monitor kernel messages over netconsole? Currently I do not see anything after 'Starting kernel ...'

dips0502,

This is the rootfs mounting problem. Make sure the following were done:

- There is only one partition on the HDD. And this partition is labeled rootfs. This partition should be type Ext3.
- The copying command cp -aR were executed while you are root user (not sudo). The copying must be done on a different Linux box.

Try booting after you've made adjustments as above. If it does not boot into Debian, then we might need to look at u-boot envs. So it is best that you post the listing of

fw_printenv

Notes:

It is possible to have multiple partitions, and to use different filesystem such as Ext4, but u-boot envs must be set to reflect those settings.

netconsole always stops output when kernel is starting. It is possible to output more, but the booting process must get passed the rootfs mounting phase, and some set up must be done after Debian is already running.

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

Ah..I see. There are actually 2 partitions on the HDD. Both are of type ext3. I thought if I labeled the partition holding rootfs as 'rootfs', it'll do.

Here is the fw_printenv output -

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

dips0502,

> Ah..I see. There are actually 2 partitions on the
> HDD. Both are of type ext3. I thought if I labeled
> the partition holding rootfs as 'rootfs', it'll
> do.

Exactly! if there is one partition then the partition label is not that important. When there are more than one partition, regardless whether they are in the same drive or in different drives, they should be labeled to differentiate between the two, and to help the kernel mounting the correct one. For example, they can be named this way:

sata_root=LABEL=rootfs_sata
usb_root=LABEL=rootfs_usb

So in Debian:

fw_setenv sata_root 'LABEL=rootfs_sata'
fw_setenv usb_root 'LABEL=rootfs_usb'

And then make sure they are labeled as such using tune2fs command (or when formatting with mke2fs). For example,

tune2fs -L rootfs_sata /dev/sda1 
tune2fs -L rootfs_usb /dev/sdb1

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



Edited 1 time(s). Last edit at 06/08/2015 11:17AM by bodhi.

After the changes, I was able to boot from the usb with the hard disk slotted in. However, I wasnt able to boot from only the hard disk alone. So, I booted off the usb, mounted the hard disk and re-created the Debian rootfs from scratch on it. Then rebooted with only the hard disk. And now I have what I wanted! Thanks again bodhi!

bodhi Wrote:
-------------------------------------------------------
> dips0502,
>
> > The current value for these variables are:
> >

> > rootfstype=ext3
> > mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
> >

> >
> > I guess I should be keeping these. Just need a confirmation.
>
> Yes, it looks good. That's the correct mtdparts. And remmeber when you created the rootfs on USB stick, the instruction said use Ext3. So if you did that then this env rootfstype is correct. Also make sure the ethaddr was set to your MAC address.
>
Hello Bodhi,

Now, I am trying to flash your u-boot on my Seagate GoFLEX Home as well as my Seagate GoFLEX NET. It looks like the same as a Seagate Dockstar's mtdparts you mentioned here. So, I reckon it safe to use the above mtdparts and with the following command for both my Seagate GoFLEX Home and/or Seagate GoFLEX NET.

fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'

Also, since I will be formatting my SATA HDD with an EXT4, then I should change from rootfstype=ext3 to rootfstype=ext4 in the environment setting, right?

habibie,

> Now, I am trying to flash your u-boot on my
> Seagate GoFLEX Home as well as my Seagate GoFLEX
> NET. It looks like the same as a Seagate
> Dockstar's mtdparts you mentioned
> here.
> So, I reckon it safe to use the above mtdparts and
> with the following command for both my Seagate
> GoFLEX Home and/or Seagate GoFLEX NET.
>

fw_setenv mtdparts
> 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'

Correct.

> Also, since I will be formatting my SATA HDD with
> an EXT4, then I should change from
> rootfstype=ext3 to rootfstype=ext4
> in the environment setting, right?

However, there is no need to adjust anything other what I wrote in the u-boot installation instruction. For example, that rootfstype is obsolete, we don't use it anymore. I'd suggest that you just follow the installation instruction and not looking at any other threads such as this one for info. It is easy to get confused by conflicting info from multiple threads.

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

Bodhi,

Thank you and now my Seagate GoFLEX Home is up running with debian ARM.

Hello.

After these steps the machine boots from hard disk when both drives are present.

In case I want to boot from USB, is there a method ?

kartikayec,

> Hello.
>
> After these steps the machine boots from hard disk
> when both drives are present.
>
> In case I want to boot from USB, is there a method
> ?

If both have rootfs then it will be whichever drive is enumerated by u-boot first. So the rootfs should be on USB drive only to ensure that will happen.

However, you can tell u-boot to boot kernel from USB and then mount rootfs from USB, by changing u-boot envs and changing the HDD rootfs label.

Pls get the listing of current u-boot envs, and post here:

fw_printenv

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