Nice mod Rob! I've added your mod to the wiki thread: QuoteUnder/Over the hood Moddingby bodhi - Debian
schnee, > This SSD works with 4.0, but it does not work with > 4.1 and 4.4 kernels. > I tried other HDD HTS723216L9 > SA60 (160G) and an SSD Intel SSD 320 series 160 GB > and both works fine. Thanks for the correction! This is very good info. It's proved that the Intel SSDSC2BF180A4L has some quirks that only surface in later kernel 4.1+. Especially is that 4.0by bodhi - Debian
schnee, This time there are 2 problems: 1) the u-boot envs. 2) the SSD could not be initialized properly (which is the same as before). 1) The bootargs was not set properly usb_set_bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 Should be: usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10" 2) The SATA initialization migby bodhi - Debian
cdlenfert, Yes, it is possible to boot Debian without touching stock software in NAND (Open the box and connect a SATA HDD to the hidden port inside). Unfortunately, there is no one-page tutorial for this. However, you can take a look at this post from shv: http://forum.doozan.com/read.php?3,16017,17297#msg-17297 It is more like a summary of steps than tutorial. And the link in that pby bodhi - uBoot
Rob, Glad you got it working! In case someone looking, here is the post where gregg_a_g described how to set up wifi on Pogo Pro V3: http://forum.doozan.com/read.php?2,16044,21638#msg-21638by bodhi - Debian
Also, another thing. Did you use the new u-boot envs image? I noticed you are still using /dev/sda2 as the root device. If you have "flashed" (i.e. put it in the SSD) the new u-boot default envs, then you would have used root=LABEL=rootfs for the root device. And the sda2 partition should be labeled rootfs.by bodhi - Debian
schnee, > i installed today the new uboot on my sata drive w > ith partial success. The new uboot loads, but i st > ill use the old SPL from warehead. It is OK to run WarheadSE old SPL. U-boot is really more important to replace. > I will try to test with USB soon too. Before you do that, a couple things to make sure that were not the cause: 1. Your env is not right:by bodhi - Debian
Kuki, There are 2 installation threads here: Released kernel/rootfs: http://forum.doozan.com/read.php?2,12096 Released u-boot: http://forum.doozan.com/read.php?3,12381 It will not be possible to boot stock FW after installing new u-boot. At least not yet (I have not tried this, since it is low priority on my list). > Which kernel should I take (and from where) for > the NSA325by bodhi - Debian
GeekSmith, > I'm going to start fiddling with a couple PogoPlug > Mobiles next week and I see that the rescue system > s for Kirkwood involve replacing the stock OS. Is > there a reason for that? I'm sure it's fun to do, > and I get that. But is there any reason I couldn't > use a similar approach to the Oxnas/PogoV3? Yes, you could. The reason I dby bodhi - Rescue System
schnee, The log showed you have not installed the new u-boot. However, I'm not sure yet why your SSD works in older kernel but not the new one. I'll take a look to see if I can tell if the sata-oxnas driver in kernel 4.4.38 have changed something that could cause this. You could try to boot with a USB drive using a new rootfs with with kernel 3.17, and then with 4.4.38, to seby bodhi - Debian
Last post moved here: http://forum.doozan.com/read.php?2,32538by bodhi - Debian
Ornella, Cool! glad you got it working again.by bodhi - uBoot
shv, QuoteI uploaded the mtd1 image of Seagate Goflex Net: Link. The mtd2 image of Seagate Goflex Net can be downloaded from this Link. Thanks! QuoteI had to use the flash command without --noecc option to restore mtd2. nandwrite /dev/mtd2 mtd2 nanddump and naddump older and newer versions have different options. So if a specific nandwrite is older, then sometime the option is not avaby bodhi - uBoot
Rob, Look in the kernel and rootfs release thread: http://forum.doozan.com/read.php?2,16044by bodhi - Debian
Ornella, You are booting Arch u-boot: > U-Boot 2016.09.01-1 (Oct 10 2016 - 23:12:58 -0600) > Arch Linux ARM > Pogo E02 And Arch kernel: > [ 0.000000] Linux version 4.4.28-1-ARCH (buildu > ser@leming) (gcc version 6.2.120160830 (GCC) ) #1 > PREEMPT Sat Oct 29 00:27:49 MDT 2016 Did you try to get help at Arch Linux ARM forum? https://archlinuxarm.org/forumby bodhi - uBoot
Last post moved here;: http://forum.doozan.com/read.php?3,32522by bodhi - uBoot
Please see the release thread for the new rootfs and updated installation procedure.by bodhi - Debian
The new rootfs and kernel package have been uploaded. Please see 1st post for download link and installation procedure. QuoteZyxel NAS326 Installation Updated 05 Feb 2017 QuoteUpdated 04 Feb 2017: This Debian-4.9.0-mvebu-tld-12-rootfs-bodhi.tar.bz2 has been uploaded. QuoteUpdated 03 Feb 2017: Kernel linux-4.9.0-mvebu-tld-12 package has been uploaded.by bodhi - Debian
Rob, The kernel is new and you can run with Debian jessie. Upgrading kernel alone does not make it jessie, you would have to change the /etc/apr/source.list and then upgrade Debian packages too. Debian jessie source will upgrade your system packages to the later versions that work with kernel 4.4.38. Before you do this, you must backup your rootfs, because it will be a massive change. If any tby bodhi - Debian
I'm done building this kernel and rootfs. The known problem with SPI will need to be fixed in u-boot. The ethernet MAC address problem probably will be fixed in next kernel release (so we don't have to hard code it in /etc/network/interfaces). Will upload new rootfs and new instruction for NSA326 soon in the release thread.by bodhi - Debian
@NAZIM, Let me restate this problem, see if I describe it correctly. > i have same problem. i tried update my nsa325v2 an > d failed. HDD2 led constantly active. You let it boot normally (without kwboot), the NSA325 seems to be stuck at boot. Nothing happens, and the HDD2 LED is solid green. Did the box reset at every 30 seconds and back to the same behavior again? Have you tby bodhi - uBoot
schnee, > I have minimal knowledge about uboot. I simply use > a version from warheadSE, with some modifications > -> so it is not intentional. In that case, you should install the new u-boot 2015.10: http://forum.doozan.com/read.php?3,16017by bodhi - Debian
Joey, It is working fine for me. Have you tried again?by bodhi - Off-Topic
GeekSmith, > @bodhi -- If you have a unit open and accessible, > can you see if the the ground pin on the socket go > es all the way through the board? Sorry I don't have one off-line right now. Anyone?by bodhi - Off-Topic
Hi schnee, > Maybe the whole uboot enviroment needs an update. > I will have to dig into it, as i am not an expert. > Can you suggest some good documentation? Look at my u-boot release thread (it's u-boot 2015.10 now). The new default u-boot envs automate everything. But your own build for 2013 u-boot does not necessary have all the features as in 2015.10, so you can onlyby bodhi - Debian
schnee, I see. The problem is you did not set the bootargs env explicitly. You are relying on the internal bootargs. That's not a very good approach. Because you had to partition your disk the way this bootargs specifies where your rootfs is (i.e. /dev/sda2). If you define the bootargs in the envs, then the rootfs partition could be any where you want it to be. You can use the lable rootfby bodhi - Debian
Gravelrash, > the simplest way i do it - is not to use "solder" > at all. what i use is solder paste a > nd use the heat of the iron held close to the pad > to do the work for me. That might have been what my friend did. But I don't know for sure.by bodhi - Off-Topic
Den, > Cloning was done with a cloning dock (standalone, > without use of computer) This could be problematic. But I don't know how your dock work so can't say for sure. Usually, if you clone a HDD --> a HDD, then the sectors would be replicated. But from a USB to HDD, I am not sure if this dock does that. You can do the cloning in Linux, if you clone your USB rootfsby bodhi - Debian
Den, Check your rootfs cloning process. Were you root user? how did you clone it?by bodhi - Debian