debootstrap failed

Hi all I managed to repair my DockStar with Jtag TIAO
but now when I install Debian seen the script with Jeff I was error message:

W: http://cdn.debian.net/debian/pool/main/z/zlib/zlib1g_1.2.3.4.dfsg-3_armel.deb was corrupt
W: Couldn't download package zlib1g (ver 1:1.2.3.4.dfsg-3 arc armel)
I: Chosen extractor for .deb packages: ar
W: Failure trying to run: chroot /tmp/debian mount -t proc proc /proc
debootstrap failed.

how to
thank you

Did you use Shyd's newer version of Jeff's script? AFAIK, Jeff's script no longer works... There is a thread called "Squeeze Installer Broken" or something such... find Shyd's first entry on that... it will explain the fix/new script needed.


BTW, good job recovering your box w/ JTAG. It is a nice tool to have around.

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

• My Weather Station: (Pogoplug E02/Debianized 1-Wire Weather-Station/Cam)
• Linux 3.3.2 for Kirkwood Debian package
• Newer U-Boot for Pogoplug E01/E02, Dockstar, GoFlex Net/Home
• Rescue V2.8.1 for Pogoplug, Dockstar, GoFlex Net/Home, Zyxel NSA320 & many others
• Kirkwood Downloads (via my Dropbox public folder)
• davy's Github Repo's AFPDplug, SMBPlug, OWFSPlug, Cloudprint, Optware-DG, uBoot ...

Salvation davygravy
Thank you for your response
I it is not which I used I followed a tutorial is his be:
ce_kernel_redstone_v63.img
ce_ramdisk_v2.0b.img
How do I?
otherwise I just even install Debian Lenny that I install?
Thank you

In general, follow the steps on this tutorial: http://jeff.doozan.com/debian/

but use this script from Shyd, instead of Jeff's Script :

wget http://dev.shyd.de/dockstar/dockstar.debian-squeeze.sh

or see http://forum.doozan.com/read.php?2,4244,4587#msg-4587

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

• My Weather Station: (Pogoplug E02/Debianized 1-Wire Weather-Station/Cam)
• Linux 3.3.2 for Kirkwood Debian package
• Newer U-Boot for Pogoplug E01/E02, Dockstar, GoFlex Net/Home
• Rescue V2.8.1 for Pogoplug, Dockstar, GoFlex Net/Home, Zyxel NSA320 & many others
• Kirkwood Downloads (via my Dropbox public folder)
• davy's Github Repo's AFPDplug, SMBPlug, OWFSPlug, Cloudprint, Optware-DG, uBoot ...

hello davygravy
I tried that
thank you for your help;-)

Now I have another problem here is what it tells me when I'm connected to the serial port:
U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### 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
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...
thank

Hey DJDavid, it seems that some enviroment variables are not well defined. Please attach your enviroment here typing printenv from uboot's prompt!

Hello pazos
I do not understand what you ask me
but parcontre ca boot on my USB Key is therefore the possibillity of t he fixed my problem by being in Debian
thank you

up !!!