Pogoplug E02 - fuse libfuse2 failed to install

I started my E02 after a year or two. Used webmin to update the old packages.
Ran into problems after fuse libfuse2 failed to install.

Preparing to unpack .../fuse_2.9.4-1_armel.deb ...
Unpacking fuse (2.9.4-1) over (2.9.2-4) ...
Preparing to unpack .../libfuse2_2.9.4-1_armel.deb ...
Unpacking libfuse2:armel (2.9.4-1) over (2.9.2-4) ...
Setting up libfuse2:armel (2.9.4-1) ...
Setting up fuse (2.9.4-1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
DTB: kirkwood-sheevaplug.dtb
flash-kernel: installing version 2.6.32-5-kirkwood
Generating kernel u-boot image... done.
Taking backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Taking backup of uInitrd.
Installing new uInitrd.
Couldn't find /usr/lib/linux-image-2.6.32-5-kirkwood/kirkwood-sheevaplug.dtb
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
.. install failed!

After this package failed, everything is failing to install. I've left it on so i dont lose connectivity to the box.
I downloaded the latest 4.1 kernel too.

What went wrong? Did the webmin try to install wrong mtd on my e02 and my debian installation is borked?
What should i do? I don't have any spare usb devices right now to even make a new installation.

Vinay,

What is your current U-Boot and Debian version? please post output of

grep -a --null-data U-Boot /dev/mtd0ro 
dmesg

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Output of line 1:

���������U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo by Jeff DoozanU-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!

Output of line 2 is mostly uncorrectable errors like this

[  296.709735] uncorrectable error : 
[  296.713165] uncorrectable error : 
[  296.716589] uncorrectable error : 
...............
[  300.328021] uncorrectable error :

I have an old backup i made with acronis in 2012. If i over write the usb with the old backup will it start working again?

Vinay,

> I have an old backup i made with acronis in 2012.
> If i over write the usb with the old backup will
> it start working again?

Yes that should work.

Furthermore, even though your u-boot ins quite old, it should be able to boot my Debian-3.16.0-kirkwood-tld-2 rootfs:
http://forum.doozan.com/read.php?2,12096

Scroll down to the section:

Quote

Updated 02 Sept 2014:

Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.16.0-kirkwood-tld-2 (and its new features).

Follow the instruction closely and create a rootfs on a USB stick.

Basically, on another Linux box, as root user (sudo won't work), create a single Ext3 partition on the USB stick. Untar the Debian 3.16 rootfs to it. And boot with this stick.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

So i should use a new usb stick? Can't i just format the old non working one as ext3 partition and use it?
Can't i use the 4.xx version build? Is it because of old uboot? Any way to upgrade my old uboot to new one?
Sorry if i sound like an irritating kid. :)

Vinay Wrote:
-------------------------------------------------------
> So i should use a new usb stick? Can't i just
> format the old non working one as ext3 partition
> and use it?
> Can't i use the 4.xx version build? Is it because
> of old uboot? Any way to upgrade my old uboot to
> new one?
> Sorry if i sound like an irritating kid. :)

You should boot the 3.16 rootfs first :) yes, it is because of old u-boot, it's simpler to use 3.16. But if you follow the instruction on 3.18.5 very closely (especially the appended DTB part), you can boot with it, too.

And yes you can reformat the old USB stick, if you don't have important data on it. After booted into Debian successfuly, then move on to install new u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Vinay,
>
> What is your current U-Boot and Debian version?
> please post output of
>

> grep -a --null-data U-Boot /dev/mtd0ro 
> dmesg
>

I formatted the old usb disk to ext3 and did as was written in the instructions. I dont know where the usb type goes so i left it.
I still get these errors. The uboot error s the same whereas the dmesg error is a bit different.

[  356.475450] __nand_correct_data: uncorrectable ECC error
[  356.480786] __nand_correct_data: uncorrectable ECC error
[  356.486362] __nand_correct_data: uncorrectable ECC error
[  356.491694] __nand_correct_data: uncorrectable ECC error

After searching on this site, I found fwenv. I'm pasting a printout of it.

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_installed=0
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:25:31:04:76:5C
arcNumber=2097
root@debian:~#

How do i know the installation went right?

Vinay,

> How do i know the installation went right?

Your envs look good. Are you booting with the new 3.16 rootfs on USB? If that is true then please reboot

shutdown -r now

And post the output of

dmesg
mount

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Sorry. I think I messed up. I didn't do this part you asked me to.

 After booted into Debian successfuly, then move on to install new u-boot.

I'm also getting some locale errors. I tried installing locales, but it does not go away.
Will look at how to install uboot first. I just have to copy the new uboot to a temp folder on the usb stick as root from a linux machine and then attach the stick to pogo and go on from there, i hope? I only have one pogo so im not taking chances.

Vinay Wrote:
-------------------------------------------------------
> Sorry. I think I messed up. I didn't do this part
> you asked me to.
>

 After booted into Debian successfuly, then
> move on to install new u-boot.

>
> I'm also getting some locale errors. I tried
> installing locales, but it does not go away.
> Will look at how to install uboot first. I just
> have to copy the new uboot to a temp folder on the
> usb stick as root from a linux machine and then
> attach the stick to pogo and go on from there, i
> hope? I only have one pogo so im not taking
> chances.

You don't have to install new u-boot. I thought we should check how your system running first. That's what dmesg and mount output will show.

After it's running OK, then think about new u-boot. It is not very important to install new u-boot right away, you could wait until you need to use advance features that it provides.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ah. Okay then, here's the output of dmesg:

root@debian:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c07c303c, node_mem_map cfdfb000
[    0.000000]   DMA zone: 512 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 65536 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(dat             a)
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 245692K/262144K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 16452K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07248b0   (7283 kB)
[    0.000000]       .init : 0xc0725000 - 0xc0765444   ( 258 kB)
[    0.000000]       .data : 0xc0766000 - 0xc07c975c   ( 398 kB)
[    0.000000]        .bss : 0xc07c975c - 0xc08144dc   ( 300 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    7.378156] Console: colour dummy device 80x30
[    7.378176] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    7.467952] pid_max: default: 32768 minimum: 301
[    7.468045] Security Framework initialized
[    7.468095] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    7.468106] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    7.468824] Initializing cgroup subsys devices
[    7.468865] Initializing cgroup subsys freezer
[    7.468883] Initializing cgroup subsys net_cls
[    7.468911] Initializing cgroup subsys blkio
[    7.468977] CPU: Testing write buffer coherency: ok
[    7.469323] Setting up static identity map for 0x5273f0 - 0x527448
[    7.470828] devtmpfs: initialized
[    7.473713] prandom: seed boundary self test passed
[    7.477727] prandom: 100 self tests passed
[    7.477743] pinctrl core: initialized pinctrl subsystem
[    7.478196] regulator-dummy: no parameters
[    7.478535] NET: Registered protocol family 16
[    7.478943] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    7.479763] cpuidle: using governor ladder
[    7.479780] cpuidle: using governor menu
[    7.479895] Kirkwood: MV88F6281-A0, TCLK=200000000.
[    7.479915] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[    7.479923] Feroceon L2: Cache support initialised.
[    7.480499] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[    7.480530]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[    7.509493] vgaarb: loaded
[    7.509852] usbcore: registered new interface driver usbfs
[    7.509928] usbcore: registered new interface driver hub
[    7.510055] usbcore: registered new device driver usb
[    7.511046] Switched to clocksource orion_clocksource
[    7.549789] NET: Registered protocol family 2
[    7.550782] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    7.550818] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    7.550849] TCP: Hash tables configured (established 2048 bind 2048)
[    7.550920] TCP: reno registered
[    7.550934] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    7.550956] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    7.551219] NET: Registered protocol family 1
[    7.551562] RPC: Registered named UNIX socket transport module.
[    7.551573] RPC: Registered udp transport module.
[    7.551581] RPC: Registered tcp transport module.
[    7.551588] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    7.551617] PCI: CLS 0 bytes, default 32
[    7.551905] Unpacking initramfs...
[    8.055375] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[    8.055513] NetWinder Floating Point Emulator V0.97 (double precision)
[    8.056673] futex hash table entries: 256 (order: -1, 3072 bytes)
[    8.056741] audit: initializing netlink subsys (disabled)
[    8.056796] audit: type=2000 audit(0.670:1): initialized
[    8.057619] zbud: loaded
[    8.057890] VFS: Disk quotas dquot_6.5.2
[    8.057940] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.058506] NFS: Registering the id_resolver key type
[    8.058567] Key type id_resolver registered
[    8.058576] Key type id_legacy registered
[    8.058602] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    8.058616] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    8.058786] jffs2: version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[    8.059092] msgmni has been set to 491
[    8.059248] Key type big_key registered
[    8.061754] alg: No test for stdrng (krng)
[    8.061871] bounce: pool size: 64 pages
[    8.061937] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    8.061956] io scheduler noop registered
[    8.061970] io scheduler deadline registered
[    8.062136] io scheduler cfq registered (default)
[    8.062569] mv_xor mv_xor.0: Marvell shared XOR driver
[    8.101122] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    8.141114] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    8.141289] mv_xor mv_xor.1: Marvell shared XOR driver
[    8.181112] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    8.221111] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    8.221548] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    8.222552] console [ttyS0] disabled
[    8.242651] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[    8.794697] console [ttyS0] enabled
[    8.799791] nand: Could not find valid ONFI parameter page; aborting
[    8.806244] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    8.812640] nand: Hynix NAND 128MiB 3,3V 8-bit
[    8.817099] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    8.822806] Scanning device for bad blocks
[    8.935764] 4 cmdlinepart partitions found on MTD device orion_nand
[    8.942073] Creating 4 MTD partitions on "orion_nand":
[    8.947243] 0x000000000000-0x000000100000 : "u-boot"
[    8.952637] 0x000000100000-0x000000500000 : "uImage"
[    8.957982] 0x000000500000-0x000002500000 : "rootfs"
[    8.963362] 0x000002500000-0x000008000000 : "data"
[    8.969374] libphy: Fixed MDIO Bus: probed
[    8.986002] libphy: orion_mdio_bus: probed
[    8.990235] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   10.072205] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:04:76:5c
[   10.081196] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   10.087755] ehci-pci: EHCI PCI platform driver
[   10.092303] ehci-orion: EHCI orion driver
[   10.096408] orion-ehci orion-ehci.0: EHCI Host Controller
[   10.101881] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   10.109656] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   10.131084] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   10.137219] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   10.144065] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.151339] usb usb1: Product: EHCI Host Controller
[   10.156240] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[   10.162986] usb usb1: SerialNumber: orion-ehci.0
[   10.168376] hub 1-0:1.0: USB hub found
[   10.172226] hub 1-0:1.0: 1 port detected
[   10.177051] mousedev: PS/2 mouse device common for all mice
[   10.491105] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   10.642670] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   10.649421] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   10.656615] usb 1-1: Product: USB2.0 Hub
[   10.661522] hub 1-1:1.0: USB hub found
[   10.665666] hub 1-1:1.0: 4 ports detected
[   10.951420] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[   11.062044] usb 1-1.1: New USB device found, idVendor=08ec, idProduct=0020
[   11.068966] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.076334] usb 1-1.1: Product: USB Flash Drive
[   11.080882] usb 1-1.1: Manufacturer: SanDisk
[   11.085190] usb 1-1.1: SerialNumber: 0D41A67102D308CD
[   11.191078] rtc-mv rtc-mv: internal RTC not ticking
[   11.196169] i2c /dev entries driver
[   11.200616] hidraw: raw HID events driver (C) Jiri Kosina
[   11.206418] drop_monitor: Initializing network drop monitor service
[   11.212971] TCP: cubic registered
[   11.216311] NET: Registered protocol family 17
[   11.220944] Key type dns_resolver registered
[   11.225982] registered taskstats version 1
[   11.231132] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   11.238286] PM: Hibernation image not present or could not be loaded.
[   11.239310] Freeing unused kernel memory: 256K (c0725000 - c0765000)
[   11.322005] udevd[55]: starting version 175
[   11.506038] mvsdio mvsdio: no pins associated
[   11.516704] SCSI subsystem initialized
[   11.565405] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[   11.614006] scsi0 : usb-storage 1-1.1:1.0
[   11.627549] usbcore: registered new interface driver usb-storage
[   11.660320] usbcore: registered new interface driver uas
[   12.612028] scsi 0:0:0:0: Direct-Access     SanDisk  USB Flash Drive  6.51 PQ: 0 ANSI: 0 CCS
[   12.651363] sd 0:0:0:0: [sda] 7883775 512-byte logical blocks: (4.03 GB/3.75GiB)
[   12.659680] sd 0:0:0:0: [sda] Write Protect is off
[   12.664653] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08
[   12.665079] sd 0:0:0:0: [sda] No Caching mode page found
[   12.670431] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   12.684442]  sda: sda1
[   12.689951] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   12.707106] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   21.783978] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
[   23.062230] udevd[235]: starting version 175
[   23.512866] alg: hash: Test 3 failed for mv-sha1
[   23.517544] 00000000: 10 bf d7 00 71 0b bb 83 3a 26 d0 97 13 05 99 f5
[   23.539997] 00000010: 3a 92 53 3c
[   23.599770] alg: hash: Test 1 failed for mv-hmac-sha1
[   23.605942] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
[   23.621148] 00000010: b7 c3 16 0c
[   24.414772] random: nonblocking pool is initialized
[   29.779123] NET: Registered protocol family 10
[   31.062145] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   33.531395] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, ful duplex, flow control disabled
[   33.541322] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@debian:~#

And output of mount is:

root@debian:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=30711,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=25184k,mode=755)
/dev/sda1 on / type ext2 (rw,noatime,errors=remount-ro,user_xattr,acl)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=50360k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
root@debian:~#

Vinay,

Everything looks great! except that your USB rootfs right now is Ext3, but your u-boot env still set to Ext2. It works for booting, but Ext3 journal is not used.

dmesg

[   21.783978] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2

u-boot envs

usb_rootfstype=ext2

Since you have only one Pogo, and no serial console, I'm hesitate to suggest installing new u-boot. Because there is no recovery path on Pogo E02, if anything goes wrong during u-boot installation, you would have to connect JTAG. So please look at the u-boot thread and decide.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Any way to change the uboot env to ext3?

Is new uboot required or will my pogo work with the old one properly? If its absolutely required then I might do it.

I tried setting up net console by reading the tutorial here.
http://forum.doozan.com/read.php?3,14,14

I cant get it working. I'm stuck at this part and don't understand it.

Note: the above command will start a 'view-only' console. If you want to be able to interact with uBoot, you need to run the first 'nc' instance in the background and then use a second instance to send the commands back to the Dockstar: 
nc -l -u -p 6666 &
nc -u 192.168.1.100 6666
# run killall nc after you've finished to kill the background nc process

Now when your start your Dockstar, your server should display the boot process.

I typed exactly as written and rebooted the plug to see if I can see the boot process, but nothing shows up on either of the terminals in my pc. I'm running the commands from a linux mint pc. Do I have to type the fw_setenv text every time or its done once and for all?

I also came across some weird error in which the plug just wouldn't boot up. I put a 512MB swap file after partitioning the disk and the plug booted into it once. In the plug I set the swap disk on. After that the plug wouldn't boot into debian. After i deleted the swap file it started working again. I ran fsck on the disk thinking it had errors but turned out to be fine. Why doesn't this like swap partition? It boots too slow without swap i think. Takes almost 1.5 - 2 minutes for the green light to come on.

Vinay Wrote:
-------------------------------------------------------
> I tried setting up net console by reading the
> tutorial here.
> http://forum.doozan.com/read.php?3,14,14
>
> I cant get it working. I'm stuck at this part and
> don't understand it.
>

> Note: the above command will start a 'view-only'
> console. If you want to be able to interact with
> uBoot, you need to run the first 'nc' instance in
> the background and then use a second instance to
> send the commands back to the Dockstar: 
> nc -l -u -p 6666 &
> nc -u 192.168.1.100 6666
> # run killall nc after you've finished to kill the
> background nc process
> 
> Now when your start your Dockstar, your server
> should display the boot process. 
>

>
> I typed exactly as written and rebooted the plug
> to see if I can see the boot process, but nothing
> shows up on either of the terminals in my pc. I'm
> running the commands from a linux mint pc. Do I
> have to type the fw_setenv text every time or its
> done once and for all?
>

fw_setenv is permanent. Please post your u-boot envs:

fw_printenv

I don't remember if your u-boot supports netconsole (I think it does). Also, netconsole is tricky, usually the netcat version in your nc server (i.e. Mint pc) has to match the nc version on the Pogo. Check Mint's version of netcat, you should use netcat traditional on Mint.

> I also came across some weird error in which the
> plug just wouldn't boot up. I put a 512MB swap
> file after partitioning the disk and the plug
> booted into it once. In the plug I set the swap
> disk on. After that the plug wouldn't boot into
> debian. After i deleted the swap file it started
> working again. I ran fsck on the disk thinking it
> had errors but turned out to be fine. Why doesn't
> this like swap partition? It boots too slow
> without swap i think. Takes almost 1.5 - 2 minutes
> for the green light to come on.

Swap file or swap partition? in either cases, the fstab definition should have the option to ignore error in mounting. For example, this is my swapfile (the last 0 is the switch to ignore erro):

/swapfile1     swap            swap    defaults          0       0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Swap partition. I had put a line in fstab with uid of the swap partition and mount as swap and the two 0 0 too. In the plug i even used swapon -s to see if the partition was active. It was not in use but did show up as a swap partition. After i shut down the plug, it just wouldn't start up properly. The plug would just show the amber light even after half an hour. Trying to ssh into it gave an error that there was no connection or route. In my router, the plug didn't even show up in the dhcp list, so probably it didn't even boot into debian properly. After deleting the swap partition and editing the fstab file, i sync'd the drive and put into the plug. It booted up in a minute and the green light came on.

fw_printenv output:

root@debian:~# 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_installed=0
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:25:31:04:76:5C
arcNumber=2097
serverip=192.168.10.109
ipaddr=192.168.10.112
if_netconsole=ping $serverip
startstart_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
root@debian:~#

The net version is the open bsd version on my mint. (netcat-openbsd 1.105-7ubunt amd64)
I installed the traditional version a few minutes back. will check if it works.
I don't know how to make it work i guess. I made netcat-traditional as default in my mint. Then typed these in three different terminals. I don't see anything in either of them.

nc -lkup 6666 10.10.10.6 6666
nc -l -u -p 6666
nc -u 192.168.10.112 6666

Is there a way to send udp packets to the mint machine from the plug on port 6666?

Vinay,

> After i shut
> down the plug, it just wouldn't start up properly.
> The plug would just show the amber light even
> after half an hour.

If the swap partition was created as the 1st partition then I think it was your problem (check it using fdisk on Mint). The rootfs must be the 1st partition. However, if you use a swap file then you will not have this problem.

You u-boot envs look good. Except for one typo: startstart_netconsole!

start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;

> The net version is the open bsd version on my
> mint. (netcat-openbsd 1.105-7ubunt amd64)
> I installed the traditional version a few minutes
> back. will check if it works.
> I don't know how to make it work i guess. I made
> netcat-traditional as default in my mint.

nc -lup 6666 192.168.10.112 6666

or

nc -kup 6666 192.168.10.112 6666

should work.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

How do I change the typo in fw_setenv?

Vinay Wrote:
-------------------------------------------------------
> How do I change the typo in fw_setenv?

The same way you did when changing u-boot envs in Debian for netconsole. The 1st command sets the new variable, the 2nd one erase the wrong variable.

fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
fw_setenv startstart_netconsole

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

He he. That worked. I got this output from the plug while booting up.

vinay@MediaPC ~ $ nc -kup 6666 192.168.10.112 6666

U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo 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
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-0x000008000000 : "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: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        728
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
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)
2756040 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6032465 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2755976 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-2
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6032401 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Vinay Wrote:
-------------------------------------------------------
> He he. That worked. I got this output from the
> plug while booting up.
>
>

> vinay@MediaPC ~ $ nc -kup 6666 192.168.10.112
> 6666
> 
> U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
> Marvell-PinkPogo 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
> 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-0x000008000000 : "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: attached mtd1 to ubi0
> UBI: MTD device name:            "mtd=3"
> UBI: MTD device size:            91 MiB
> UBI: number of good PEBs:        728
> UBI: number of bad PEBs:         0
> UBI: max. allowed volumes:       128
> UBI: wear-leveling threshold:    4096
> UBI: number of internal volumes: 1
> UBI: number of user volumes:     0
> UBI: available PEBs:             717
> UBI: total number of reserved PEBs: 11
> UBI: number of PEBs reserved for bad PEB handling:
> 7
> UBI: max/mean erase counter: 1/1
> UBIFS error (pid 0): ubifs_get_sb: cannot open
> "ubi:rootfs", error -19
> Error reading superblock on volume 'ubi:rootfs'!
> 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)
> 2756040 bytes read
> Loading file "/boot/uInitrd" from usb device 0:1
> (usbda1)
> 6032465 bytes read
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-3.16.0-kirkwood-tld-2
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    2755976 Bytes = 2.6 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
>    Image Name:   initramfs-3.16.0-kirkwood-tld-2
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    6032401 Bytes = 5.8 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
>

Cool! I recall that with this old version u-boot, to interrupt the boot at count down, you'll have to press Control-J repeatedly.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Sorry for not replying till now, had been away.
Should I upgrade the uboot or is this old uboot okay to use for 24 hrs usage?

Vinay Wrote:
-------------------------------------------------------
> Sorry for not replying till now, had been away.
> Should I upgrade the uboot or is this old uboot
> okay to use for 24 hrs usage?

Nothing is wrong with this u-boot. It's just older and does not have new features. It's great for your purpose right now.

You can take a look at the description of the new u-boot and decide. If you have other plugs such as GoFlex Home/Net, PogoV4, ..(.where there is an easy way to recover from bad flash) then I would definitely recommend to update. The Pogo E02 does not. So it depends on your risk tolerance.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Seems mouth watering, but with linux I think I would go with that old saying -If it's not broke, don't mend or something like that. I'll use this plug as is for a month or two and then decide if its worth the risk. Thanks a lot for your help Bodhi. :)

Vinay Wrote:
-------------------------------------------------------
> Seems mouth watering, but with linux I think I
> would go with that old saying -If it's not broke,
> don't mend or something like that. I'll use this
> plug as is for a month or two and then decide if
> its worth the risk. Thanks a lot for your help
> Bodhi. :)

You're welcome! I think you've made the right decision. Give it sometime :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I installed deluged on my plug cause transmission daemon wouldn't even connect to peers. Thing is free memory seems to be always full now. With transmission daemon running, it was always around 50% free of 250MB I think. Now it's around 245MB always. There's just 4-5 MB free now. Should I make a swap file (not partition since my install does not boot with swap partition) so that some resources are freed? Cached memory is always around 150MB now.
OR should I get another USB stick and format it as swap and put it in fstab? I think out of 3.5 GB, just around 700MB must have been utilised even after all the dependencies deluge installed.

Vinay Wrote:
-------------------------------------------------------
> I installed deluged on my plug cause transmission
> daemon wouldn't even connect to peers. Thing is
> free memory seems to be always full now. With
> transmission daemon running, it was always around
> 50% free of 250MB I think. Now it's around 245MB
> always. There's just 4-5 MB free now. Should I
> make a swap file (not partition since my install
> does not boot with swap partition) so that some
> resources are freed? Cached memory is always
> around 150MB now.
> OR should I get another USB stick and format it as
> swap and put it in fstab? I think out of 3.5 GB,
> just around 700MB must have been utilised even
> after all the dependencies deluge installed.

What is your output of

free

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Output of free:

root@debian:~# free
             total       used       free     shared    buffers     cached
Mem:        251832     245116       6716          0      73388      73372
-/+ buffers/cache:      98356     153476
Swap:            0          0          0