garyang, Your uBoot env for rootfs type is: usb_rootfstype=ext2 So try to extract the rootfs again to an EXT2 formatted USB drive. And try booting with that.by bodhi - Debian
shv, I did not remove the linux-2.6.x kernel packages. I don't think it matters. And flash-kernel problem is really a don't care, because we are not using any of the /boot files anyway. Before the apt-get update, apt-get upgrade, I just put a hold on udev with: echo "udev hold" | dpkg --set-selections And the upgrade just went without problem. And you're riby bodhi - uBoot
dhead666 Wrote: ------------------------------------------------------- > Jeez Bodhi, how did I miss that ? > I kept the wires soldered to the serial port, so > it was only a matter of unscrewing the box and > connecting to usb-ttl, like 30 seconds of labor. > I did get the "xmodem: Bad message" and had to run > kwboot over and over for 10 min' until it staby bodhi - Debian
laprjns Wrote: ------------------------------------------------------- > bodhi Wrote: > -> :) now for some reason, the kernel is not > booting. > Are we sure that the kernel is not booting? > Maybe it's not getting an IP. I suggest that they > try deleting any persistent net rule in > /etc/udev/rules.d/ Yeah, it could be the problem. Hard to tell whatby bodhi - uBoot
restamp, It works fine in cron.daily with the full path for --exclude. Thanks for your help :)by bodhi - Debian
The instruction on 1st post: To install, you must have NAND tools and fw_env tools installed first. See here: http://forum.doozan.com/read.php?2,11663,11713#msg-11713 If you running from Pogoplug OS, install fw_envs tools as described above, and then make sure the /etc/fw_env.config looks like below: cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector siby bodhi - Debian
@shv, I did. But my Arch kernel on NAND is older, I beleive. I recalled WarheadsSE has done at least one update. Mine is running on Debian wheezy rootfs. But the kernel is still ALARM 2.6.31.6_SMP_820.by bodhi - uBoot
restamp, I think so too. I'm changing the --exclude to use the full path, and will see how it goes. Thanks,by bodhi - Debian
Davy's Dropbox link: https://www.dropbox.com/sh/nwt2kbvetvgvroo/sm-hZ0B4jU/Kirkwood/uboot/Pogoplug4Seriesby bodhi - Debian
Josef, Your arcNumber is 2998, meaning it is for the Dockstar, not GoFlexNet. When you boot your old 2.6.39, it set your box as a Dockstar, which is OK. The new uBoot is GoFlex Net version, so your arcNumber needs to be set to 3089 to be correct. But don't change arcNumber yet because you have to boot with a kernel that supports it after you've done that. Using my rootfs, it will worby bodhi - uBoot
Josef, Since you don't have serial console, netconsole is a must before attempting to change any thing in uBoot. Even that, serial console is strongly recommended :) Do you keep a log of what's going on during the installation? To get it boot back to Debian to troubleshoot, use this 3.8.11 rootfs in this thread: http://forum.doozan.com/read.php?2,12096 See this section: Updby bodhi - uBoot
mgiammarco Wrote: ------------------------------------------------------- > David, have you solved the problem? > Can anyone help? > It is incredible that I have bricked a GOFLEX > without doing anything. > Why is the green light always on after boot? What > does it mean? > > Thanks, > Mario Mario, The green light means that uBoot has successfully booteby bodhi - uBoot
Oakley470, Pardon me if I state the obvious below! I just want to cover all the details. > U-Boot 2011.12 (Feb 20 2012 - 21:21:59) > Pogoplug E02 > > SoC: Kirkwood 88F6281_A0 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 MiB > In: serial > Out: serial > Err: serial > Net: egiga0 > 88E1116 Initialized on egiga0 >by bodhi - uBoot
Restamp, Indeed, I did not have any quote surrounding the exclude patterns! your explanation makes sense. I'd bet that is the answer. However, I always thought the rsync exclude patterns, if specified without a full path, they are relative to the source. In this case it is /*, and the manual seems to indicate that: ANCHORING INCLUDE/EXCLUDE PATTERNS As mentioned earlierby bodhi - Debian
gaogao Wrote: ------------------------------------------------------- > can it be used on NSA320? No, this version is for GoFlex Net only. It could be used for GoFlex Home, though. The reason: each uBoot image is built using the board file for that hardware. So when you run Jeff's install script, it actually selects the right version for you.by bodhi - uBoot
@Oakley470, NP. Your uBoot env for rootfstype is currently set to ext2. Take the rootfs USB stick to a Linux box and convert it to ext2 using tune2fs. Boot with it. If not successful, go back to serial console and please get the output of > printenv and post it here. It's a really good sign that it got to the point where it is right now. Might need to tweak some uBoot envs to gby bodhi - uBoot
Thanks restamp! I use relative path for --exclude (I did try full path, too). I have not had time to try to figure this one out. Perhaps you can spot something rsync --version rsync version 3.0.9 protocol version 30 #!/bin/sh echo `date` "Started rsync daily backup" >> /tmp/rsync.backup.daily.log Host=`hostname` if [ $Host = "tldDebian" ]; thenby bodhi - Debian
Oakley470 Wrote: ------------------------------------------------------- > Your method did not work, i get the exact same > process as originally stated above when booting > with the ext3 drive in. I downloaded your rootfs, > extracted and placed all 3 files in the root of > the empty drive and nothing was different in the > boot process. Oakley470, In each alternatby bodhi - uBoot
First, you should get it booted back to either Arch or Debian. From there you can restore it easily. Take either: - Arch rootfs at Arch site or - my rootfs: http://forum.doozan.com/read.php?2,12096 (Updated 19 June 2013) or - Davy's rootfs: http://forum.doozan.com/read.php?2,7806 Put it on an empty USB thumb, and try booting with it.by bodhi - uBoot
restamp, I've scheduled 2 rsync dry-run cron jobs to run consecutively today and got the result. The root cron job ran correctly, excluding all the directories. The cron.daily did not, it showed the same behavior before, did not exclude any directory! So I guess Syong has the right idea above, could be something about permission. Could it be something change in security policy that we areby bodhi - Debian
@pbg4, > p.p.s. a quick look in the config of the > 3.8.11-kirkwood-tld-3 kernel revealed that > marvell phy is not!! included in the kernel,.. > > @bodhi: was this intention to use the generic > mii_phy and not the mii_marvell_phy??,... > I'll have to test that and recompile the > marvell_phy as a module and see if things with > the stock uboot get imby bodhi - Debian
servercat Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > @servercat, > > > > Whenever that happen, don't reboot, stay in the > > rescue system and run the install script again. > > There was nothing that could be done at that point > since eveby bodhi - Debian
@servercat, Whenever that happen, don't reboot, stay in the rescue system and run the install script again. But it seems too late now, because you have rebooted? if yes, serial console is the only way if you can't get in the rescue system again.by bodhi - Debian
@restamp, Thanks for the valuable info! I put the new entry in the root cron and the dry-run works :) ... but only after I rebooted both the source and destination boxes. The inital root cron attempt showed the same behavior (not excluding directorries). That caused me to think a little bit about what I did during testing. I did abort a cron daily dry-run when I saw a massive number of filesby bodhi - Debian
kuleszdl, The reason was that how WarheadsSE original set it up, in order to make it work he has to get some NDA info from the manufacturer, so I'm not sure if moving the kernel to USB would be feasible with the current uBoot (I did not try). It could be booted directly from the internal SATA port, since it is always picked up first, and there is instruction for that at Arch site.by bodhi - uBoot
kuleszdl, I was hoping somebody would be able to build and flash Debian to NAND the same way WarheadsSE did for Arch. That would give us an upgrade path. But it seems it was not that easy. If pazos still visits this forum, I am sure he can tell us much more about this.by bodhi - uBoot
Hi, Anybody running rsync in a cron job to backup rootfs? Once in a while I run rsync in a script to backup my debian development plug rootfs to another plug. It always works fine, excluding typical directories that we should exclude such as /proc, /dev,... Now I'm starting to get organize :) and want to execute it inside a cron.daily. And I found out from dry-run that it does not excludby bodhi - Debian
kuleszdl, It does make some differences using wheezy rootfs this way. Something like udev can't be upgraded without new kernel 3.x.x, but userland packages will be upgraded OK. I did the apt-get update and apt-get upgrade using wheezy apt source, and quite a few were upgraded (including xfce) so it worked well for me.by bodhi - uBoot
kuleszdl Wrote: ------------------------------------------------------- > Hi folks, > > I've set up a complete guide on how to create a > Debian Squeeze rootfs from scratch via > debootstrap, merging information from this thread > and various other tutorials and completing it > with a few missing bits. It's available on > Howtoforge: > > http:by bodhi - uBoot