I'm sorry, I misread your original post. It sounds like your Dockstar may be getting hung up while attempting to boot from your nand installation. If that's the case, you can force it to boot the rescue system by creating an empty file named 'rescueme' on the root of your ext2 formatted USB drive. Make sure that drive is the only thing connected to the Dockstar and then rby Jeff - Debian
Thanks for the report Johanes. It should work now.by Jeff - Rescue System
Thanks for reporting that. Some of the environment variables changed with the newer uBoot and I forgot to updated this installer with the changes. It's fixed now. To use the 'rescueme' option, make sure you only have one USB device connected, make sure that the first partition on that device is formatted as ext2, and then create an empty file in the root directory called 'by Jeff - Debian
Yes, you can still use netconsole. With netconsole, you tell the Dockstar what IP address to use, instead of letting it get one from your router. -- Jeffby Jeff - Debian
Configure netconsole and watch the boot log. It should show you where things are going wrong. If you're still having trouble, post your netconsole log. -- Jeffby Jeff - Debian
I have a SanDisk Cruzer Micro 4GB and another one that looks exactly alike but does not have the 'Micro' label. Both work perfectly. The one with out the 'Micro' label seems to be a bit faster. I have a Kingston DataTraveler 4GB that does not cold-boot. It's also painfully slow. -- Jeffby Jeff - Debian
This looks like your problem: # scanning bus for devices... 4 USB Device(s) found # scanning bus for storage devices... error in inquiry # 1 Storage Device(s) found The bootloader is only detecting one device and apparently erroring on the second device. It's then telling the kernel to boot from the first device, which it assumes will be sda. However, once the kernel starts, itby Jeff - uBoot
Many people have successfully booted from a hard drive. If you're having problems, you should configure netconsole and watch the boot log. -- Jeffby Jeff - Debian
If you haven't changed any uBoot environment variables since installing it, don't worry about posting your config. Instead, get netconsole running so you can see the output of uBoot. It will usually tell you exactly what is happening. Most likely your hard drive isn't spinning up fast enough to be detected. -- Jeffby Jeff - uBoot
@gorgone: I forgot to update the rescue installer after I made changes to the uBoot installer. It should be working now. Thanks! -- Jeffby Jeff - Rescue System
Yes, that will work fine. -- Jeffby Jeff - Debian
I ran the squeeze installer several times yesterday without any problems. You can always try a different mirror -- Jeffby Jeff - Debian
@dinlaca: The sources and compilation instructions are available on the uBoot page and a few additional resources, including default environment settings are available on the GitHub repo. This is pretty much just "out of the box uBoot" so ECC and TFTP behave exactly as they do on other uBoot devices. If you're interested in modifying their behavior, I'm always happy to coby Jeff - uBoot
I've updated uBoot to use the stable 2010.09 release and I've updated the installer support for both the GoFlex Net and the Pink Pogoplug. Many thanks to Peter Carmichael for providing the GoFlex Net support. The latest uBoot also supports a new 'arcNumber' environment variable. This variable will let you set the machine ID that gets passed to the kernel. The machine IDby Jeff - uBoot
@gorgone: The installer git repo is at http://github.com/doozan/DebianInstaller If you're interested in maintaining your installer, you should probably fork that project. After you do that, I'll be very happy to merge some of your changes back into the main script. -- Jeffby Jeff - Debian
This is a great idea! I'd be happy to give you space on this site to host this. Send me an email and I'll get you an account. -- Jeffby Jeff - Rescue System
You have two choices. You can adjust the drive scanner to check partition 5 instead of partition 1. Or, you can disable the drive scanner and tell uBoot to always boot from sda5. To adjust the scanner, run the following commands: setenv usb_scan_1 'usb=0:5 dev=sda5' setenv usb_scan_2 'usb=1:5 dev=sdb5' setenv usb_scan_3 'usb=2:5 dev=sdc5' setenv usb_scanby Jeff - uBoot
It looks like your device shipped with a bad image on mtd1. You can follow this guide to reflash the partition. Note to everyone else: Don't follow the above guide unless you're in an identical situation. It is not a good method of 'resetting' a device that you screwed up yourself and we see too many people on this forum (and others) who think it's a good fix-all. Iby Jeff - uBoot
I'll be happy to consider any patches to the script that you'd like to submit.by Jeff - Debian
The Dockstar uBoot doesn't have support for IDE or SATA (because the Dockstar has neither). Wait until you have a serial cable and then follow Peaslaker's directions for building a uBoot with SATA support.by Jeff - Debian
Save yourself the headache and get a serial cable. The GoFlex Home is uncharted territory, and I'd urge you to be a little more careful with what you do to it: not everything that works on the Dockstar is going to work for you on the GoFlex and you don't want to end up bricking your device.by Jeff - Debian
Peaslaker has done a lot of work with GoFlex Net. I would start by looking at his stuff here.by Jeff - Debian
To answer your question more directly: it would have worked the same way whether or not you had disabled the Pogoplug services. The Pogoplug OS is simply a small, custom linux distro. Inside this distro is a program that provides the Pogoplug services. This program creates a VPN between you and Cloud Engines that is used for sharing files and applying updates to the Pogoplug OS. One of theby Jeff - Debian
I looked at this with someone else a few months ago. As I recall it ships with a uBoot with USB support and its rootfs is running a much more modern kernel than the Dockstar, making it perfect for either booting a distro from USB or simply creating a chroot environment. The device has a 'support' page at http://<DEVICE_IP_ADDRESS>/support.html The ssh login is root/sohoadmiby Jeff - Debian
Alll of your "errors" are perfectly safe. The errors that look like this: Warning: Bad CRC, using default environment ## Error: "ethaddr" not defined Are caused when the script tries to read some existing variables from the environment. Since a new Dockstar has no environment, it will generate these errors. The ECC failed: 6 error is just part of the output of nanddby Jeff - Debian
Rather than reflash the old Pogoplug environment, it may be even easier to just install the Rescue System. -- Jeffby Jeff - Debian
Your bootlog looks fine. The UBIFS error is just uBoot checking to see if you have a bootable system installed on mtd3. And the bootlog should stop with "Starting kernel ..." because that's the point when the kernel takes over and stops sending debug messages. You should check your router logs to see if Debian is getting a different IP address. -- Jeffby Jeff - Debian
It's just checking for a bootable system on mtd3. You don't have one, so it fails. Don't worry about it.by Jeff - Debian
I mistyped my first command. Run this from the Rescue System and try again: fw_setenv usb_init ''by Jeff - Debian
The log you posted doesn't look like it matches the configuration you posted with it. Please capture and post a fresh bootlog, starting with the Dockstar's power unplugged.by Jeff - Debian