Total noob here--have hit a brick wall and have tapped out my limited knowledge. I'm stuck and in need of help. I attempted a Wheezy install based on the scripts on doozan.com but it failed at the Debootstrap stage. A bit (LOL!) of research revealed success in trying Squeeze first and then upgrading. I tried that and got what I thought was a functional Squeeze install. On reboot I logged in to what I assumed was my new Debian install, and after many hours of trying to find a way to manually install apt-get (as it was missing) in the limited space available (what? My USB key is 1GB!!) I learned my USB key wasn't booting and I had logged in to the Pogoplug instead.
Like I said--noob. ;)
So I chalked it up to a bad USB key (all I have are non-branded generics--no idea of make or manufacturer) and tried another, first with Wheezy. That failed at Debootstrap again. Nuked the partitions and redid them in fdisk and ran the Squeeze script. It took.
This time I ran fw_printenv before rebooting:
And I had read hours of this forum to learn that using netconsole is invaluable to seeing what is going on. Set up the monitoring variables and this is what I get when I boot:
There are simply too many errors here for me to tackle alone. Could someone help me interpret them? Is this indeed a USB brand issue, or something else? From my limited research it seems it's not finding (or erroring?) out on a portion of the NAND too?
I'm confused because people are directed to troubleshoot this by installing Rescue System V2--but I tried that and of course it won't let me do that from within the Pogoplug OS/Limited Debian and says I have to boot off USB.
But that's the exact problem I'm having. How do I install Rescue System V2 to fix my USB booting issue, if it requires booting off USB?
My head is spinning! I am able to follow directions, and have had to cross-reference four installation "walkthroughs" and multiple threads on this forum just to get this far. I'm a critical thinker. I hope I'm not coming here missing something horribly obvious, but that's entirely possible.
The pressure's on for me to get this up and running as a baby monitor. Any and all help is greatly appreciated! Thanks!
PS I don't have access to a dedicated Linux box, though I could set up a LiveCD (suggestions?) if that's something required to get this working...
Like I said--noob. ;)
So I chalked it up to a bad USB key (all I have are non-branded generics--no idea of make or manufacturer) and tried another, first with Wheezy. That failed at Debootstrap again. Nuked the partitions and redid them in fdisk and ran the Squeeze script. It took.
This time I ran fw_printenv before rebooting:
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_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params 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:25:31:00:B4:85 arcNumber=2097
And I had read hours of this forum to learn that using netconsole is invaluable to seeing what is going on. Set up the monitoring variables and this is what I get when I boot:
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: 726 UBI: number of bad PEBs: 2 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: 715 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: read_nand_cached: error reading nand off 0x500000 size 8192 bytes ........ done. ### JFFS2 load complete: 524288 bytes loaded to 0x800000 ## Starting application at 0x00800200
There are simply too many errors here for me to tackle alone. Could someone help me interpret them? Is this indeed a USB brand issue, or something else? From my limited research it seems it's not finding (or erroring?) out on a portion of the NAND too?
I'm confused because people are directed to troubleshoot this by installing Rescue System V2--but I tried that and of course it won't let me do that from within the Pogoplug OS/Limited Debian and says I have to boot off USB.
But that's the exact problem I'm having. How do I install Rescue System V2 to fix my USB booting issue, if it requires booting off USB?
My head is spinning! I am able to follow directions, and have had to cross-reference four installation "walkthroughs" and multiple threads on this forum just to get this far. I'm a critical thinker. I hope I'm not coming here missing something horribly obvious, but that's entirely possible.
The pressure's on for me to get this up and running as a baby monitor. Any and all help is greatly appreciated! Thanks!
PS I don't have access to a dedicated Linux box, though I could set up a LiveCD (suggestions?) if that's something required to get this working...