Unfortunately, I am not using btrfs on any of my NAS. Perhaps others might chime in.by bodhi - Debian
> I setup a btrbk remote backup that transfers btrfs > subvolumes. Source is a amd64 machine targetting a > NSA325v2 with latest kirkwood kernel and bookworm > tarball. > > It fails with the error message "ERROR: ... > invalid tlv in cmd tlv_type = 816" on the target > machine. > Any advice how to continue? > If you have not done this. The fiby bodhi - Debian
raffe, > It boots with a USB and continue with the rest on > HD. But it never booted up. Wife want me out for > dinner, so I did not have much time to check why. > Then I read > https://forum.doozan.com/read.php?2,32146 "Updated > 16 Dec 2023: Rootfs > Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 has > been uploaded. ". Is this something I need to do?by bodhi - Debian
Daniel, The rootfs is basic rootfs with only a few necessary packages installed. It is a debootstrap rootfs, and the following packages installed on top: Quotehttps://forum.doozan.com/read.php?2,12096 - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-by bodhi - Debian
This is quite serious for Internet facing servers. SSH was compromized by a backdoor in xz-utils (specifically xz versions 5.6.0 and 5.6.1) https://lwn.net/Articles/967180/ QuoteAndres Freund has posted a detailed investigation into a backdoor that was shipped with versions 5.6.0 and 5.6.1 of the xz compression utility. It appears that the malicious code may be aimed at allowing SSH authentby bodhi - Debian
> Hi guy's is it possible to replace the 128mb nand > chip on the nsa320 with and 256 oder 512mb nand or > even bigger > to place the full uboot + rootfs and omv os > something in it > so it doesn't need to be bootet from usb ? Debian rootfs is too large to store on NAND. Especially if you run OMV, rootfs should be on HDD/SSD.by bodhi - Off-Topic
See the Wiki topics QuoteKey daemon (button control) Multimedia keyboard daemon for Linux How to use set up button to reboot or shutdown with Key Daemon (esekeyd) Shutdown with Power button with regret option by esekeydby bodhi - uBoot
@Tedious_1, > Is 15 to 20 MB/s is standard for these devices? > What are you guys seeing? Have you looked at these 2 threads in the Wiki thread? QuoteIncrease NFSD max_block_size Reduce NFSD threads The 1st post about NFS max_block_size. And how to set it. In the 2nd post davidalfa got about 60MBs read on his Dockstar (the 2nd version), which is basically the same as this Gby bodhi - Debian
frankenstein3, > architecture frm the Pogo. First I spent a long > time configuring a recent build 6.7.5 (or was it > 6.5.7 or 7.6.5????). The Pogo did boot, but > stopped with a kernel panic. If you created the rootfs correctly then it will boot without problem. Use Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and follow the instruction closely. Don't substitute anyby bodhi - Debian
pczerepaniak & Trond, I've tried WOL on my Mirabox and it did not work either. Note that in /etc/init.d/halt the NETDOWN is not clear. So the halt action would shutdown the network. halt -d -f $netdown $poweroff $hddown So I explicitly modified this initscript to do halt -d -f $poweroff $hddown Even with the above change, WOL does nothing. Translate all of the aboveby bodhi - Debian
> some more testing revielt that it only work´s if > i tipe it 6-10 times in a row only then it´l > connect sort of right an the speed´s are somewhat > ok´ish > The symptom indicates the auto-negotiation has failed to recognize the speed is Gbs. And that could be a few reasons. 1. The cable is faulty, or only work intermittenly. Try changing to a CAT 5e/6 cable. 2.by bodhi - uBoot
> what can i do now ? As I mentioned, if the RTC does not work try apt-get install fake-hwclock > The comments > > ip link set eth0 down && ip link set eth0 up > If this command works, add it to the end of /etc/rc.local (before exit 0).by bodhi - uBoot
OTOH, your system is strange. [ 10.742011] rtc-mv f1010300.rtc: registered as rtc0 [ 10.747725] rtc-mv f1010300.rtc: setting system clock to 2024-03-18T23:07:08 UTC (1710803228) That rtc-mv should not be even showing up. The rtc0 should be rtc-pcf8563 as typical in Zyxel NSA32x boxes: [ 5.300838] rtc-pcf8563 0-0051: registered as rtc0 [ 5.307683] rtc-pcf8563 0-0051: settinby bodhi - uBoot
> all with an new cr2032 :-) Does not matter much with this shown in boot log. Perhaps that battery has expired? [ 10.742011] rtc-mv f1010300.rtc: registered as rtc0 [ 10.747725] rtc-mv f1010300.rtc: setting system clock to 2024-03-18T23:07:08 UTC (1710803228) [ 10.757340] i2c /dev entries driver [ 10.762322] i2c i2c-0: Not using recovery: no suitable method provided [ 10by bodhi - uBoot
OK, so post dmesg to see what was the system clock when you boot up. It should be set to whatever is in the RTC. dmesg And connect serial console to see if it has any problem running during boot.by bodhi - uBoot
Most of Kirkwood boards use standard JTAG header. Unbricking examples (in the Wiki thread). Pogo E02: https://forum.doozan.com/read.php?3,21789 Dockstar: https://forum.doozan.com/read.php?2,127079,127629#msg-127629 The above have the same SoC as this Netspace 2.by bodhi - uBoot
@sudos, > because of the encryption algorithms in > place for most file transfer protocols, samba and > NFS included. None of them are supported by the > kirkwood's hardware encryption acceleration > onboard so far as I understand, and even at that, > nothing makes use of that to my knowledge these > days either. As far as the Kirkwood kernel is concerned, maby bodhi - Debian
Look for JTAG at J12. https://wikidevi.wi-cat.ru/LaCie_Network_Space_2by bodhi - uBoot
Have you set your timezone? ls -l /etc/localtimeby bodhi - uBoot
Thaks for testing! NSA310> pci BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 00.00.00 0x11ab 0x6281 Bridge device 0x04 01.00.00 0x10ec 0x8168 Network controller 0x00 That's what I want to see. > Some random thoughts and questions: > 1) Is the "pci_hosby bodhi - Debian
Hi Peter, Here is the new build. uboot.2023.04-tld-1.nsa310.kwb_mar_17_2024.tar sha256: edd862674a87020f3cbf7ae781414d48fcb98220c3dc0c84e5e5e3051d7da4fe uboot.2023.04-tld-1.nsa310.kwb_mar_17_2024.tar 136506f4484c93092c6e823cb60c55f4399321bf62aac21b35533db5ffd69c32 uboot.2023.04-tld-1.nsa310.kwb Run kwboot with it, interrupt the u-boot countdown, and dm tree pci dm treeby bodhi - Debian
> now is it possible to let the copy led only blink > for the SSD on the 4th usb port ? > so that the usb led only blink´s for usb 1-3 ? No it's not possible.by bodhi - uBoot
onewithforce, Congrats !by bodhi - Debian
Hi Peter, Stay tune for another version.by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > Quoteis it possible to assign the copy led to an > specific drive/usb port and disable the usb led > for an specifig usb port ? > > Not possible in userspace. Hold on. Let's try to see if it works. List the current LEDs to see the exact spelling for each of the LED triggers: ls -l /sys/class/by bodhi - uBoot
onewithforce, Your u-boot envs were already populated with some much older version. So kwboot the latest u-boot 2023.04-tld-1 will not boot into Debian due to envs mismatched. Try kwboot using uboot.2017.07-tld-1.nsa325.mtd0.kwb. This version would boot into Debian with your current envs. kwboot is meant to be tested so that you know there is a rescue path. But not to boot all the way iby bodhi - Debian
Quoteis it possible that some of the problem´s are from an not working RTC or problem´s with the DNS ? Not RTC or DNS. Quoteis it possible to assign the copy led to an specific drive/usb port and disable the usb led for an specifig usb port ? Not possible in userspace.by bodhi - uBoot
"The shared folder for the 6TB-A is visible on my CentOS when doing the mount, but it shows empty." Most likely it's permission.by bodhi - Debian
optim, > I tried going direct from Jessie to the newest > Bookworm release on a GoFlex Home, that boots off > the hard drive. That's too big a jump. Debian does not support skipping release. And you're skipping 2 releases! > Whats my best option for fixing this? I prefer to > remove the HD and repair it on another computer > (not sure if that possible).by bodhi - Debian