Hi bodhi! It worked! By removing and reinstalling esekeyd after system upgrade, esekeyd now is correctly configured. I'm not using KEY_POWER or KEY_RESTART at the moment. This is my esekeyd.conf: KEY_133:/usr/bin/logger -s -i "COPY Button pushed" KEY_116:/sbin/shutdown -h now Now I have a small problem with minidlna. When I reboot the NAS it fails to start. It works ifby krono - Debian
Hi bodhi! It seems I've troubles with esekeyd... Setting up esekeyd (1.2.7-2) ... Restarting a multimedia keyboard daemon for Linux: esekeydinvoke-rc.d: initscript esekeyd, action "restart" failed. dpkg: error processing package esekeyd (--configure): installed esekeyd package post-installation script subprocess returned error exit status 1 Errors were encountered while prby krono - Debian
Hi guys! I have debian buster on my good NSA325v2. I've a lot of packages installed and configured for my purpose. Is it safe to run a full-upgrade on this machine? I know the better way would be installDoozan bullseye image from scratch, but I don't want to spend much time on installing and configuring all of the packages I need. Do you have suggestions? Thank you in advance. Kinby krono - Debian
Hi guys! @Dyce have you found out how to report degraded raid using red leds? Please share it. Thank you. Ivanby krono - Debian
Ok bodhi! Now the NAS is directly connected through an UPS. That should be the best work condition. I will take care of dmesg logs. Furthermore, I finally decided to get out the wires for serial console. Thanks a lot for help! Ivanby krono - Debian
Netconsole keep silcence resetting the preboot variable. Now serial console works like a charm and it seems the NAS boot up correctly. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.10.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Thu Jan 14 20:28:12 PST 2021 [ 0.000000] CPU: Feroceoby krono - Debian
Perfect! I will use a multimeter to observe the power output. How can smoothly disable netconsole? Thanks for help, yet! :) Ivanby krono - Debian
Ok, I generated a new rootfs. It seems to work, but we did not understand what was the problem. Now, serial console doesn't work anymore, only netconsole works. Could it be netconsole and serial console interfere with each other? How can I know what was the cause of the original issue? I have to know if I can solve definetly substituting the power supply or not. Thanks for help. Ivanby krono - Debian
Done! U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 No link on egiga0 ping failed; host 192.168.1.123 is not alive No link on egiga0 ping failed; host 192.16by krono - Debian
Ok! I used this post as reference for serial pins header, it works. Find below the log from serial console: U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 No lby krono - Debian
Ok, I installed Debian on my NSA325v2 after a stock firmware fault recovered using serial console. I decided to resort serial console again! Now I forgot the right pins on the board, can sombody help me? In order to correctly use serial console, do I need to disable netconsole? Thanks for help. Ivan P.S. Find attached the board picture, and a detail of pins I roughly remember related tby krono - Debian
Hi bodhi! I don’t know if those messages appeared again. Unfortunately I can’t get SSH access to the NAS, it doesn’t work. Do you think it could be interesting to re-create the usb rootfs and observe dmesg on runtime? If yes, should I use another usb stick? Thanks for help! Ivanby krono - Debian
The issue described here came back also with my new usb flash drive! Furthermore, now NAS is connected to an UPS to avoid voltage breaks or overshoots. Using netconsole I found out kernel correctly boots up, but the NAS doesn't answer to ping neither smb or ssh connection work. Accessing the usb flash by my linux laptop I can see last log. This is in /var/log/dmesg: [ 0.00000by krono - Debian
Good! Thanks a lot for help. Regards. Ivanby krono - Debian
Hi bodhi, I don't know why... Now it works! I didn't change configuration. To make it works on CentOS 8 only two steps are needed: 1) Open UDP port 6666 on the public zone # firewall-cmd --zone=public --add-port=6666/udp success 2) Run netcat as user $ nc -l -u -p 6666 Restarting my NAS I obtained the logs below. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)by krono - Debian
Hello, ok, I installed may new rootfs on a fresh USB stick. I found out that in my old USB stick there's not the /etc folder anymore? I definitely think it was an USB device problem (I hope so!). However, I configured environment variables for netconsole in u-boot, but I receive nothing on my server. I'm running CentOS 8 on my laptop and I opened udp port 6666. When I run nmap onby krono - Debian
Unfortunately I removed my serial interface after upgrading u-boot and install Debian. I'm pretty sure I didn't install netconsole when upgrading u-boot. Can I do it now, without using serial console? However, I booted NAS with a fresh USB rootfs (based on your Debian-5.2.9 image). How can I recover my last installation? Could it be possible my rootfs usb is dying? Is it not possiblby krono - Debian
I’m waiting for help... :) Ivanby krono - Debian
After few days I had the same problem, but at the moment I’ve not yet reboot. It seems that file system has been mounted as read-only. root@NAS:/home/user# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: base-files cups cups-client cups-common cups-coby krono - Debian
I forgot to say you I'm using your last u-boot. Anyway I solved recreating a new rootfs with your last distribution and reinstalling all of my old softwares (I hope so). Now it seems to work well. Find attached my last dmesg logs [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3by krono - Debian
Hi guys! I've been away for a while! Debian installation worked very well on my NSA325v2 until yesterday! Yesterday I performed an "apt -y upgrade & shutdown -r now", and my NAS has not appeared on the network anymore. Root fs is installed onto an usb stick, then I tried to solve the problem running fsck on the disk from my laptop, but nothing; a lot of nodes have been cleaby krono - Debian