Debian installation failed from Rescue system v1

Hi everyone!

Yesterday my dockstar stopped working after a reboot. So today I started to install a new debian with Jeff's script.

I think I installed before the rescue system v1 (first available here in the forum... about 4 months ago). So I want to install debian to a new 4GB USB stick (3,6GB ext2, 256MB swap).

I think something in the script fails. It can't create a folder. Here's the log:

login as: root
root@192.168.2.110's password:
rescue:~# cd /tmp
rescue:/tmp# wget http://jeff.doozan.com/debian/dockstar.debian-lenny.sh
Connecting to jeff.doozan.com (69.163.187.226:80)
dockstar.debian-lenn 100% |*******************************|  7137  --:--:-- ETA
rescue:/tmp# chmod +x dockstar.debian-lenny.sh
rescue:/tmp# ./dockstar.debian-lenny.sh
!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

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

If you lose power while the bootloader is being flashed,
your device could be left in an unusable state.


This script will configure your Dockstar to boot Debian Lenny
from a USB device.  Before running this script, you should have
used fdisk to create the following partitions:

/dev/sda1 (Linux ext2, at least 400MB)
/dev/sda2 (Linux swap, recommended 256MB)


This script will DESTROY ALL EXISTING DATA on /dev/sda1
Please double check that the device on /dev/sda1 is the correct device.

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

If everything looks good, type 'ok' to continue: ok



SOURCE FILES

Please enter the path to the install files
If the install files are not found in the specified directory, they will be downloaded there
If you don't care, just press Enter

Source Path: [/tmp/debian]


Connecting to jeff.doozan.com (69.163.187.226:80)
install_uboot_mtd0.s 100% |*******************************| 17281  --:--:-- ETA
Installing Bootloader
# 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
## Valid uBoot detected: [dockstar jeff-2010-10-23-current ebd566de30c6521e65fb1255415c037f pogov1 jeff-2010-10-23-current]
## The newest uBoot is already installed on mtd0.

# uBoot installation has completed successfully.
Connecting to jeff.doozan.com (69.163.187.226:80)
mke2fs               100% |*******************************|   393k 00:00:00 ETA
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
225344 inodes, 899632 blocks
44981 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=922746880
28 block groups
32768 blocks per group, 32768 fragments per group
8048 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
Setting up swapspace version 1, size = 271430144 bytes



Downloading packages to /tmp/debian

Downloading Debian base
Connecting to jeff.doozan.com (69.163.187.226:80)
base.tar.bz2         100% |*******************************|   121M 00:00:00 ETA

Downloading sheeva kernel
Connecting to jeff.doozan.com (69.163.187.226:80)
sheeva-2.6.33-uImage 100% |*******************************|  2773k 00:00:00 ETA
Connecting to jeff.doozan.com (69.163.187.226:80)
sheeva-2.6.33-Module 100% |*******************************|  4305k 00:00:00 ETA
tar: invalid option -- j
BusyBox v1.17.1 (2010-09-15 13:07:46 EDT) multi-call binary.

Usage: tar -[cxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...

Create, extract, or list files from a tar file

Operation:
        c       Create
        x       Extract
        t       List
Options:
        f       Name of TARFILE ('-' for stdin/out)
        C       Change to DIR before operation
        v       Verbose
        O       Extract to stdout
        h       Follow symlinks
        exclude File to exclude
        X       File with names to exclude
        T       File with names to include

./dockstar.debian-lenny.sh: line 286: can't create /tmp/debian/etc/fstab: nonexistent directory
tar: invalid option -- z
BusyBox v1.17.1 (2010-09-15 13:07:46 EDT) multi-call binary.

Usage: tar -[cxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...

Create, extract, or list files from a tar file

Operation:
        c       Create
        x       Extract
        t       List
Options:
        f       Name of TARFILE ('-' for stdin/out)
        C       Change to DIR before operation
        v       Verbose
        O       Extract to stdout
        h       Follow symlinks
        exclude File to exclude
        X       File with names to exclude
        T       File with names to include





Installation complete

You can now reboot your device into Debian.
If your device does not start Debian after rebooting,
you may need to restart the device by disconnecting the power.

Reboot now? [Y/n] Y
rescue:/tmp#

I hope somebody can help me....

You're using an outdated script to install an outdated Debian release.
Use http://jeff.doozan.com/debian/dockstar.debian-squeeze.sh

Thanks for your tip, but the newer script stops earlier.

login as: root
root@192.168.2.110's password:
rescue:~# cd /tmp/
rescue:/tmp# wget http://jeff.doozan.com/debian/dockstar.debian-squeeze.sh
Connecting to jeff.doozan.com (69.163.187.226:80)
dockstar.debian-sque 100% |*******************************| 10602  00:00:00 ETA
rescue:/tmp# chmod +x dockstar.debian-squeeze.sh
rescue:/tmp# ./dockstar.debian-squeeze.sh
touch: /sbin/26022011132137: Read-only file system


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

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

If you lose power while the bootloader is being flashed,
your device could be left in an unusable state.


This script will configure your Dockstar to boot Debian Squeeze
from a USB device.  Before running this script, you should have
used fdisk to create the following partitions:

/dev/sda1 (Linux ext2, at least 400MB)
/dev/sda2 (Linux swap, recommended 256MB)


This script will DESTROY ALL EXISTING DATA on /dev/sda1
Please double check that the device on /dev/sda1 is the correct device.

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

If everything looks good, type 'ok' to continue: ok
Connecting to jeff.doozan.com (69.163.187.226:80)
install_uboot_mtd0.s 100% |*******************************| 17281  00:00:00 ETA
Installing Bootloader
# 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
## Valid uBoot detected: [dockstar jeff-2010-10-23-current ebd566de30c6521e65fb1255415c037f pogov1 jeff-2010-10-23-current]
## The newest uBoot is already installed on mtd0.

# uBoot installation has completed successfully.
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
225344 inodes, 899632 blocks
44981 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=922746880
28 block groups
32768 blocks per group, 32768 fragments per group
8048 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
Setting up swapspace version 1, size = 271430144 bytes
Connecting to cdn.debian.net (129.143.116.10:80)
debootstrap.deb      100% |*******************************| 58232  --:--:-- ETA
rw-r--r-- 0/0      4 Nov 12 07:07 2010 debian-binary
rw-r--r-- 0/0   1171 Nov 12 07:07 2010 control.tar.gz
rw-r--r-- 0/0  56868 Nov 12 07:07 2010 data.tar.gz
tar: invalid option -- z
BusyBox v1.17.1 (2010-09-15 13:07:46 EDT) multi-call binary.

Usage: tar -[cxtvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...

Create, extract, or list files from a tar file

Operation:
        c       Create
        x       Extract
        t       List
Options:
        f       Name of TARFILE ('-' for stdin/out)
        C       Change to DIR before operation
        v       Verbose
        O       Extract to stdout
        h       Follow symlinks
        exclude File to exclude
        X       File with names to exclude
        T       File with names to include

mv: can't rename './usr/sbin/debootstrap': No such file or directory
mv: can't rename './usr/share/debootstrap': No such file or directory
# checking for /usr/share/debootstrap/pkgdetails...

# Installing /usr/share/debootstrap/pkgdetails...
Connecting to jeff.doozan.com (69.163.187.226:80)
wget: can't open '/usr/share/debootstrap/pkgdetails.md5': No such file or directory
Connecting to jeff.doozan.com (69.163.187.226:80)
wget: can't open '/usr/share/debootstrap/pkgdetails.md5': No such file or directory
## Could not install /usr/share/debootstrap/pkgdetails from http://jeff.doozan.com/debian/pkgdetails, exiting.
rescue:/tmp#

Why stops the script?

Re-install the rescue system. The tar function in the your current rescue system doesn't support the -z option. See here http://forum.doozan.com/read.php?4,1133,1133#msg-1133

That I already wanted, 5 minutes ago:

rescue:~# cd /tmp/
rescue:/tmp# wget http://jeff.doozan.com/debian/rescue/install_rescue.sh
Connecting to jeff.doozan.com (69.163.187.226:80)
install_rescue.sh    100% |*******************************|  7743  --:--:-- ETA
rescue:/tmp# chmod +x install_rescue.sh
rescue:/tmp# ./install_rescue.sh
This script must be run from outside your Pogoplug install or Rescue System.
Please boot from a USB device and try again.
rescue:/tmp#

:)) Bad thing because I don't have a working USB installation here. Tomorrow I can get a Debian-USB-installation. Then I will boot from USB, update the rescue system and then a clean install.

Bad because today I wanted to install the new debian with tons of services. Bad thing that my other USB installation is broken...

That's what this is for. Download the latest version, unpack the zip, rename uImage-rescue and uInitrd-rescue to uImage and uInitrd and place them in /boot on an ext2 formatted USB stick.

Cool, I will try it! Thanks. If it fails I have to wait until tomorrow...

Just a quick FYI: Since the RAM based rescue system is basically the same as the installable rescue system, the rescue system installer will complain about being run from within the rescue system. You can either remove the check from the script, if you're sure that you know what you're doing, or simply run the Debian installer from the RAM based rescue system.

Thanks for that information. In the I will be back at home and can install the new rescue system because I have a working USB stick at home.

Nevertheless I tried to install my backup of the stick (yeah, i found it on the harddrive). I tared the whole usb stick, but I got errors when I extract it. It seems that it can't create the devices:

tar: .: Cannot utime: Operation not permitted
tar: .: Cannot change mode to rwxr-xr-x: Operation not permitted
tar: dev/snd/controlC1: Cannot mknod: Operation not permitted
tar: dev/snd/pcmC1D0c: Cannot mknod: Operation not permitted
tar: dev/snd/pcmC1D0p: Cannot mknod: Operation not permitted
tar: dev/snd/seq: Cannot mknod: Operation not permitted
tar: dev/snd/timer: Cannot mknod: Operation not permitted
tar: dev/net/tun: Cannot mknod: Operation not permitted
tar: dev/loop0: Cannot mknod: Operation not permitted
tar: dev/ppp: Cannot mknod: Operation not permitted
tar: dev/sdb2: Cannot mknod: Operation not permitted
tar: dev/sdb1: Cannot mknod: Operation not permitted
tar: dev/sdb: Cannot mknod: Operation not permitted
tar: dev/sda2: Cannot mknod: Operation not permitted
tar: dev/sda1: Cannot mknod: Operation not permitted
tar: dev/sda: Cannot mknod: Operation not permitted
tar: dev/bsg/1\:0\:0\:0: Cannot mknod: Operation not permitted
tar: dev/bsg/0\:0\:0\:0: Cannot mknod: Operation not permitted
tar: dev/hidraw0: Cannot mknod: Operation not permitted
tar: dev/bus/usb/001/005: Cannot mknod: Operation not permitted
tar: dev/bus/usb/001/004: Cannot mknod: Operation not permitted
tar: dev/bus/usb/001/003: Cannot mknod: Operation not permitted
tar: dev/bus/usb/001/002: Cannot mknod: Operation not permitted
tar: dev/bus/usb/001/001: Cannot mknod: Operation not permitted
tar: dev/pts/0: Cannot mknod: Operation not permitted
tar: dev/pts/ptmx: Cannot mknod: Operation not permitted
tar: dev/pts: implausibly old time stamp 1970-01-01 00:00:00
tar: dev/network_throughput: Cannot mknod: Operation not permitted
tar: dev/network_latency: Cannot mknod: Operation not permitted
tar: dev/cpu_dma_latency: Cannot mknod: Operation not permitted
tar: dev/psaux: Cannot mknod: Operation not permitted
tar: dev/input/event0: Cannot mknod: Operation not permitted
tar: dev/input/mice: Cannot mknod: Operation not permitted
tar: dev/ubi_ctrl: Cannot mknod: Operation not permitted
tar: dev/mtdblock3: Cannot mknod: Operation not permitted
tar: dev/mtd3ro: Cannot mknod: Operation not permitted
tar: dev/mtd3: Cannot mknod: Operation not permitted
tar: dev/mtdblock2: Cannot mknod: Operation not permitted
tar: dev/mtd2ro: Cannot mknod: Operation not permitted
tar: dev/mtd2: Cannot mknod: Operation not permitted
tar: dev/mtdblock1: Cannot mknod: Operation not permitted
tar: dev/mtd1ro: Cannot mknod: Operation not permitted
tar: dev/mtd1: Cannot mknod: Operation not permitted
tar: dev/mtdblock0: Cannot mknod: Operation not permitted
tar: dev/mtd0ro: Cannot mknod: Operation not permitted
tar: dev/mtd0: Cannot mknod: Operation not permitted
tar: dev/ttyS0: Cannot mknod: Operation not permitted
tar: dev/ttyS1: Cannot mknod: Operation not permitted
tar: dev/ptmx: Cannot mknod: Operation not permitted
tar: dev/tty63: Cannot mknod: Operation not permitted
tar: dev/tty62: Cannot mknod: Operation not permitted
tar: dev/tty61: Cannot mknod: Operation not permitted
tar: dev/tty60: Cannot mknod: Operation not permitted
tar: dev/tty59: Cannot mknod: Operation not permitted
tar: dev/tty58: Cannot mknod: Operation not permitted
tar: dev/tty57: Cannot mknod: Operation not permitted
tar: dev/tty56: Cannot mknod: Operation not permitted
tar: dev/tty55: Cannot mknod: Operation not permitted
tar: dev/tty54: Cannot mknod: Operation not permitted
tar: dev/tty53: Cannot mknod: Operation not permitted
tar: dev/tty52: Cannot mknod: Operation not permitted
tar: dev/tty51: Cannot mknod: Operation not permitted
tar: dev/tty50: Cannot mknod: Operation not permitted
tar: dev/tty49: Cannot mknod: Operation not permitted
tar: dev/tty48: Cannot mknod: Operation not permitted
tar: dev/tty47: Cannot mknod: Operation not permitted
tar: dev/tty46: Cannot mknod: Operation not permitted
tar: dev/tty45: Cannot mknod: Operation not permitted
tar: dev/tty44: Cannot mknod: Operation not permitted
tar: dev/tty43: Cannot mknod: Operation not permitted
tar: dev/tty42: Cannot mknod: Operation not permitted
tar: dev/tty41: Cannot mknod: Operation not permitted
tar: dev/tty40: Cannot mknod: Operation not permitted
tar: dev/tty39: Cannot mknod: Operation not permitted
tar: dev/tty38: Cannot mknod: Operation not permitted
tar: dev/tty37: Cannot mknod: Operation not permitted
tar: dev/tty36: Cannot mknod: Operation not permitted
tar: dev/tty35: Cannot mknod: Operation not permitted
tar: dev/tty34: Cannot mknod: Operation not permitted
tar: dev/tty33: Cannot mknod: Operation not permitted
tar: dev/tty32: Cannot mknod: Operation not permitted
tar: dev/tty31: Cannot mknod: Operation not permitted
tar: dev/tty30: Cannot mknod: Operation not permitted
tar: dev/tty29: Cannot mknod: Operation not permitted
tar: dev/tty28: Cannot mknod: Operation not permitted
tar: dev/tty27: Cannot mknod: Operation not permitted
tar: dev/tty26: Cannot mknod: Operation not permitted
tar: dev/tty25: Cannot mknod: Operation not permitted
tar: dev/tty24: Cannot mknod: Operation not permitted
tar: dev/tty23: Cannot mknod: Operation not permitted
tar: dev/tty22: Cannot mknod: Operation not permitted
tar: dev/tty21: Cannot mknod: Operation not permitted
tar: dev/tty20: Cannot mknod: Operation not permitted
tar: dev/tty19: Cannot mknod: Operation not permitted
tar: dev/tty18: Cannot mknod: Operation not permitted
tar: dev/tty17: Cannot mknod: Operation not permitted
tar: dev/tty16: Cannot mknod: Operation not permitted
tar: dev/tty15: Cannot mknod: Operation not permitted
tar: dev/tty14: Cannot mknod: Operation not permitted
tar: dev/tty13: Cannot mknod: Operation not permitted
tar: dev/tty12: Cannot mknod: Operation not permitted
tar: dev/tty11: Cannot mknod: Operation not permitted
tar: dev/tty10: Cannot mknod: Operation not permitted
tar: dev/tty9: Cannot mknod: Operation not permitted
tar: dev/tty8: Cannot mknod: Operation not permitted
tar: dev/tty7: Cannot mknod: Operation not permitted
tar: dev/tty6: Cannot mknod: Operation not permitted
tar: dev/tty5: Cannot mknod: Operation not permitted
tar: dev/tty4: Cannot mknod: Operation not permitted
tar: dev/tty3: Cannot mknod: Operation not permitted
tar: dev/tty2: Cannot mknod: Operation not permitted
tar: dev/tty1: Cannot mknod: Operation not permitted
tar: dev/vcsa1: Cannot mknod: Operation not permitted
tar: dev/vcs1: Cannot mknod: Operation not permitted
tar: dev/vcsa: Cannot mknod: Operation not permitted
tar: dev/vcs: Cannot mknod: Operation not permitted
tar: dev/tty0: Cannot mknod: Operation not permitted
tar: dev/console: Cannot mknod: Operation not permitted
tar: dev/tty: Cannot mknod: Operation not permitted
tar: dev/kmsg: Cannot mknod: Operation not permitted
tar: dev/urandom: Cannot mknod: Operation not permitted
tar: dev/random: Cannot mknod: Operation not permitted
tar: dev/full: Cannot mknod: Operation not permitted
tar: dev/zero: Cannot mknod: Operation not permitted
tar: dev/port: Cannot mknod: Operation not permitted
tar: dev/null: Cannot mknod: Operation not permitted
tar: dev/mem: Cannot mknod: Operation not permitted
tar: dev/vga_arbiter: Cannot mknod: Operation not permitted
tar: Exiting with failure status due to previous errors

Do you have an advice for me?

It looks like you're trying to untar to a file system which doesn't support Unix specialties like permissions and device nodes. Either that or you're not logged in as root.

Thanks for your hints!

I have a really strange problem: I have a working dockstar here with no rescue system and a working usb stick. This stick wont work on my other dockstar which have the old rescue system.
Also my backup from this system won't run from usb. This is really strange! Does anybody have some ideas why this happen? At the moment no USB device will boot. I also can't update the rescue system that the script will work.

I will try to boot without any sticks and flash the uboot. I hope this will work!

Edit:
I flashed the uboot but no change. It seems that my dockstar is bricked from now to then. Very strange! No stick will boot from usb...

Edit2:
Will netconsole help me? Arghs, I think I have to start a new thread because the problem is more difficult...



Edited 3 time(s). Last edit at 02/27/2011 02:50PM by Ultrazauberer.

You need to be more systematic. Don't try to copy complete Debian installations if you can't tar|untar without help. That's just going to introduce new sources of problems. Don't blindly flash boot loaders if you don't know why the existing one doesn't work (or even IF it isn't working right). I've told you how to make a USB stick with a known working rescue system, but you didn't even mention if you've tried doing that. It appears you skipped it and went back to trying to make a clone of a full-blown Debian installation work. And we don't know if that is an installation from the same Dockstar or from another one. Neither do we know if you've successfully cloned a full installation from that backup before. You could post your boot loader environment, you could tell us if you have access to the uBoot console, either via the serial port or through netconsole. Have you at any point changed the arcNumber? Other boot loader parameters? Do you have a different USB stick you could try? Can you tell if the boot loader accesses the USB stick (activity light?)

Debug in small steps. Analyze before modifying.

Ok, thanks for the advices:
- last year I made a copy of my working debian system by taring the whole root drive to an external hdd
- today I untared this file (with no errors, as root user from an ubuntu live cd) on a newly ext2 formatted usb stick (first partition 3,4GB bootable ext2, second partition 256MB swap)
- I set the boot flag
- I putted the usb stick into the first usb port on the broken dockstar (which is the same dockstar that created the tar backup file)
- then I powered on the dockstar, the led is flashing green and red
- after 2 minutes the flashing is gone and I know debian must be up, but my router doesn't show me any dhcp request
- so I pinged the whole dynamic ip range, no replies
- also my mac address is bounded to an static ip address, this ip also show no activity
- without usb stick my dockstar is booting the old rescue system
- it also gets my defined ip address (I can connect to the rescue system)
- I have 2 other working dockstars here with working usb-sticks
- I tried these 2 working usb sticks on the broken dockstar but after booting (led goes off) I have no network activity again
- I can nothing tell about the usb-stick activity because I have just tiny usb sticks without leds :(
- I haven't set up a netconsole but I will try it if it helps
- here is the fw_printenv

rescue:~# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
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_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
ethaddr=00:10:75:1A:CE:E6
rescue_installed=1
arcNumber=2097
rescue:~#

I'm happy that you motivated to help me. Sorry that my posts confuses you.

Edit: The last thing I modified on my broken dockstar (when it was working) was to install pyLoad. This worked very well and after 3 days I just want to make a clean reboot and the dockstar never came up on network. Since this my dockstar seems to be broken.



Edited 1 time(s). Last edit at 02/27/2011 03:22PM by Ultrazauberer.

- last year I made a copy of my working debian system by taring the whole root drive to an external hdd
- today I untared this file (with no errors, as root user from an ubuntu live cd) on a newly ext2 formatted usb stick (first partition 3,4GB bootable ext2, second partition 256MB swap)

This is good and in principle it should work, but there's a lot that can go wrong and you should try something simpler first.

- I set the boot flag

This is unnecessary. The uBoot boot loader executes the boot scripts from its environment and those determine where the boot loader looks for the kernel and initial ramdisk files.

- I putted the usb stick into the first usb port on the broken dockstar (which is the same dockstar that created the tar backup file)

It's good that it's from the same Dockstar.

- then I powered on the dockstar, the led is flashing green and red

I don't think it's supposed to flash red unless there is an error or the starting OS makes it flash red. Not sure about this though.

- after 2 minutes the flashing is gone and I know debian must be up, but my router doesn't show me any dhcp request
- so I pinged the whole dynamic ip range, no replies
- also my mac address is bounded to an static ip address, this ip also show no activity

That's no good then. Too many things can be the cause, so let's try something simpler.

- without usb stick my dockstar is booting the old rescue system
- it also gets my defined ip address (I can connect to the rescue system)

Good, but you can't flash a new rescue system from inside the system which runs from flash memory.

- I have 2 other working dockstars here with working usb-sticks
- I tried these 2 working usb sticks on the broken dockstar but after booting (led goes off) I have no network activity again

This is not a sign of a problem with your Dockstar. You would have to modify a configuration file in Debian. Otherwise the network doesn't come up on a different Dockstar due to the different MAC address.

- I can nothing tell about the usb-stick activity because I have just tiny usb sticks without leds :(

We'll have to make do without that information then.

- I haven't set up a netconsole but I will try it if it helps

Netconsole would help, yes, but we'll see if we can make the Dockstar load from USB without touching the boot loader environment first.

- here is the fw_printenv

I see that you're still using arcNumber=2097. That's good because it means the current version of the RAM based rescue system should work. The version for arcNumber=2998 isn't published yet.

I suggest you try the RAM based rescue system as described in a previous comment. That's just two files that you place in /boot/uImage and /boot/uInitrd on an ext2 formatted USB stick. You can try to boot this USB stick with one of your other Dockstars first, to see if you've set it up right. When the rescue system has started successfully, the Dockstar LED blinks in a heartbeat rhythm.

Thanks for your tip with the rescue system! It boot proberly on my working dockstar and also on the broken one (I think so, because the booting duration is much longer than without usb stick).
How can I identify if I on the USB rescue system or on the nand rescue system? And when I'm in the usb rescue system, how I have to modify the rescue installation script from jeff, that the rescue check will be skipped?

Big thanks!

Edit: I would delete these lines from install_rescue.sh

if [ -d /usr/local/cloudengines/ -o -f /etc/rescue.version ]; then
  echo "This script must be run from outside your Pogoplug install or Rescue Sy$
  echo "Please boot from a USB device and try again."
  exit 1
fi

But I will start first when I get a positive response. I don't know if I'm on the right environment. :)

Edit2: Ok, I've tried it on my own and it seems to work. Will boot now!

rescue:/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 jeff.doozan.com (69.163.187.226:80)
valid-uboot.md5      100% |*******************************|   756  --:--:-- ETA
## uBoot is good

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

# Installing Rescue System

Erasing 128 Kibyte @ 400000 -- 100 % complete.
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
Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 220 -- 100 % complete
ubiformat: formatting eraseblock 255 -- 100 % complete
# Rescue System installation has completed successfully.
rescue:/tmp#

Edit3: The new rescue system is flashed and the first shock was the non-blinking LED. But all is fine and the debian installer script is currently running! Thanks for your help John Doe.



Edited 3 time(s). Last edit at 02/28/2011 01:14PM by Ultrazauberer.