(Solved) After Debian install, it boots back to PogoPlug, E02

I'm sorry for asking another can't boot to debian question but after 3 hours, I just can't find a solution. I did search and tried a bunch of solutions but non of them worked for me. I know I'm missing something simple. I received PogoPlug E02 today and tried to install Wheezy but got an error "Kernel Too Old" then I installed Arch and it works fine but I prefer Debian since I used it before. I tried to follow this tutorial http://rolandsoft.blogspot.com/2013/02/installing-debian-wheezy-for.html but after installing Squeeze and rebooting it goes back to PogoPlug default OS. Here is the output I'm getting with errors UBIFS error, uInitrd. What's the proper and easy way to install Wheezy? It looks like USB Hard Drive is not getting mounted on boot.

Quote
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
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... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "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: 91 MiB
UBI: number of good PEBs: 728
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: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
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'!
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
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.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...

Edited 2 time(s). Last edit at 12/13/2013 01:15AM by Almaz.

You should install Squeeze and and then upgrade to Wheezy:
http://projects.doozan.com/debian/

then change /etc/apt/sources.list to point to wheezy, and
apt-get update
apt-get upgrade

Or use this ready-made rootfs:
http://forum.doozan.com/read.php?2,12096

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

I got stock on step number 1. After I install Squeeze and reboot, it goes to PogoPlug OS instead of Squeeze. What should I do?

Edit: Forgot to mention before installing anything I formatted the drive on another linux machine using Gparted as EXT3 if it makes any difference.



Edited 1 time(s). Last edit at 12/12/2013 03:27AM by Almaz.

Don't need to use gparted. Use fdisk to create partition, and e2fsck to format as ext3. Just a precaution to make sure that it is MBR partition. If you can use fdisk to list partition, and see that it is not GPT, then it's fine.

Sometime you need to power down and cold boot, instead of reboot to see if Squueze was installed OK.

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

I'm really going nuts. I just set it up again and back to square one. It just keeps booting back to PogoPlug instead of Debian. Do you see any problems with me doing "fdisk"?

Quote
Disk /dev/sda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 188 1510078+ 83 Linux
/dev/sda2 189 221 265072+ 82 Linux swap

Edited 1 time(s). Last edit at 12/12/2013 04:02AM by Almaz.

Mount the stick on another box and examine /boot directory. uImage and uInitrd are missing from that directory then Squeeze installation was not successful.

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

I'm already one step further. I was able to boot from a hard drive to Debian but I can't connect to it. It's not showing up in DHCP, even tried to setup static IP for it in my Router but it looks like eth0 is down or maybe ssh is not even running. So far in order to get it working I had to do
1) Install Squeeze without rebooting
2) ./mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
3) ./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd

I remount Debian drive and CHROOT it. Tried to change /etc/network/interfaces to
auto eth0
iface eth0 inet static
address 192.168.3.31
netmask 255.255.255.0
gateway 192.168.3.1

I'm still not able to get access to PogoPlug Debian. I can't even ping it. What's the next step to get it on the network so I can ssh to it.

Quote
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
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... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "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: 91 MiB
UBI: number of good PEBs: 728
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: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
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'!
stopping USB..
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1435696 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4535463 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.32-5-kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1435632 Bytes = 1.4 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-2.6.32-5-kirkwood
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4535399 Bytes = 4.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Just installed your ROOTFS on a different usb stick and booted up PogoPlug. The same problem, orange led lights up, and it's not showing up in DHCP table on my router. Tried a different router as well just to double check. I'm totally stuck and can't figure it now past this point. I need ideas where to start troubleshooting.



Edited 3 time(s). Last edit at 12/13/2013 01:14AM by Almaz.

Problem solved. UBOOT env were set to EXT3, where Debian script automatically format the drive to EXT2. I'm just amazed no one even posted anything about it.

Almaz Wrote:
-------------------------------------------------------
> Problem solved. UBOOT env were set to EXT3, where
> Debian script automatically format the drive to
> EXT2. I'm just amazed no one even posted anything
> about it.

Right after you run Jeff script, uBoot env is set to Ext2, and the drive is set to Ext2.

The mismatched usbrootfs type problem is very common, there are many posts about it. If the uBoot env is set to Ext2 then it will boot Ext3 fine, but not the other way around.

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

Thanks bodhi, I wish you would tell me that yesterday :). I spent probably 6 hours on it and troubleshooting by trial and error. Anyway I ended up using your rootfs and I can say great job. So far the only errors I can see from your rootfs

Quote
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Setting up samba (2:3.6.6-6+deb7u2) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
-bash: debconf:: command not found
root@debian:/etc/samba# debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline

but otherwise it looks good and it would save me some time from doing all the manual updates. I didn't check what's wrong with Perl yet. By the way what's the advantages using your Kernel vs Wheezy original kernel?



Edited 2 time(s). Last edit at 12/13/2013 03:28AM by Almaz.

Almaz,

The dialog is just another package that usually used whenever you install a package, missing it does not hurt anything, because the apt-get falls back to teletype. I did not install it since I expect users to install it when they see the errors (will do that for the next release to keep it simpler, it looks like a problem but it is not). So:

apt-get install dialog

should fix it.

My kernel build has proper patches for most of the Kirkwood boxes. So depending on the Kirkwood variant, it has patch to control LEDs, SATA, so on,… Things that are particular to the hardware. The vanilla kernel only has the basic reference board supports and the Dockstar variant support (e.g. no SATA on the reference board, LEDs are not the appropriate settings...).

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



Edited 1 time(s). Last edit at 12/13/2013 03:48AM by bodhi.

Thank you. I hope to see more updates from you. If it's possible to put some WiKi or Sticky in regards to the problem I was having. I'm sure I'm not the last and not the first one with a similar problem who can't boot to Debian. I was almost ready to give up and switch to Arch which takes minutes to install without any problems.

Hi

I have the same problem, but my understanding of pogoplug, uboot and how to install on them seems to be more limited.

So. I am that far:

1) I have a pogoplug E02 (the pink one...)
2) I have installed the newest uboot, and also reset the environment from http://projects.doozan.com/uboot/install_uboot_mtd0.sh
3) I installed debian squeeze from dockstar.debian-squeeze.sh

This completed without error (in contrast to the wheezy with the kernel to old error message).

Now when I reboot pogoplug with the external hdd in which I installed debian, it boots into pogoplug.

The file system of /dev/sda is ext2

In /boot/ of the debian installation I have:

Pogoplug:/tmp/sda/boot$ ls -l
-rw-r--r--    1 root     root      1006219 Sep 25  2013 System.map-2.6.32-5-kirkwood
-rw-r--r--    1 root     root        84134 Sep 25  2013 config-2.6.32-5-kirkwood
-rw-r--r--    1 root     root      4535174 Jan  1 00:17 initrd.img-2.6.32-5-kirkwood
-rw-r--r--    1 root     root      1435632 Sep 25  2013 vmlinuz-2.6.32-5-kirkwood

I had Arch installed on the same extermal hdd and it seemed confusing to a me as an old Ubuntu user... but it worked and booted.

So: what can I do now? What is missing?

Thanks,

Rainer

Try to run the following to fix it

Quote
mkdir /tmp/debian
mount /dev/sda1 /tmp/debian
#/tmp/debian/usr/sbin/chroot /tmp/debian /bin/bash
export PATH=$PATH:/usr/sbin:/sbin
cd /tmp/debian/usr/bin
./mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd
cd /tmp
sync
umount /dev/sda1
reboot -f

Thanks for your prompt reply.

I get the following:

1) after the chroot, the tmp is empty, presumibly because /tmp/debian is set as root. SO I had to run the commands as follow:

root@Pogoplug:/# /usr/bin/mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d /boot/vmlinuz-2.6.32-5-kirkwood /boot/uImage
Image Name:   Linux-2.6.32-5-kirkwood
Created:      Sat Jan  1 00:04:52 2000
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1435632 Bytes = 1401.98 kB = 1.37 MB
Load Address: 0x00008000
Entry Point:  0x00008000
root@Pogoplug:/# /usr/bin/mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d /boot/initrd.img-2.6.32-5-kirkwood /boot/uInitrd
Image Name:   initramfs-2.6.32-5-kirkwood
Created:      Sat Jan  1 00:05:35 2000
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    4535174 Bytes = 4428.88 kB = 4.33 MB
Load Address: 0x00000000
Entry Point:  0x00000000
root@Pogoplug:/#
root@Pogoplug:/tmp# sync
bash: /bin/sync: Input/output error
root@Pogoplug:/tmp# umount /dev/sda1
warning: can't open /etc/mtab: No such file or directory
umount: /dev/sda1: not found
root@Pogoplug:/tmp# reboot -f

Rebooted and booted into debian. Perfect. I guess, the chroot was not needed?

Thanks a lot,

Rainer

Nope, CHROOT wasn't needed and as you can see I had "#" in the beginning of the line, so the line wasn't running to begin with.



Edited 1 time(s). Last edit at 12/13/2013 05:24PM by Almaz.