Welcome! Log In Create A New Profile

Advanced

Rescue System v2

Posted by Jeff 
Re: Rescue System v2
March 30, 2015 04:10PM
@restamp,

Thanks restamp! forgot about that, fat fingers :) in any case, e2fsck won't check the mounted file system even if we try.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System v2
April 03, 2015 11:08AM
Hi bodhi,
I run the fsck , I used a new device , but never complete boot . I tried to change the env of uboot and now I no longer land in rescue .
Have a suggestion ?
I can repeat the flash from the beginning ?
Thanks

U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:52:18)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'mmc' - try 'help'
Unknown command 'ide' - try 'help'

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

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	312579760 	000d9e74-01	83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'mmc' - try 'help'
Unknown command 'ide' - try 'help'
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
EHCI timed out on TD - token=0x800d8d80
EHCI timed out on TD - token=0x800d8d80
4055568 bytes read in 11321 ms (349.6 KiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.19.3-1-ARCH
   Created:      2015-03-27  10:17:41 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4055504 Bytes = 3.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Unknown command 'mmc' - try 'help'
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'ide' - try 'help'
** Bad device ide 0 **
** Bad device ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


U-Boot 2014.07-tld-2 (Sep 20 2014 - 00:52:18)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:
Re: Rescue System v2
April 03, 2015 05:26PM
nicco,

> complete boot . I tried to change the env of uboot
> and now I no longer land in rescue .
> Have a suggestion ?
> I can repeat the flash from the beginning ?

No need to. If you have saved the u-boot envs before changing, you can put them in uEnv.txt and boot. Once you you can boot Arch, then worry about saving them. If you did not save the u-boot envs then post back I will find the file and post the content here.

> Image Name: Linux-3.19.3-1-ARCH
> Created: 2015-03-27 10:17:41 UTC
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 4055504 Bytes = 3.9 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... Bad Data CRC

Your Arch kernel uImage is not good. So you can mount the USB drive on a different Linux box and regenerate it, or use a fresh rootfs on USB (extract the Arch tarball again to it).

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Rescue System v2 fails to install
May 05, 2015 10:13AM
I first submitted my request for help under the Macplug string since that is what I have installed. But I was trying to install the Rescue system over it so I am putting it here.
I ran into the following problem trying to update my Dockstar/Macplug to the rescue system. I eventually want to install the wheezy or squeeze but ran into similar problems and thought I would try something else to get out the current distro.

Paul

MacPlug:/tmp# ./install_rescue.sh

This script will install a rescue system on your NAND.
It will OVERWRITE ALL OF THE POGOPLUG FILES.

This script will replace the kernel on on mtd1 and the rootfs on mtd2.

This installer will only work on a Seagate Dockstar or 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/ubiformat...
# checking for /usr/sbin/flash_eraseall...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...
## Verifying new uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133   0:00:00 ETA
##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##
## uBoot is good

# Downloading Rescue System
Connecting to download.doozan.com (50.116.34.13:80)
uImage-mtd1.img.md5  100% |*******************************|    32   0:00:00 ETA
Connecting to download.doozan.com (50.116.34.13:80)
uImage-mtd1.img      100% |*******************************|  3584k  0:00:00 ETA
Connecting to download.doozan.com (50.116.34.13:80)
rootfs-mtd2.img.md5  100% |*******************************|    32   0:00:00 ETA
Connecting to download.doozan.com (50.116.34.13:80)
rootfs-mtd2.img      100% |*******************************| 28288k  0:00:00 ETA

# Installing Rescue System

./install_rescue.sh: line 262: /usr/sbin/flash_eraseall: not found
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
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
Writing data to block 18 at offset 0x240000
Writing data to block 19 at offset 0x260000
Writing data to block 20 at offset 0x280000
Writing data to block 21 at offset 0x2a0000
Writing data to block 22 at offset 0x2c0000
Writing data to block 23 at offset 0x2e0000
Writing data to block 24 at offset 0x300000
Writing data to block 25 at offset 0x320000
Writing data to block 26 at offset 0x340000
Writing data to block 27 at offset 0x360000
./install_rescue.sh: line 270: /usr/sbin/flash_eraseall: not found
ubiformat: error!: please, first detach mtd2 (/dev/mtd2) from ubi0
Installation failed.
MacPlug:/tmp# ls /usr/sbin/flash_eraseall -alt
-rwx------    1 root     root          8192 Jan  1 00:07 /usr/sbin/flash_eraseall
MacPlug:/tmp#
Re: Rescue System v2 fails to install
May 05, 2015 06:21PM
@Paul,

Probably your NAND is now hosed. If I interpreted the below correctly, u-boot was flashed, but there was error in writing the rescue image after that.

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
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
..
..
./install_rescue.sh: line 270: /usr/sbin/flash_eraseall: not found
...
....

To be sure, don't reboot until you can install a known good u-boot from the command line. Since I believe you are doing this on a Dockstar or Pogo E02? it is always a danger to be locked out whenever you messing with NAND and see any error. Though in this case, if u-boot that was flashed is good, then you can recover with serial console.

Also, there was no indication that the mtd0 (block 0 to 7) was erased successfully before it was written. So I'd doubt that your u-boot can be used now.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 05/05/2015 06:24PM by bodhi.
Re: Rescue System v2 fails to install
May 05, 2015 11:51PM
Well . . .
I can still boot to the uboot prompt. Can I flash from there?
Yes, this is a dockstar. I had used a jtag on it a few years back but I'm pretty rusty.
I can read from USB and tftp too. So shouldn't I be able to load something?
Thanks.
Paul
Re: Rescue System v2 fails to install
May 06, 2015 12:07AM
@Paul,

If you can still boot to u-boot prompt then there is no need to reflash there. You can boot into Debian with USB roofs and decide what to do. And, you could run this rescue system with the latest u-boot I've released.

The part where it's needed is the rescue images. So the installation script should be modified as mentioned in Jeff's instruction:

Quote

The installer will check to make sure you're running the latest uBoot, so make sure you upgrade that before anything else. If you don't want to upgrade uBoot, you can comment out the check as long as you're not running the stock Pogoplug uBoot.

and in the script:

if [ "$UBOOT_DETAILS" = "" ]; then
  echo "##"
  echo "## uBoot is not up-to-date"
  echo "## Please install the newest uBoot and then re-run this installer."
  echo "##"
  exit 1
fi

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System v2 fails to install
May 06, 2015 07:20AM
bodhi,
Okay!
When I get a chance later I will set up a thumb drive. I had been searching for such instructions on the site but there are so many different things going on I couldn't sort out which I needed.
So, I want to set up a usb drive with the file system. I am guessing your signature has the necessary fs.
Thank you very much.
Paul
Re: Rescue System v2 fails to install
May 06, 2015 04:46PM
z3bram3n Wrote:
-------------------------------------------------------
> bodhi,
> Okay!
> When I get a chance later I will set up a thumb
> drive. I had been searching for such instructions
> on the site but there are so many different things
> going on I couldn't sort out which I needed.
> So, I want to set up a usb drive with the file
> system. I am guessing your signature has the
> necessary fs.

Yes. That's the latest rootfs, all NAND tools are already installed in it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System v2
May 07, 2015 09:31PM
OK bodhi,

I made it back from the edge. Thanks. I setup the usb stick with the latest fs and typed boot at the uboot prompt. It found the fs and booted. I then did the rescue install. Now I am relearning hylafax to preserve my retro fax modem (you can still file medical claims via fax -- something you guys not here don't have to worry about!). Thanks again.

Paul
Re: Rescue System v2
June 29, 2016 11:56AM
Hi,
Boot from a USB device (or a Debian NAND install) and run the following commands:

How can i boot from USB with my standard Goflex NET ?

i have an USB to Serial interface and i can log in by serial interface
i can start "dropbear start" but if i log in it is different to the serial login
some commands does'nt work...
Re: Rescue System v2
June 29, 2016 12:18PM
To install rescue system, best to install Debian on USB first (you also need to adjust u-boot envs to boot USB, since you are booting with stock u-boot): http://forum.doozan.com/read.php?2,12096. And then install rescue system.


1. With that said, usually we just install latest Debian (mentioned above) and new u-boot: http://forum.doozan.com/read.php?3,12381. And boot from USB or SATA.

2. Read about the latest Debian rootfs/kernel and new u-boot here to learn more. You migh not want to run Debian from NAND since it is very limited comparing to USB/SATA.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 06/29/2016 12:19PM by bodhi.
Re: Rescue System v2
January 04, 2017 03:35PM
hi
I forgot my uboot password.
How can I reset password?
Is Reinstall solve it?
sorry for my english.
==================================
I have install rescue system.

root@debian:~# grep -a --null-data U-Boot /dev/mtd0ro
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!

there is something wrong.
shoud i reinstall rescue system?



Edited 1 time(s). Last edit at 01/05/2017 01:19AM by dryice212.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: