Wheezy script debootsrap decompress issue

Hello,
I've recovered my dockstar via serial cable today after a few hours of works... all started when I tried a dist-upgrade to wheezy sometime ago. However, now the problem is that I think the wheezy install script

I don't think the problem is this one
http://forum.doozan.com/read.php?2,4881

but I think the problem is that the deboostrap.deb package now contains data.tar.xz instead of data.tar.gz
I've prepared a data.tar.gz by myself and now the script is going on but I've been stuck on this for a bit so maybe there could be something to be done. I'm not sure if xz is a workable format from pogoplug, from mine it seems not. However after all the hammering today on my dockstar who knows what I'm running now. I want to install rescue system as soon after wheezy install finishes. But now I'm stuck at FATAL: kernel too old problem in deboostrap.log
These things are really hard to hammer! :-)

Sounds very familiar. I too had to make my own package containing data.tar.gz. instead of .xz and modify the installer script to fetch it from a local HTTP server instead.

To get around the "FATAL: kernel too old" problem installing wheezy, I installed the RescueV3 tarball (sorry I don't have the link handy... I found the link somewhere on this forum) on a USB stick and booted off that, then ran the wheezy installer from there.

Note I had to modify it to install to /dev/sdb1 and /dev/sdb2 since I was booted off a USB stick on /dev/sda1. Then after the install finished I didn't reboot right away but mounted the newly installed partition and edited etc/fstab to correct the swap partition to /dev/sda2.

I found it helpful to add rsyslog and telnetd to the list of extra packages, so I could try and troubleshoot some problems I am having with initial SSH in to the new system.

Hello,
just for further reference I am now going to try with these steps
http://rolandsoft.blogspot.it/2013/02/installing-debian-wheezy-for.html

Hello,
can please someone confirm my uboot env is okay?

-sh-3.2# 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_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:50:43:00:02:02
arcNumber=2097
fw_setenv=serverip 192.168.1.204
ipaddr=192.168.1.100
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
usb_set_bootargs=setenv bootargs console=$console root=UUID=$usb_root_uuid rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_root_uuid=846f98f1-d318-436f-b860-78f77d80f635
-sh-3.2#

This needs to be fixed:

fw_setenv=serverip 192.168.1.204

This is OK:

usb_set_bootargs=setenv bootargs console=$console root=UUID=$usb_root_uuid rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_root_uuid=846f98f1-d318-436f-b860-78f77d80f635

But a better approach is using rootfs label:
http://forum.doozan.com/read.php?3,8044,8152#msg-8152

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



Edited 1 time(s). Last edit at 03/29/2014 05:13PM by bodhi.

Hello,
I have mistakenly replied here at this topic
http://forum.doozan.com/read.php?3,255

Lallo,

It booted in to Pogo OS in NAND. Looks like your Debian USB rootfs is bad (not the drive, the rootf itself):

Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
** File not found /boot/uImage
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd

EDIT: clarified.

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



Edited 1 time(s). Last edit at 03/30/2014 06:10PM by bodhi.

Hello bodhi
and thanks a lot for your help up to know.
I don't know what to say about the rootfs, I've tried with another usb key just to be sure but the problem is still the same because obviously it is not the usb key to be broken. However I can't understand how can the rootfs be broken if Jeff's install script seems to always run properly.
Could the problem be the name of the kernel?

-sh-3.2# mount /dev/sda1 /mnt/
-sh-3.2# ls
bin                      mnt                      tmp
dev                      proc                     uboot-original-mtd0.kwb
etc                      root                     usr
lib                      sbin                     var
linuxrc                  sys
-sh-3.2# cd /mnt/
-sh-3.2# ls
bin         home        media       root        sys         vmlinuz
boot        initrd.img  mnt         sbin        tmp
dev         lib         opt         selinux     usr
etc         lost+found  proc        srv         var
-sh-3.2# cd boot/
-sh-3.2# ls
System.map-2.6.32-5-kirkwood  initrd.img-2.6.32-5-kirkwood
config-2.6.32-5-kirkwood      vmlinuz-2.6.32-5-kirkwood

Besides I remember that at the beginning of time my dockstar had a pogoplug root password "stxadmin" by default. Lately in the attempt of recover the dockstar I think I have mistakenly flashed into mtd a different firmware which has "ceadmin" root password by default. Could this be the issue?
Is there a way to find the proper version of my pogoplug dockstar?

Thanks,
Lallo

Hello,
the following fixed my booting issues... now it's just a matter to upgrade to wheezy!

No lease, forking to background
starting pid 329, tty '': '/bin/sh'
-sh-3.2# mount /dev/sda1 /tmp/debian
mount: mounting /dev/sda1 on /tmp/debian failed: No such file or directory
-sh-3.2# cd /mnt/
-sh-3.2# ls
-sh-3.2# mount /dev/sda1 .
[   43.000000] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
-sh-3.2# chroot /mnt /bin/bash
ge08000 -n Linux-2.6.32-5-kirkwood -d /boot/vmlinuz-2.6.32-5-kirkwood /boot/uIma
Image Name:   Linux-2.6.32-5-kirkwood
Created:      Sat Jan  1 00:01:05 2000
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1435632 Bytes = 1401.98 kB = 1.37 MB
Load Address: 0x00008000
Entry Point:  0x00008000
ot/uInitrd initramfs-2.6.32-5-kirkwood -d /boot/initrd.img-2.6.32-5-kirkwood /bo
Image Name:   initramfs-2.6.32-5-kirkwood
Created:      Sat Jan  1 00:01:19 2000
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    4534996 Bytes = 4428.71 kB = 4.32 MB
Load Address: 0x00000000
Entry Point:  0x00000000
root@Pogoplug:/# ls
bin   etc         lib         mnt   root     srv  usr
boot  home        lost+found  opt   sbin     sys  var
dev   initrd.img  media       proc  selinux  tmp  vmlinuz
root@Pogoplug:/# cd boot
root@Pogoplug:/boot# ls
System.map-2.6.32-5-kirkwood  uImage
config-2.6.32-5-kirkwood      uInitrd
initrd.img-2.6.32-5-kirkwood  vmlinuz-2.6.32-5-kirkwood
root@Pogoplug:/boot#

Sorry for the wrong copy and paste.
This were the proper commands:

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d /media/sdb1/boot/vmlinuz-2.6.32-5-kirkwood /media/sdb1/boot/uImage 

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d  /media/sdb1/boot/initrd.img-2.6.32-5-kirkwood  /media/sdb1/boot/uInitrd