Hello, bodhi Wrote: ------------------------------------------------------- > Nothing to be concerned about. mtd5 is where stock > kernel is. Yeah I guess that explains why the stock kernel got bricked ages ago :D. Thank you for your help and the amazing work you are doing for everyone :)by Dyce - Debian
Okay it seems the system now booted correctly and I can connect to it via SSH, but the ECC errors are still present. Is it something I should be concerned about? [ 25.757245][ T184] process '/usr/bin/fstype' started with executable stack [ 25.757245][ T184] process '/usr/bin/fstype' started with executable stack [ 25.948308][ T194] EXT4-fs (sdd1): mounting ext3by Dyce - Debian
I was browsing forum posts and stumbled upon this one https://forum.doozan.com/read.php?2,126874 I will try to boot up with old disk, add the nofail to fstab and post results here.by Dyce - Debian
Hello, I have NSA325v2 running on 5.10.7-kirkwood-tld-1. Everything worked smoothly until I decided to change smaller disk in a raid1 array for a larger one. When I changed the disks, the nas wont boot properly and I cannot connect to it via SSH. When I changed the disk back to original configuration, everything works fine. The system wont event boot without new disk (only one disk from the miby Dyce - Debian
Sorry for the late reply. bodhi Wrote: > See > the > Wiki topic > > > QuoteKey daemon (button control) > > Multimedia keyboard daemon for Linux > How to use set up button to reboot or shutdown > with Key Daemon (esekeyd) I will look into it, thank you very much!by Dyce - Debian
One last question came to my mind. My power button is not working when the device is running. Is there a way to execute shutdown command when I press (or hold) the power button?by Dyce - Debian
Hello, > I don't think the buzzer works on this box. Strange, because IIRC it worked when I was using stock OS long time ago (it played beep sound when I long-pressed the power button to shut the box down), but it's not a problem, it is a small price to pay for getting rid of the original OS. > Look in your rootfs /etc/rc.local for example how > to manipulate theby Dyce - Debian
Hello, I am running Debian with 5.2.9 kirkwood kernel on my device which I installed from this awesome website. I was wondering if there is any way to interact with the LEDs and speaker on the device (e.g. I want my sata1/sata2 leds turn red and play a beep sound when there is a disk failure -> mdadm detects a degraded array). I found some files in /sys/class/leds but tbh I dont really knowby Dyce - Debian
Hello bodhi, sorry for the late reply. After running e2fsc it found so many errors that I was not even surprised it failed to boot after repair. I installed Debian 5.2.9 on USB and it is indeed booting again! Thank you for saving my NAS (again) and for the amazing hard work you are doing for many of us. I owe you once more!by Dyce - uBoot
Hello again, I was not sure if I should make a new post, because maybe some information in this post could be useful. My NSA325v2 failed to connect to network, so I hooked it up to serial console to see whats up. Here is the output. 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 eby Dyce - uBoot
My stock system was not booting, so that was not option for me anyway, but when I connected the second disk, debian recognized it is a raid1 array and automagically created the raid1 for me, I just had to mount it and all of my data is there. Thank you again for all the help and sorry for bothering you with so many questions. Have a nice day and THANK YOU once more!by Dyce - uBoot
Hello again, thank you very much for you help! I successfully flashed u-boot and was able to boot debian from USB. Have a nice day and keep up the amazing work you are doing! edit: any idea on how I can get my data from HDD's (raid1) ? debian lists the partitions as unknown type Device Boot Start End Sectors Size Id Type /dev/sda1 63 1028159 102809by Dyce - uBoot
Hello, I used "su" command to log in as root user. I suppose that is enough right? Then I used gparted to set up the USB according to instructions. I am going to redo it again from scratch, just in case I did something wrong. I will edit this reply after with result. Edit: Okay, I was now able to boot into debian, here is the console output. I will try to flash uboot now and willby Dyce - uBoot
Hello again, I restored the original uImage and boot using that, here is the console output, which is for some reason different than what I had previously (before appending DTB), I have no idea why... Anyway, here it is: Michal-NB ~ # kwboot -t -B 115200 /dev/ttyUSB0 -b '/home/michal/Desktop/uboot.2017.07-tld-1.nsa325.mtd0.kwb' -p Sending boot message. Please reboot the target...by Dyce - uBoot
Hello again, Thank you for help, I was able to get one step further, successfully used kwboot and get the box to boot from USB, but now I am stuck here Michal-NB boot # kwboot -t -B 115200 /dev/ttyUSB0 -b '/home/michal/Desktop/uboot.2017.07-tld-1.nsa325.mtd0.kwb' -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [.................................by Dyce - uBoot
I've read some topics around here and what other info bodhi asked from people, so I include that here (sorry for spamming) printenv command gives Marvell>>printenv bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/devby Dyce - uBoot