Linux Device Hacking - Rescue System

GoFlex Net not installed UBoot (1 reply)

Den-J — Thu, 21 Mar 2013 16:39:36 -0400

Hi,

i found this tutorial:
http://morschi.com/2012/10/05/seagate-goflex-net-debian/

However, I have not installed the latest uboot and therefore cannot install the rescue system into NAND. After 6 hours of searching through google and this website, I cannot find anything which helps.

# 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.
##

With the Rescue system on an USB Stick I am able to ssh box. But without the rescue system/USB Stick the box does not boot properly. What can I do?

Best regards

I installed Rescue System, now I can't boot into anything. (9 replies)

Cassie — Sun, 17 Feb 2013 15:43:18 -0500

I had my GoFlex Home working on USB, but then I installed the Rescue System into NAND using Jeff's script. I tried to reboot into the Rescue System , but the green light just kept flashing, after about an hour, I tried to boot from first my Debian USB, then My Arch Linux USB. in both cases green light went solid, but the light on the USB stick kept flashing non stop.

I haven't been able to get netconsole, and I don't know what the IP is, since it changed every boot (so did the MAC address). This is what my fw_env loooked like before I rebooted.

ddr_rd="0x1100000"
arcNumber="3338"
baudrate="115200"
boot_auto="rd_args='rootfstype=auto'; run boot_rdaddr_kern=0x680000"
boot_kern="run set_bootargs; bootm \$addr_kern"
boot_rd="run set_bootargs; bootm \$addr_kern \$addr_rd"
bootdelay="3"
chain="nand read.e 0x800000 0x480000 0x80000; go 0x800200"
console="ttyS0,115200"
ethact="egiga0"
ethaddr="02:50:43:26:87:63"
ext2_auto="ext2load \$boot_dev \$addr_rd /boot/uInitrd"
ext2_boot="run ext2_rd boot_rd; run ext2_auto boot_auto; run boot_kern"
ext2_kern="ext2load \$boot_dev \$addr_kern /boot/uImage"
ext2_rd="ext2load \$boot_dev \$addr_rd /uInitrd"
fast_boot="run fast_rd ubi_args ubi_fallback"
fast_rd="ubifsmount fast; ubifsload \$addr_rd /uInitrd"
fat_boot="run fat_rd boot_rd"
fat_kern="fatload \$boot_dev \$addr_kern /boot/uImage"
fat_rd="fatload \$boot_dev \$addr_rd /uInitrd"
hd_args_0="boot_dev='ide 0:1'; dev_args='root=/dev/sda1'"
hd_args_1="boot_dev='ide 1:1'; dev_args='root=/dev/sdb1'"
hd_boot="run ide_start; for scan in 0 1; do run hd_args_\$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback; done"
ide_start="ide reset"
led_error="orange blinking"
led_exit="green off"
led_init="green blinking"
mtddevname="u-boot"
mtddevnum="0"
mtdids="nand0=orion_nand"
mtdparts="mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(pogoplug),-(root)"
nc_start="setenv stdin nc; setenv stdout nc; setenv stderr nc; version"
nc_test="ping \$ncip"
ipaddr="10.0.1.14"
ncip="10.0.1.13"
ncipk="10.0.1.12"
serverip="10.0.1.11"
stderr="nc"
stdin="nc"
stdout="nc"
partition="nand0,0"
preboot="run ubi_start silent_boot; run nc_test nc_start; run usb_start"
rescue="dev_args='ubi.mtd=root rootfstype=preboot'; boot_dev='usb 0:1'; run ext2_kern ext2_auto boot_rd; boot_dev='ide 0:1'; run ide_start ext2_kern ext2_auto boot_rd; run silent_rd ubi_fallback; run fast_rd ubi_fallback; run ubi_rd ubi_fallback"
set_bootargs="setenv bootargs console=\$console \$mtdparts \$dev_args \$rd_args netconsole=@\$ipaddr/eth0,@\$ncipk/"
silent_boot="run silent_rd ubi_args ubi_fallback"
silent_rd="ubifsmount silent; ubifsload \$addr_rd /uInitrd"
ubi_args="dev_args='ubi.mtd=root'"
ubi_boot="run ubi_rd ubi_args ubi_fallback"
ubi_fallback="run ubi_kern boot_rd"
ubi_kern="ubifsmount boot; ubifsload \$addr_kern /boot/uImage"
ubi_rd="ubifsmount ramdisk; ubifsload \$addr_rd /uInitrd"
ubi_start="ubi part root"
usb_args_0="boot_dev='usb 0:1'; dev_args='root=/dev/sda1 rootdelay=10'"
usb_args_1="boot_dev='usb 1:1'; dev_args='root=/dev/sdb1 rootdelay=10'"
usb_args_2="boot_dev='usb 2:1'; dev_args='root=/dev/sdc1 rootdelay=10'"
usb_args_3="boot_dev='usb 3:1'; dev_args='root=/dev/sdd1 rootdelay=10'"
usb_boot="for scan in 0 1 2 3; do run usb_args_\$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback;done"
usb_start="usb start"
bootcmd="addr_kern='0x800000'; run fast_boot; run hd_boot; run usb_boot; run ubi_boot;"

Is there any way I can get into it with nc? My deskop IP is 10.0.1.11, and at the time that I fw_setenv, the IP of the GoFlex was 10.0,14 Please tell me exactly what I need to enter in my terminal.

OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package (16 replies)

davygravy — Tue, 28 May 2013 18:42:48 -0400

Its taken me a week or so, but I've nearly got it completed... all in NAND flash... all built with Buildroot...

1-Wire File System : Also known as OWFS, it allows one to seamlessly attach and monitor Dallas/Maxim sensors and instruments, such as temperature, humidity, count/quantity, air pressure, windspeed, etc. One can also write it to an LCD.
Temploggerd : A simple daemon that polls OWFS data and formats it to publish on an interactive web page.
Motion : Records images from a (web)cam, examines them for changes, and detects motion. Very configurable and customizable, can be controlled remotely via a separate webpage.
lighttpd : serve up the data and images from the items above.

The current setup has www in /tmp so that things can be collected without messing w/ the UBIFS partition - with an option for periodically syncing the contents to a backup dir/site.

Ping OK - SSH Connection Refused -Rehash'd (3 replies)

maihoaomv — Sun, 03 Mar 2013 18:36:25 -0500

I've got the same problem on my GoFlex Home as techrat in his post "Ping OK - SSH Connection Refused - What Next???" at http://forum.doozan.com/read.php?2,6249,6252#msg-6252

I flub'd it when I tried to flash the rescue onto the NAND. Now it will boot to the USB, the led is green and steady, I can ping it either by IP or rescue.local. I can see "local" on my network but when I try to ssh in I get "ssh: connect to host rescue.local port 22: Connection refused". I tried several things suggested in the forum without sucess. I think I'm going to have to use the serial cable to fix it.

How do I re-flash it over the serial connection?

Thanks

Bootup DHCP issues (18 replies)

john3voltas — Fri, 18 Jan 2013 04:55:22 -0500

(previous subject was "Can't connect to Dockstar" because I didn't notice that after booting the box was lacking an IP address)

1 or 2 years ago I installed both Jeff Doozan's uBoot and Rescue System.
Then I ran Arch Linux for ARM during that period.
A week ago, I had a power outage and after that my I haven't been able to connect to my Dockstar again.
I can't connect to it regardless of having tried to boot both Arch and the Rescue System.
I don't have a serial cable but I have connected to the plug during boot using netconsole.
Here is a log trying to boot to Rescue System:

C:\nc111nt_rodneybeede>nc -u -l -p 6666

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

And this was trying to boot to Arch on USB pendisk:

C:\nc111nt_rodneybeede>nc -u -l -p 6666

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2856016 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.1.10-13-ARCH
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2855952 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Also, here is a DHCP log of TFTPD32 during the Dockstar's boot:

Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:10:75:1A:BD:D7 [05/10 20:57:42.234]
Client requested address 0.0.0.112 [05/10 20:57:42.250]
DHCP: proposed address 192.168.1.99 [05/10 20:57:54.309]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:10:75:1A:BD:D7 [05/10 20:57:54.309]
Client requested address 0.0.0.112 [05/10 20:57:54.309]
DHCP: proposed address 192.168.1.99 [05/10 20:58:06.305]
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:10:75:1A:BD:D7 [05/10 20:58:06.305]
Client requested address 0.0.0.112 [05/10 20:58:06.305]
DHCP: proposed address 192.168.1.99 [05/10 20:58:18.302]
3188 Request 2 not processed [05/10 20:58:18.302]
3188 Request 2 not processed [05/10 20:58:18.302]
3188 Request 2 not processed [05/10 20:58:18.302]

Seems like the device is asking for an IP lease but then something fails.
So I grabbed my USB pendisk with Arch Linux ARM and modified /etc/rc.conf to set it up for a static IP.
But even so I still can't connect to the device.
I am beginning to wonder if installing the Rescue System was a good idea...
Is there anything else I could try before getting a serial cable?
BTW, can someone advise me on a good ebay/amazon deal to buy a serial cable to connect to my Dockstar.
Preferrably a cable ready for this device that won't force me to get a solder iron or a special cable-end.
Thanks in advance.
Cheers

Rescue system install on tftp? Need Help (3 replies)

tobi1337 — Thu, 04 Oct 2012 19:36:21 -0400

Hey Guy´s i have some problems to install a Rescue System on my Dockstar. The NAND was complete erased and i reflash the uboot on JTAG with Openocd. What am I doing wrong?

Thanks!
Tobi

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
Marvell>> nand erase 0x100000 0x400000

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete.
OK
Marvell>> tftp 0x800000 uImage-mtd1.img
Using egiga0 device
TFTP from server 192.168.2.36; our IP address is 192.168.2.210
Filename 'uImage-mtd1.img'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         ########################################################
done
Bytes transferred = 3670016 (380000 hex)
Marvell>> nand write.e 0x800000 0x100000 0x380000

NAND write: device 0 offset 0x100000, size 0x380000
 3670016 bytes written: OK
Marvell>> tftp 0x1000000 rootfs-mtd2.img
Using egiga0 device
TFTP from server 192.168.2.36; our IP address is 192.168.2.210
Filename 'rootfs-mtd2.img'.
Load address: 0x1000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######
done
Bytes transferred = 28704768 (1b60000 hex)
Marvell>> setenv rescue_set_bootargs 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params'
Marvell>> setenv 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'
Marvell>> setenv bootcmd 'run bootcmd_usb; usb stop; run rescue_bootcmd; reset'
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0xc0000 -- 100% complete.
Writing to Nand... done
Marvell>> run rescue_bootcmd

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.3.2-kirkwide (davygravy@bitbaker64) (gcc version 4.3.5 (Buildroot 2010.08) ) #1 Mon May 28 13:23:17 CDT 2012
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    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)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 122080k/122080k available, 8992k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06c06c8   (6882 kB)
[    0.000000]       .init : 0xc06c1000 - 0xc06eb000   ( 168 kB)
[    0.000000]       .data : 0xc06ec000 - 0xc0734c38   ( 292 kB)
[    0.000000]        .bss : 0xc0734c5c - 0xc07a4294   ( 446 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:114
[    0.000000] gpiochip_add: registered GPIOs 0 to 31 on device: orion_gpio0
[    0.000000] gpiochip_add: registered GPIOs 32 to 49 on device: orion_gpio1
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[    0.000000] Console: colour dummy device 80x30
[   12.788749] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   12.878682] pid_max: default: 32768 minimum: 301
[   12.878785] Security Framework initialized
[   12.878803] SELinux:  Disabled at boot.
[   12.878850] Mount-cache hash table entries: 512
[   12.879133] Initializing cgroup subsys cpuacct
[   12.879145] Initializing cgroup subsys devices
[   12.879155] Initializing cgroup subsys freezer
[   12.879163] Initializing cgroup subsys net_cls
[   12.879210] CPU: Testing write buffer coherency: ok
[   12.879426] Setting up static identity map for 0x511040 - 0x51107c
[   12.880083] devtmpfs: initialized
[   12.881449] NET: Registered protocol family 16
[   12.881946] Kirkwood: MV88F6281-A0, TCLK=200000000.
[   12.881960] Feroceon L2: Cache support initialised.
[   12.886274] bio: create slab  at 0
[   12.886639] vgaarb: loaded
[   12.886905] SCSI subsystem initialized
[   12.887253] usbcore: registered new interface driver usbfs
[   12.887324] usbcore: registered new interface driver hub
[   12.887419] usbcore: registered new device driver usb
[   12.887996] Switching to clocksource orion_clocksource
[   12.913140] NET: Registered protocol family 2
[   12.913373] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[   12.913955] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[   12.914055] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   12.914109] TCP: Hash tables configured (established 4096 bind 4096)
[   12.914119] TCP reno registered
[   12.914129] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   12.914152] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   12.914382] NET: Registered protocol family 1
[   12.914694] RPC: Registered named UNIX socket transport module.
[   12.914705] RPC: Registered udp transport module.
[   12.914713] RPC: Registered tcp transport module.
[   12.914720] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   12.914785] NetWinder Floating Point Emulator V0.97 (double precision)
[   12.915331] audit: initializing netlink socket (disabled)
[   12.915366] type=2000 audit(0.110:1): initialized
[   12.923927] VFS: Disk quotas dquot_6.5.2
[   12.924158] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   12.926830] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   12.927949] JFFS2 version 2.2. (NAND) (SUMMARY)  Â© 2001-2006 Red Hat, Inc.
[   12.928525] fuse init (API version 7.18)
[   12.928998] SGI XFS with security attributes, large block/inode numbers, no debug enabled
[   12.930380] msgmni has been set to 238
[   12.931664] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   12.931678] io scheduler noop registered
[   12.931686] io scheduler deadline registered
[   12.931721] io scheduler cfq registered (default)
[   12.931779] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   12.931815] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   12.968099] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   13.008077] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   13.048068] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   13.088068] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   13.088408] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   13.108934] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   13.599817] console [ttyS0] enabled
[   13.604413] ONFI flash detected
[   13.607665] ONFI param page 0 valid
[   13.611193] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD)
[   13.618904] Scanning device for bad blocks
[   13.771060] Bad eraseblock 1990 at 0x00000f8c0000
[   13.780042] 4 cmdlinepart partitions found on MTD device orion_nand
[   13.786333] Creating 4 MTD partitions on "orion_nand":
[   13.791512] 0x000000000000-0x000000100000 : "u-boot"
[   13.797353] 0x000000100000-0x000000500000 : "uImage"
[   13.803185] 0x000000500000-0x000002500000 : "rootfs"
[   13.808933] 0x000002500000-0x000010000000 : "data"
[   13.814788] UBI: attaching mtd2 to ubi0
[   13.818669] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[   13.824962] UBI: logical eraseblock size:    129024 bytes
[   13.830397] UBI: smallest flash I/O unit:    2048
[   13.835120] UBI: sub-page size:              512
[   13.839762] UBI: VID header offset:          512 (aligned 512)
[   13.845619] UBI: data offset:                2048
[   13.899747] UBI: max. sequence number:       2
[   13.914295] UBI: attached mtd2 to ubi0
[   13.918079] UBI: MTD device name:            "rootfs"
[   13.923149] UBI: MTD device size:            32 MiB
[   13.928060] UBI: number of good PEBs:        256
[   13.932697] UBI: number of bad PEBs:         0
[   13.937152] UBI: number of corrupted PEBs:   0
[   13.941618] UBI: max. allowed volumes:       128
[   13.946256] UBI: wear-leveling threshold:    4096
[   13.950982] UBI: number of internal volumes: 1
[   13.955438] UBI: number of user volumes:     0
[   13.959903] UBI: available PEBs:             250
[   13.964534] UBI: total number of reserved PEBs: 6
[   13.969260] UBI: number of PEBs reserved for bad PEB handling: 2
[   13.975294] UBI: max/mean erase counter: 1/1
[   13.979584] UBI: image sequence number:  0
[   13.983700] UBI: background thread "ubi_bgt0d" started, PID 41
[   13.989735] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   13.996627] mv643xx_eth smi: probed
[   14.002278] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:xx:xx:xx:xx:c6
[   14.011167] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   14.017768] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   14.023112] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   14.058053] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   14.078035] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   14.084047] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   14.090879] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   14.098145] usb usb1: Product: Marvell Orion EHCI
[   14.102869] usb usb1: Manufacturer: Linux 3.3.2-kirkwide ehci_hcd
[   14.109000] usb usb1: SerialNumber: orion-ehci.0
[   14.114091] hub 1-0:1.0: USB hub found
[   14.117871] hub 1-0:1.0: 1 port detected
[   14.122117] Initializing USB Mass Storage driver...
[   14.127101] usbcore: registered new interface driver usb-storage
[   14.133151] USB Mass Storage support registered.
[   14.138066] mousedev: PS/2 mouse device common for all mice
[   14.143713] i2c /dev entries driver
[   14.147687] device-mapper: uevent: version 1.0.3
[   14.152677] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
[   14.161235] cpuidle: using governor ladder
[   14.165423] cpuidle: using governor menu
[   14.170608] TCP cubic registered
[   14.173852] NET: Registered protocol family 17
[   14.178373] Registering the dns_resolver key type
[   14.183557] registered taskstats version 1
[   14.188362] console [netcon0] enabled
[   14.192038] netconsole: network logging started
[   14.196584] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   14.202951] Initializing network drop monitor service
[   14.208251] md: Waiting for all devices to be available before autodetect
[   14.215068] md: If you don't use raid, use raid=noautodetect
[   14.221388] md: Autodetecting RAID arrays.
[   14.225507] md: Scanned 0 and added 0 devices.
[   14.229990] md: autorun ...
[   14.232796] md: ... autorun DONE.
[   14.236177] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[   14.243274] Please append a correct "root=" boot option; here are the available partitions:
[   14.251683] 1f00            1024 mtdblock0  (driver?)
[   14.256762] 1f01            4096 mtdblock1  (driver?)
[   14.261856] 1f02           32768 mtdblock2  (driver?)
[   14.266939] 1f03          224256 mtdblock3  (driver?)
[   14.272032] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

recovery system - how? (no replies)

chrs — Tue, 25 Sep 2012 11:42:09 -0400

So after getting debian on my dockstar I installed the recovery system, and it works fine. My question is, how does it work/ how to use it?

Basically I have my dockstar running deb 6.0.5, and accidentally deleted the entire /var/log folder. shortly there after the system started giving me "filesystem is read only" errors and then I rebooted, nd now it wont boot at all, just gives me the orange blinking heartbeat light. The system boots recovery just fine and I can mount the usb stick and view/edit the filesystem, but how do I determine why it's not booting like normal since the system is headless, and in addition how do I use the 'recovery' system to actually recover the system so it boots fine again?

Trying to install rescue system on new GoFlex Net (16 replies)

alexisazen — Mon, 15 Oct 2012 15:11:28 -0400

Hi all!

I just got a new GoFlex Net and I am trying to install debian on a USB stick. Initially I tried running Jeff's script but got the same message as here.
After trying with another USB stick, decided to try the recommendation of running the USB rescue system and then installing the rescue system in the nand, booting from that & then installing debian on the stick.
The USB rescue system booted OK but but when I try to install the rescue system it says that I need to install the newest uboot first. I have already installed ubit davygravy-2012-04-19 and I can't figure out what to try next. Any hints?

MacPlug & SMBPLug : Mac/AFPD or Windows/SMB + Print services in a flash/NAND image (37 replies)

davygravy — Sat, 04 May 2013 19:00:55 -0400

MacPlug : Filesharing/AFPD, Printserver/p910nd and much more, all in NAND Flash
SMBPlug : Filesharing/Samba, Printserver/p910nd and much more, all in NAND Flash

Installation is by a bootable USB image. You simply format a USB flash drive, untar the installer image on it, boot the USB drive (using default UBoot settings), run 4 install commands, and then reboot.

Works out-of-the-box:

Apple-style afpd access for NAS and TimeMachine storage [ MacPlug only]
Windows-style Samba access for NAS and TimeMachine storage [ SMBPlug only]
p910nd printer daemon for USB printers (just needs printer name)
sftpd, sshd & ssh
Avahi/Bonjour zeroconf network service advertising

Also includes (requires some configuration):

ssl/tls w/ trust certificate
msmtp and mailx (msmtp is tested and works for sending email via gmail.com)
inadyn (dyndns updater client)
nfsd and nfs utilities (only in MacPlug)
CIFS mounts and CIFS utilities (only in SMBPlug)
smartmontools
filesystem utilities for ext2/3/4, parted (partition editor), and others
gdisk (for setting up partitions larger than 2TB)
wide variety of maintenence/rescue tools and setup utilities

The image is pretty much flash-and-go if you read and follow the directions, but can be customized a bit.

Background:
This image was built using buildroot-2012.08 and Ubuntu/Debian, and bits of Jeff's V2 fs-skeleton are there. The package selection is very different, though. I wanted to build something that would mesh well with Macs/Linux mainly, be robust enough to __always__ withstand power outages and the like, and be simple. For me, robust=plug-n-go-even-after-power-outages.

A major change in Buildroot with uClibc 0.31.2 brought NPTL support, which allowed BerkeleyDB to play nicely with Netatalk. This took a while to get configured correctly, but the results have been positive.

It was also a bit of a challenge to get Samba 3.6.6 to fit nicely in a UBI image that wouldn't fill up 32MB entirely.

What I didn't want was a boxlet with a bloated webserver, perl, python, compilers or any development stuff - just a small rootfs that would fit inside 32MB of flash and let a little Kirkwood box do what it does best - low power consumption, small footprint, good server-performance-per-wattage, etc.

Requirements:

Pogoplug E01/E02, Dockstar, GoFlexNet/Home, perhaps other Kirkwood boxes
a large USB-based-SATA or SATA Hard Drive (for AFP Fileserving and TimeMachine/Capsule NAS)
a USB printer that is supported under Windows, Mac and/or Linux
a USB flash drive (512MB or larger) for use as installation media, known working/bootable w/ your Kirkwood box
familiarity with command-line activities, and a Desktop/Laptop with a working local network connection and ssh client access
tested and working socat/netcat access so that you can control the boot process OR serial access with tested and working minicom access
Windows users should install Bonjour print services before setting up your printer

Installation:
0. Understand the disclaimer : Flash at your own risk - there is always some level of risk in when flashing a chip; I've flashed some of my devices dozens of times and they are fine. For me, MacPlug/SMBPlug both work wonderfully, but YMMV. There is no warranty, neither implied nor expressed. Proceed at your own risk.

0. Make a decision: Do you want AFPD (Apple's Filesharing Protocol, successor to AppleTalk/AppleShare), or do you want Samba (More Windows-centric, though it is also used with Linux and Mac)

1. Format the USB flash drive to ext2 and copy the desired tarball to it:

and expand the tarball using something like tar xvf .

2. Make sure only the USB flashdrive drive is plugged in, and not the USB printer and USB hard drive

3. Boot the USB flashdrive on your Kirkwood box (UBoot's default settings should work fine), log in using username=root , password=root

4. Plug in the USB harddrive and prepare it by formatting the first partition as ext4 (all other partitions can be anything, even swap)

5. STOP and READ: this step will erase whatever kernel and rootfs that is currently residing in mtd1 and mtd2, respectively. If this is not acceptable to you, or if you are unsure of what you are doing, you should stop here and go no further.

If this is what you want to do, then proceed with flashing these files to your NAND partitions mtd1 and mtd2.
Use the following sequence of commands two erase and write to mtd1 and mtd2:

cd /img_files
flash_erase /dev/mtd1 0 0
nandwrite /dev/mtd1 uImage-mtd1.img
flash_erase /dev/mtd2 0 0
ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y

Normal output for this should look like:

MacPlug:/img_files# flash_erase /dev/mtd1 0 0
Erasing 128 Kibyte @ 3e0000 -- 100 % complete 
MacPlug:/img_files# nandwrite /dev/mtd1 uImage-mtd1.img
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 26 at offset 0x340000
Writing data to block 27 at offset 0x360000
MacPlug:/img_files# flash_erase /dev/mtd2 0 0
Erasing 128 Kibyte @ 1fe0000 -- 100 % complete 
MacPlug:/img_files# ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 s
libscan: scanning eraseblock 255 -- 100 % complete  
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 212 -- 100 % complete  
ubiformat: formatting eraseblock 255 -- 100 % complete  
MacPlug:/img_files#

6. Halt your Kirkwood box, remove the USB flash drive

7. Plug in the USB printer and boot (power down & back up)

8. Log in using ssh, user=root, password=root

9. Adjust the printer spec and name, and choose new passwords. Note that if you are using SMBPlug, the smbpasswd binary is not included, but rather the pdbedit binary is included instead, and provides the same functionality for our uses.

Also make the needed changes to enable the following servers/daemons/services/features from the following list:

Samba - the default setup is for a 192.168.x.x network, so if you are using something else, you'll need to modify /etc/smb.conf
inadyn - DYNDNS updater client
NFSD - network file system daemon, great for Linux/Mac OS X [ only in MacPlug ]
CIFS-Utils - mount a Samba share _on_ this device,
avah-daemon - Bonjour/Avahi advertising of servers and information via network, enabling ZeroConf setup for printers, etc.
msmtp - allows access via SSL/TLS to Google's Gmail service, and many other email providers
cron jobs - using crond and the crontab, set up whatever scripts you'd like to run on a scheduled basis
swap - you can use a swap partition on the hard drive and use it in conjunction w/ the NAND/UBIFS rootfs
customize your hostname
customize the printer type/model in the product=( your-printer-brand-and-model-according-to-cups ) in the /etc/avahi/services/p910nd.services file; this will allow your printer client on most computers to automagically configure itself
automatically advertise and identify your printer(s) - also in /etc/avahi/services/p910nd.service, the line my-printers-brand-and-model @ %h
lm-sensors - if your machine has any sensors (like the Zyxel NSA-320), you can configure those so you can get period/scheduled emails about warnings/status
smartd and smartmontools - set up your system to send you scheduled reports on your drives usage, capacity and health; get email messages when the drive is showing signs of failing health

To make changes to this read-only filesystem :

mount -o rw,remount /         #this remounts the ubifs partition for read-write access
< do-all-of-your-changes-and-test-them-out-to-make-sure-they-are-complete>
mount -o ro,remount /         #this returns the ubifs partition to the default read-only access

10. Browse your LAN with a Avahi/Bonjour scanner and check for function

11. From your Mac, Windows or Linux box, open a Finder window and select the Shared/Network icon. You should be able to see MacPlug on a Mac, while on Windows, add a network place - just as you would for any Samba share. Select it, and wait 15-30 seconds while it generates a database file. When asks for authentication, enter username "timemachine", and password "timemachine" (unless you have changed your password(s)).

12. Enjoy.

Wanted/thought about, but didn't include:
- AirPrint included ... CUPSLite, where are you? We'd also need foomatic and *ostScript of some sort. Too big for now, but this may be a possibility in the future... Printerd, a new print spooler...
- Media Servers ... currently not that well supported in Buildroot...
- LibInklevel : would be great to query ink level in printers... unfortunately, a required libieee component compiles but does not function...

Predefined users:
root, password is root
timemachine, password is timemachine

ZyXEL NSA320 install from scratch (3 replies)

r9brian — Mon, 13 May 2013 09:12:15 -0400

Guys

I recently purachsed a NSA320 and would like to try out your Resuce System. I am interested in having control of the Hard Drives in the system, specifically disabling the drive "head parking" feature on Western Digital and Seagate drives. (I am hoping to use the hdparm program)

My Question: The uboot configuration does not specifically name the NSA320. I am unsure of the procedure. Could you tell me the steps to install "Rescue" on a NSA320 that I have taken right out of the box?

Thanks in advance for helping a "n00b" It should get you brownie points with the man upstairs(whomever you believe is up there :-) )

Rescue V3.0 : A work in progress ... wanna help? (38 replies)

davygravy — Sun, 26 May 2013 03:59:29 -0400

Anyone who wants to try out a development/alpha version of a possible Rescue System V3.0 is welcome to, and certainly anyone who wants to contribute to the effort, try to solve problems, etc. is encouraged to do so.

Jeff's original V1 & V2 have served us well... recently I put out a V2.8.1 which should run on over a dozen different Kirkwood boxes... but all of these are still based on 2010.08 Buildroot sources...

I've recently worked w/ Buildroot 2012.02 and 2012.05** to try to truly bring this up-to-date - current _everything_, and so it will boot on a wide variety of Kirkwood boards (see README for the list) .

Some new features that were truly needed, IMHO, and are now in Buildroot's package inventory, have been added.

parted : the GNU command-line-interface Partition Editor (handy for resizing partitions on drives)
sdparm : a utility for setting parameters in SATA drives (perhaps more useful than hdparm)
gdisk : utility for creating EFI/GPT partitions (enables us to use drives larger than 2.1 TB)

A USB-based tarball for trial is available here : http://dl.dropbox.com/u/1015928/Kirkwood/rescue/USB-Rescue-tarballs/rootfs-br2012.02_06082012.tar
This image will boot without _any_ changes to the default U-Boot env variables. Simply follow the directions on the README-USB-Rescue-tarballs document.

Ideas for a few more key/crucial utilities?

Maybe you want to help getting systemd/sysvinit or udev working on it? Currently none of them are included... maybe they should be left out, to keep it as truly a "Rescue" system, and not really a applications-oriented system.

It just takes a few minor modifications to turn it into a UBIFS image. Size is a concern, though, and maybe some of the extra apps that had been included could be removed, to save space under the hood.

** I tried to use the 2012.05 BR source, but something in it seems to disagree w/ kernel patches. Until this is solved, I'll be sticking w/ 2012.02. It has all the infrastructure that is necessary, and any "new" packages we need to add in to it can be back-ported.

Rescue V2.8.2 : many enhancements + full kernel support for GoFlexNet/Home, Zyxel NSA3x0 and many others (58 replies)

davygravy — Wed, 15 May 2013 15:16:42 -0400

.............. Doozan Forum
Kirkwood/*Plug* Recovery System
.......... V2.8.2 : Oct 29 2012

rescue login:

(Status : Test on 4 Mach-Types, awaiting tests on others )Kirkwood/*Plug*/Dockstar Rescue V2.8.2 : GPT support & many other enhancements + full kernel support for GoFlexNet/Home, Zyxel NSA3x0 and many others...

All of the features from Jeff'sV2, plus:

Well-tested and tuned Linux 3.3.2 kernel w/ lots of modules
GPT/EFI support in kernel and with the "gdisk" utility
Bonjour/Zeroconf/Avahi advertising of services: ( use ssh root@rescue.local to log in w/o hunting for the IP address)
fixes for the "Too Many Bad Blocks" NAND driver problem on GoFlex Net/Home
tweaks to udev so that SATA devices are handled more nicely, plus proper function in 3.x kernels
lm-sensors for the Zyxel NSA320 and any other supported Kirkwood device that has sensor on board
p910nd print server : very lightweight and easy to set up
fixed an intermittent problem w/ ntpd so that the time sync is more positive

This is a modest nudge upward in terms of function, but it should work on many more machines-. I've tested it out on Dockstar, Pogoplug E02, GoFlex Home and my Zyxel NSA320... it works very well... as always, respect the standard, mandatory boilerplate-language disclaimer: you accept all responsibility for using these files and the commands shown below. It works great for me, but I don't know what your level of expertise is... use at your own risk.

===================================

Download Link: RescueV2.8.1-05282012.tar.gz

(or for V2.8.2 use this link : https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz == but change commands for flashing accordingly !)

INSTALLATION:
Right now it is just manual installation - make sure you use the instructions for _your_ machine, not another:

***Newer U-Boot w/ L2 cache bug-fix required***http://forum.doozan.com/read.php?3,6965,6965#msg-6965

On PogoplugV1/V2, GoFlex Net/Home and Dockstar:

# make sure your **arcNumber** is correctly set, and check your console/netconsole connectivity in case of problems

#  Pogoplug E02    3542 if you have a kernel that supports it, or you can use 2097 (sheevaplug) if you have a truly vanilla mainline kernel that has no PogoE02-specific support in it
#
# Dockstar and PogoplugV1/E01    2998
#
# GoFlex Net and GoFlex Home    3089 if you have a kernel that supports it, or you can use 2678 (sheevaplug-eSATA) if you have a vanilla mainline kernel (but you'll likely experience the bad-blocks-NAND-mtd problem)
#   [ ! yes, you can use the same arcNumber for both of these GoFlex devices ! ]

# boot into Debian or something _other_ than the "rescue system" 
# download it to your Kirkwood device/Dockstar/Pogoplug/GoFlex
# untar it after downloading
tar zxvf RescueV2.8.1-05282012.tar.gz

# using tools from mtd-utils 

flash_eraseall /dev/mtd1
nandwrite /dev/mtd1 uImage-mtd1.img


flash_eraseall /dev/mtd2
ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y


fw_setenv set_bootargs_rescue 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts'
fw_setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
fw_setenv bootcmd_pogo 'run bootcmd_rescue'
fw_setenv rescue_installed 1

For the Zyxel NSA320:

# make sure your arcNumber is correctly set, and check your console/netconsole connectivity in case of problems
#  Zyxel NSA320    3956  for arcNumber


# boot into Debian or something _other_ than the "rescue system" 
# download it to your Zyxel NSA320
# untar it after downloading
tar zxvf RescueRescueV2.8.1-05282012.tar.gz


# using tools from mtd-utils 


flash_eraseall /dev/mtd7
nandwrite /dev/mtd7 uImage-mtd1.img 


flash_eraseall /dev/mtd8
ubiformat /dev/mtd8 -s 512 -f rootfs-mtd2.img -y

fw_setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x4640000 0xa00000; bootm 0x800000'
fw_setenv set_bootargs_rescue 'setenv bootargs console=$console ubi.mtd=8 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts'

===========================================

USAGE NOTES:
0. Booting into the Rescue System: from within netconsole or serial, execute the following:

run bootcmd_rescue

1. ssh login is easy - you probably won't need the ip address of your box anymore (username root ; password root):

ssh root@rescue.local

This should work on any Bonjour/Zeroconf/Avahi-enabled machine, and perhaps on some others.

2. Changes to the Read-Only rootfs: temporarily make it read-write...
You can make changes to the system, but be careful as there is little margin for error.

mount -o remount,rw /
#  make whatever changes you want to, such as adding modprobe commands to /etc/init.d/rcS
#  then revert to ro
mount -o remount,ro /

One important change to consider is to set your own password!

3. For special hardware, e.g. sensors Make selected kernel modules load at boot time.
The kernel has much of the in-common hardware support built-in, not as modules. Since some machines have extra capabilities or non-common hardware, modules supporting this must be loaded by hand, or added to the /etc/init.d/rcS startup script. For example:


#hardware monitoring on the Zyxel NSA320:
modprobe nsa3xx-hwmon

============================================

BUILDING IT:
(We will assume you already have the normal build-essential components that one would have: normal Buildroot dependencies...)

Go to somewhere in your own home directory, and as a normal user (not as root):

mkdir rescuebuilddir
cd rescuebuilddir
wget http://buildroot.uclibc.org/downloads/buildroot-2010.08.tar.gz
tar zxf buildroot-2010.08.tar.gz
wget http://dl.dropbox.com/u/1015928/Kirkwood/rescue/rescue-V2.8-applyto-buildroot2010.08.patch
cd buildroot-2010.08
patch -p1 < ../rescue-V2.8-applyto-buildroot2010.08.patch
wget http://dl.dropbox.com/u/1015928/Kirkwood/rescue/custom-RescueV2.8.1.tar.gz
tar zxf custom-RescueV2.8.tar.gz
cp custom/buildroot-config .config
make

After anywhere from about a half hour to two hours, your build should finish. In Jeff's original setup, multiple processors were not enabled. It is currently set for 6 processors (my build box is a 3.6GHz Quad Core : a full run took about 35 minutes on my desktop machine- YMMV).

Once the run is finished:

cd output/images

cat <rootfs.cfg
[ubifs]
mode=ubi
image=rootfs.ubifs
vol_id=0
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
END

ubinize -o rootfs-mtd2.img -m 2048 -p 128KiB -s 512 rootfs.cfg
dd if=uImage of=uImage-mtd1.img bs=512K conv=sync

Your completed uImage-mtd1.img and rootfs-mtd2.img image files should now be ready.

pogo e02 boots usb but doesn't get network dhcpcd not requesting (1 reply)

wxtofly — Sat, 10 Mar 2012 14:54:54 -0500

I have tried everything I could find to get the pogoplug to be directly connected to the internet while booting from usb.

It does fine booting from the original firmware.

Attempts with both Debian and Arch have give the same result. The pogoplug boots.
Wireshark shows that it starts broadcasting for DHCP discovery, is offered DHCP but it never gets around to the next REQUEST and ACK. When the original firmware runs, the DISCOVERY OFFER REQUEST ACK sequence is fairly quick.

I have been unsuccessful getting a netconsole connection, or a serial usb connection, but rebooting to pogoware, I can re mount the usb and look at the logs that had been generated.

I have also been unable to decipher the exact sequence that happens when debootstrap installs a package. It would seem that should be easy, but there are several steps in the chain. If someone could tell me the manual steps to say download, ar, tar the files to the appropriate place that would be great. I'd try another dhcp client other than dhcpcd.

Any other solutions would be appreciated. The critical part of this is that when finally setup, the pogo will not be on any LAN. only the big wide internet.

Thanks
TJ wxtofly
http://wxtofly.home.comcast.net/

Is the rescue system install irreversible? (2 replies)

Mycorunner — Mon, 12 Dec 2011 09:13:48 -0500

Simple question: Is there any way to get the original pogoplug software back after installing the rescue system, or is it an irreversible process?

How to... Rescue System on Dockstar running ArchLinux (6 replies)

hockeyrulesx4 — Thu, 26 Jul 2012 14:42:55 -0400

Hello,

I've had ArchLinuxARM (and PlugBox Linux prior) on a Dockstar for the past year and just recently saw these posts about Jeff's Rescue System V2.

I currently run ArchLinuxARM from a USB stick and have a 1 TB external drive attached to one of the other USB ports. I had a USB stick go bad on me a while back and the Dockstar would boot into the old plugOS (without trying to phone home), so I was able to reinstall ArchLinuxARM on a new USB stick. Does this replace this old plugOS bootup?

Can I install the Rescue System by unplugging both the USB stick and 1 TB drive, rebooting into plugOS, and then downloading and running the install script or should the install script be run when the Dockstar is booted into ArchLinuxARM with the USB stick and 1 TB drive attached.

Thanks!

How to get dockstar nand back on dockstar from rescue system nand (no replies)

rgtaa — Thu, 13 Oct 2011 10:08:58 -0400

hi guys
I know jeff did the rescue system for putting on his special rescue files on nand.

What I'm looking to do is install using a jeff-like way to put orginal pogoenvironment back on nand so I could have access to pogo software again . I have the backup nand which I made in the past ... how do I get it back on nand of rescue system in easy way.

I notice a number of people are interested in doing this. So could someone post a how-to, thanks.

XFS supported in ARM? Stable? (3 replies)

davygravy — Thu, 01 Nov 2012 10:56:36 -0400

I hope this is not minutia ... but for a long time XFS was very unstable/unreliable on ARM. Is this no longer the case?

If fixed, can anyone point me to the docs on it? I'd had no idea it was fixed.

Accidently set arcNumber=, now wont boot. (18 replies)

linuxtechie — Sat, 12 Nov 2011 14:58:52 -0500

Folks,

I accidently (my kid was playing around, while I was looking around for the number, she apparently even managed to reboot the machine, me and my luck) managed to set arcnumber to nothing. Now its not able to boot. I have tried a reset as well, but guess thats also is not working.

Any help please.

+LT

buildroot-2011.08-rc2 with kernel 3.0.3 on GoFlex Net - a "Go" (no replies)

moishap — Mon, 12 Sep 2011 01:33:51 -0400

Good news for those like me (not looking for an easy way :-) messing with their units just for the sake of hacking. I was able to build the distro this weekend with the latest kernel, after applying patches I found on http://archlinuxarm.org
As I don't feel like having my 2T hard drives full of music and movies reformated and planning to use my USB port for the multimedia, being an old school *nix die-hard, I used root=/dev/nfs on my Fedora workstation to simplify build-install-test-reboot cycle (great help). So I'm yet to try flashing it to NAND (shouldn't be an issue) and maybe even flashing the u-boot itself, which was built OK as well. But for now things are looking great.

Dockstar OPENWRT on Rescue System V2 (1 reply)

maxiedo — Thu, 15 Sep 2011 17:40:19 -0400

Dockstar is currently running rescue system V2 and Debian on USB hard drive. Is it possible to install openwrt into different USB hard drive?
I want to be able to switch between Debian and openwrt by simply switching USB hard drive. Thanks for reading and appreciated any comments.

Rescue install failed. (1 reply)

rfanch3r — Thu, 28 Jul 2011 05:50:42 -0400

I accidently quit the install_rescue.sh script and reran it but i am getting the following:

# 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: error!: file "/tmp/rootfs-mtd2.img" (size 3764513 bytes) is not multiple of eraseblock size (131072 bytes)
error 0 (Success)
Installation failed.
root@debian:/tmp# ls -la
total 7292
drwxrwxrwt 2 root root 100 Jan 1 03:06 .
drwxr-xr-x 21 root root 4096 Jul 27 2011 ..
-rwxr-xr-x 1 root root 7743 Oct 26 2010 install_rescue.sh
-rw-r--r-- 1 root root 3764513 Jan 1 02:51 rootfs-mtd2.img
-rw-r--r-- 1 root root 3670016 Feb 17 2011 uImage-mtd1.img

Anyone point me to the fix or show me a similar forum post on the same issue, I couldn't find one.

Dockstar does not boot (13 replies)

acognard — Sun, 17 Jul 2011 13:46:24 -0400

Hi all,
(sorry for my english :))
i am facing a new issue with my ds.

using another VM linux, i use

nc -l -u -p 6666

to see boot log without any usb disk.

but it turns around

1. U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
   2. Marvell-Dockstar/Pogoplug by Jeff Doozan
   3. Hit any key to stop autoboot:  4

i hit return key

1. Marvell>> ls
   2. ls
   3. drwxr-xr-x        0 Thu Dec 18 20:30:04 2008 bin
   4. drwxr-xr-x        0 Thu Jan 15 19:07:02 2009 dev
   5. drwxr-xr-x        0 Tue Aug 11 05:52:40 2009 etc
   6. drwxr-xr-x        0 Thu Dec 18 20:30:04 2008 lib
   7. lrwxrwxrwx       11 Wed Aug 26 22:27:00 2009 linuxrc -> bin/busybox
   8. drwxr-xr-x        0 Thu Dec 18 21:45:09 2008 mnt
   9. drwxr-xr-x        0 Tue Feb 26 17:26:05 2008 proc
  10. drwxr-xr-x        0 Tue Mar 10 23:53:33 2009 root
  11. drwxr-xr-x        0 Thu Dec 18 20:30:04 2008 sbin
  12. drwxr-xr-x        0 Sat Jan 01 00:13:48 2000 sys
  13. drwxr-xr-x        0 Sat Jan 01 00:13:40 2000 tmp
  14. drwxr-xr-x        0 Thu Jan 15 18:31:53 2009 usr
  15. lrwxrwxrwx        8 Wed Aug 26 22:27:00 2009 var -> /tmp/var
  16. -rw-r--r--       67 Sat Jan 01 04:40:49 2000 uboot-original-mtd0.kwb.md5
  17. -rw-r--r--   524288 Sat Jan 01 04:40:51 2000 uboot-original-mtd0.kwb

below the complete trace

   1. ### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
   2. Scanning JFFS2 FS: ........ done.
   3. ### JFFS2 load complete: 524288 bytes loaded to 0x800000
   4. ## Starting application at 0x00800200 ...
   5.
   6. U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
   7. Marvell-Dockstar/Pogoplug by Jeff Doozan
   8. Hit any key to stop autoboot:  0
   9. (Re)start USB...
  10. USB:   Register 10011 NbrPorts 1
  11. USB EHCI 1.00
  12. scanning bus for devices... 3 USB Device(s) found
  13.        scanning bus for storage devices... 0 Storage Device(s) found
  14. ** Block device usb 0 not supported
  15.
  16. ** Invalid boot device **
  17. Creating 1 MTD partitions on "nand0":
  18. 0x000002500000-0x000010000000 : "mtd=3"
  19. UBI: attaching mtd1 to ubi0
  20. UBI: physical eraseblock size:   131072 bytes (128 KiB)
  21. UBI: logical eraseblock size:    129024 bytes
  22. UBI: smallest flash I/O unit:    2048
  23. UBI: sub-page size:              512
  24. UBI: VID header offset:          512 (aligned 512)
  25. UBI: data offset:                2048
  26. UBI: attached mtd1 to ubi0
  27. UBI: MTD device name:            "mtd=3"
  28. UBI: MTD device size:            219 MiB
  29. UBI: number of good PEBs:        1751
  30. UBI: number of bad PEBs:         1
  31. UBI: max. allowed volumes:       128
  32. UBI: wear-leveling threshold:    4096
  33. UBI: number of internal volumes: 1
  34. UBI: number of user volumes:     0
  35. UBI: available PEBs:             1730
  36. UBI: total number of reserved PEBs: 21
  37. UBI: number of PEBs reserved for bad PEB handling: 17
  38. UBI: max/mean erase counter: 1/1
  39. UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
  40. Error reading superblock on volume 'ubi:rootfs'!
  41. ** Block device usb 0 not supported
  42. ** Block device usb 1 not supported
  43. ** Block device usb 2 not supported
  44. ** Block device usb 3 not supported
  45. ** Block device usb 0 not supported
  46. ** Block device usb 0 not supported
  47. Wrong Image Format for bootm command
  48. ERROR: can't get kernel image!
  49. stopping USB..
  50. ### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
  51. Scanning JFFS2 FS: ........ done.
  52. ### JFFS2 load complete: 524288 bytes loaded to 0x800000
  53. ## Starting application at 0x00800200 ...
  54.
  55. U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
  56. Marvell-Dockstar/Pogoplug by Jeff Doozan
  57. Hit any key to stop autoboot:  4

Does anyone can help me on this issue ?
Tks in advance
Arnaud

Recover rcS from Marvell or CE prompt? (1 reply)

zhaozh — Fri, 03 Jun 2011 22:10:50 -0400

Hello all,
I tried to add new lines in rcS file but it seems the rcS is corrupted and I lost the network access. Then I used serial to monitor and I got error info: rcS not exist... but it gets to the PogoPlug prompt too. I went to /etc/init.d folder and I can see rcS file is there and a copy of it before changing rcS.copy.

My device is PogoPlug, then I use:
mount -o rw,remount /
but it says that ... I forget what the error message.

So I think even I am in shell prompt but I may lost most of the functions.

My question is can I make the system writable from Marvell or CE prompt and copy files so that I can recover the rcS file?

Thanks!
zhaozh

How to rescue from "Install Plugbox Linux with kernel in NAND memory" (no replies)

zhaozh — Fri, 13 May 2011 12:06:07 -0400

Hi all,
I tried to install Plugbox Linux in NAND of my PogoPlug V2 and I guess I skipped the step:
on /dev/sda1 kernel_nand_installer

cd /tmp
wget http://jeff.doozan.com/debian/goflex/v0.6/uInitrd
wget http://jeff.doozan.com/debian/goflex/v0.6/start_ubit
chmod +x start_ubit
./start_ubit

# Enter UBIT commands at the ubit-v0.6# prompt.
uboot_install pinkpogo
on /dev/sda1 kernel_nand_installer     

#  3 minutes later...
exit           # leave the UBIT shell
/sbin/reboot  # reboot so the install can complete

Now the system just stuck on this when I monitored with serial communication.
## Starting application at 0x00800200 ...

Is there any way to rescue this unit?

See my other post for reference:
http://forum.doozan.com/read.php?3,4772

Thanks!
zhaozh

smartctl (1 reply)

Ananon — Fri, 27 May 2011 00:19:09 -0400

Is anyone able to check the SMART status of USB hard drives in the rescue environment? It seems to me that USB external drives are not supported? In Debian I can specify drive type as "usbcypress", but such parameter is not possible in Rescue.

DHCP doesn't work what is the default IP on rescue System ? (1 reply)

Val532 — Fri, 02 Sep 2011 20:36:01 -0400

Hi,

I have a problem when i start my freeagent dockstar whitout any usb drive it's doesn't get any Ip.

And when i launch nmap -sP169.254.1.0/16 i found nothing.

Any help ? What's is the default Ip for descue system v2 ?

IPGK Failure (2 replies)

manxam — Thu, 10 May 2012 23:59:27 -0400

Thanks for all of your hard work on this Jeff! I do have an issue though with V2 that I'm hoping you can help me with.

when running ipkg-cl (both with the filesystem ro and rw) every command is met with "Successfully Terminated" but it doesn't actually DO anything. I cannot 'update', 'list', nor 'search'

ipkg-cl by itself does show me the help but that's it.

Any ideas?

Thanks!

Edit: I just realized that handhelds.org is offline and has been since mid-feb. Is this where the package repository was being stored? If so, is there an alternative package management system that we can use?

"Dual Boot" between rescue and usb? (5 replies)

edinger — Thu, 17 Mar 2011 15:12:28 -0400

Hi,
I want to switch between the installed debian system on usb an the rescue-system (V2) from script/remote.
So the normal way (shutting down, unplugging usb, boot into rescue and re-plug usb) is not possible.
How can I hande this? I'm a little bit scary changing anything in the boot environment, but I think the correct use of fw_setenv is the right way.
Finally I want to use it for planned regular backups of the usb-system.
Has anybody implemented something similar?

Dieter

Here is the current output of 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:D9:23
arcNumber=2097
rescue_installed=1

Debian installation failed from Rescue system v1 (14 replies)

Ultrazauberer — Mon, 28 Feb 2011 12:36:35 -0500

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....

Rescue System v2 (24 replies)

Jeff — Sat, 16 Mar 2013 23:02:15 -0400

I've updated the Rescue System with support for the new arcNumber (Dockstar & GoFlex Net) and support for runlevels via a new sysvinit based startup and a few new utilities. I've dropped the zcip configuration, because it never really worked anyways.

This will replace the Pogoplug kernel on mtd1 and the Pogoplug system on mtd2 with a more sophisticated system.

What's new in this release:

Kernel support for Dockstar/GoFlexNet arcnumbers
cleaner 'first-boot' initialization scripts
sysvinit
sqlite3
iptables
microperl
udev
lsof
socat
openvpn

The rescue system includes:

ipkg
ext2/3/4 create and repair utilities
ubifs support/utilities
flash/nand utilities
md/raid support/utilities
ntfs-3g
xfs support/utilities
reiserfs support
nfs support
lvm support/utilities
ssh/sshfs/openssl
openvpn
iptables
wget/curl/links/ncftp/rsync
vi/nano
screen
sqlite3
kernel 2.6.32-18 with dockstar/goflex patches + tons of modules for whatever you may have connected

The default login is 'root' with password 'root'

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.

Boot from a USB device (or a Debian NAND install) and run the following commands:

cd /tmp
wget http://jeff.doozan.com/debian/rescue/install_rescue.sh
chmod +x install_rescue.sh
./install_rescue.sh

The system is based on buildroot which is a pretty nice tool for this sort of thing. If you'd like to build your own images, you can do so with the following commands:

cd /usr/src
wget http://buildroot.uclibc.org/downloads/buildroot-2010.08.tar.gz
tar -xzvf buildroot-2010.08.tar.gz
cd buildroot-2010.08
git clone https://github.com/doozan/RescueSystem.git custom
cp custom/buildroot-config .config
make

If you're compiling on a multi-core machine, you may want to do 'make menuconfig' before 'make' and adjust 'number of jobs to run simultaneously' under 'build options' Be prepared to wait, the entire build process will likely take many hours.

After you've built the image, you can create the flashable images with the following commands:

cd output/images

cat <rootfs.cfg
[ubifs]
mode=ubi
image=rootfs.ubifs
vol_id=0
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
END

ubinize -o rootfs-mtd2.img -m 2048 -p 128KiB -s 512 rootfs.cfg
dd if=uImage of=uImage-mtd1.img bs=512K conv=sync

I'm more than happy to accept patches against this to add any requested features.

-- Jeff