I use this command to 'copy' installs (this assumes that you've booted into Debian and that your 'new' drive is mounted in '/tmp/backup': tar \ --exclude=/lost+found \ --exclude=/tmp \ --exclude=/sys \ --exclude=/proc \ -cf - / | ( cd /tmp/backup ; tar -xpvf - ) Your bootlog looks fine. With netconsole, the last think you'll see isby Jeff - Debian
It's not a typo, it's a script that the installer creates. The script has a few workarounds to fix some app compatibility in the read-only environment. -- Jeffby Jeff - Debian
All of my changes are available on http://jeff.doozan.com/debian/uboot/build_uboot.htm The Denx code tree is frozen for their 2010.09 release, and these patches are really just a hack on the sheevaplug board config. I'm not sure it's worth the maintenance headache of adding yet "almost sheevaplug" another board config to the Denx tree. -- Jeffby Jeff - uBoot
This is just a cosmetic change, it is in all other ways identical to the older uBoot from 8/25. By default, the led will blink green while uBoot is running and turn off when control is passed to the kernel. The light will switch to blinking orange if there is an error. You can adjust the lights to fit your personal preference by modifying the "led_init", "led_exit", andby Jeff - uBoot
QuoteJeffIf you get an error when running 'netconsole' on your server, you may want to just run netcat directly: 'nc -lu 6666 & ; nc -u 192.168.1.100 6666'by Jeff - uBoot
The uBoot installer puts fw_setenv/printenv utils in /usr/sbin of your Pogoplug installation. The Debian uboot-envtools package will put them in the same place. If you're running something else, you can just reboot into Pogoplug and run or copy them from there.by Jeff - uBoot
It's not finding the 'uboot-original-mtd0.kwb' file in your Pogoplug install. You'll need to boot into Debian, mount the Pogoplug partition, and download that file. The following commands should do it: mount -t jffs2 /dev/mtdblock2 /mnt cd /mnt wget http://jeff.doozan.com/debian/uboot/uboot-original-mtd0.kwb cd / umount /mnt -- Jeffby Jeff - uBoot
@gorgone, that error is nothing to worry about. @seiatwork You're not doing anything wrong. If you look at the log, it's not finding an ext2 partition on your USB drive. So that fails, and it starts booting Pogoplug. Loading file "/boot/uImage" from usb device 0:1 (usbda1) Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - usb 0:1 ** Have you iby Jeff - uBoot
Original files were here: http://download.pogoplug.com/prod/ and are mirrored here: http://plugapps.com/os/pogoplug/ce_mirror/by Jeff - Debian
You're still running the old uBoot. From uBoot: run bootcmd_original That'll get you into Pogoplug. From there, run the mtd0 uBoot installer, and you should be fine. -- Jeffby Jeff - uBoot
Nothing is wrong. That's when the kernel starts booting. The kernel isn't configured for netconsole.by Jeff - Debian
Yes, the new uBoot support reading from UBIFS partitions.by Jeff - Debian
You should connect a serial cable or configure netconsole to watch the boot process. When you can see what it's doing, it much easier to figure out what's going wrong.by Jeff - uBoot
Flip, that's exactly what you should see if you do not have a USB drive attached. It will always try loading USB first, and if that fails (the error message), then it will boot into Pogoplug.by Jeff - uBoot
Just re-run the uBoot installer, it will reset the environment.by Jeff - uBoot
fw_setenv usb_init 'usb start'by Jeff - uBoot
You're correct, the errors you're seeing are coming from a corrupted blparam environment. That's one of the errors that the new uBoot fixes so you should be fine now. The installer is very careful and would have given you a big scary warning if it couldn't install properly. -- Jeffby Jeff - uBoot
You need to install uBoot on the second Dockstar. And watch out for Debian's udev stuff. On the second Dockstar, your network card will be eth1 instead of eth0 until you edit /etc/udev/rules.d/70-persistent-net.rules -- Jeffby Jeff - uBoot
In my very informal testing, if it's connected to the Internet, the Dockstar waits about 90 minutes before auto-updating and disabling the SSH. I think most people can connect to SSH and kill the update within that window. If you want to be really safe, disconnecting your router from the Internet is your best bet. Just make sure you re-connect the Internet connection after running 'by Jeff - Debian
That will work, yes. In fact, if you're fast enough, you can even skip the Activation step. After you connect it to the network, find its IP address and connect with ssh. After you've connected, run killall hbwd and then continue with the Debian installer. If you can't ssh into it, you'll have to activate it and then re-enable SSH from the Pogoplug website. -- Jeffby Jeff - Debian
If you want to have multiple storage devices connected, you still need to use the USB Scanner script. -- Jeffby Jeff - uBoot
Thanks for reporting the mv error, I've updated the uBoot installer to fix that. However, that has nothing to do with your problem. That output is exactly what netconsole should show when your system boots properly. After the "Starting Kernel" message, control is passed to the kernel, which does not send anything to netconsole. I think your system is running. You should cheby Jeff - Debian
Are you running just a normal install of Debian from my scripts, or have you made changes or installed other packages? From your dmesg log, your system is actually booting just fine as far as the kernel is concerned. Something in userspace is causing it to reboot. You didn't use any of these ugly "echo reboot >> /etc/rcS" hacks or anything, did you ? You should check tby Jeff - Debian
There's only one type of Dockstar, so you're fine. The Pogoplugs are completely different devices and very easy to tell apart (one is bright Pink, the other is not). -- Jeffby Jeff - uBoot
That dmesg looks like it was from a successful boot. I'd try deleting it and then booting again to see if it gets re-created. If it does get re-created, it shows that your system is actually booting. If it doesn't get re-created, you may need to look into building a serial cable to look for the actual error. -- Jeffby Jeff - Debian
Is there a long pause between: Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... and U-Boot 2010.03-01266-g42f7128-dirty (Aug 23 2010 - 23:14:54) Marvell-Dockstar/Pogoplug by Jeff Doozan Hit any key to stop autoboot: 0 ? That's where the kernel would start booting and, unfortunately, you can't see it's messages over netconsole. Youby Jeff - Debian
I've updated the mtd0 uBoot again with some fixes for some USB devices. If you're having any troubles getting things too boot, this upgrade is the first place to start. To upgrade (from the instructions for installing mtd0 uBoot): cd /tmp wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh chmod +x install_uboot_mtd0.sh ./install_uboot_mtd0.sh -- Jeffby Jeff - uBoot
Run the mtd0 uBoot installer again. It's been updated to a newer version with better USB support. If the new version doesn't work for you, then netconsole is the next step. -- Jeffby Jeff - Debian
Oops, I misunderstood. I guess I should have read your original post more closely. It sounds like your Plug has 'upgraded' itself and disabled dropbear. Since you can get into Debian, you're completely fine. Just mount mtdblock2 someplace like /tmp/pogo and then edit /tmp/pogo/etc/init.d/db At the bottom of that file, there should be a line that looks like this: #/usr/sbiby Jeff - Debian