Can't get uBoot to install, and I may have corrupted by plug

Development on core packages and the distribution goes on in here.

Can't get uBoot to install, and I may have corrupted by plug

Postby drock1985 » Mon Dec 13, 2010 9:10 pm

Hi,

I had a previously working Arch Linux ARM install linux installation when one day, my Arch Linux ARM install died. No lights, just a high pitch screeching sound when plugged in. Assuming it was a hardware failure, I exchanged the unit (it was under a month old) and I now have a replacement one.

That being said, I am now having some MAJOR issues trying to get uBoot installed, and the Arch Linux ARM (or debian, not sure which way i'm going this time) to install. This is my output from putty, but basically when I try to run the uboot installer program (even with the --no-uboot-check option) I am getting an error and scared to go any further. I'm not sure what to do, i'm hoping someone can help me.
$this->bbcode_second_pass_code('', 'Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb.md5 100% |*******************************| 74 --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
-bash-3.2# rm install_uboot_mtd0.sh
-bash-3.2# wget http://Arch Linux ARM.com/os/pogoplug/uboot/install_uboot_mtd0.sh
Connecting to Arch Linux ARM.com (206.217.217.39:80)
install_uboot_mtd0.s 100% |*******************************| 17281 --:--:-- ETA
-bash-3.2# chmod +x install_uboot_mtd0.sh
-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 GoFlex Net
Seagate Dockstar
Pogoplug v1
Pogoplug Pink
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:
Exiting. uBoot was not installed.
-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 GoFlex Net
Seagate Dockstar
Pogoplug v1
Pogoplug Pink
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 (69.163.187.226:80)
valid-uboot.md5 100% |*******************************| 756 --:--:-- ETA
## Unknown uBoot detected on mtd0: b5123ad4df03b5f64e43f6d7fe644b27
##
## 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.
##
## If you have installed a diffirent uBoot on mtd0, and understand the
## risks, you can re-run the installer with the --no-uboot-check parameter
##
## Installation cancelled.
-bash-3.2#
-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 GoFlex Net
Seagate Dockstar
Pogoplug v1
Pogoplug Pink
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:
Exiting. uBoot was not installed.
-bash-3.2# ./install_uboot_mtd0.sh --no-uboot-check


!!!!!! 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 GoFlex Net
Seagate Dockstar
Pogoplug v1
Pogoplug Pink
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 (69.163.187.226:80)
valid-uboot.md5 100% |*******************************| 756 --:--:-- ETA
## Unknown uBoot detected on mtd0: b5123ad4df03b5f64e43f6d7fe644b27
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Pogoplug v1
4 - Pogoplug v2 - Pink
5 - Other
4
Selected Pogoplug v2 - Pink

# Installing uBoot
## Installing pinkpogo jeff-2010-10-23
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb.md5 100% |*******************************| 74 --:--:-- ETA
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb 100% |*******************************| 512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000
MTD Erase failure: Input/output error
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to jeff.doozan.com (69.163.187.226:80)
uboot.mtd0.kwb.md5 100% |*******************************| 74 --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.
-bash-3.2# ls
hbplug.log resolv.conf usb
install_uboot_mtd0.sh uboot-mtd0-dump var
mtd0.uboot uboot.mtd0.kwb
nanddump uboot.mtd0.kwb.md5
-bash-3.2# nandwrite
Usage: nandwrite [OPTION] MTD_DEVICE INPUTFILE
Writes to the specified MTD device.

-a, --autoplace Use auto oob layout
-j, --jffs2 force jffs2 oob layout (legacy support)
-y, --yaffs force yaffs oob layout (legacy support)
-f, --forcelegacy force legacy support on autoplacement enabled mtd device
-n, --noecc write without ecc
-o, --oob image contains oob data
-s addr, --start=addr set start address (default is 0)
-p, --pad pad to page size
-b, --blockalign=1|2|4 set multiple of eraseblocks to align to
-q, --quiet don't display progress messages
--help display this help and exit
--version output version information and exit
-bash-3.2# flash_erase /dev/mtd0 0 4
-bash: flash_erase: command not found
-bash-3.2# nandwrite /dev/mtd0 uboot.mtd0.kwb
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Writing data to block 60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 80000
-bash-3.2#
')

If anyone has any idea of what I am doing wrong, and how I can fix this (if it can be fixed) please tell me! I miss my little media server!
drock1985
 
Posts: 1
Joined: Mon Dec 13, 2010 9:04 pm

Re: Can't get uBoot to install, and I may have corrupted by

Postby peaslaker » Thu Dec 23, 2010 5:06 pm

$this->bbcode_second_pass_code('', ' flash_erase: command not found')

That there is your problem. Failed erase because the tool wasn't present. Not sure why as the install script should download it.
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: Can't get uBoot to install, and I may have corrupted by

Postby MrXindeed » Tue Feb 08, 2011 5:06 pm

I'm having the same problem.
My DockStar won't let me do a flash_erase, or mkdir, or chmod, or vi.
Just says command not found.
Help!
MrXindeed
 
Posts: 4
Joined: Tue Feb 08, 2011 5:02 pm

Re: Can't get uBoot to install, and I may have corrupted by

Postby Pehr » Thu Feb 02, 2012 6:37 pm

I have a Seagate GoFlex Net with the exact same problem. Did any of you manage to fix it?
Pehr
 
Posts: 1
Joined: Thu Feb 02, 2012 6:35 pm

Re: Can't get uBoot to install, and I may have corrupted by

Postby dinjo » Fri Feb 03, 2012 6:52 am

I just feel the script should build all required packages from NAND something like this and use the commands from /tmp/tmproot.

$this->bbcode_second_pass_code('', 'mkdir -p /tmp/tmproot
mount -t ubifs ubi0:rootfs /tmp/tmproot
')
dinjo
 
Posts: 258
Joined: Mon Nov 28, 2011 5:59 am


Return to Arch Linux ARM

Who is online

Users browsing this forum: No registered users and 7 guests