Linux Device Hacking - Rescue System

Re: Stupid mistake - brick or recoverable?

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

Just for the sake of completeness: the answer is "recoverable".

The idea I had in my original post actually did work. So, if anybody else is interested, this is what can be done, if need be:

1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 via

dd if=/dev/mtdx of=nsa320_mtdx.img

2. Flash those images to the one needing re-construction via

flash_eraseall /dev/mtdx
nandwrite /dev/mtdx nsa320_mtdx.img

Maybe other noobs apart from myself will profit from this.

Re: Stupid mistake - brick or recoverable?

chessplayer — Wed, 15 May 2013 09:23:56 -0400

WarheadsSE,

ok, thanks, but: this means ???

What I have done meanwhile is create images of mtd0 - mtd8 (using dd) from the second NSA320 I am currently fiddling with. Is that about the same you were suggesting?

Re: Stupid mistake - brick or recoverable?

WarheadsSE — Wed, 15 May 2013 09:13:43 -0400

Sounds to me like a nanddump is in order.

Stupid mistake - brick or recoverable?

chessplayer — Wed, 15 May 2013 05:16:24 -0400

Hi guys,

unbelievable, but in spite of the red alert text in the first post, i managed to erase mtd1 and mtd2 on one of my Zyxel NSA320s when trying to install the rescue system (wanted to do everything quickly, since I need to go out for a while in a minute and copy and pasted the wrong commands ...).

Now the machine is still running and I have others with which I could try to remedy the situation if I only knew enough to do so. Therefore, here is what I believe to be the case:

a) mtd1 = uboot_env and mtd2 = key_store (from looking at fw_printenv)
b) uBoot is still there as it is in mtd0

fw_printenv still gives me the values I expect to see, but maybe it does not read directly from /dev/mtd1? What is/dev/mtd2 used for (key_store)? Can I reboot with it overwritten?

If not, will the following help:

1. Extract images of /dev/mtd1 and /dev/mtd2 from another NSA320 (will be a challenge, but google will be my friend ...)
2. Flash those images to the one currently under re-construction

Any help would be greatly appreciated, as always ...

Re: ZyXEL NSA320 install from scratch

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

Hi guys,

by 'his method', davy is referring to this post, but seeing how old this post is, you probably know that already.

Myself, I am at the point where I can boot from a USB-drive (but not just any drive; one is working, another isn't; furthermore, it does not seem to want to acquire an ip address all the time ...). Booting the exact same image from HDD is not possible though, but I believe that is is a problem of the drive. I need to do more testing.

So, if we all work together, maybe we can describe the process together with all the nooks and crannies like which drives work all in one place.

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

chessplayer — Mon, 13 May 2013 09:00:49 -0400

Der Freibeuter Wrote:
-------------------------------------------------------
... snip ...
> 3. Whe i got both files i should download
> flash_erase and nandwrite:
>
> wget
> http://download.doozan.com/uboot/flash_erase
> wget
> http://download.doozan.com/uboot/nandwrite

No, this is not necessary, since flash_erase and nandwrite are already available
>
... snip ...
>
> So the next steps, after flashing those both
> images i boot into Rescue Mode and enter
>
> run bootcmd_rescue

No, you are way past this point once the rescue system is booted up ...
>
> And the last problem, i got on my pc ubuntu as os,
> but i didnt found anything about the netconsole
> how to use it on thos forum. whalt should i
> exactly do to use it?

Look here and maybe here also
>
> I know, a lot of quesions, ive rtfm but i want to
> be on the right side.
>
> thx

Hope this helps!

Cheers,

chessplayer

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

Der Freibeuter — Sun, 12 May 2013 04:47:22 -0400

Ok,

i did it and also set the machid to dd6. But before i reboot i wait for feedback ;) I hope my Debian on stick will boot up,

Thx

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

Der Freibeuter — Sat, 11 May 2013 16:41:45 -0400

@ Basti

dpkg-reconfigure tzdata einfach ausführen ;-)

Hi Folks,

i wanna say thanks your your work, but i had a lot of questions. I have got a Pogo E02 with the Rescue System v2 on it, latest uboot installed trough the sh script and Debian on a USB Stick. Now i want to update to the latest 2.8.2 Rescue System but im not sure if i am right and before i brick my Pogo i want to her if my steps were ok.

1. I had set my Pogo with this command the Arch Number 3542

/usr/sbin/fw_setenv arcNumber 3542

2. After that i download the Arch Rescue System 2.8.2

wget https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz

untar it

tar zxvf RescueV2.8.2-10292012.tar.gz

3. Whe i got both files i should download flash_erase and nandwrite:

wget http://download.doozan.com/uboot/flash_erase
wget http://download.doozan.com/uboot/nandwrite

4. And flash mtd0 and mtd1 with these commands:

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

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

and set this values:

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

I think this is right?!

Ok, but on the instrutions on the first page tehere also stands Pogoplug E02 3542 if you have a kernel that supports it

Did my default Armel Kernel from Debian boot up again?

So the next steps, after flashing those both images i boot into Rescue Mode and enter

run bootcmd_rescue

And the last problem, i got on my pc ubuntu as os, but i didnt found anything about the netconsole how to use it on thos forum. whalt should i exactly do to use it?

I know, a lot of quesions, ive rtfm but i want to be on the right side.

thx

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Fri, 10 May 2013 14:48:30 -0400

I decided that I wanted to add a wifi stick to my plug while waiting for my sensors to come in. Looks like I will have to add the necessary tools to the image with buildroot, and make a driver for my realtek rtl8188cus module. So I started by grabbing the source for the drivers from realtek.com and added some lines for the dockstar

CONFIG_PLATFORM_ARM_926T = y

and

ifeq ($(CONFIG_PLATFORM_ARM_926T),y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN
ARCH := arm
CROSS_COMPILE := /tmp/owfsplug/output/host/usr/bin/arm-unknown-linux-uclibcgneabi
KVER := 3.2.7
KSRC := /tmp/owfsplug/output/build/buildroot-config
endif

and I get the errors

make[1]: Entering directory `/tmp/owfsplug/output/build/buildroot-config'
make[1]: *** No rule to make target `modules'.  Stop.
make[1]: Leaving directory `/tmp/owfsplug/output/build/buildroot-config'
make: *** [modules] Error 2

I really think I may be out of my league here, but I would appreciate some guidance if you had any.

Re: MacPlug & SMBPLug : Mac/AFPD or Windows/SMB + Print services in a flash/NAND image

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

I am having the exact same problem, I tried all 3, but no joy, getting a little frusterated

edit: turns out that rescue_installed was set to 0, booted from a stick and ran fw_setenv rescue_installed 1 and that fixed my problem

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

basti523 — Sat, 04 May 2013 04:45:53 -0400

how can is set the right timezone on this rescue system? i need Europe/Berlin.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Mon, 29 Apr 2013 09:46:40 -0400

Looks like Maxim is no longer producing the lightning detector, can be had from hobby-boards, but Maxim still does sample requests, so I can at least get temp and humidity sensors to play with. Thanks for suggesting, I have requested samples from them before when I was trying to teach myself electronics, and forgot that they did that.

So far everything is going well on my plug. Had some issues mounting my Samba share for the images at first, fstab wouldn't read from a credentials file, or wait for the network to come up, I even started pulling from git to try and add samba hoping something in smbcient would fix it but went with an if-up.d script instead (at least now I know how to pull from git, and that buildroot stuff is pretty cool, I wonder what the space restraints on mtd1 are for adding packages).

Re: MacPlug & SMBPLug : Mac/AFPD or Windows/SMB + Print services in a flash/NAND image

thomas — Mon, 29 Apr 2013 01:16:49 -0400

davygravy Wrote:
-------------------------------------------------------
> I'm thinking that space was _really_ limited

Now that I've been playing with SMBplug for a while, I'm wondering if it would be possible to add a few things to make it even better. If there's not space (as noted above), then so be it.

Having said that:
1. It'd be useful to attach NTFS volumes >2 TB. Right now, /tmp/messages says:
Apr 28 23:23:27 SMBPlug kern.err kernel: [ 377.530436] NTFS-fs error (device sda1): parse_ntfs_boot_sector(): Volume size (2TiB) is too large for this architecture. Maximum supported is 2TiB. Sorry.

Perhaps adding NTFS-3G would fix this?

2. Autofs or something like it would be a nice convenience.

As noted at http://dev.shyd.de/2011/01/dockstar-nas-automount-hd-idle-samba-ftp/ it'd be neat if drives would automount. (Is this supposed to happen? If so, I'm missing something. I remounted / rw and added in mount points and entries in /etc/fstab with noauto for three drives, and now it works if I ssh into the box and mount them by hand after a reboot / power outage.)

3. hd-idle and appropriate configuration files would be good, too, to both save power and disk life.

Finally, as seen from OS X, I'm getting two entries in the Finder sidebar. One is SMBPLUG and the other is SMBPlug-SMB. They both go away when I stop Avahi and I can see where SMBPlug-SMB is defined in one of the Avahi services files. The SMBPLUG entry, I thought, was coming from OS X seeing samba, but that icon also went away when I stopped /etc/init.d/S50avahi-daemon so now I'm not so sure.

I can connect to SMBPLUG with timemachine/timemachine username/password but attempting to attach to SMBPlug-SMB fails. When I hit on the Connect As... button in order to enter a username, I get "There was a problem connecting to the server SMBPlug-SMB. The server may not exist or it is unavailable at this time." etc etc. Any ideas on how to fix this?

Re: MacPlug & SMBPLug : Mac/AFPD or Windows/SMB + Print services in a flash/NAND image

Thomas — Sun, 28 Apr 2013 21:54:45 -0400

Nevermind the message above this one.

I tried the SMBplug and the MacPlug and neither worked. Then I tried the OWFSplug and that did work! So, I tried the SMBplug and it worked that time.

Perhaps the NAND in my Dockstar is glitchy.

In any case, thanks again!

Re: MacPlug & SMBPLug : Mac/AFPD or Windows/SMB + Print services in a flash/NAND image

Thomas — Sun, 28 Apr 2013 19:49:36 -0400

Hi -

I, too, am writing to thank Davy, but also to report a lack of success with SMBplug.

I downloaded the current 0.7 tar file for SMBplug linked in the first post and made a USB stick. The boot from there worked fine (unlike a lot of other USB images for my Dockstar).

I noticed a couple of odd things when I flashed the SMBplug. Here is the output. Look out for the fact that:

1. Only 23, not 25 blocks were flashed by the first portion
2. One of the output messages was at number 211, not 212, in the second portion.

Farther below, I've used netconsole to produce the looping attempts to boot from the built-in memory.

Here was the flashing sequence:
SMBPlug:/img_files# flash_erase /dev/mtd1 0 0
Erasing 128 Kibyte @ 3e0000 -- 100 % complete
SMBPlug:/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 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
SMBPlug:/img_files# flash_erase /dev/mtd2 0 0
Erasing 128 Kibyte @ 1fe0000 -- 100 % complete
SMBPlug:/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 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 211 -- 100 % complete
ubiformat: formatting eraseblock 255 -- 100 % complete
SMBPlug:/img_files# reboot

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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
** 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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1752
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: 1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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'!
** 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..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...

and loop.

Any ideas what to do from here?

Thanks!
Thomas

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Sat, 27 Apr 2013 09:18:56 -0400

IIRC Maxim IC has some sort of offer where they'll send you a limited grab bag of sensors

I got enough sensors to play with for free.

The usb adaptor can be had for $10 or so if you watch ebay.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Thu, 25 Apr 2013 21:54:39 -0400

OK, finally had some time to sit down and flash it to one of my plugs, up and running. Tomorrow hopefully I will have time to tweak motion a little, and research some 1-wire devices to get a little weather station going. Finally have motion running on a dock that will survive a power outage! Thank you sir, great work!

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Sun, 21 Apr 2013 00:46:26 -0400

OK, this is pretty much finished now. A lot closer to working out of the box.

The rootfs.tar tarball is for a USB pendrive. Once booted, that rootfs is a working OWFSplug system, but also it has the img files for flashing it to NAND. AFAIK, the only adjustments needed would be to set up the device IDs of the 1-Wire sensors, change (if necessary) the motion-usbcamera-modules in /etc ... ? Maybe the timezone in /etc/TZ.

Works without or with an attached USB drive, but I suggest using a USB drive, as /tmp will fill up quickly w/ images, movies and rrdb database files.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Tue, 16 Apr 2013 20:33:51 -0400

good to know

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Sun, 14 Apr 2013 20:35:39 -0400

Something to note... the tarball I posted is USB rootfs only... I'm doing some final touches now on what I've got in git, and if it boots and functions correctly, I'll build UBIFS and kernel bins for flashing.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Sat, 13 Apr 2013 22:48:41 -0400

Much thanks, I can't wait to play around with this. I wold be useless at helping with git, but have several dockstars, pogos, a goflex and some pi's to play with if you needed any testing done. I have been looking at your weather station the last few days and convincing myself that it would be a fun project to set one up, so this will definitely see some use.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Sat, 13 Apr 2013 20:06:17 -0400

kk, bitz. I've uploaded an old tarball here: https://dl.dropboxusercontent.com/u/1015928/Kirkwood/OWFSplug/OWFSplug-rootfs.tar ... mind you, this may be "roughly hewn" but should be bootable on a USB stick.

I'm currently tidying up my git repo, adding in some needed items and culling out the cruft...

https://github.com/davygravy/owfsplug

The README shows the basics....

Will post a NAND image when I'm satisfied w/ it. If you are interest and know git, you can propose commits via Github.

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Thu, 11 Apr 2013 22:07:48 -0400

davygravy Wrote:
-------------------------------------------------------
> @bitz: I will try to post a tarball ASAP.
>
> Be aware that what I post would be bootable, but
> would need some editting to set up things like
> where you want to stop the images, how you'd want
> to process them with the embedded ffmpeg (which is
> built into the image).

Thanks, I am looking forward to it. Setting up motion should be no problem

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Thu, 11 Apr 2013 21:13:35 -0400

@bitz: I will try to post a tarball ASAP.

Be aware that what I post would be bootable, but would need some editting to set up things like where you want to stop the images, how you'd want to process them with the embedded ffmpeg (which is built into the image).

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

bitz — Sun, 07 Apr 2013 21:23:39 -0400

Thanks for this. Any chance you could provide a tarball, or point me to a guide for compiling from git?

Re: OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package

davygravy — Sun, 07 Apr 2013 20:36:42 -0400

I finally got around to committing this to git, and now hosted on github.com

https://github.com/davygravy/owfsplug

Re: GoFlex Net not installed UBoot

Westley Paynter — Thu, 21 Mar 2013 16:39:36 -0400

Check out here

http://projects.doozan.com/uboot/

Re: Rescue System v2

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

Will this rescue system work on Pogoplug Mobile? or we do have one for it?

Re: Recovery System ready for use

twinclouds — Sat, 16 Mar 2013 22:59:42 -0400

Will this rescue system work on Pogoplug Mobile? or we do have one for it?
(Not sure if this is the right place, so I posted it on another thread also.)

Re: Ping OK - SSH Connection Refused -Rehash'd

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

I had the same issue. Create the usb disk with fdisk and then copy the files with root access.