New Pink Pogoplug B04 bricked

[timstegeman]

@Taker
I had the same problems you had to boot into ALARM OS.

Try the following procedure: (Execute all as root)
1. Create one (and only one) new ext3 partition with cfdisk.
2. mkfs.ext3 /dev/sdc1 <-- change to the correct drive
3. mount /dev/sdc1 /mnt
4. cd /mnt
5. tar -zxvf /home/tim/ArchLinuxARM-oxnas-latest.tar.gz <-- change to correct location
6. cd /
7. umount /mnt
8. Edit the file disk_create. Change disk to the correct drive and remove the last line (line 34) that writes the kernel with dd.
9. Execute the script and wait till all data is written to disk.
10. Try to boot again with:
$this->bbcode_second_pass_code('', '
setenv bootargs "root=/dev/sda1 console=ttyS0,115200 rootwait mem=128M"
run select0 load1
bootm 60500000
')

[Taker]

YEAAAAAHH !!! Thanks a lot, Tim!

I followed your instructions step-by-step and now it boots into ALARM OS:
$this->bbcode_second_pass_code('', '
[ 3.000000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 3.000000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 3.010000] usb 1-1: Product: USB2.0 Hub
[ 3.020000] usb 1-1: configuration #1 chosen from 1 choice
[ 3.020000] hub 1-1:1.0: USB hub found
[ 3.030000] hub 1-1:1.0: 4 ports detected

> Arch Linux ARM

> http://www.archlinuxarm.org

------------------------------
:: Mounting Root Read-Only [DONE]
bootlogd: cannot deduce real console device
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
:: Starting UDev Daemon [DONE]
:: Triggering UDev uevents [DONE]
:: Loading Modules [DONE]
:: Waiting for UDev uevents to be processed [DONE]
:: Bringing up loopback interface [DONE]
:: Checking Filesystems [DONE]
:: Mounting Local Filesystems [DONE]
[DONE]
...

Arch Linux 2.6.31.6_SMP_820 (alarm) (ttyS0)

alarm login:
')
(I still have to use the uImage.nopci file in disk_create script instead of uImage.pci)

No I'm going to try to bring it back to my flash using your 1st description and my backup of mdt0

[WarheadsSE]

As always, first things first:
pacman -Syf udev-oxnas (say yes to replacing udev)
reboot
pacman -Syy
pacman -Syu
reboot

[Taker]

I did WarheadSE's :
$this->bbcode_second_pass_code('', 'pacman -Syf udev-oxnas (say yes to replacing udev)
reboot
pacman -Syy
pacman -Syu
reboot')

and Tim's :
$this->bbcode_second_pass_code('', 'flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-mtd0-dump')
after successful boot into Alarm OS.

I disconnected the sata drive but after next reboot, the device hangs up during kernel loading. Also after changing to:
$this->bbcode_second_pass_code('', 'setenv bootcmd "run boot_nand"
saveenv
reset')
Then I used the code: (from http://archlinuxarm.org/forum/viewtopic.php?f=29&t=1203)
$this->bbcode_second_pass_code('', 'setenv bootcmd "run boot_nand"
setenv bootargs "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x25,0x31,0x00,0xd4,0x6f mem=128 poweroutage=yes"')
and now I suppose it boots successfully into the stock busybox:
$this->bbcode_second_pass_code('', '/ # busybox
BusyBox v1.16.1 (2010-12-01 15:27:23 PST) multi-call binary.
Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.

Usage: busybox [function] [arguments]...
or: function [arguments]...

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.

Currently defined functions:
[, [[, arp, ash, awk, basename, brctl, bunzip2, bzcat, bzip2, cat,
chattr, chgrp, chmod, chown, chroot, clear, cmp, cp, crond, cut, date,
dd, depmod, df, diff, dirname, dmesg, dnsdomainname, du, echo, egrep,
eject, env, expr, false, fdflush, fdisk, fgrep, fsck, fuser, getty,
grep, gunzip, gzip, halt, head, hexdump, hostname, hush, ifconfig,
ifdown, ifplugd, ifup, init, insmod, ionice, ip, ipaddr, iplink,
iproute, iprule, iptunnel, kill, killall, less, ln, login, losetup, ls,
lsattr, lsmod, lspci, lsusb, lzop, lzopcat, md5sum, mkdir, mkdosfs,
mke2fs, mkfifo, mkfs.ext2, mkfs.vfat, mknod, modprobe, more, mount, mv,
nc, netstat, nice, nmeter, nohup, nslookup, od, passwd, pidof, ping,
ping6, pivot_root, poweroff, printf, ps, pwd, rdev, readlink, realpath,
reboot, renice, reset, rm, rmdir, rmmod, route, sed, seq, sh, sha1sum,
sleep, sort, split, stat, strings, stty, su, sulogin, sum, swapoff,
swapon, sync, sysctl, tail, tar, taskset, tee, telnet, telnetd, test,
time, top, touch, tr, traceroute, traceroute6, true, tty, tune2fs,
udhcpc, umount, uname, uniq, unlzop, uptime, usleep, vi, wc, wget,
which, who, whoami, xargs, yes, zcat, zcip

/ # ps
PID USER VSZ STAT COMMAND
1 root 2220 S init
2 root 0 SW< [kthreadd]
3 root 0 SW< [migration/0]
4 root 0 SW< [ksoftirqd/0]
5 root 0 SW< [migration/1]
6 root 0 SW< [ksoftirqd/1]
7 root 0 SW< [events/0]
8 root 0 SW< [events/1]
9 root 0 SW< [khelper]
12 root 0 SW< [async/mgr]
79 root 0 SW< [kblockd/0]
80 root 0 SW< [kblockd/1]
85 root 0 SW< [ata/0]
86 root 0 SW< [ata/1]
87 root 0 SW< [ata_aux]
108 root 0 SW [pdflush]
109 root 0 SW [pdflush]
110 root 0 SW< [kswapd0]
111 root 0 SW< [aio/0]
112 root 0 SW< [aio/1]
113 root 0 SW< [nfsiod]
115 root 0 SW< [crypto/0]
116 root 0 SW< [crypto/1]
250 root 0 SW< [scsi_eh_0]
253 root 0 SW< [scsi_eh_1]
257 root 0 SW< [ox820direct_eh]
260 root 0 SW< [mtdblockd]
275 root 0 SW< [ubi_bgt0d]
277 root 0 SW< [rpciod/0]
278 root 0 SW< [rpciod/1]
283 root 0 SW< [ubifs_bgt0_0]
406 root 2220 S udhcpc -b -i eth0 -H Pogoplug
413 root 0 SW< [khubd]
440 root 1876 S /usr/local/cloudengines/bin/hbwd /usr/local/cloudeng
441 root 2224 R -/bin/sh
442 root 8508 S /usr/local/cloudengines/bin/hbplug
480 root 2244 S /usr/sbin/dropbear -P /var/dropbear.pid
506 root 2224 R ps
/ #
')

[WarheadsSE]

That is indeed the stock busybox

Something you will want to do, if that device is connecting to my.pogoplug.com: update the device's ID in uboot. The pogoplug services read the cesvcid uboot variable to identify your device.


We should pull this entire process into a single "Recovery My Brick" process.

[Taker]

Thanks WarheadsSE for the hint about the device's ID.

I'm going to change it later and I think it's just nice to have, because my intention was not to use it perfectly with my.pogoplug.com when I bought it a few month ago

Something is left a little bit unusual. The memory test during boot process reports some 'uncorrectable errors':
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader XCE_STAGE1: 1.1: Tue Feb 8 01:40:26 PST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001C01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
Uncorrectable error(s) encountered in page with starting address 0x00040000.

Uncorrectable error(s) encountered in page with starting address 0x00040000.

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading NAND, Image 1
Hdr len: 0x0001C030
Hdr CRC: 0x39F6D832
OK')
but as shown in my last post the device boots!

Comparing it to my 2nd 'untouched' B04-Pogo:
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Thu Jul 29 19:36:02 PDT 2010
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001C01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading NAND, Image 0
Hdr len: 0x0001C030
Hdr CRC: 0x39F6D832
OK')

Any idea why there are two entries during boot sequence of the de-bricked device (Reading NAND, Image 0 ... Reading NAND, Image 1)?
The 'untouched' has only one without errors.

[WarheadsSE]

Yup. Burned block in that spot, so it switched to the secondary copy. There are actually 4 copies of uboot in nand :p

[Taker]

Okkaaayyyyy

May be now it's a good time to do what I tried 5 month ago, kill pogosoft and install linux for adults.I think I'll skip the 'brick'-step this time

[WarheadsSE]

I should really generate a new rootfs...

I have to get power back first...

currently at work

[Taker]

So finally I installed Archlinux to my new stock device using:
http://archlinuxarm.org/platforms/armv6/pogoplug-provideov3
and everything went fine.

I have never thought that it could be such an awesome adventure

@Warhead
Should I write a summarisation of my steps to de-brick my device in an new topic with your suggested title 'Recovery My Brick'?
Or would some of the admins at least will mark this topic here as solved?

Taker