Hello, thanks for your hints Bodhi. I was aware of the solution via /root/set_persistent_mac_address or /etc/network/interfaces, but that means that the random MAC always reports first unfortunately, and then the HW Mac is set. I didn't realize until today that there is no separate U-Boot for NAS326, only the "stock U-Boot". I think I will use macchanger for my existing systeby ptosch - Debian
Hi Guys. After updating my NAS326 to kernel 5.13 I have a few questions. 1. The MAC address is still not fixed. In U-boot the variable ethaddr is set (from the sticker under the NAS326), but the kernel log still says "Using random mac address". I have already written the variable in the kernel command line out of desperation, but it is always ignored: [ 0.000000] Kernel cby ptosch - Debian
I found the matter : "It's a new feature which optimizes block allocations for very large file systems. The work being done by ext4lazyinit is to read the block allocation bitmaps so we can cache the buddy bitmaps and how fragmented (or not) various block groups are, which is used to optimize the block allocator." "To revert old behavior, the filby ptosch - Debian
Hello, thanks, these settings resolved my boot problems, I can boot with the new kernel. Now there is a very strange thing going on: as soon as I mount my big 2.7TB partition, ext4lazyinit starts and is using sda1 very heavy for about 90 seconds This is output of iotop: 2945 be/4 root 1102.72 K/s 0.00 B/s 0.00 % 95.78 % The partiton in question is fscked and no errors occurby ptosch - Debian
Hello, I followed the instructions to update to kernel 5.13.8 but booting ends in kernel panic: VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 It looks like bootargs are not handled over to the kernel: Kernel command line: console=ttyS0,115200 Bute bootargs are set to console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=armada-nand:2m(u-boby ptosch - Debian
I did not check nfs because I think the test with ftp is sufficient to prove that the problem lies within samba. As a workaround i set socket options in smb.conf to SO_RCVBUF=32768 and SO_SNDBUF=32768 . Now transfer is reliable, unfortunately speed dropped from 100MB/sec to 70MB/sec. I am going to play with the buffersizes to get higher reliable transfers. Strange that nobody else has theby ptosch - Debian
Hi Bodhi, after several test it seems to have something to do with cifs and files around 4096000000 bytes size. When connecting with ftp (I installed ftpd server on nas326) I can transfer files without reproducing this problem. Only when copying over a cifs share (cifs server on nas326) this problem occurs (copy direction is nas326->client). Getting files with "smbclient -U ....&quoby ptosch - Debian
Hello, unfortunately ethernet does not work occasionally. It usually happens when large files are transferred. The nas326 box does not respond to any network activities. On the box itself everything seems to be fine, IP is still bound to the eth port, but no network response. If I do /etc/init.d/network restart, then something crashes: [84945.616863] IPv6: ADDRCONF(NETDEV_CHANGE): eth0:by ptosch - Debian
Hi Bodhi, with Your help I am now on Debian stretch, MAC address is stable and several disk IO tools report a silent system. Only iotop has still the same output as described in my first post, but the USB LED flickering stopped. Thank You! Cheers, Peterby ptosch - Debian
Hi Bodhi, ok, I try to update to 9.1 first... I hope with this upgrade the MAC randomization stops too ;) Greetings, Peterby ptosch - Debian
Hi Bodhi, but there is definitely something accessing my USB drive as I can see the USB LED flickering every two seconds. Cheers, Peterby ptosch - Debian
Hello, I am using my NAS326 with a USB flash stick to boot from with Kernel linux-4.12.4-mvebu-tld-1 and Debian-4.9.0-mvebu-tld-12-rootfs-bodhi.tar.bz2 As always when using flash memory I look if something is writing frequently to this disk. And I found this: root@nas326:/boot# iotop -obtqqq 15:40:03 7 be/4 root 0.00 B/s 0.00 B/s 0.00 % 99.99 % 15:40:05 7 be/4by ptosch - Debian
Its not about the error message. The command "scsi init" hangs. The last message is "scanning bus for devices..." but the command does not release the command prompt, it looks like the command crashed. I tried a second 3TB harddrive but it is the same.by ptosch - Debian
Cool, I found my thread ;) I connected the serial console since setting "LABEL=rootfs" in fstab did not help. I found there were some variables not set, after setting them directly in uboot, i could boot from my small 160GB test harddisk. But there is a problem initializing my big 3TB harddrive, in uboot I cannot initialize it: Net: | port | Interface | PHY addressby ptosch - Debian
Hello again ;) unfortunately I could not manage to boot from internal Harddisk on my brand new NAS326. After a while it boots to stock firmware. This is how partitions and fstab look like: /mnt # parted /dev/sda print Model: ATA TOSHIBA DT01ACA3 (scsi) Disk /dev/sda: 3001GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Sizeby ptosch - Debian
Hey Bodhi, I even read something about esekeyd when flying though the threads, but still decided to use the more complicated way... Half-asperger-mind ;) Once again thank You, installing and configuring took 5 minutes, everything works now as expected! Cheers, Peterby ptosch - Debian
Hi all, i have some problems catching the copy button press event. Buttzy10169 wrote on December 08, 2013 this comment: QuoteButtzy10169 And the following python script lets you do something with the copy button: from evdev import InputDevice from select import select from subprocess import call dev = InputDevice('/dev/input/event0') while True: r,w,x = seby ptosch - Debian
Hi Bodhi, I solved this by setting machid=831. Seems like this kernel ignores arcnumber and uses machid. This is how it looks now: host 192.168.10.254 is alive Using egiga0 device host 192.168.10.254 is alive Using egiga0 device host 192.168.10.254 is alive Using egiga0 device host 192.168.10.254 is alive Uncompressing Linux......................................................by ptosch - uBoot
OK, its not arcNumber, just tested with the old value. Anyway, how should it, before ENV flash old value was 2097 too, and it didn't boot.by ptosch - uBoot
Hi Bodhi, ah, this is how it was meant; at least it was pretty exciting setting the env: does it boot after this? ;) Back to topic: yes, my rescue was fully working before the new Uboot . I attached the dockstar to serial console (although it is broken, only garbage is displayed, but some times You can see some words), and after the 34th reset I got an unscrambled output!: host 192.by ptosch - uBoot
This seems to be quite konfusing. Now I set the following: fw_setenv rescue_installed 1 fw_setenv rescue_set_bootargs 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params' fw_setenv rescue_bootcmd 'if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x80000by ptosch - uBoot
Just tried: DockStar> nand read.e 0x800000 0x100000 0x400000 nand read.e 0x800000 0x100000 0x400000 NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK DockStar> bootm 0x800000 bootm 0x800000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.32.18-dockstar Created: 2010-09-16 20:04:19 UTC Image Type: ARM Linuxby ptosch - uBoot
Oh dear, how could I be so blind, I forgot to set the last variable "preboot". Thanks for the hint, netconsole is working again. So after the ENV flash (and after setting variable preboot) now I tried first time to boot from rescue (means pure dockstar without any USB devices connected). Unfortunately now it doesn't even load a kernel. Here is the output: U-Boot 2015.10by ptosch - uBoot
Panic! I flashed the ENVs with uboot.2014.07-tld-3.environment.img, and now I have no netconsole output. Server, where nc is started: 192.168.10.254, dockstars IP: 192.168.10.100 After resetting the dockstar I can seen no ping returning, when the dockstar is in Uboot. After a while it boots into the attached USBStick, and is pingable. Before the ENV flash, I could start the dockstar, it pingby ptosch - uBoot
Well, booting from my USBstick is working. So at least I can boot from USB. But when the stick is not used (just using plain dockstar), I expect the dockstar to boot into the rescue system. The rescue system even starts loading image "Linux-2.6.32.18-dockstar" (like mentioned before), but it does not boot to the end, so I could log in. Before updating the Uboot, booting from reby ptosch - uBoot
Hi Bodhi, after updating to new Uboot 2015.10 (which worked very well btw.), I updated my USB-Stick to Devuan Jessie with Kernel 4.6, which seems to run pretty smooth. The only problem is: the rescue system doesn't boot through, so I could not login to it. In netconsole I can see the kernel beeing loaded: NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OKby ptosch - uBoot
Okey, the problem seems to be the command "ide reset" which takes a very long time to initialize the HDD. Right now the system boots off USB stick and continues booting rootfs from HDD. But I know: if the system is cold-started and there is reason to fsck a disk, then watchdog will be activated and the boot loop begins until I fsck manually. So the only solution is a UBoot whicby ptosch - Debian
Up to no avail ! The corrupted FS - guess where it does come from: the watchdog resets the nsa35 just right after the sda2 has been mounted! Anyway: I set bootdelay to 1 . I fsck'ed sda2. I cold rebooted, watchdog strikes again ! At which line in the kernellog.txt can we see that the watchdog is beeing disabled ? Is it this line ?: [ 18.189428] nsa3xx-hwmon nsa3xx-hwmon:by ptosch - Debian
Bodhi, thanks for the Kernel 3.16.0-kirkwood-tld-1 package, now booting and hwclock works fine. But there is still another nasty problem: the watchdog is constantly resetting my nsa325 after I switched from USB boot to Sata internal HD boot. This happened on kernel 3.15, and on kernel 3.16 it is unfortunately the same. I cannot believe it ! I am not going to buy a bunch of 3TB disks toby ptosch - Debian
I attached the output from the printenv command from the console. I was experimenting on the console with direct command (without variables). mw.l f1010100 0020c000; ide reset; ext2load ide 0:1 0x800000 /uImage; ext2load ide 0:1 0x01100000 /uInitrd ; bootm 0x800000 0x1100000; mw.l f1010100 0020c000; ide reset; ext2load ide 0:1 0x800000 /uImage; ext2load ide 0:1 0x01100000 /uInitrd ; bootby ptosch - Debian