Thank you, for your hints. TL;DR : vendor has obviously changed one or some component(s) of the USB flashdisk brand/model I used for years, which caused the initially reported obscure behaviour Using the udevadm command I could recognize that the devices I bought at different occasions have amongst others different model IDs. This is explains the different behaviour despite of using seemiby jfp - Debian
Thank you for responding quickly. As recommended I tried it with "zswap.enabled" as well as with additionallly "zswap.compressor" removed. Same behaviour, same dmesg messages :-( Further maybe helpful hints are welcome. With best regards, Joeby jfp - Debian
PS.: root@XX-1:/tmp# uname -a Linux xx-1 5.7.1-kirkwood-tld-1 #1.0 PREEMPT Sun Jun 7 20:57:38 PDT 2020 armv5tel GNU/Linux root@xx-1:/tmp# cat /proc/cmdline console=ttyS0,115200 rw rootwait loglevel=8 ipv6.disable=1 zswap.enabled=1 zswap.compressor=lz4 rootfstype=ext4 root=/dev/mapper/vg0-root root@xx-1:/tmp# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdaby jfp - Debian
Hello Bodhi, I'm using a few Samsung GoFlexNet for years using the jessie based rootfs. Devices are booting by loading uImage, uInitrd and the DTB-file from an usb flashdisk [ U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:17:19 -0700) ] and switches to HDD (LVM on LUKS). At the beginning of this year I decided to switch the GoFlexNet to the buster based rootfs. The previous (jessie-bby jfp - Debian
Volker, because you were able to "kwboot" into a current uBoot I would suggest you to boot debian from a prepared rootfs usb flashdisk as described here. Put the working uboot image you used successfully with kwboot onto the flashdisk too. Finally go ahead with the instruction provided by bodhi here. For the NSA325v2 at least the environment needs to be flashed according B.by jfp - uBoot
bodhi, >CONFIG_SECCOMP is the last item in "Kernel Features" section. It should be there when you make menuconfig. Thx a lot, that helped. While I'm now was able to get compilation native as well as using ct-ng I am still struggling with the package generation. Can you provide some hints regarding packaging a (cross- and/or native-)compiled kernel and it's headeby jfp - Debian
Hello bodhi, 1rst off all thanks a lot for your efforts and contributions. A few days before I started playing around with firejail. When got it compiled and installed (on zyxel 325v2) I recognized that seccomp is not activated. Assuming it could be only one option I decided to cross-compile a kernel (4.2.0-kirkwood-tld-1) with the use of your config and patch utilizing crosstool-ng runnby jfp - Debian
Hello, two days ago I read the question for informations about utilizing encryption on the nas. I am running Debian on a NSA325v2 on LVM on LUKS on raid(mdadm). So this question reminded me to my own efforts when I tried to encrypt the whole nas. Therefore I started to draft a short list of instructions with the intention of publishing it here. Now it seems I misestimated the scope ofby jfp - uBoot
@tomas, hoping that I catched the task correctly I'll step in. I'm running LVM on LUKS on RAID based on bodhis prepwork provided bye his root filesystem mentioned above. After booting from the flash disk you need to install the missing subsystems and their utilities (i.e. mdadm, lvm2 , maybe also cryptsetup). Next you will prepare the disks ( eventually partitioning, create a mirby jfp - Debian
@bodhi, I booted another NSA325v2 using flashdisk and HDD's from the setup shown above. Despite of the fact that the ethernet interface name has been changed due to the different MAC address everything went fine. Meanwhile it seems that the serial console at my first device passed away which indicates that I most probably run into that trouble due to a HW problem. Thanks a lot!by jfp - Debian
@bodhi, here my bootlog from dmesg: root@zn325-1:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.18.5-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Thu Feb 5 17:58by jfp - Debian
@bodhi, after removing systemd by apt-get install sysvinit-core sysvinit sysvinit-utils apt-get remove --purge --auto-remove systemd echo -e 'Package: systemd\nPin: origin ""\nPin-Priority: -1' > /etc/apt/preferences.d/systemd syslogd is putting still similar messages into the log. ... ... Mar 12 13:35:58 zn325-1 vmunix: [ 26.736289] EXT4-fs (dm-3): mounby jfp - Debian
Hello, maybe I overlooked an solution but I wasn't successful to find any hint. I installed wheezy on a NSA325-v2 (lvm on LUKS on RAID-1) using Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 md5: fae6cfbec8c58da0066af1041cf89f2a The box has been flashed with uboot.2013.10-tld-1.nsa325.bodhi.tar md5: ae163289cb6a5db6bb897c0b96d5264a Finally I replaced the kernel withby jfp - Debian
Hello, after checking UART loading I flashed this u-boot on to my NSA325v2 using the steps described above. It worked as promised/expected ;-). Great work, thank you, bodhi! This enabled me to boot my (fully LUKS-encrypted) installation directly from a 3TB genuine GPT-partitioned drive. To be honest I had to find out that I have to remove parenthesis from variables (found it later on deby jfp - uBoot