install_uboot_mtd0.sh halts with unknown md5 checksum

I have tried to install the new uboot on a stock GoFlex Home. I only just opened the box a few hours ago and this is the first modification that I have tried. I did initially make the mistake of having a usb drive mounted the first time that I tried to run the script. It failed then too. I have a Bad CRC according to fw_printenv as shown below. The install script output after power cycling and trying again is given below that:

First, has anyone else had the same kind of issue?
Is this a result of forgetting to remove the usb drive?
How do I solve this?
Do I force the newest uboot on?
Do I force the original uboot on?

-bash-3.2# ./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

This is what I see when I run the install script:

-bash-3.2# ./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...
--14:25:22--  http://jeff.doozan.com/uboot/valid-uboot.md5
Resolving jeff.doozan.com... 50.116.34.13
Connecting to jeff.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://projects.doozan.com/uboot/valid-uboot.md5 [following]
--14:25:23--  http://projects.doozan.com/uboot/valid-uboot.md5
Resolving projects.doozan.com... 50.116.34.13
Connecting to projects.doozan.com|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1133 (1.1K) [text/plain]
Saving to: `/tmp/valid-uboot.md5'

100%[==============================================>] 1,133       --.-K/s   in 0s

14:25:23 (41.1 MB/s) - `/tmp/valid-uboot.md5' saved [1133/1133]

## Unknown uBoot detected on mtd0: 2d38dfa63e541f11e23c27e377fa1c91
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.

Edited 1 time(s). Last edit at 11/07/2012 06:43PM by handy1.

The USB drive should not effect UBoot installation. If the installation script detects a version of UBoot that was already installed, but did not recognize it, then it would output that warning. But I don't recall that it reports this info when installing from a stock GoFlex Home. Perhaps Seagate GFHome has a different UBoot now?

> -bash-3.2# ./fw_printenv
> Warning: Bad CRC, using default environment
>

This CRC erorr indicated that your fw_env.config is either incorrect or was not installed. And the log you posted above seems to be incompleted. Is it the whole log you've got? there should be a lot more going on before the line:

# Validating existing uBoot...

Usually, I would suggest these steps, if the log shows normal installation activities:

- boot with the stock FW, and ssh in, enable root (you've already done that).
- look at dmesg to make sure that it does not report any bad block.
- run install_uboot_mtd0.sh again with nocheck option

However, I can not tell from your log that it's OK to do the above steps. Please post the whole log if you have it.

I was no longer able ssh into the device. I did download a bootable image that I put on a usb key. I was able to boot from that and run the install with the nocheck option. I am now back to stock settings.

Thank you for your help.

Great! if you're back to stock then you could login throught the web interface, creat user and enable SSH and do the installation again.

Thank you for your help.

It is verymuch appreciated

I also have the same md5sum of the mtd0:
MD5: 2d38dfa63e541f11e23c27e377fa1c91 /tmp/uboot-mtd0-dump
SHA1: 19b7cd40400632fd4f6db706e07bd69092224e00 /tmp/uboot-mtd0-dump
SHA256: a05f057df1e9819f19bd8c6adf5695f931bc4013f53ca6670fcc0d8ed3996f3c /tmp/uboot-mtd0-dump

handy1 Wrote:
-------------------------------------------------------
> I have tried to install the new uboot on a stock
> GoFlex Home. I only just opened the box a few
> hours ago and this is the first modification that
> I have tried. I did initially make the mistake of
> having a usb drive mounted the first time that I
> tried to run the script. It failed then too. I
> have a Bad CRC according to fw_printenv as shown
> below. The install script output after power
> cycling and trying again is given below that:
>
> First, has anyone else had the same kind of issue?
>
> Is this a result of forgetting to remove the usb
> drive?
> How do I solve this?
> Do I force the newest uboot on?
> Do I force the original uboot on?
>
>

> -bash-3.2# ./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
>

>
>
> This is what I see when I run the install script:
>
>

> -bash-3.2# ./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...
> --14:25:22-- 
> http://jeff.doozan.com/uboot/valid-uboot.md5
> Resolving jeff.doozan.com... 50.116.34.13
> Connecting to jeff.doozan.com|50.116.34.13|:80...
> connected.
> HTTP request sent, awaiting response... 301 Moved
> Permanently
> Location:
> http://projects.doozan.com/uboot/valid-uboot.md5
> [following]
> --14:25:23-- 
> http://projects.doozan.com/uboot/valid-uboot.md5
> Resolving projects.doozan.com... 50.116.34.13
> Connecting to
> projects.doozan.com|50.116.34.13|:80...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1133 (1.1K) [text/plain]
> Saving to: `/tmp/valid-uboot.md5'
> 
> 100%[=============================================
> =>] 1,133       --.-K/s   in 0s
> 
> 14:25:23 (41.1 MB/s) - `/tmp/valid-uboot.md5'
> saved [1133/1133]
> 
> ## Unknown uBoot detected on mtd0:
> 2d38dfa63e541f11e23c27e377fa1c91
> ##
> ## The installer could not detect the version of
> your current uBoot
> ## This may happen if you have installed a
> different uBoot on
> ## /dev/mtd0 or if you have bad blocks on
> /dev/mtd0
> ##
> ## If you have bad blocks on mtd0, you should not
> try to install uBoot.
> ##
> ## Installation cancelled.
>