thanks bodhi that worked. I was able to set the size with the commands from debian. I moved the /etc/initramfs-tools/conf.d/custom.conf to /home to back it up. then for completness here are the commands i ran to get the uInitrd back to the larger size: update-initramfs -u mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.13.6-kirkwood-tld-1 -d initrd.by Pickle - Debian
ive been using the /etc/initramfs-tools/conf.d/custom.conf fix proposed from my thread, which was mentioned above. is there anyway to make the change nickg proposed directly on the system or does this require a recompile of the dtb files from the kernel source tree?by Pickle - Debian
I tried added the file "/etc/initramfs-tools/conf.d/custom.conf" to my system and I still get: root@NSA320:~# cd /boot root@NSA320:/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.6.5-kirkwood-tld-1 -d initrd.img-5.6.5-kirkwood-tld-1 uInitrd Image Name: initramfs-5.6.5-kirkwood-tld-1 Created: Wed Jun 10 09:31:40 2020 Image Type:by Pickle - Debian
im debating if I should just stick with 5.5.1 for now since I dont really care to reinstall omv and setup anything else from scratch again. There nothing in the kernel that i know that i would need to have. Thanks for help so far as alwaysby Pickle - Debian
Here are the sizes: -rw-r--r-- 1 root root 13182617 Apr 28 11:12 initrd.img-5.5.1-kirkwood-tld-1 -rw-r--r-- 1 root root 12944762 Apr 28 22:02 initrd.img-5.6.5-kirkwood-tld-1 just looking in boot though did you intend for this typo? config-5.6.5-kikrwood-tld-1 zImage-5.6.5-kikrwood-tld-1 would this effect the install process?by Pickle - Debian
bodhi, ran the esfsck and no problem i purged all kernels but 5.5.1 did the reinstall and ended up with the same CRC error Edit: So just copying the old 5.5.1 uInitrd gets the 5.6.5 kernel to boot. I tried running the mkimage again and back to the error. Here are the commands after the kernel cleanup: root@NSA320:/boot# tar -xvf linux-5.6.5-kirkwood-tld-1-bodhi.tar.bz2 linux-by Pickle - Debian
i have ext3 for the usb driver so i wont have that problem then. sorry but i dont understand what you want me to try. I am already back to running with the old kernel and the old initrd. if i run through the kernel upgrade process I end up with the bad uInitrd and wrong CRC.by Pickle - Debian
thought it was ext4, but my fstab shows it is ext3. I dont have a problem getting the system running again. I have a complete copy of /boot before the upgrade, so i went back to that /boot and like i mentioned before the system boots again and runs like normal. running the dpkg command then mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.6.5-kirkwooby Pickle - Debian
Ive tried to update to the latest kernel. and the initram fails. I fsck my disk, i restored my boot backup and tried a second time with the same result. My previous kernel is the 5.5.1 U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: seby Pickle - Debian
thanks for the feedback! so im booting off a usb and i dont really care to add the swap there. and ive already used the full drive for my shares. my conclusion is just add a swap file to one of my shares. root@NSA320:/sharedfolders/share1# cd /export/share1/ root@NSA320:/export/share1# fallocate -l 2G swapfile root@NSA320:/export/share1# chmod 600 swapfile root@NSA320:/export/share1by Pickle - Debian
checked my dmesg and so far it looks like just adding the vm.min_free_kbytes = 65536 has resolved the issue (no kernel panics). I did not create a swap file.by Pickle - Debian
Did a copy from this device to another on my network and ive got quite a few of these repeating: Seems a lot about memory do i need a swap file? [68299.714581] kswapd0: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null) [68299.724020] CPU: 0 PID: 112 Comm: kswapd0 Not tainted 5.5.1-kirkwood-tld-1 #1.0 [68299.732087] Hardware name: Marvell Kirkwood (Flattened Deviceby Pickle - Debian
Thanks for the assurance and I did the backup first. Everything seems to function fine. But i took a look at some of the logs and these messages stood out. So i dont know if something from my old config files isnt compatible now. Anyone opinion are these worth bothering with? dmesg: [ 26.302177] random: 7 urandom warning(s) missed due to ratelimiting [ 27.935214] systemd[1]: File /lby Pickle - Debian
Just updated to the latest kernel with no problems. I dont want to reimage my entire usb rootfs and setup from scratch. Is switching the repo url's to buster another safe to upgrade? Otherwise im just going to let it be.by Pickle - Debian
thanks that worked replacing 325 with 320.by Pickle - Debian
bodhi thanks for the work and effort you put into providing the binaries and instructions. It really is incredible. Im running OMV now and just about have everything setup. I need get my backups back onto the new hard drive to replace the one that went bad. I have more power with ssh and omv that i didnt have before. Only thing I dont think is the same is the LEDS on the front of the box. Bby Pickle - Debian
and i also upgraded to the latest kernel 4.18.4 and its working thinking about if i should update the debian to a newer dist. (edit. whoops looks like stretch is the latest) is there really much benefit to enabling systemd?by Pickle - Debian
Looks like im not quite there. Eth0 isnt being setup [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Cannot find device "eth0" Failed to get interface index: No such device If you think you have received thisby Pickle - Debian
just rebooted and was greeted by the uboot output: U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server Setting up my usb with the debian rootfs now. Update: Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terby Pickle - Debian
Turns out the cable was bad, ive hooked up a bypass and everything worked as expected. Im not sure if this an issue: / # cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # NAND example /dev/mtd1 0x0000 0x20000 0x20000 4 step 1 i think i saying this ok for nsa3XX, butby Pickle - Debian
Bodhi, seeing output is not the issue. im having issues transmitting to break the boot to get the uboot terminal.by Pickle - Debian
So ive got the TTL serial cable today and I can see the output but i cant get a key press to register to break the boot cycle. Pretty sure I have the right pins connected. Any suggestions for this? Im using this cable https://www.amazon.com/gp/product/B014GZTCC6/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 I connected the black gnd to the pin on the right going left theres a blank spaby Pickle - Debian
I had another video stop while playing looking at the dmesg log the nas reboot itself https://pastebin.com/t71SCex9 I have a TTL cable on the way so I can get the serial terminal, ill have to wait until then.by Pickle - Debian
i suspect maybe the first drive is starting to die. This pulled from dmesg over telnet on the nsa320 sd 0:0:0:0: Unhandled sense code sd 0:0:0:0: Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: Sense Key : 0x3 Descriptor sense data with sense descriptors (in hex): 72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 0a 9a cc 20 sd 0:0:0:0: ASC=0x0 ASCQ=0x0 end_by Pickle - Debian
bodhi Wrote: > > If you mount the drive on your laptop > How to mount a JBOD partition? When i looked at the drives in gparted it couldnt tell what it was. Edit: Telnet on the NSA320 worked and I pulled this from dmesg https://pastebin.com/EkfEJyGz there are no logs in /var/ogby Pickle - Debian
Yes that is basically the last line. In the dmesg output i actually disconnected and reconnected. Actually i think might have misunderstood your request. Did you want me to get the logs from NAS? These were logs from attaching the drives to my laptop. If you wanted to see logs from the NAS I think ill have to do it from a terminal connected to the NAS since the partition type (jbod) wasnt recby Pickle - Debian
I didnt have /var/log/messages but have the systemd journal messages. Is that what you are looking for? Seagate drive Aug 27 19:36:07 seashell kernel: scsi 4:0:0:0: Direct-Access ST3000DM 001-1CH166 0041 PQ: 0 ANSI: 0 Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0 Aug 27 19:36:07 seashell kernel: sd 4:0:0:0: 1565565872 512-byte logical blocks:by Pickle - Debian
Its still running Zyxel's default firmware 4.70 Thats probably a good thing to try. I will hook both of my drives through my usb sata adapter tonight and post any output.by Pickle - Debian
My NSA320 has been acting odd lately and before I give up and get new hardware Id like to update it to newer uboot/kernel. (issue is that drives seem to drop and the nsa iteself seems unresponsive. Light for hd1 turns orange, but reboot clears it. Disk checks and SMART info dont point out any issues. Nothing in logs. After reboot things work ok and then after a while the process has to be repeatby Pickle - Debian