Still having trouble with a new uboot install

Following a prior difficulty and reflashing back to factory, I have managed to mess up my GoFlex Home again. This is the sequence of events:

1. Mess up the gfh while installing uboot.
2. booted from usb with a debian image
3. tried to redo the uboot install, but failed
4. reflashed to factory (2.7.1)
5. successfully replaced sshd so that I could ssh in without the long username.
6. installed uboot via the install_uboot_mtd0.sh script without error other than: cannot overwrite ethaddr
7. set up netconsole via fw_setenv
8. set arcnumber via fw_setenv
9. restart failed to connect to network and no netconsole or ssh access
   flashing green then flashing orange
10. failed to boot from usb
    flashing green led then no leds at all
11. failed to reflash back to factory
12. flashing green led, then usb led flashed twice, followed by orange flashing led,never got the white flash
    tried 2.7.1 and 2.5.3

Any ideas? I do not yet have a serial cable. I ordered one about a week ago, but it is not here yet.

Below is the output from fw_printenv (I saved it before rebooting):
Is there something wrong with the uboot environment? or is there some way that I can connect to it?
I have not installed recovery

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
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;
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:b4:1a:2e
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0
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
arcNumber=3089
serverip=192.168.0.89
ipaddr=192.168.0.94
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

Edited 1 time(s). Last edit at 11/19/2012 12:15AM by handy1.

"8. set arcnumber via fw_setenv"

I'd suggest not to do this, until *after* you have booted into Debian a couple times, and have verified that netconsole works. With arcNumber 2097, the LED won't flash correctly, but you can find the IP address and ping the box to know when it's finished booting. The reason is the stock Debian that you've installed might not have support for the GoFlex Home or Goflex Net arcNumber (IIRC, that it does not have the patch for machine 3089 or 3338 incorporated).

In the mean time, without netconsole or serial console, you can get davy's rootfs and create a USB thumb, and boot with it. See this post for where to get that rootfs:
http://forum.doozan.com/read.php?2,7806

That is exactly the image I was trying to boot from. It allowed me to rescue my Goflex Home before, but it does not seem to work this time.

Is it simply that I need an image with a kernel that supports the arcnumber? If so, where can I find one?
If it is the arcnumber, the I believe that all I need to do to get it to boot normally is to revert the arcnumber
back to default.?
Can the arcnumber also be the reason that I cannot reflash back to factory?

Is there something wrong with my net console setup that prevents it from working? Or is this also the result of the arcnumber? My gfh never seems to get onto my network.

When booting from USB, does the volume have to be labeled anything in particular? I have tried ROOTFS as that was necessary previously, but it didn't work. Neither did ARM_FS.

Thank you so much for your help. I am very grateful.

- The UBoot envs that you've listed are from the stock FW, not the new UBoot envs from the new UBoot. I recall that after you've run install_uboot_mtd0.sh, the correct command to print envs is /usr/sbin/fw_printenv.

- Davy's rootfs image does work with arcNumber 3089. So you already got one working.

- It's not possible to restore to stock using Seagate FW restore procedure after installing new UBoot (i.e. changed mtd0). The only known method to restore stock FW is by reflashing saved mtd0 directly to NAND. But I hope you will not need to do that. Especially you will have serial console.

- I think mostlikely the reason you can't see the GFH on the network is because the kernel never got the point where the IP request is sent out to the router.

- I don't think arcNumber was the cause of your netconsole not working.

Suggestion:

1. Power down, unplug the USB drive (also if you have the SATA drive in the dock before, remove it too). Power up again to see if it boots back to the stock kernel.

2. If it does boot the stock kernel, then you can try to log in the same way you did before through ssh. If you can't log in, try the web interface to reregister another username/password, and log in through ssh.

3. If you can log in back to the box while it's running the stock kernel, then you can rerun install_uboot_mtd0.sh again.

4. If you are able to run install_uboot_mtd0.sh at that point, then print out envs with /usr/sbin/fw_printenv and save the output. Then, set up netconsole with /usr/sbin/fw_setenv.

5. Follow the same procedure before to install Debian.

handy1 Wrote:
-------------------------------------------------------
> That is exactly the image I was trying to boot
> from. It allowed me to rescue my Goflex Home
> before, but it does not seem to work this time.
>
> Is it simply that I need an image with a kernel
> that supports the arcnumber? If so, where can I
> find one?
> If it is the arcnumber, the I believe that all I
> need to do to get it to boot normally is to revert
> the arcnumber
> back to default.?
> Can the arcnumber also be the reason that I cannot
> reflash back to factory?
>
> Is there something wrong with my net console setup
> that prevents it from working? Or is this also
> the result of the arcnumber? My gfh never seems to
> get onto my network.
>
> When booting from USB, does the volume have to be
> labeled anything in particular? I have tried
> ROOTFS as that was necessary previously, but it
> didn't work. Neither did ARM_FS.
>
> Thank you so much for your help. I am very
> grateful.

The uboot env that I included was after the install_uboot_mtd0.sh completed. There was no apparent error other than the mentioned inability to set ethaddr.

I have tried booting to the stock software several times and it just never gets to the green led. It flashes green for 2 or 3 seconds then flashes orange forever.

I cannot boot the stock kernel, nor an image from USB, nor can I see it on the network. Should have my serial cable in a few days. Is there anything else that I should try before it comes in?

And thanks again.

handy1 Wrote:
-------------------------------------------------------
> The uboot env that I included was after the
> install_uboot_mtd0.sh completed. There was no
> apparent error other than the mentioned inability
> to set ethaddr.

If you've used /usr/sbin/fw_printenv to list the envs after installation and get this list then I don't think the installation was successful.
I wonder how did you answer to this question below during installation or if it was asked:

You are already running the latest uBoot.
Would you like to reset the uBoot environment? [N/y] y

>
> I have tried booting to the stock software several
> times and it just never gets to the green led. It
> flashes green for 2 or 3 seconds then flashes
> orange forever.
>
> I cannot boot the stock kernel, nor an image from
> USB, nor can I see it on the network. Should have
> my serial cable in a few days. Is there anything
> else that I should try before it comes in?
>

Because of the UBoot envs above do not look right for the new UBoot, so netconsole probably does not work.

However you could try to check: pinging 192.168.0.94 continuously before power up the GFH. When you power up the GFH, if you see the GFH response to the ping briefly for a few seconds then you do have netconsole.

Without netconsole, I think waiting for serial cable is the only way.

Another thought: the GFH reflash to stock procedure is very flaky, it took about 5 tries for it to get to the white LED when I did it.

I ran fw_printenv after installing the new uboot, but before rebooting.

I did not get the question about already having the latest uboot, because I had a fresh reflash to factory.

I have tried the reflash to factory several times, but nothing. I will give it a few more tries. I will also try pinging 192.168.0.94 as well. Though I do not believe that it will work. The router does not see the GFH connect at any time. At least there is nothing in the log.

Thanks again.

I was finally able to boot a usb image (RescueV2.8.2_USB_Bootable_rootfs_with_imgfiles-10292012). Something is very strange though. I now have a different uboot environment than before (the one above).

I only managed to get it connected to the network once and upon reboot, I could not get it to connect again.

This is turning out to be quite an adventure.

the new environment is:

ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
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
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
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
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
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
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_list=1 2 3 4
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_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
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
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

got it to boot again from usb after about 15 more tries.

I reinstalled uboot. It said that I had the newest uboot, so I updated the environment to a known good environment.
I added netcnsole. no change to arcnumber this time.

I don't have the time to check that it is ok. I have to go to work. Will update the status when I have a chance to check it out.

This is the output:

rescue:/tmp# ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |************************************************************************************************************|  1133  --:--:-- ETA
## Valid uBoot detected: [goflexnet davygravy-2012-04-19-current]
## The newest uBoot is already installed on mtd0.


You are already running the latest uBoot.
Your current uBoot environment should be reasonable.  However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] y

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |************************************************************************************************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment    100% |************************************************************************************************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |************************************************************************************************************|    32  --:--:-- ETA

# uBoot installation has completed successfully.

rescue:/tmp# fw_setenv serverip 192.168.0.89
rescue:/tmp# fw_setenv ipaddr 192.168.0.94
rescue:/tmp# fw_setenv if_netconsole 'ping $serverip'
rescue:/tmp# fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
rescue:/tmp# fw_setenv preboot 'run if_netconsole start_netconsole'

handy1 Wrote:
-------------------------------------------------------
> got it to boot again from usb after about 15 more
> tries.
>
> I reinstalled uboot. It said that I had the newest
> uboot, so I updated the environment to a known
> good environment.
> I added netcnsole. no change to arcnumber this
> time.
>
> I don't have the time to check that it is ok. I
> have to go to work. Will update the status when I
> have a chance to check it out.
>
> This is the output:
>
>

> rescue:/tmp# ./install_uboot_mtd0.sh
> 
> 
> !!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER 
> !!!!!!
> 
> If you lose power to your device while running
> this script,
> it could be left in an unusable state.
> 
> This script will replace the bootloader on
> /dev/mtd0.
> 
> This installer will only work on the following
> devices:
>  Seagate Dockstar
>  Seagate GoFlex Net
>  Seagate GoFlex Home
>  Pogoplug v1
>  Pogoplug Pink (v2)
> Do not run this installer on any other device.
> 
> By typing ok, you agree to assume all liabilities
> and risks
> associated with running this installer.
> 
> If you agree, type 'ok' and press ENTER to
> continue: ok
> # checking for /usr/sbin/nandwrite...
> # checking for /usr/sbin/nanddump...
> # checking for /usr/sbin/flash_erase...
> # checking for /usr/sbin/fw_printenv...
> # checking for /etc/fw_env.config...
> 
> # Validating existing uBoot...
> Block size 131072, page size 2048, OOB size 64
> Dumping data starting at 0x00000000 and ending at
> 0x00080000...
> Connecting to jeff.doozan.com (50.116.34.13:80)
> Connecting to projects.doozan.com
> (50.116.34.13:80)
> valid-uboot.md5      100%
> |*************************************************
> **************************************************
> *********|  1133  --:--:-- ETA
> ## Valid uBoot detected: [goflexnet
> davygravy-2012-04-19-current]
> ## The newest uBoot is already installed on mtd0.
> 
> 
> You are already running the latest uBoot.
> Your current uBoot environment should be
> reasonable.  However, if you're having
> any probems booting, you can reset the environment
> variables to know good values.
> Would you like to reset the uBoot environment?
> [N/y] y
> 
> # Installing uBoot environment
> Connecting to download.doozan.com
> (50.116.34.13:80)
> uboot.environment.md 100%
> |*************************************************
> **************************************************
> *********|    32  --:--:-- ETA
> Connecting to download.doozan.com
> (50.116.34.13:80)
> uboot.environment    100%
> |*************************************************
> **************************************************
> *********|   128k 00:00:00 ETA
> Erase Total 1 Units
> Performing Flash Erase of length 131072 at offset
> 0xc0000 done
> Writing data to block 6 at offset 0xc0000
> 
> # Verifying uBoot environment
> Block size 131072, page size 2048, OOB size 64
> Dumping data starting at 0x000c0000 and ending at
> 0x000e0000...
> Connecting to download.doozan.com
> (50.116.34.13:80)
> uboot.environment.md 100%
> |*************************************************
> **************************************************
> *********|    32  --:--:-- ETA
> 
> # uBoot installation has completed successfully.
> 
> rescue:/tmp# fw_setenv serverip 192.168.0.89
> rescue:/tmp# fw_setenv ipaddr 192.168.0.94
> rescue:/tmp# fw_setenv if_netconsole 'ping
> $serverip'
> rescue:/tmp# fw_setenv start_netconsole 'setenv
> ncip $serverip; setenv bootdelay 10; setenv stdin
> nc; setenv stdout nc; setenv stderr nc; version;'
> rescue:/tmp# fw_setenv preboot 'run if_netconsole
> start_netconsole'
> 
>

I think it looks great. And the envs you've listed in the post above also good.