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
Congrats! Evidently you're pretty well verse in Linux so solving this problem is not that difficult :) I'm merely suggesting clues, can't really take credit for real solution! but if you'd like, please direct any contribution to the site, i.e. it'd cost Jeff something to host this site for us, I'm sure.by bodhi - Debian
@fly & davidnewton, See this post: http://forum.doozan.com/read.php?2,12933,12936#msg-12936by bodhi - Debian
BuckNaked, Try these possible solutions in this order. If one did not work, try the next. 1. Take the USB Debian stick to another Linux box and change it to Ext3 if it was Ext2. Your uBoot env rootfstype is set to ext3. (assuming the stick is mounted as sdb1): tune2fs -O ^has_journal /dev/sdb1 then reboot with the USB stick. If it did not work try the next step. 2. ssh into rescue sby bodhi - Debian
BuckNaked, SSH into rescue system and print out fw_printenv And let's take a look at that. Also, it's best to setup netconsole right after you have a successful Debian installation (in fact, a successful uBoot installation would be enough to setup netconsole). http://forum.doozan.com/read.php?3,14by bodhi - Debian
mgiammarco Wrote: ------------------------------------------------------- > Here is my sequence: > > - installed NSA320 boot image on usb > - updated > - installed iscsi initiator for a test > - all ok for one week > - added 1tb 2.5 external hdd > - modified it to 3049 (not remember exact number) > to let it see the hdd I assumed you've rebooted afterby bodhi - uBoot
Gents, Did you guys try to upgrade your rootfs to wheezy when this happened? If you can recall the event or have a log, it would be easier to figure out what went wrong.by bodhi - uBoot
@tree, What instruction did you use to generate the initrd.img-3.9-1-kirkwood ? was it generated automatically by flash-kernel when you upgrade to jessie? If it was, try to install the kernel deb package again. But before doing that, remove flash-kernel. And then afer successfully install kernel 3.9-1-kirkwood, generate the uImage and uInitrd manually: mkimage -A arm -O linux -T kernel -by bodhi - Debian
@mgiammarco, Netconsole normally stops the output there (unless you have set up custome boot parameters, or load the module earlier in initrd). Did you try to ssh in? do you use static IP or dynamic IP?by bodhi - uBoot
servercat, Hmm... Since you are booting with the rescue system on USB, it would be sda1. The install script (squeeze or wheezy) will need to write over the sda1 drive, so it is not possible :) sorry I forgot about that. There is a way to force rescue system stick to be assigned sdb1 but it's not foolproof, it's trial and error. You could install uBoot only by running the script iby bodhi - Debian
@habibie, It is possible if Jeff can add this option to his installation script. But this change will effect a lot of sites out there that are using his script to install Kirkwood plugs. Their documentation will need to change to reflect this. I would imagine that the script must be changed in a way that people just say "yes" or press Enter to ignore the option of using different namby bodhi - uBoot
@servercat, Without seeing your current uBoot envs, it's hard to tell exactly what the problem is. However, I'm guessing: - Since you can only boot from the rescue roofts on a USB stick, it means the rescue is setup to load from the stick, not from NAND. - The problem with a lot bad blocks shown in dmesg, and then fw_printenv responds with "Too few good blocks within rangeby bodhi - Debian
If you are booting with a USB thumb drive, 1st thing to do is to mount that stick to a different Linux box and check for error with e2fsck. You did not say your boot drive was formatted ext2 or ext3, but if it was ext2 then when the power went down its file system must have been corrupted.by bodhi - Debian
dheerajjotwani Wrote: ------------------------------------------------------- > # fw_printenv > Warning: Bad CRC, using default environment > bootcmd=bootp; setenv bootargs root=/dev/nfs > nfsroot=${serverip}:${rootpath} > ip= > ${ipaddr}:${serverip}:${gatewayip}:${netmask}:${ho > stname}::off; bootm > bootdelay=5 > baudrate=115200 >by bodhi - Debian
Please see 1st post for an uploaded uBoot image for GoFlex Net.by bodhi - uBoot
Since you've installed Arch, your uBoot envs will probably need to be adjusted in order to boot Debian. Please login into Arch, and print your uBoot envs with fw_printenv and post the output here. Usually it is just a couple of simple changes.by bodhi - Debian
@pancho22, Good news! the new uBoot build I just created does work with >2TB HDD. This is when the HDD is attached as a second drive formatted as EXT3. http://forum.doozan.com/read.php?3,12381,12890#msg-12890 Running without netconsole works fine. With netconsole, a work around is needed as described in that post. I'll upload it for testing sometime today.by bodhi - uBoot
I've finally figured out these netconsle problems in the later uBoot versions and how work around them. Testing with u-boot.2013.07-rc1 1. netconsole input driver seems to regress. Second character in command got lost consistenly. This is due to a recursion logic in drivers/net/netconsole.c that processes characters from a buffer. I modified the recursion logic slightly and it seems toby bodhi - uBoot