LeggoMyEggo, You're in good shape with u-boot. Just need to get latest rootfs (Updated 02 Nov 2014) from this thread: http://forum.doozan.com/read.php?2,16044 Put it on a USB thumb drive following the instruction and boot with it.by bodhi - Debian
Also see this recall notice: http://www.cpsc.gov/en/Recalls/2011/Cloud-Engines-Recalls-Pogoplug-Video-File-Sharing-Device-Due-to-Fire-Hazard/ http://www.engadget.com/2011/06/17/cloud-engines-recalls-potentially-flammable-pogoplug-video/by bodhi - Debian
LeggoMyEggo, Basically, if you can access the box through JTAG, then you can recover by flashing the latest OXNAS u-boot: http://forum.doozan.com/read.php?3,16017 To make sure we can give appropriate suggestion, please capture your console log and post here. This is to see it is compatible.by bodhi - Debian
nekitip, > I'm sure this is not the right place for this > post, but I need to tell the world what I've done, > and what they should not! You are right that this post should be a new thread. Perhaps tittle it: Debian Jessie and systemd problem ?by bodhi - Debian
drdevil44 Wrote: ------------------------------------------------------- > WarheadsSE - that'd be great thanks. I presume > the GPIOs are memory mapped but I don't have the > datasheet. > > Bodhi, thanks, I've uploaded the boot log here: > > http://pastebin.com/7bfcDcaX Looks like the serial boot log did not give any clue as why the watchdog stillby bodhi - uBoot
John Tetreault, Not all eSata enclosures are supported by the kernel. If you have the right cable, like this one, you could try to plug the HDD in directly using SATA cable, and get power from USB to see if it was the enclosure problem. Which enclosure are you using?by bodhi - Debian
drdevil44 Wrote: ------------------------------------------------------- > Thanks for your help. I noticed today that the > HDD leds dont come on either with the debian > kernel so I wonder if this might be a config > problem. I've pasted by bootvars below, where > bootcmd_debian is for the debian kernel and > bootcmd_linux is for the arch kernel. I've > aby bodhi - uBoot
max2014 Wrote: ------------------------------------------------------- > Ok, now I understand and have now all tools. > > Have some bad blocks: > > dmesg | grep -i 'bad' > > [ 11.863780] Scanning device for bad blocks > [ 11.882630] Bad eraseblock 196 at > 0x000001880000 > [ 11.966838] Bad eraseblock 1258 at > 0x000009d40000 > &gby bodhi - Rescue System
Adam, > has Jeff abandoned the main debian script he made > at http://projects.doozan.com/debian/ ? (it would > be nice to know officially that it doesnt actually > work anymore) Jeff has stopped maintaining the script. The u-boot part still works fine, but it installs the 2011.x u-boot. The Debian part is not up-to-date anymore so it is problematic. > > is there nby bodhi - Debian
See this: http://forum.doozan.com/read.php?3,12381by bodhi - Rescue System
max, Did you follow the instruction in the rootfs thread: Especially section 4: Quotecd /media/sdb1/boot cp -a zImage-3.17.0-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-goflexnet.dtb >> zImage.fdt mv uImage uImage.orig mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.17.0-kirkwood-tld-1 -d /media/sdb1/boot/zImage.fdt /media/sdb1/boot/uImage synby bodhi - Rescue System
Gareth, > So it looks like it's getting past that point but > failing to disable it for some reason - are we > certain that this kernel has the watchdog disable > in it? Yes it does. Do you have serial console log when it failed to boot? I think it's time to move your booting problem to this thread: http://forum.doozan.com/read.php?2,14351.by bodhi - uBoot
Fox, Not enough information in your post to give specific suggestion. However, let's try: > I have trouble with my GoFlex Home. > It work with U-Boot and Arch Linux, then the HDD > is broken. I install new one, but get the blibking > green led. - Do you know which u-boot version you are running? if not, which procedure were used to install Arch LInux? - Did you keepby bodhi - uBoot
monkmandolins, I don't use VAMP so can't give you specific advice. Perhaps some VAMP-specific forums would have this info.by bodhi - uBoot
balbes150, Thanks! Looks like I've missed this during the patch creation (it was created after the dtbs were compiled). One more line should be added: arch/arm/boot/dts/Makefile + kirkwood-nsa320.dtb \ + kirkwood-nsa325.dtb \by bodhi - Debian
Gareth, Yes. I should have said "Debian kernel" :) Arch is smaller with no initrd. That's made some difference in how soon the watchdog can be killed. And it is done during kernel init.by bodhi - uBoot
Gareth, Whatever works for you is good! The reason I'd suggested USB because if you can't boot 3.16-tld-2 on HDD then chance is that you will still have the same problem no matter which kernel you can try. The Arch patch is basically the same as my patch. In fact, that's where my NSA325 section of the patch came from (WarheadsSE is the developer for all things non-FDT NSA325)by bodhi - uBoot
Actually, I would like Gareth to try 3.16-tld-2 or earlier if booting stock u-boot, and 3.17-tld-1 if booting new u-boot. It would help others to know what to do when they have watchdog problem. It's great that 3.18 works, however it will benefit only a few :)by bodhi - uBoot
JohnW, Again, I did not need to do anything extra. System time just works out of the box. I am not sure why it was necessary for you to remove ntpdate, either. Anybody else has similar experience with the latest rootfs? if so, please post your observation.. If your ntpd is not running, start it, and it wiil be automatically run during reboot.by bodhi - Debian
JohnW Wrote: ------------------------------------------------------- > Just a note... The ntp-daemon doesn't autostart > with Debian on the 3.16 and 3.17 rootfs. > > You can start in manually. Tried some stuff > recommended by others on different forums to make > it work but didn't succeed. > > I have had to reinstall it to make it work with > &quoby bodhi - Debian
Arch Linux ARM: http://archlinuxarm.org/platforms/armv7/amlogic/odroid-c1by bodhi - Debian
@monkmandolins, usb_load_uimage=ext2load usb 0x800000 /uImage usb_load_uinitrd=ext2load usb 0x1100000 /uInitrd should be usb_load_uimage=ext2load usb $device 0x800000 /uImage usb_load_uinitrd=ext2load usb $device 0x1100000 /uInitrd If the above ddid not work, then make sure your rootfs (where /uImage and /uInitrd are) resides on partition 1. See this post for explanation about bootby bodhi - uBoot
Gareth, - Try booting kernel 3.16 with USB thumb drive only. - UART booting the NSA325 is quirky. You need to press power button, wait for it to turn off, then on again, and then execute kwboot within 1 second. All else fails, you can post the entire serial console log here.by bodhi - uBoot
megov, > #console=ttyS0,115200n8 earlyprintk root=/dev/ram0 > panic=3 :::DB88FXX81:eth0:none mtdparts=*here is a > long string* > > As I saw in documentation, "earlyprintk" may be > extended with mode detailed uart specifications. > I've tried both short and long form of it. Also I > change number of ttyS* in "console" and uart* in >by bodhi - uBoot
@Gareth, If you are running with stock u-boot then use Kernel 3.16.0-kirkwood-tld-2 (Updated 02 Sept 2014) in my kernel thread. Newer kernel in the thread will need newer u-boot.by bodhi - uBoot
@Don, I'll take a look at this in about a couple of weeks when I get home.by bodhi - Debian
@ shivahoj, If you could, downgrade to Kernel 3.16.0-kirkwood-tld-3 or earlier and let me know if everything is OK with it.by bodhi - Debian
:)) cool HW hack with the clothes pin.by bodhi - Debian
Don, > #grep -i f2fs /boot/config-3.17.*-tld-1 > CONFIG_F2FS_FS=y > CONFIG_F2FS_STAT_FS=y > CONFIG_F2FS_FS_XATTR=y > CONFIG_F2FS_FS_POSIX_ACL=y > CONFIG_F2FS_FS_SECURITY=y > CONFIG_F2FS_CHECK_FS=y > > Does that mean that f2fs is already in the kernel, > and no further action necessary to support it (ie > no need to rebuild uInitrd) ? Yes, it meby bodhi - Debian
@Don, grep -i f2fs /boot/config-3.17.*-tld-1 And btw, you could take out the rootfstype from bootargs. Make it a little easier to switch back to Ext3.by bodhi - Debian