The easiest thing to do is to create a rootfs on USB thumb drive, get it from here: http://forum.doozan.com/read.php?2,12096 Boot with this, and then while in Debian you can figure out why the Rescue system did not boot. If you're trying to install a new Debian system, then you can continue using this rootfs, too, as a a starting point.by bodhi - Rescue System
U-Boot 2013.10 image was uploaded. Please see 1st post for download link and instruction.by bodhi - uBoot
Try this ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.01-tld-1.netgear_ms2110.mtd0.kwb -pby bodhi - Debian
HighTower, Sorry you're out of luck here! I don't know if there is any kwboot that was built for Intel boxes. You could try to search for that. It's important because this is the recovery path when and if anything goes wrong. I don't know if the Stora can be recovered using JTAG (since I don't own one).by bodhi - Debian
HighTower, See this thread for new u-boot: http://forum.doozan.com/read.php?3,12381 This thread for latest kernel and rootfs: http://forum.doozan.com/read.php?2,12096 And this was the Stora u-boot working thread: http://forum.doozan.com/read.php?3,14931 If you decide to install u-boot, make sure that you can boot with UART first. Your boot ROM version is 00000121, so it shoud be abby bodhi - Debian
velo, The MAC address printed on the sticker is the right one, always. You'll need to set it in your network interfaces config file (in Debian it is in /etc/network/interfaces). Or set it in your u-boot env: fw_setenv ethaddr xx:xx:xx:xx:x If one was assigned and it's not the same as one on the sticker, then it was assigned by the kernel, or u-boot temporarily.by bodhi - uBoot
I've also posted this problem at Arch site to get more feedback. ---------------------------------------------------------------- Netconsole problem in kernel 3.12.13 oxnas. Did anybody set up netconsole in Arch successfully? I'm seeing this problem running Debian and I thought it is probaly in Arch, too. Apparently, the carrier detect happened so fast that it was deemed untrustwby bodhi - Debian
Thanks ingmar! hmm, wondering why my patch was not successful. I'll try again.by bodhi - Debian
velo, 1. After you've connected the serial cable hardware, you can use putty on Windows, Terminal on Mac, or picocom, screen,... on Linux (there are many other programs on Linux). See varkey's instruction on his website (it's for the GoFlex Net, but the communication settings are the same for all Kirkwood plugs, and the Pogo V4 is one): http://varkey.in/seagate-goflex-net-seriby bodhi - uBoot
Here is post that has Pogo V3 Classic DTB attached (it's untested). It might work with the Pogo Pro kernel. http://forum.doozan.com/read.php?3,15912,16053#msg-16053 And I've updated 1st post to add more info.by bodhi - Debian
@Ingmar, No, I haven't. I did try to bring it to 3.14, but patching has some strange problem and I have not looked further. I thought the openwrt is a straight patch from kref sources. Perhaps you know there is more patch on top ?by bodhi - Debian
thebladerunner, The kernel/rootfs that I uploaded in this thread is the latest out there. Thanks to kref works. The summary for the current status re Pogo V3: - new U-Boot is available (but I have not uploaded it yet). See here. - new Debian kernel and wheezy rootfs are available. - installation must be done manually (no script) You are running the B01, which does not have PCI, I assuby bodhi - Debian
Rootfs Debian-3.12.13-oxnas-tld-5 was uploaded. Please see 1st post for download link.by bodhi - Debian
Arnaud, You should check your USB rootfs for errors with fsck. Also list your files with so that it sorted by time stamp, ls -l is a little hard to read (while I am trying to read French :). ls -lartby bodhi - Debian
helpless, The symptom indicates that you're probably running an old U-Boot (perhaps 2009)? Old U-Boot does not work with kernel 3.2.xx and later. If that's true, you should restore your usb stick to the previous back up before the upgrade, and then install the latest kernel here: http://forum.doozan.com/read.php?2,12096 Make sure you have a back up stick, too. Since your kernel iby bodhi - Debian
Kernel linux-3.12.13-oxnas-tld-5 package was uploaded. Please see 1st post for download link.by bodhi - Debian
DavideDG, I've included all LM sensors in the kernel as modules. You might check to see if the specific LM sensors for NSA325 V2 are loaded. CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM70=m CONFIG_SENSORS_LM73=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_by bodhi - Debian
Older rootfs and kernel releases ============================================================== Updated 10 Feb 2019: Kernel linux-4.4.174-oxnas-tld-1 package was uploaded. New/Update features: - Pick up upstream security patches. Warning: we are seeing a reboot problem with this kernel version. The reboot is causing a shutdown. So use the previous kernel, if you need this rebooby bodhi - Debian
@Val532, So did you test the U-Boot for Lacie D2Net_V2 that I've uploaded? http://forum.doozan.com/read.php?3,12381,15828#msg-15828by bodhi - uBoot
FYI, It is possible now to have a boot menu in U-Boot, but it only works in serial console (as a terminal). Boot menu does not work with netconsole.by bodhi - uBoot
Tilator, Thanks for the typo catch! I'm going to release another kernel Pogo Pro V3 version. Since kref's kernel config is for Arch, I've been discovering more and more settings that I need to add for Debian to work properly.by bodhi - uBoot
DavideDG, Others have not reported seeing the error with sensor in their NSA325. I think it is best to post in this thread: http://forum.doozan.com/read.php?2,14351by bodhi - Debian
DavideDG, It does not ring a bell! it is strange that your initramfs would look for the kernel in NAND. I think that's where the stock kernel resides? if it looks for mtdblock6 then it would not be that weird. [ 14.004579] 0x000000000000-0x000000100000 : "uboot" [ 14.009710] 0x000000100000-0x000000180000 : "uboot_env" [ 14.015215] 0x000000180000-0x0000002000by bodhi - Debian
@WarheadsSE, Whenever you're ready, I'd like to pull in the NSA3xx.by bodhi - uBoot
tilator, Quote> BTW: I took a look at your kernel. My device does > not have PCI and it will not boot with PCI enabled > kernel. If you can compile it without PCI support > I can give it a try. You could try to boot with this attached dtb. I think it should work with the Pogo V3 Classic, even booting the full Pogo Pro kernel, since it does not have pci controller in it.by bodhi - uBoot
tilator, Quote> It seems to me like the whole trouble comes from > the device tree. I suppose SATA_OXNAS_MAX_PORTS = > 1 setting in kernel sata_oxnas.c file is hard > coded solely because port count has not come > properly from device tree and someone has decided > to hard code it there. > > Am I right? > I suppose SATA_OXNAS_MAX_PORTS setting should comeby bodhi - uBoot
Try this kernel I've just uploaded: http://forum.doozan.com/read.php?2,16044 The /proc/device-tree does polulate correctly.by bodhi - uBoot
I've created a new thread for this kernel: http://forum.doozan.com/read.php?2,16044by bodhi - uBoot
Linux Kernel 5.15.xx Oxnas package and rootfs for Pogoplug Pro V3 (with PCI) and Classic V3 (no PCI). Also the Medion Life P89626, Akitio Mycloud mini, and the possibly other OXNAS boxes such as Silverstone DC01, Iconbit I-STOR IS608 (under development). If you install this kernel on other OX820 boxes, please post your finding so it can be added to the supported list. Latest released kernel:by bodhi - Debian
tilator, I will upload the kernel and create a new thread for kernel and rootfs in Debian section (later today).by bodhi - uBoot