Recovery System ready for use I've made a Recovery System that I think will be more useful than the Pogoplug partition. This will replace the Pogoplug kernel on mtd1 and the Pogoplug system on mtd2 with a more sophisticated system. The new system includes: [list] [*] [url=http://www.handhelds.org/moin/moin.cgi/Ipkg]ipkg[/url] [*] 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 [*] wget/curl/links/ncftp/rsync [*] vi/nano [*] screen [*] kernel 2.6.32-18 with tons of modules for whatever you may have connected [/list] The default login is 'root' with password 'root' See [url=http://forum.doozan.com/read.php?4,831,876#msg-876]this post[/url] for a list of the included binaries. By default, the system will attempt to get an IP address over DHCP. It will also use the static IP address 169.254.9.17 for recovery when DHCP is not working. 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: [code] cd /tmp wget http://jeff.doozan.com/debian/rescue/install_rescue.sh chmod +x install_rescue.sh ./install_rescue.sh [/code] The system is based on [url=http://buildroot.uclibc.org]buildroot[/url] 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: [code] 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 wget http://jeff.doozan.com/debian/rescue/buildroot-dockstar.tgz tar -xzvf buildroot-dockstar.tgz cp custom/buildroot-config .config make [/code] 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: [code] cd output/images cat http://forum.doozan.com/read.php?4,831,831#msg-831 Sun, 19 May 2013 12:03:20 -0400 Phorum 5.2.18 http://forum.doozan.com/read.php?4,831,11957#msg-11957 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,11957#msg-11957 (Not sure if this is the right place, so I posted it on another thread also.)]]> twinclouds Rescue System Sat, 16 Mar 2013 22:59:42 -0400 http://forum.doozan.com/read.php?4,831,8359#msg-8359 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8359#msg-8359
Make sure you follow the flashing commands symbol-for-symbol.


The V3.0 is neither polished nor finished, though it has a few extra things in it (inadyn, parted) that could be backported to a possible V2.8.2.]]> davygravy Rescue System Fri, 15 Jun 2012 12:29:29 -0400 http://forum.doozan.com/read.php?4,831,8354#msg-8354 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8354#msg-8354
Now it's working perfectly ... So I don't really know what appended but this old rescue system seems a little dangerous nowadays.

I will try to install Rescue 2.8 now that I have an upgraded uboot.]]> ElectronikHeart Rescue System Fri, 15 Jun 2012 10:55:32 -0400 http://forum.doozan.com/read.php?4,831,8223#msg-8223 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8223#msg-8223
The uboot bootcmd can be defined in such a way that it should first try to boot from SATA, if no sata is present then it fals back to USB. If no USB then rescue system which is in NAND flash.

There is a kernel package that works perfectly w GoFlex. Find it by following the link in my sig/signature.]]> davygravy Rescue System Mon, 04 Jun 2012 07:23:51 -0400 http://forum.doozan.com/read.php?4,831,8219#msg-8219 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8219#msg-8219
How the rescue system work ? What kind of uboot environment modification is he doing that prevent me to boot from USB ?

Is this the wanted behavior ? (something like defaulting to the rescue, I don't know why I can't boot actually ...)]]> ElectronikHeart Rescue System Mon, 04 Jun 2012 05:05:19 -0400 http://forum.doozan.com/read.php?4,831,8218#msg-8218 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8218#msg-8218 http://forum.doozan.com/read.php?3,6965,8189#msg-8189

Kernel:
I don't think it is in the main line yet for GoFlex Home/Net.]]> bodhi Rescue System Mon, 04 Jun 2012 03:45:07 -0400 http://forum.doozan.com/read.php?4,831,8217#msg-8217 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8217#msg-8217
But that's not a problem, using a serial cable is simple enough ^^

The kirkwoods devices are not easy to break or to brick I should say.

It's a shame that a lot of theses tutorials are not descriptive enough, and not linked together in a coherent way.

And making it to the end without breaking anything is difficult.

Is there a new script (that flash the latest Uboot and install a s-ata arcNumber 3089 compatible kernel) on the way ?

If not I will take this opportunity to do it myself based on jeff doozan's script. (At least for Uboot, It's very frustrating to flash uboot to see that you have to flash it again but another way ...)]]> ElectronikHeart Rescue System Mon, 04 Jun 2012 02:18:24 -0400 http://forum.doozan.com/read.php?4,831,8211#msg-8211 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8211#msg-8211 These and once I found the right driver and did a little soldering they worked great.

I also bought a bunch of These and installed one right in the box, and put a standard mini stereo headphone jack (from radio shack) on the end of the wire and can serial in whenever I need to.]]> optim Rescue System Sun, 03 Jun 2012 19:21:37 -0400 http://forum.doozan.com/read.php?4,831,8210#msg-8210 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8210#msg-8210
Yes, if it does not boot, serial access is the best choice now.]]> davygravy Rescue System Sun, 03 Jun 2012 18:36:30 -0400 http://forum.doozan.com/read.php?4,831,8209#msg-8209 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8209#msg-8209
I thought it worked with arcNumber 3089

http://forum.doozan.com/read.php?4,3896 ( "with support for the new arcNumber (Dockstar & GoFlex Net)" )

When I tried to boot up with my USB Key the led (on the USB Stick) is blinking and the led from the Goflex is blinking orange a little after that. Then nothing ...

I don't know how the boot process works exactly. I will buy an USB serial adapter. I think there is no other solutions ... Or is he ?]]> ElectronikHeart Rescue System Sun, 03 Jun 2012 17:01:01 -0400 http://forum.doozan.com/read.php?4,831,8208#msg-8208 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8208#msg-8208
It will boot on nearly any kirkwood machine and it recognizes that arcNumber.]]> davygravy Rescue System Sun, 03 Jun 2012 16:38:59 -0400 http://forum.doozan.com/read.php?4,831,8206#msg-8206 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,8206#msg-8206
I have a little problem here on my Goflex Home.

I tried to install the recovery system and it's not booting, even on my USB key ...

The only thing i have done (and shoudn't have done I think) is "setenv arcNumber 3089"

Is the recovery system not booting with this arcNumber ?

What con I do ? I don't have a netconsole set ... I think I will use a serial cable. (Is there a tutorial on how to use and solder the serial cable ?)]]> ElectronikHeart Rescue System Sun, 03 Jun 2012 15:51:13 -0400 http://forum.doozan.com/read.php?4,831,6191#msg-6191 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,6191#msg-6191 Isn't it strange that it fails in the same spot (6%)?]]> Riccardo Rescue System Mon, 31 Oct 2011 09:13:14 -0400 http://forum.doozan.com/read.php?4,831,6190#msg-6190 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,6190#msg-6190 using /usr/sbin/ubiformat /dev/mtd2 -s 512 -f /tmp/rootfs-mtd2.img -y
produces the same output.
Is it safe to reboot or what should I do?
Thanks


Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 13 -- 6 % complete libmtd: error!: cannot write 131072 bytes to mtd2 (eraseblock 13, offset 0)
error 12 (Cannot allocate memory)

ubiformat: error!: cannot write eraseblock 13
error 12 (Cannot allocate memory)
Installation failed.]]> Riccardo Rescue System Mon, 31 Oct 2011 08:08:03 -0400 http://forum.doozan.com/read.php?4,831,4499#msg-4499 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,4499#msg-4499
Today i was trying to install a rescue system and got a following error:
Quote
# 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 4570273 bytes) is not multiple of eraseblock size (131072 bytes)
error 0 (Success)
Installation failed.

Somebody knows what was going wrong here?]]> Dynamo Rescue System Sun, 10 Apr 2011 06:54:28 -0400 http://forum.doozan.com/read.php?4,831,3893#msg-3893 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3893#msg-3893
Please have a look at the start post of Doozan: http://forum.doozan.com/read.php?4,831,831#msg-831

To install the image you will must have a look into the install file of Doozan and change it to not download from his site but from your ftp or copy it manually by scp and to use your self compiled image.

Maybe I will have time to release a special version of it.]]> Riffer Rescue System Thu, 17 Feb 2011 10:12:53 -0500 http://forum.doozan.com/read.php?4,831,3767#msg-3767 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3767#msg-3767
Boot into uboot-- I had already installed Jeff's modified uboot but I don't see why this shouldn't work with the pre-installed uboot. Although you will probably want to upgrade when you have a working recovery system.

First, repartition the flash/mtd device: 
mtdparts del uImage
mtdparts del rootfs
mtdparts del data

mtdparts add nand0 0x400000@0x100000 uImage
mtdparts add nand0 0x2000000@0x500000 root
mtdparts add nand0 0xdb00000@0x2500000 data

saveenv

Next, write mtd1 and mtd2. If the write for mtd2 hangs, let it go for a while (10s of minutes I would think should be sufficient). 
mw.b 0x6400000 0xff 0x400000
tftpboot 0x6400000 uImage-mtd1.img
nand erase 0x00100000 0x00400000
nand write.e 0x6400000 0x00100000 0x400000

mw.b 0x6400000 0xff 0x2000000
tftpboot 0x6400000 rootfs-mtd2.img
nand erase 0x00500000 0x02000000
nand write.e 0x6400000 0x500000 0x2000000

saveenv

Then it was a matter of setting env variables until the thing worked. This was a somewhat tedious process-- I am sure there is an easier way to do it than how I did it. I 'setenv'ed variables to match a post on the first page of this thread until it booted properly. I then installed debian to a flash drive. More twiddling with saveenv to get usb booting properly. But everything now works.

For an explanation of uboot commands, I found http://www.denx.de/wiki/U-Boot/Documentation to be helpful.]]> Peter Rescue System Tue, 08 Feb 2011 01:00:54 -0500 http://forum.doozan.com/read.php?4,831,3747#msg-3747 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3747#msg-3747 -------------------------------------------------------
> Is there any way to get the rescue boot with
> arcNumber=2998 ? Or maybe a way to restore the
> pogoplug system, because this rescue system is not
> really useful as a rescue as it can't boot...

I have the same problem too.

Until it gets fixed...I have clone my USB boot stick in case my primary boot stick fails.

Patiently waiting....
S9]]> Signal9 Rescue System Sat, 05 Feb 2011 16:19:06 -0500 http://forum.doozan.com/read.php?4,831,3733#msg-3733 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3733#msg-3733
http://wiki.openwrt.org/toh/seagate/dockstar#flashlayout

I can't figure out how to change the mtd partition sizes from openwrt. Is it using the mtd_utils? I can erase and write to mtd but can't seem to delete and resize partitions. Can they be deleted and resized when booted into openwrt without crashing the Dockstar?

If the mtd partion sizes are set from uboot (I have the Jeff's modified uboot already written to mtd0), can the rescue system be installed using tftp in uboot?]]> Peter Rescue System Fri, 04 Feb 2011 14:24:46 -0500 http://forum.doozan.com/read.php?4,831,3718#msg-3718 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3718#msg-3718 bohwaz Rescue System Thu, 03 Feb 2011 19:55:51 -0500 http://forum.doozan.com/read.php?4,831,3494#msg-3494 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3494#msg-3494
which steps i have to perform after make?

Regards]]> ratskcod Rescue System Tue, 18 Jan 2011 06:29:39 -0500 http://forum.doozan.com/read.php?4,831,3449#msg-3449 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3449#msg-3449
After fixing this, it is now OK.]]> cly Rescue System Sat, 15 Jan 2011 16:11:07 -0500 http://forum.doozan.com/read.php?4,831,3439#msg-3439 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3439#msg-3439 I have just installed the rescue system, but it failed: 
Erasing 128 Kibyte @ 2000000 -- 100 % complete.
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete  
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 203 -- 100 % complete  
ubiformat: formatting eraseblock 255 -- 100 % complete  
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
Cannot parse config file: Invalid argument
# Rescue System installation has completed successfully.

When I reboot, u-boot says: 
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 ...

Any idea?
Thanks!]]> cly Rescue System Fri, 14 Jan 2011 17:25:05 -0500 http://forum.doozan.com/read.php?4,831,3274#msg-3274 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3274#msg-3274
During some tests I lost the feature booting into pogoplug or into usb debian system.

I have only the Marvell prompt. ( thanks to netcat system )
Now I have downloaded and started the rescue system from usb.
I was able to login into the RAM Running Rescue System.

But now the rescue install install_rescue.sh doesn't work.


The Question is: how to install an new Rescue System on the dockstar system.
Cause the pogoplug doesn't work anymore.

Thanks in advance...]]> htreede Rescue System Fri, 31 Dec 2010 08:51:48 -0500 http://forum.doozan.com/read.php?4,831,3107#msg-3107 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3107#msg-3107
Now the dockstar starts up with LED working under kernel 2.6.35.9 with arcNumber 2998.

For others who want to build their own rescue image I post a short description and a new build-dockstar-archive for buildroot-2010.11 maybe tomorrow after having some tests. There have been some changes to the files Jeff supported but my job is completly based on his work. Hope all works fine for you!

//edit:

Here is my archive for kernel 2.6.35.9.

Buildroot-Dockstar.tgz 

cd /usr/src
wget http://buildroot.uclibc.org/downloads/buildroot-2010.11.tar.gz
tar -xzvf buildroot-2010.11.tar.gz
cd buildroot-2010.11
wget http://www.meineneue.de/wp-content/buildroot-dockstar.tgz
tar -xzvf buildroot-dockstar.tgz
cp custom/buildroot-config .config
make

after that you must follow the original notes by Jeff in start posting!

To install the self compiled image you have to chance Jeffs install script.
When I have time I will post an adapted version for your convenience.

Any reports are welcome!]]> Riffer Rescue System Sat, 18 Dec 2010 14:16:53 -0500 http://forum.doozan.com/read.php?4,831,3052#msg-3052 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,3052#msg-3052 Riffer Rescue System Wed, 15 Dec 2010 05:49:18 -0500 http://forum.doozan.com/read.php?4,831,2719#msg-2719 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,2719#msg-2719 -------------------------------------------------------
> Debian (USB) boot will work find with
> arcNumber=2097 or arcNumber=2998 - if set to 2998
> - the kernel allows control of the LED.
>
> But - the recovery system will ONLY boot if
> arcNumber=2097 - although it supports the LED with
> a heartbeat. (will not boot with arcNumber=2998).


I had exactly the same problem and at the end I decided to NOT set the arcNumber to another value then 2097 because only with this the rescue is able to startup - and what else is a rescue system that does not boot then nonsense?

But why have you Jeff done it this way?

Why using 2097 for the rescue system where the standard kirkwood kernel only does right led support with 2998?]]> Riffer Rescue System Sun, 28 Nov 2010 09:50:09 -0500 http://forum.doozan.com/read.php?4,831,2460#msg-2460 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,2460#msg-2460
I needed to reset the uboot.environment using nc to make it come back to life.

I think I'll forego the LED flashing correctly for now - a working dockstar is better to have!!!

;-)

PHT]]> Peter Hope-Tindall Rescue System Thu, 18 Nov 2010 21:38:35 -0500 http://forum.doozan.com/read.php?4,831,2448#msg-2448 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,2448#msg-2448
Debian (USB) boot will work find with arcNumber=2097 or arcNumber=2998 - if set to 2998 - the kernel allows control of the LED.

But - the recovery system will ONLY boot if arcNumber=2097 - although it supports the LED with a heartbeat. (will not boot with arcNumber=2998).

PHT]]> Peter Hope-Tindall Rescue System Thu, 18 Nov 2010 15:21:23 -0500 http://forum.doozan.com/read.php?4,831,2424#msg-2424 Re: Recovery System ready for use http://forum.doozan.com/read.php?4,831,2424#msg-2424
Even though the USB drives DON'T appear in /proc/partition - they are still mountable.

mount /dev/sda1 /tmp/sda1 worked fine.

Thanks,

PHT


Peter Hope-Tindall Wrote:
-------------------------------------------------------
> thanks,
>
> Just got a dockstar today - love it!
>
> I installed Debian on a flash drive (and cp -a it
> to a USB hard drive as well) - both work great.
>
> I also installed the rescue system. - which works
> fine. When I try and plug in flash drivers and
> USB hard drive when running the rescue system - I
> see the devices detected in dmesg:
>
> 44.068220] usb 1-1.2: New USB device found,
> idVendor=0781, idProduct=5408
> [ 44.075133] usb 1-1.2: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> [ 44.082493] usb 1-1.2: Product: U3 Titanium
> [ 44.086693] usb 1-1.2: Manufacturer: SanDisk
> [ 44.091023] usb 1-1.2: SerialNumber:
> 3551920EACD1C080
> [ 44.097339] usb 1-1.2: configuration #1 chosen
> from 1 choice
> [ 44.106911] scsi0 : SCSI emulation for USB Mass
> Storage devices
> [ 44.117154] usb-storage: device found at 3
> [ 44.117164] usb-storage: waiting for device to
> settle before scanning
> [ 49.107558] usb-storage: device scan complete
> [ 49.108183] scsi 0:0:0:0: Direct-Access
> SanDisk Cruzer 8.01 PQ: 0 ANSI: 0 CCS
> [ 51.297629] usb 1-1.4: new high speed USB
> device using orion-ehci and address 4
> [ 51.408720] usb 1-1.4: New USB device found,
> idVendor=1058, idProduct=1021
> [ 51.415629] usb 1-1.4: New USB device strings:
> Mfr=1, Product=2, SerialNumber=3
> [ 51.422988] usb 1-1.4: Product: Ext HDD 1021
> [ 51.427276] usb 1-1.4: Manufacturer: Western
> Digital
> [ 51.432302] usb 1-1.4: SerialNumber:
> 574D41563532333536363538
> [ 51.439173] usb 1-1.4: configuration #1 chosen
> from 1 choice
> [ 51.448880] scsi1 : SCSI emulation for USB Mass
> Storage devices
> [ 51.458898] usb-storage: device found at 4
> [ 51.458908] usb-storage: waiting for device to
> settle before scanning
> [ 56.457569] usb-storage: device scan complete
> [ 56.458557] scsi 1:0:0:0: Direct-Access WD
> Ext HDD 1021 2002 PQ: 0 ANSI: 4
>
>
> BUT - I don't see the partitions:
>
> rescue:/tmp# cat /proc/partitions
> major minor #blocks name
>
> 31 0 1024 mtdblock0
> 31 1 4096 mtdblock1
> 31 2 32768 mtdblock2
> 31 3 486400 mtdblock3
>
>
>
> Is this normal? - when I inserted both disks in
> stock pogo - they appeared in /proc/partitions
>
> How can I tell what partitions the external
> devices are are to mount them?
>
> thanks,
>
> PHT]]> Peter Hope-Tindall Rescue System Tue, 16 Nov 2010 22:25:52 -0500