Goflex Home can't boot from SATA with 3TB USB plugged in

I have a Goflex Home set up with Arch Linux booting from the SATA port. I wanted to add additional storage so I got a 3TB external USB drive. But the Goflex does not boot with the USB drive plugged in. It boots with smaller USB drives, but not this one.

It seems like the Goflex is trying to boot from the USB first, and fails because the drive is >2TB. Is it possible to change the Uboot parameters to prevent booting from USB, or to put the USB port after the SATA port?

Another thing I wanted to add is that I tried using the netconsole instructions from the Arc Linux Arm website:
http://archlinuxarm.org/platforms/armv5/seagate-goflex-home

But nothing comes up on my other Ubuntu computer at all when I restart the Goflex. Is there something else I should try besides those instructions?

Snerler Wrote:
-------------------------------------------------------
> But nothing comes up on my other Ubuntu computer
> at all when I restart the Goflex. Is there
> something else I should try besides those
> instructions?

sudo ifconfig eth0:0 10.10.10.5 && nc -lu 10.10.10.5 6666

should actually be sufficient to see U-Boot booting

Nothing comes up when I do that command and reboot the Goflex. What could be the cause? Firewall issues?

dollars to donuts your uboot environment doesn't have netconsole configured correctly.
My suggestion is to unplug your 3tb drive, boot off your sata or another usb, then post the output of 'fw_printenv' so that we can take a look at how your uboo is configured.

I too had a problem with netconsole not working and I ended up simply needing to change a few uboot environment variables and voila, uboot sends netconsole output exactly where I need it.

In addition to fixing netconsole, by seeing your current environment we should be able to help you change your boot commands so that sata always boots first (if that is your preference)

Thanks for your help so far.
I ran 'fw_printenv' but it looks like the right package was not installed with Arch Linux: "-bash: fw_printenv: command not found"

I found these steps on the forum:

Quote

cd /tmp
wget http://jeff.doozan.com/debian/uboot/fw_printenv
wget http://jeff.doozan.com/debian/uboot/fw_env.config
chmod 755 fw_printenv
chmod 644 fw_env.config
mv fw_printenv /usr/sbin
ln -s /usr/sbin/fw_printenv /usr/sbin/fw_setenv
mv fw_env.config /etc

Now I'm getting this when I run 'fw_printenv'

Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

Figured out how to use "fw_printenv." I had to put this line in my /etc/fw_env.config:

/dev/mtd0 0xa0000 0x20000 0x20000

This is the what I get by running fw_printenv:


baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
rtc_mode=active
vm_ver_smt=2.0.0
ethaddr=00:10:75:2A:03:E1
explrpk=PGCD-VKUV-XDPQ-NHBY
explrsn=NA1Y8N8Z
asm1_tag=10:12:14:02:19:06:32
console=console=ttyS0,115200
rtc_tz=PST
ntp_default=pool.ntp.org
smt_tag=10:12:14:02:19:08:18
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=no
pcieTune=no
filesize=33AA2E
bootargs=console=ttyS0,115200 root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
console2=console=ttyS0,115200
bootcmd=nand read.e 0x800000 0x100000 0x600000; setenv bootargs $(console2) $(bootargs_root); bootm 0x800000

????????

That is the nuttiest uboot environment that I have ever seen.
Pretty sure your uboot should be simpler, like Optim's setup here:

arcNumber=3338
baudrate=115200
bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot;
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=XXXXXXXXXX
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
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;
usb_device=0:1
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
serverip=192.168.1.119
usb_init=usb start; setenv usb_root LABEL=rootfs
sata_init=ide reset
sata_root=/dev/sda1
sata_rootfstype=ext2
bootcmd_sata=run sata_init; run sata_load_uimage; run set_bootargs_sata; run sata_boot;
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$sata_rootdelay rootfstype=$sata_rootfstype $mtdparts
sata_rootdelay=8
sata_device=0:1
sata_boot=if ext2load ide $sata_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi;
bootcmd=run bootcmd_usb; usb stop; run bootcmd_sata; run bootcmd_pogo; reset
sata_load_uimage=mw 0x800000 0 1; ext2load ide $sata_device 0x800000 /boot/uImage

be very careful with the prebootcmd beca

Snerler Wrote:
-------------------------------------------------------
> Figured out how to use "fw_printenv." I had to put
> this line in my /etc/fw_env.config:
>
> /dev/mtd0 0xa0000 0x20000
> 0x20000
>
> This is the what I get by running fw_printenv:
>
>
> baudrate=115200
> loads_echo=0
> ipaddr=169.254.254.253
> serverip=169.254.254.254
> rootpath=/mnt/ARM_FS/
> netmask=255.255.0.0
> run_diag=yes
> CASset=min
> MALLOC_len=1
> ethprime=egiga0
> bootargs_end=:::DB88FXX81:eth0:none
> image_name=uImage
> standalone=fsload 0x2000000 $(image_name);setenv
> bootargs $(console) root=/dev/mtdblock0 rw
> ip=$(ipaddr):$(serverip)$(bootargs_end)
> $(mvPhoneConfig); bootm 0x2000000;
> ethmtu=1500
> usb0Mode=host
> nandEcc=1bit
> netretry=no
> rcvrip=169.254.100.100
> loadaddr=0x02000000
> autoload=no
> ethact=egiga0
> rtc_mode=active
> vm_ver_smt=2.0.0
> ethaddr=00:10:75:2A:03:E1
> explrpk=PGCD-VKUV-XDPQ-NHBY
> explrsn=NA1Y8N8Z
> asm1_tag=10:12:14:02:19:06:32
> console=console=ttyS0,115200
> rtc_tz=PST
> ntp_default=pool.ntp.org
> smt_tag=10:12:14:02:19:08:18
> stdin=serial
> stdout=serial
> stderr=serial
> mainlineLinux=no
> enaMonExt=no
> enaCpuStream=no
> enaWrAllo=no
> pexMode=RC
> disL2Cache=no
> setL2CacheWT=yes
> disL2Prefetch=yes
> enaICPref=yes
> enaDCPref=yes
> sata_dma_mode=yes
> netbsd_en=no
> vxworks_en=no
> bootdelay=3
> disaMvPnp=no
> enaAutoRecovery=no
> pcieTune=no
> filesize=33AA2E
> bootargs=console=ttyS0,115200 root=/dev/ram0 rw
> ramdisk=0x01100000,8M install_type=nand
> bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs
> rootfstype=ubifs init=/linuxrc
> console2=console=ttyS0,115200
> bootcmd=nand read.e 0x800000 0x100000 0x600000;
> setenv bootargs $(console2) $(bootargs_root);
> bootm 0x800000

Looks like you still have the original UBoot environment.

Do you guys think I should update my Uboot?

This is what I downloaded to install Uboot:

Quote

wget http://jeff.doozan.com/debian/goflex/v0.6/uInitrd
wget http://jeff.doozan.com/debian/goflex/v0.6/ubit_start

I think you can just run Jeff's Wheezy install script and it should work. But I have not tried it (I have never used the UBit install scripts), so I can't say if it will detect the old installtion and deal with it successfully.