renojim Wrote: ------------------------------------------------------- > That fsck error looks awfully familiar. I was > getting it not too long ago and I can't remember > exactly what the problem turned out to be, but I > think it was because over the years I never > updated the fstab entry for the root drive. After > an update the old entry (which was "/dev/by Bobby - Debian
The USB stick worked! Updated system: 59 new packages since last boot on 2021-12-30. Lan sharing works. Thanks for the help again! I will check on keeping the USB stick save from too may write actions. Bobbyby Bobby - Debian
Wait.... is used dd to make an image of the usb stick and mounted that. It worked,,, I can browse the files now from the image! Just copying it over now to a new usb stick. Will try booting the nas tomorrow. Thanks so far ;-)by Bobby - Debian
Thanks for the quick help! Unfortunately it doesn't mount, see the attached error. So one route now is to create a new rootfs? This link: https://forum.doozan.com/read.php?2,12096 and then "Updated 26 Sept 2021"? I had kept the system quite basic, so no great loss of packages. Just torrent/newsgroup stuff and sharing on the lan over nfs. I bought the USB drive especially fby Bobby - Debian
Hi, Having trouble doing that: sudo e2fsck /dev/sdc e2fsck 1.45.5 (07-Jan-2020) e2fsck: Read-only file system while trying to open /dev/sdc Disk write-protected; use the -n option to do a read-only check of the device. Did do this: sudo e2fsck -n -f -v -C 0 /dev/sdc1 e2fsck 1.45.5 (07-Jan-2020) Warning: skipping journal recovery because doing a read-only filesystem checkby Bobby - Debian
Hi, I had my Zyxel NSA325 up and running well on Debian, following the instructions here for uboot etc. It ran great, but somewhere along the line it got broken. One day I noticed the device wan't available at the usual lan IP. No SSH, didn't show up om nmap scan, nowhere to be seen. Reboot (physically unplugging it) didn't help. I still have the USB to serial cable, hookeby Bobby - Debian
Hi, Bodhi, your suggested scrip didn't seem to work for me, but I found a solution. My setup NSA325 running Debian 2 harddisks: /dev/sda and /dev/sdb. Configured as raid0 with mdadm, which gives me /dev/md0 as the combined drive and mounted at /media/nas Script The hdparm command from your script worked, but I seem to have trouble using that on /dev/md0. On /dev/sda or /dev/sdb iby Bobby - Debian
It worked! It booted nicely in Debian, fantastic! And many thanks for the help! I will go through the wiki for more tips and suggestions, but have a few at the moment: Upgrade Note 3 states the following and my quesion is if this applies to every time I apt-get update && upgrade? Should I always keep an eye on this? Warning: Watch the apt-get upgrade progress. If the apt-get upgrby Bobby - Debian
I suppose I still had to update uBoot and set the correct envs for booting into Debian after reboot. So I followed this: https://forum.doozan.com/read.php?3,12381 but after rebooting I got kernel panic [25651.813027][ T5050] reboot: Restarting system 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 Mby Bobby - Debian
Installed the u-boot-tools. Now fw_printenv is available. Thanks! When I reboot i'm back at the Marvell>> prompt and this: TFTP from server 10.4.52.7; our IP address is 10.4.52.165 Filename 'uImage'. Load address: 0x2000000 Loading: T T T T T T T T T T Retry count exceeded; starting again ## Booting image at 02000000 ... Bad Magic Number Unknown command 'by Bobby - Debian
I started over: followed the 26 sept 2021 update here: Linux Kernel 5.13.6 Kirkwood package and Debian rootfs did step 1 and 2. skipped step 3. I'm on stock uBoot so I did step 4 with the DTB for NSA325. step 5 took me here, because I'm on stock uBoot: Boot Kirkwood rootfs with stock u-boot I copy-pasted all the setenv commands, in one go, because there is not enough time betwby Bobby - Debian
Yes, @renojim that's correct. @Bodhi, bij Stock OS, you mean on the nas, through serial console om my linux machine? or how to boot into the rootfs (usb stick?) or how to boot into rootfs from kwboot? I don't understand. p.s. I have the USB stick in the back port and harddisks disconnected.by Bobby - Debian
Hi, I managed to kwboot U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) So next step was to make it permanent? -QuoteAfter you have booted successfully into the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2, you will need to flash u-boot image and envs image as instructed in the u-boot installation post. to make it permanent. When I type ' help' at the "NSA3by Bobby - Debian
Hi, I have an NSA325 and would like to run Debian on it. I followed your tutorial: https://forum.doozan.com/read.php?2,12096 make progress but not quite there yet: Serial connection I needed to switch tx and rx and ha to move my cables away from electrical interferences. The serial works great now. uBoot I was unable to kwboot the 2016 uboot to the nas. Executing ' run to_stockby Bobby - Debian