Recovery System ready for use

Hi,

the Problem was zcip.

After adding a working dhcp-Server the box was reachable.


Lothar

hi jeff,
i just booted my ubuntu live cd and compiled my own image according to your howto. after i tried to flash from openwrt to debian my dockstar is blinking first green then yellow. i guess i need a serial connection to unbrick it. how do i flash the image file created with your howto and how do i setup uboot?
thnx in advance
luke

Somehow the script doesn't run on my dockstar :(
It always quits with

# Installing /etc/fw_env.config...
--2010-09-24 18:03:14--  http://.md5/
Resolving .md5... failed: Name or service not known.
wget: unable to resolve host address `.md5'
http://: Invalid host name.
http://: Invalid host name.
## Could not install /etc/fw_env.config from , exiting.

Looking at the code shows:

line 196: install "$FW_PRINTENV"      "$FW_PRINTENV_URL"       755

But FW_PRINTENV_URL ist never defined!

How does the script work on all the other dockstars, or was that a previous version?

mist

FW_PRINTENV_URL is defined at the top of the script. If it's not, you should re-download the script.

Oh, sorry, I mean FW_CONFIG_URL

mist

You're correct, thanks for reporting that. I've updated the script with the correct definition for FW_CONFIG_URL.

-- Jeff

hi again,
i managed to install plugbox linux and from there your recovery system. now i like to mount a ntfs disk but it is not working:

rescue:/# mount.ntfs-3g -o ro /dev/sda1 /mnt
Failed to create '/dev/fuse': Read-only file system
Failed to create '/dev/misc/fuse': No such file or directory
ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root
rescue:/#

any suggestions?

another question: can i follow your debian install howto from the recovery system?

The error message tells you how to fix your problem.

You can run the Debian installer from the rescue system.

i tried

sudo modprobe fuse

and

modprobe fuse

allready. but same problem

hi jeff,

I have no idea where the problem is. now even a ext2 formated usb stick is not mounting ??!!
maybe I made a mistake somewhere als and uboot is misconfigured?!

flash history:
original -> openwrt -> plugbox -> YourRecoverySystem - tried to install debian with your howto -> debootstrap failed

I have no idea what to do now

rescue:~# cat /var/log/messages 
Jan  1 00:00:13 rescue syslog.info syslogd started: BusyBox v1.17.1
Jan  1 00:00:13 rescue user.info init: starting pid 82, tty '/dev/null': '/sbin/klogd -n'
Jan  1 00:00:13 rescue user.notice kernel: klogd started: BusyBox v1.17.1 (2010-09-19 20:39:55 EDT)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Initializing cgroup subsys cpuset
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Initializing cgroup subsys cpu
Jan  1 00:00:13 rescue user.notice kernel: [    0.000000] Linux version 2.6.32.18-dockstar (root@stfu.tcbnet) (gcc version 4.3.5 (Buildroot 2010.08) ) #1 Thu Sep 16 16:04:06 EDT 2010
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] CPU: VIVT data cache, VIVT instruction cache
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] Machine: Marvell SheevaPlug Reference Board
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] Memory policy: ECC disabled, Data cache writeback
Jan  1 00:00:13 rescue user.debug kernel: [    0.000000] On node 0 totalpages: 32768
Jan  1 00:00:13 rescue user.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c06321dc, node_mem_map c06ad000
Jan  1 00:00:13 rescue user.debug kernel: [    0.000000]   Normal zone: 256 pages used for memmap
Jan  1 00:00:13 rescue user.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Jan  1 00:00:13 rescue user.debug kernel: [    0.000000]   Normal zone: 32512 pages, LIFO batch:7
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Jan  1 00:00:13 rescue user.notice kernel: [    0.000000] Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Memory: 128MB = 128MB total
Jan  1 00:00:13 rescue user.notice kernel: [    0.000000] Memory: 122964KB available (5852K code, 695K data, 124K init, 0K highmem)
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] Hierarchical RCU implementation.
Jan  1 00:00:13 rescue user.info kernel: [    0.000000] NR_IRQS:114
Jan  1 00:00:13 rescue user.warn kernel: [    0.000000] Console: colour dummy device 80x30
Jan  1 00:00:13 rescue user.info kernel: [   21.474959] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Jan  1 00:00:13 rescue user.info kernel: [   21.714914] Security Framework initialized
Jan  1 00:00:13 rescue user.info init: starting pid 83, tty '/dev/tty3': '/usr/bin/tail -f /var/log/messages'
Jan  1 00:00:13 rescue user.info kernel: [   21.714933] SELinux:  Disabled at boot.
Jan  1 00:00:13 rescue user.warn kernel: [   21.714953] Mount-cache hash table entries: 512
Jan  1 00:00:13 rescue user.info kernel: [   21.715203] Initializing cgroup subsys ns
Jan  1 00:00:13 rescue user.info kernel: [   21.715217] Initializing cgroup subsys cpuacct
Jan  1 00:00:13 rescue user.info kernel: [   21.715225] Initializing cgroup subsys devices
Jan  1 00:00:13 rescue user.info kernel: [   21.715234] Initializing cgroup subsys freezer
Jan  1 00:00:13 rescue user.info kernel: [   21.715242] Initializing cgroup subsys net_cls
Jan  1 00:00:13 rescue user.info kernel: [   21.715275] CPU: Testing write buffer coherency: ok
Jan  1 00:00:13 rescue user.info kernel: [   21.715826] devtmpfs: initialized
Jan  1 00:00:13 rescue user.info kernel: [   21.717247] regulator: core version 0.5
Jan  1 00:00:13 rescue user.info kernel: [   21.717350] NET: Registered protocol family 16
Jan  1 00:00:13 rescue user.info kernel: [   21.717735] Kirkwood: MV88F6281-A0, TCLK=200000000.
Jan  1 00:00:13 rescue user.info kernel: [   21.717746] Feroceon L2: Cache support initialised.
Jan  1 00:00:13 rescue user.debug kernel: [   21.718143] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
Jan  1 00:00:13 rescue user.debug kernel: [   21.718165]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
Jan  1 00:00:13 rescue user.warn kernel: [   21.720713] bio: create slab <bio-0> at 0
Jan  1 00:00:13 rescue user.info kernel: [   21.721007] vgaarb: loaded
Jan  1 00:00:13 rescue user.notice kernel: [   21.721272] SCSI subsystem initialized
Jan  1 00:00:13 rescue user.info kernel: [   21.721523] usbcore: registered new interface driver usbfs
Jan  1 00:00:13 rescue user.info kernel: [   21.721583] usbcore: registered new interface driver hub
Jan  1 00:00:13 rescue user.info kernel: [   21.721682] usbcore: registered new device driver usb
Jan  1 00:00:13 rescue user.info kernel: [   21.722119] Switching to clocksource orion_clocksource
Jan  1 00:00:13 rescue user.info kernel: [   21.727464] NET: Registered protocol family 2
Jan  1 00:00:13 rescue user.info kernel: [   21.727715] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:13 rescue user.info kernel: [   21.728493] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Jan  1 00:00:13 rescue user.info kernel: [   21.728593] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 00:00:13 rescue user.info kernel: [   21.728647] TCP: Hash tables configured (established 4096 bind 4096)
Jan  1 00:00:13 rescue user.info kernel: [   21.728656] TCP reno registered
Jan  1 00:00:13 rescue user.info kernel: [   21.728813] NET: Registered protocol family 1
Jan  1 00:00:13 rescue user.info kernel: [   21.729081] RPC: Registered udp transport module.
Jan  1 00:00:13 rescue user.info kernel: [   21.729090] RPC: Registered tcp transport module.
Jan  1 00:00:13 rescue user.info kernel: [   21.729097] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  1 00:00:13 rescue user.warn kernel: [   21.729251] NetWinder Floating Point Emulator V0.97 (double precision)
Jan  1 00:00:13 rescue user.info kernel: [   21.729497] audit: initializing netlink socket (disabled)
Jan  1 00:00:13 rescue user.notice kernel: [   21.729529] type=2000 audit(0.242:1): initialized
Jan  1 00:00:13 rescue user.notice kernel: [   21.736365] VFS: Disk quotas dquot_6.5.2
Jan  1 00:00:13 rescue user.warn kernel: [   21.736625] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan  1 00:00:13 rescue user.info kernel: [   21.739237] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan  1 00:00:13 rescue user.notice kernel: [   21.740863] Registering the dns_resolver key type
Jan  1 00:00:13 rescue user.notice kernel: [   21.740914] Slow work thread pool: Starting up
Jan  1 00:00:13 rescue user.notice kernel: [   21.741038] Slow work thread pool: Ready
Jan  1 00:00:13 rescue user.info kernel: [   21.741047] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
Jan  1 00:00:13 rescue user.info kernel: [   21.741817] fuse init (API version 7.13)
Jan  1 00:00:13 rescue user.info kernel: [   21.742303] SGI XFS with security attributes, large block/inode numbers, no debug enabled
Jan  1 00:00:13 rescue user.info kernel: [   21.743866] msgmni has been set to 240
Jan  1 00:00:13 rescue user.info kernel: [   21.745951] alg: No test for stdrng (krng)
Jan  1 00:00:13 rescue user.info kernel: [   21.746119] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan  1 00:00:13 rescue user.info kernel: [   21.746132] io scheduler noop registered
Jan  1 00:00:13 rescue user.info kernel: [   21.746139] io scheduler anticipatory registered
Jan  1 00:00:13 rescue user.info kernel: [   21.746147] io scheduler deadline registered
Jan  1 00:00:13 rescue user.info kernel: [   21.746410] io scheduler cfq registered (default)
Jan  1 00:00:13 rescue user.info kernel: [   21.752389] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Jan  1 00:00:13 rescue user.info kernel: [   21.752849] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
Jan  1 00:00:13 rescue user.info kernel: [   22.134854] console [ttyS0] enabled
Jan  1 00:00:13 rescue user.info kernel: [   22.138942] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Jan  1 00:00:13 rescue user.info kernel: [   22.147561] Scanning device for bad blocks
Jan  1 00:00:13 rescue user.notice kernel: [   22.227601] 4 cmdlinepart partitions found on MTD device orion_nand
Jan  1 00:00:13 rescue user.notice kernel: [   22.233913] Creating 4 MTD partitions on "orion_nand":
Jan  1 00:00:13 rescue user.notice kernel: [   22.239080] 0x000000000000-0x000000100000 : "u-boot"
Jan  1 00:00:13 rescue user.notice kernel: [   22.244644] 0x000000100000-0x000000500000 : "uImage"
Jan  1 00:00:13 rescue user.notice kernel: [   22.250080] 0x000000500000-0x000002500000 : "rootfs"
Jan  1 00:00:13 rescue user.notice kernel: [   22.255556] 0x000002500000-0x000010000000 : "data"
Jan  1 00:00:13 rescue user.notice kernel: [   22.261239] UBI: attaching mtd2 to ubi0
Jan  1 00:00:13 rescue user.notice kernel: [   22.265120] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Jan  1 00:00:13 rescue user.notice kernel: [   22.271415] UBI: logical eraseblock size:    129024 bytes
Jan  1 00:00:13 rescue user.notice kernel: [   22.276849] UBI: smallest flash I/O unit:    2048
Jan  1 00:00:13 rescue user.notice kernel: [   22.281574] UBI: sub-page size:              512
Jan  1 00:00:13 rescue user.notice kernel: [   22.286222] UBI: VID header offset:          512 (aligned 512)
Jan  1 00:00:13 rescue user.notice kernel: [   22.292081] UBI: data offset:                2048
Jan  1 00:00:14 rescue user.notice kernel: [   22.356496] UBI: attached mtd2 to ubi0
Jan  1 00:00:14 rescue user.notice kernel: [   22.360263] UBI: MTD device name:            "rootfs"
Jan  1 00:00:14 rescue user.notice kernel: [   22.365360] UBI: MTD device size:            32 MiB
Jan  1 00:00:14 rescue user.notice kernel: [   22.370256] UBI: number of good PEBs:        256
Jan  1 00:00:14 rescue user.notice kernel: [   22.374905] UBI: number of bad PEBs:         0
Jan  1 00:00:14 rescue user.notice kernel: [   22.379368] UBI: max. allowed volumes:       128
Jan  1 00:00:14 rescue user.notice kernel: [   22.384016] UBI: wear-leveling threshold:    4096
Jan  1 00:00:14 rescue user.notice kernel: [   22.388742] UBI: number of internal volumes: 1
Jan  1 00:00:14 rescue user.notice kernel: [   22.393215] UBI: number of user volumes:     1
Jan  1 00:00:14 rescue user.notice kernel: [   22.397681] UBI: available PEBs:             0
Jan  1 00:00:14 rescue user.notice kernel: [   22.402153] UBI: total number of reserved PEBs: 256
Jan  1 00:00:14 rescue user.notice kernel: [   22.407055] UBI: number of PEBs reserved for bad PEB handling: 2
Jan  1 00:00:14 rescue user.notice kernel: [   22.413098] UBI: max/mean erase counter: 11/2
Jan  1 00:00:14 rescue user.notice kernel: [   22.417474] UBI: image sequence number: 0
Jan  1 00:00:14 rescue user.notice kernel: [   22.421512] UBI: background thread "ubi_bgt0d" started, PID 38
Jan  1 00:00:14 rescue user.notice kernel: [   22.427550] MV-643xx 10/100/1000 ethernet driver version 1.4
Jan  1 00:00:14 rescue user.info kernel: [   22.433331] mv643xx_eth smi: probed
Jan  1 00:00:14 rescue user.notice kernel: [   22.438617] net eth0: port 0 with MAC address 02:50:43:05:70:b5
Jan  1 00:00:14 rescue user.info kernel: [   22.444663] console [netcon0] enabled
Jan  1 00:00:14 rescue user.info kernel: [   22.448344] netconsole: network logging started
Jan  1 00:00:14 rescue user.info kernel: [   22.452912] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  1 00:00:14 rescue user.info kernel: [   22.459509] orion-ehci orion-ehci.0: Marvell Orion EHCI
Jan  1 00:00:14 rescue user.info kernel: [   22.464821] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
Jan  1 00:00:14 rescue user.info kernel: [   22.502170] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
Jan  1 00:00:14 rescue user.info kernel: [   22.522157] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
Jan  1 00:00:14 rescue user.info kernel: [   22.528161] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jan  1 00:00:14 rescue user.info kernel: [   22.534994] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  1 00:00:14 rescue user.info kernel: [   22.542260] usb usb1: Product: Marvell Orion EHCI
Jan  1 00:00:14 rescue user.info kernel: [   22.546986] usb usb1: Manufacturer: Linux 2.6.32.18-dockstar ehci_hcd
Jan  1 00:00:14 rescue user.info kernel: [   22.553464] usb usb1: SerialNumber: orion-ehci.0
Jan  1 00:00:14 rescue user.info kernel: [   22.558375] usb usb1: configuration #1 chosen from 1 choice
Jan  1 00:00:14 rescue user.info kernel: [   22.564107] hub 1-0:1.0: USB hub found
Jan  1 00:00:14 rescue user.info kernel: [   22.567896] hub 1-0:1.0: 1 port detected
Jan  1 00:00:14 rescue user.info kernel: [   22.572073] Initializing USB Mass Storage driver...
Jan  1 00:00:14 rescue user.info kernel: [   22.577074] usbcore: registered new interface driver usb-storage
Jan  1 00:00:14 rescue user.info kernel: [   22.583131] USB Mass Storage support registered.
Jan  1 00:00:14 rescue user.info kernel: [   22.587973] mice: PS/2 mouse device common for all mice
Jan  1 00:00:14 rescue user.info kernel: [   22.593288] i2c /dev entries driver
Jan  1 00:00:14 rescue user.info kernel: [   22.597586] device-mapper: uevent: version 1.0.3
Jan  1 00:00:14 rescue user.info kernel: [   22.602639] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Jan  1 00:00:14 rescue user.info kernel: [   22.611203] cpuidle: using governor ladder
Jan  1 00:00:14 rescue user.info kernel: [   22.615470] cpuidle: using governor menu
Jan  1 00:00:14 rescue user.info kernel: [   22.619523] Registered led device: dockstar:green:health
Jan  1 00:00:14 rescue user.info kernel: [   22.624950] Registered led device: dockstar:orange:health
Jan  1 00:00:14 rescue user.notice kernel: [   22.630430] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
Jan  1 00:00:14 rescue user.notice kernel: [   22.636842] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
Jan  1 00:00:14 rescue user.info kernel: [   22.682190] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
Jan  1 00:00:14 rescue user.info kernel: [   22.722188] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
Jan  1 00:00:14 rescue user.info kernel: [   22.762239] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
Jan  1 00:00:14 rescue user.info kernel: [   22.802185] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
Jan  1 00:00:14 rescue user.info kernel: [   22.809066] TCP cubic registered
Jan  1 00:00:14 rescue user.info kernel: [   22.812333] NET: Registered protocol family 17
Jan  1 00:00:14 rescue user.debug kernel: [   22.816848] Gating clock of unused units
Jan  1 00:00:14 rescue user.debug kernel: [   22.816856] before: 0x00dfc3fd
Jan  1 00:00:14 rescue user.debug kernel: [   22.816864]  after: 0x00c701d9
Jan  1 00:00:14 rescue user.warn kernel: [   22.817172] registered taskstats version 1
Jan  1 00:00:14 rescue user.info kernel: [   22.821993] Initalizing network drop monitor service
Jan  1 00:00:14 rescue user.info kernel: [   22.827108] md: Waiting for all devices to be available before autodetect
Jan  1 00:00:14 rescue user.info kernel: [   22.833940] md: If you don't use raid, use raid=noautodetect
Jan  1 00:00:14 rescue user.info kernel: [   22.840019] md: Autodetecting RAID arrays.
Jan  1 00:00:14 rescue user.info kernel: [   22.844155] md: Scanned 0 and added 0 devices.
Jan  1 00:00:14 rescue user.info kernel: [   22.848617] md: autorun ...
Jan  1 00:00:14 rescue user.info kernel: [   22.851416] md: ... autorun DONE.
Jan  1 00:00:14 rescue user.info kernel: [   22.906046] usb 1-1: new high speed USB device using orion-ehci and address 2
Jan  1 00:00:14 rescue user.notice kernel: [   22.913675] UBIFS: recovery needed
Jan  1 00:00:14 rescue user.notice kernel: [   22.996773] UBIFS: recovery deferred
Jan  1 00:00:14 rescue user.notice kernel: [   23.000376] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
Jan  1 00:00:14 rescue user.notice kernel: [   23.006427] UBIFS: mounted read-only
Jan  1 00:00:14 rescue user.notice kernel: [   23.010019] UBIFS: file system size:   30836736 bytes (30114 KiB, 29 MiB, 239 LEBs)
Jan  1 00:00:14 rescue user.notice kernel: [   23.017718] UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
Jan  1 00:00:14 rescue user.notice kernel: [   23.025068] UBIFS: media format:       w4/r0 (latest is w4/r0)
Jan  1 00:00:14 rescue user.notice kernel: [   23.030928] UBIFS: default compressor: lzo
Jan  1 00:00:14 rescue user.notice kernel: [   23.035051] UBIFS: reserved for root:  0 bytes (0 KiB)
Jan  1 00:00:14 rescue user.warn kernel: [   23.040765] VFS: Mounted root (ubifs filesystem) readonly on device 0:16.
Jan  1 00:00:14 rescue user.info kernel: [   23.047686] Freeing init memory: 124K
Jan  1 00:00:14 rescue user.info kernel: [   23.076252] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
Jan  1 00:00:14 rescue user.info kernel: [   23.083011] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jan  1 00:00:14 rescue user.info kernel: [   23.090181] usb 1-1: Product: USB2.0 Hub
Jan  1 00:00:14 rescue user.info kernel: [   23.112491] usb 1-1: configuration #1 chosen from 1 choice
Jan  1 00:00:14 rescue user.info kernel: [   23.122415] hub 1-1:1.0: USB hub found
Jan  1 00:00:14 rescue user.info kernel: [   23.132688] hub 1-1:1.0: 4 ports detected
Jan  1 00:00:16 rescue user.info kernel: [   38.455496] eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Jan  1 00:00:17 rescue daemon.info ifplugd(eth0)[69]: Link beat detected.
Jan  1 00:00:19 rescue daemon.info ifplugd(eth0)[69]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jan  1 00:00:19 rescue daemon.warn ifplugd(eth0)[69]: client: udhcpc (v1.17.1) started
Jan  1 00:00:19 rescue daemon.warn ifplugd(eth0)[69]: client: Sending discover...
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: Sending select for 192.168.11.43...
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: Lease of 192.168.11.43 obtained, lease time 600
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: deleting routers
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: route: SIOCDELRT: No such process
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: adding dns 192.168.11.1
Jan  1 00:00:20 rescue daemon.warn ifplugd(eth0)[69]: client: adding dns 192.168.11.254
Jan  1 00:00:47 rescue daemon.warn ifplugd(eth0)[69]: client: ntpd: bad address 'pool.ntp.org'
Jan  1 00:00:47 rescue daemon.warn ifplugd(eth0)[69]: client: run-parts: /etc/network/if-up.d/ntpd exited with code 1
Jan  1 00:00:47 rescue daemon.err ifplugd(eth0)[69]: Program execution failed, return value is 1.
Jan  1 00:01:10 rescue user.info sshd[105]: Accepted password for root from 192.168.11.1 port 49702 ssh2
Sep 25 02:43:14 rescue user.err passwd: /etc/passwd: Read-only file system
Sep 25 02:43:14 rescue user.err passwd: can't update password file /etc/passwd
Sep 25 02:43:22 rescue user.info kernel: [  223.822476] usb 1-1.2: new high speed USB device using orion-ehci and address 3
Sep 25 02:43:22 rescue user.info kernel: [  223.934190] usb 1-1.2: New USB device found, idVendor=3538, idProduct=0054
Sep 25 02:43:22 rescue user.info kernel: [  223.941100] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 25 02:43:22 rescue user.info kernel: [  223.948461] usb 1-1.2: Product: Intelligent
Sep 25 02:43:22 rescue user.info kernel: [  223.952695] usb 1-1.2: Manufacturer: I-Stick mini
Sep 25 02:43:22 rescue user.info kernel: [  223.957422] usb 1-1.2: SerialNumber: 110360b0614503
Sep 25 02:43:22 rescue user.info kernel: [  223.963413] usb 1-1.2: configuration #1 chosen from 1 choice
Sep 25 02:43:22 rescue user.info kernel: [  223.973228] scsi0 : SCSI emulation for USB Mass Storage devices
Sep 25 02:43:22 rescue user.debug kernel: [  223.983511] usb-storage: device found at 3
Sep 25 02:43:22 rescue user.debug kernel: [  223.983521] usb-storage: waiting for device to settle before scanning
Sep 25 02:43:27 rescue user.debug kernel: [  228.982432] usb-storage: device scan complete
Sep 25 02:43:27 rescue user.notice kernel: [  228.983526] scsi 0:0:0:0: Direct-Access     pqi      IntelligentStick 0.00 PQ: 0 ANSI: 2
Sep 25 02:45:22 rescue user.info kernel: [  343.773192] usb 1-1.2: USB disconnect, address 3
Sep 25 02:45:27 rescue user.info kernel: [  348.522474] usb 1-1.3: new high speed USB device using orion-ehci and address 4
Sep 25 02:45:27 rescue user.info kernel: [  348.634191] usb 1-1.3: New USB device found, idVendor=3538, idProduct=0054
Sep 25 02:45:27 rescue user.info kernel: [  348.641102] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 25 02:45:27 rescue user.info kernel: [  348.648462] usb 1-1.3: Product: Intelligent
Sep 25 02:45:27 rescue user.info kernel: [  348.652700] usb 1-1.3: Manufacturer: I-Stick mini
Sep 25 02:45:27 rescue user.info kernel: [  348.657424] usb 1-1.3: SerialNumber: 110360b0614503
Sep 25 02:45:27 rescue user.info kernel: [  348.663377] usb 1-1.3: configuration #1 chosen from 1 choice
Sep 25 02:45:27 rescue user.info kernel: [  348.673081] scsi1 : SCSI emulation for USB Mass Storage devices
Sep 25 02:45:27 rescue user.debug kernel: [  348.683366] usb-storage: device found at 4
Sep 25 02:45:27 rescue user.debug kernel: [  348.683376] usb-storage: waiting for device to settle before scanning
Sep 25 02:45:32 rescue user.debug kernel: [  353.682559] usb-storage: device scan complete
Sep 25 02:45:32 rescue user.notice kernel: [  353.683651] scsi 1:0:0:0: Direct-Access     pqi      IntelligentStick 0.00 PQ: 0 ANSI: 2

^ When I check the dmesg on debain, it usually shows the device name etc for eg /dev/sdb1 when you connect the hard disk.

But in the rescue system it stops before that just like shown above.

How do I find the device name to mount the hard disk?

rescue:/sbin# dmesg|tail -10
[ 6540.327574] usb-storage: device scan complete
[ 6540.328440] scsi 0:0:0:0: Direct-Access CENTON DS Pro 0.00 PQ: 0 ANSI: 2
[ 7005.837270] sd 0:0:0:0: [sda] 31588352 512-byte logical blocks: (16.1 GB/15.0 GiB)
[ 7005.846508] sd 0:0:0:0: [sda] Write Protect is off
[ 7005.851380] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[ 7005.851391] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7005.860758] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7005.866892] sda: sda1 sda2
[ 7006.739627] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 7006.745754] sd 0:0:0:0: [sda] Attached SCSI removable disk


rescue:/sbin# fdisk -l

Disk /dev/mtdblock0: 1 MB, 1048576 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/sda: 16.1 GB, 16173236224 bytes
64 heads, 32 sectors/track, 15424 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 14649 15000560 83 Linux
/dev/sda2 14650 15424 793600 82 Linux swap

...
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 203 -- 100 % complete
ubiformat: formatting eraseblock 255 -- 100 % complete
## Error: "rescue_installed" not defined
# Rescue System installation has completed successfully.

Script runs fine, only the rescue_installed not difinied worries me a little bit. Can I risk to reboot?

nevermind



Edited 1 time(s). Last edit at 10/11/2010 07:58AM by gorgone.

Hi everybody,

I'm also using buildroot to create a complete system (not only for rescue purposes) which should be able to act as:
- fileserver (samba, ftp)
- printserver (cups)
- media streaming/sharing
- webserver
- some other tiny tools I haven't thought about now

I'm working on cleaning up and put it online via gitorius or something else.


I realized that you are using XFS (I integrated the newest xfsprogs into br already). But I encountered a strange behaviour of xfs running on my dockstar, which I described here:
http://www.spinics.net/lists/xfs/msg01232.html

It seems, that armv5te is not ready (probably will never be) for productive usage with XFS, since it uses VIVT and not VIPT (VIPT seems to be fixed in xfs upstream).
Does XFS really behave in a correct manner under the rescue system introduced in this thread?

Regards,
Ossy

Linkstation LS-GL V1 use CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ) and XFS.
http://buffalo.nas-central.org/wiki/Category:LSPro

I use XFS wich Debian Squeeze.

Short feedback: The rescue System seems to work fine on my "GoFlex Home" box, too.

But access to SATA port failed as under debian, see: http://forum.doozan.com/read.php?2,1762

My debian filesystem get corrupt every time there is a power failure and I have to manually run an fsck so that it boots again. The issue is, when the filesystem contains error it doesn't go into rescue system, but gets stuck during boot.

Is there any solution to this problem? Can it be configured in such a way that if its shutdown due to a powerfailure, it has to go to rescue system, run a file system check and then reboot to debian?

varkey i second that .... same problem for me

Hey there I've also tried to install the recovery system. I get an error shorty after the beginning of the installation:

# 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 13 --  6 % complete  libmtd: error!: cannot write 131072 bytes to mtd2 (eraseblock 13, offset 0)
        error 12 (Cannot allocate memory)

ubiformat: error!: cannot write eraseblock 13
           error 12 (Cannot allocate memory)
Installation failed.

What should I do now?

harrim4n

hi jeff i integrate uboot and rescue to my script
and it works fine
but the rescue givs me a error for old uboot
i use your two orginal flashing scripts with a call
so nothing can go wrong there ;-)

--2010-10-25 02:34:10--  http://jeff.doozan.com/debian/rescue/install_rescue.sh
Resolving jeff.doozan.com... 69.163.187.226
Connecting to jeff.doozan.com|69.163.187.226|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7769 (7.6K) [application/x-sh]
Saving to: `install_rescue.sh'

100%[=====================================================================================================================================================================>] 7,769       39.1K/s   in 0.2s

2010-10-25 02:34:10 (39.1 KB/s) - `install_rescue.sh' saved [7769/7769]


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...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
--2010-10-25 02:34:15--  http://jeff.doozan.com/debian/uboot/uboot.mtd0.kwb.md5
Resolving jeff.doozan.com... 69.163.187.226
Connecting to jeff.doozan.com|69.163.187.226|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 49 [text/plain]
Saving to: `/tmp/uboot.md5'

100%[=====================================================================================================================================================================>] 49          --.-K/s   in 0s

2010-10-25 02:34:15 (1.71 MB/s) - `/tmp/uboot.md5' saved [49/49]

##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##

my flash is latest uboot

root@debian:~# md5sum /tmp/mtd0.uboot
ebd566de30c6521e65fb1255415c037f  /tmp/mtd0.uboot

i think its an error in http://jeff.doozan.com/debian/uboot/uboot.mtd0.kwb.md5
into is 7acb243fb8c3f131f1a165b3dc64faaf uboot.mtd0.kwb
but u read in the script mtd0.uboot

## Valid uBoot detected: [dockstar jeff-2010-10-23-current]
## The newest uBoot is already installed on mtd0.


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

# uBoot installation has completed successfully.

Edited 4 time(s). Last edit at 10/24/2010 08:02PM by gorgone.

@gorgone: I forgot to update the rescue installer after I made changes to the uBoot installer. It should be working now. Thanks!

-- Jeff

Jeff Wrote:
-------------------------------------------------------
> @gorgone: I forgot to update the rescue installer
> after I made changes to the uBoot installer. It
> should be working now. Thanks!
>
> -- Jeff


work thanks
found a little error

2010-10-25 18:44:02 (20.4 MB/s) - `/tmp/valid-uboot.md5' saved [643/643]

[: 230: unexpected operator
## uBoot is good

Hi,

I've got a little problem installing the rescue system. After downloading the install_rescue.sh and executing it stops with the error:

##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##

BUT - I've done a fresh install of uboot with the installation to internal flash. AND install of uboot tells me it is already up do date, if I want to reset it. So now I am at a loss. Maybe the MD5 is not correct?

Any Ideas?

Johanes

Thanks for the report Johanes. It should work now.

Hi,

it will not accept the new registered arcNumber 2998 for the Seagate DockStar.
Will this be fixed?

Hello,
I installed the rescue-system with Jeffs script und all looks good. But after a reboot I don't get a IP-Adress.
The serial-log gives the followed output:

[    1.657655] usb 1-1: configuration #1 chosen from 1 choice                                            
[    1.663607] hub 1-1:1.0: USB hub found                                                                
[    1.669770] hub 1-1:1.0: 4 ports detected                                                             
Initializing random number generator... read-only file system detected...done                            
Starting network...                                                                                      
ntpd: bad address 'pool.ntp.org'                                                                         
run-parts: /etc/network/if-up.d/ntpd exited with code 1                                                  
udhcpc (v1.17.1) started                                                                                 
Sending discover...                                                                                      
Sending discover...                                                                                      
[   16.846876] eth0: link up, 1000 Mb/s, full duplex, flow control disabled                              
Sending discover...                                                                                      
Sending select for 192.168.0.26...                                                                       
Sending select for 192.168.0.26...                                                                       
Sending select for 192.168.0.26...                                                                       
No lease, failing                                                                                        
Starting Network Interface Plugging Daemon: eth0.                                                        
Starting sshd: OK                                                                                        
Starting heartbeat LED...

The /etc/network/interfaces:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
up echo default-on > /sys/class/leds/dockstar\:green\:health/trigger
down echo none > /sys/class/leds/dockstar\:green\:health/trigger

Any ideas??

regards
Stefan

I went for it!
I just installed the Recovery System! :)
It works for me, I get IP address and I SSH'ed in. Thanks Jeff! :)



Edited 1 time(s). Last edit at 11/04/2010 10:54PM by rgtaa.

Hello!

I have debian squeeze running from the dock hd on the dockstar.

Two weeks ago I installed the rescue system. Had a test that it really worked.

But now it does not.

After shutdown the dockstar with "halt -p" after the lights go off on hd I pull it out and restart the dockstar by pull and plugging the power cable. By my understanding now the rescue should boot up and get an ip from my router (dhcp is on). But this never happens. The led first blinks green, then orange and then turns off.
fw_setenv arcNumber is set to 2998. At my first test two weeks ago the led turned to a heartbeat pulse after a while. But now it does nothing. Even after waiting 10 minutes the dockstar does not show up in the dhcp management page of my router.

What can I do now? Any hint for me?

To make things clear: The system boots every time and very stable from the hdd. But I have to do some managements with fdisk at the hdd in the dock and now I can not because the rescue system fails.

I'm not sure, but if you start from hard drive boot or usb stick, you can always load recovery system on again.
Jeff can advise you if he has a fix, but before I installed recovery system, I asked Jeff and he said, if it screws up, just load it again from usb boot drive. I installed the recovery system because my pogoenvironment lost SSH , so I figured I have nothing to lose, and I loaded the Recovery system from boot drive. Good luck.



Edited 2 time(s). Last edit at 11/05/2010 06:15PM by rgtaa.