dharry Wrote: ------------------------------------------------------- > Hi, > > My old debian installation for my Goflex Home is > dieing because of to many bad blocks on the USB > stick. > > So I tried to Install a fresh image to a new USB > stick like described in section "Updated 31 Oct > 2014:" > > > But the system don't bootby bodhi - Debian
codier, These rescue envs were missing some variables. In serial console, reset the 3 envs below and then boot. Once you are in Debian, you can set them permanently with fw_setenv, setenv 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' setenv rescue_bootcmdby bodhi - uBoot
@LeggoMyEggo, Read the rest of the thread from the post I've posted above.by bodhi - Debian
codier, It is now much easier with serial console. You can create the 3.16 or 3.17 rootfs per instruction: http://forum.doozan.com/read.php?2,12096 Pls boot with the new rootfs and let us know once you're in Debian (post serial console log here if problem). Meanwhile I will take a look at your u-boot envs for rescue settings.by bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > I have 3.17 running on a PP E02 and the RAM shows > up as 128MB but information from the Arch Linux > site and others says the E02 is supposed to have > 256MB of RAM. Is this a limitation in the kernel > or is 'free -h' giving incorrect info? It means you are not running it as Pogo E02by bodhi - Debian
monkmandolins, Thanks, good to see LXDE. I'm using xfce, which is pretty lightweight, but it is not performing well running a web browser.by bodhi - Debian
codier, Should try these in order: 1. Try netconsole, if you can connect with netconsole, it is easy to fix. 2. Recreate the 3.17 or 3.16 USB rootfs from scratch, by try booting with it, observe LED light to see the booting progress, if any. 3. Try davygravy's rescue tarball (since you have rescue installed). If all 3 above failed, then 4. Connect serial console.by bodhi - uBoot
Codier, Power up, and interrupt neconsole, get the listing of u-booot envs and post here: printenvby bodhi - uBoot
It is. Separate power source is needed. 2 choices: 1. eSata enclosure or 2. a cable directly connect to the port but the HDD draws power source from outside. EDITED: wrong link for the cable (I can't seem to find the correct one on my bookmarks)by bodhi - uBoot
wtip Wrote: ------------------------------------------------------- > I've been wanting to setup my dockstar as a backup > NAS using BTRFS and it's snapshots feature. > I just went through the process of installing the > linux-3.17.0-kirkwood-tld-1-bodhi kernel and setup > the system, only to discover that the 3.17.0 > kernel corrupts the BTRFS snapshots. >by bodhi - Debian
tucansam Wrote: ------------------------------------------------------- > Thank you for your reply. > > Prior to seeing your reply, I had used the USB > stick method to try to re-flash with the latest > Seagate software (power on holding down reset, > wait for white LED). Now when I turn the device > on, the green LED blinks quickly, forever. > Nothing else hby bodhi - uBoot
Mangix Wrote: ------------------------------------------------------- > I bought a sata extension cable. It works in my > computer but not on the pogoplug. What type of Sata cable? It would be best to post link to the picture or spec. > It really sounds > like the boot loader is not initializing it. I'd doubt that would be the case. I think it is most likely power iby bodhi - uBoot
@megal0maniac, Cool! my pleasure to be able to contribute to Linux device hacking community.by bodhi - Debian
Mangix, QuoteBut as I said it does not even power on. Also, it's a 3.5 inch drive. How do you connect it to the Pogo V4? using an enclosure? or a direct cable? if it's an 3.5" HDD, it needs its own power source.by bodhi - uBoot
See this Arch installation page for information about how to get into the box with SSH through the device product key: http://archlinuxarm.org/platforms/armv5/seagate-goflex-home If the above does not work, you can also SSH in and try these: user: root password: ceadmin or passowrd: stxadminby bodhi - uBoot
Mangix Wrote: ------------------------------------------------------- > Hello, > > I'm currently using the latest version of U-Boot > for my Pogoplug v4 and am having a hard time > figuring out why my SATA drive will not spin up. > It is connected to the SATA port on the > pogoplug(not USB). > > I found that bootcmd_ide starts off with "ide > rby bodhi - uBoot
@codier Looks like you did replace the envs with new default envs so you need to restore them on top of what you have: These are rescue system related envs installed by Jeff's script. Use fw_setenv to set each of these at comand line. rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmdby bodhi - uBoot
Adam, The below bold lines are my correction. First, because you are inside a live Pogo E02, and with 2 more sync commands to make sure: cd /boot cp -a zImage-3.17.0-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-pogo_e02.dtb >> zImage.fdt # I added the following line to deal with the uImage.orig file that i created the first time i ran this script in december mv uImage.orig uImagby bodhi - Debian
Adam Wrote: ------------------------------------------------------- > i looked back at my install notes, and it is > definitely because i didnt change > "kirkwood-goflexnet.dtb" to > "kirkwood-pogo_e02.dtb" > > > ok so now i know that i improperly installed two > pogo e02 units, but they are both about 1000 miles > away right now. what elby bodhi - Debian
Adam, > status:green:health status:orange:fault > These are correct for Pogo E02 > in the other three, /sys/class/leds/ contains: > status:green:health status:white:left0 > status:white:left2 status:white:right0 > status:white:right2 > status:orange:fault status:white:left1 > status:white:left3 status:white:right1 > status:white:right3 >by bodhi - Debian
codier, You need to tell us which Linux system you can boot into, or if you can't boot at all. For example, stock Pogo OS, Debian, Arch, rescue system .... They are slightly different when it comes to how to make fw_printenv and fw_setenv available... I am not sure I undertand what your current system is, and what you are trying to get to.by bodhi - uBoot
codier Wrote: ------------------------------------------------------- > Hi Bodhi, > > I already made your latest one which is 31 Oct > 2014 version of 3.17 > I will start from there and if I can boot in then > I will my env. It's pain in the xxx as I really > have hard time to use putty to check each env > line. > is there any easy way to read the env?by bodhi - uBoot
Can you remote login to those boxes? if you can then it's easy to look at possible syntax errors in rc.local (most of the the time it is that simple).by bodhi - Debian
Waynosan, See this thread to see what needs to be done. Note that the instruction to backup NAND from Pogo POS is slightly different than from inside Debian or Arch. But it should give you some idea about the technical details (this instruction can not be used as is in your case). And, you don't need to connect serial console to the virgin E02 to do it. However, I'd say that you sby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > A small correction: kernel 3.17 for Oxnas was > not > > come from Jeff. It's my kernel build which is a > > derivative of kref's kernel build! > > > Hehe I thought your name was Jeffby bodhi - Debian
hachigo, > Is it necessary to flash the default u-boot env > when you update the U-Boot? All it seems to do for > my Pogoplug v2 is brick it. No, it is not necessary. And the flashing instruction in the 1st post advised you not to do it if your current u-boot is from Jeff's script, or your u-boot env is already at 0xC0000 . Only flash it if you are installing from stock.by bodhi - uBoot
Waynosan, I've noticed you said: QuoteI have at my disposal, a box with Linux Mint (I'm a linux noob though), Win 7 x64, and another E02 Pogoplug, which I do not want to modify in any way, but perhaps it may be helpful for troubleshooting. You could restore your modded Pogo E02 to factory using the other virgin Pogo E02 mtd0. Let me know once you decide one way or the other. Wouby bodhi - uBoot
@Buck, Looks like my hunch about kermel version is probably correct. It is an old bug, but don't know it has been fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437466 In any case, good luck and let us know.by bodhi - Debian
A small correction: kernel 3.17 for Oxnas was not come from Jeff. It's my kernel build which is a derivative of kref's kernel build!by bodhi - Debian