The /dev/sda2 problem seems to have resolved (itself!) I did install mdadm but did not do anything with it. Anyway, I am now seeing a /dev/md0 device for the (1 drive) raid volume (and which was not there earlier) and that mounts up fine to access the old XFS filesystem. I will add a mount to /etc/fstab. root@debian:~# mkdir /media/big root@debian:~# mount /dev/md0 /media/big [ 146.by Hilsen - Debian
It continues to go well I think. Now enabled swap and rebuilt the kernel files so now booting successfully 5.15.5. Just got to figure out how to mount that sda2 partition....?? root@debian:~# mkdir /mnt/sda2 root@debian:-# mount /dev/sda2 /mnt/sda2 mount: /mnt/sda2: unknown filesystem type 'linux_raid_member'. The 5.15.5 boot log... U-Boot 2017.07-tld-1 (Sep 05 20by Hilsen - Debian
Hi Bodhi, All seems to be going well. I post the boot log below finishing with an fw_printenv, this is actually the second boot, the first boot also booted to the shell successfully with the default pogoxxx.dtb, at which point i fw_setenv updated the dtb identifier to the nsa310b-lmsensor-redusbled.dtb, and adjusted the other env settings as recommended. I have not yet setup a swap file,by Hilsen - Debian
Thanks bodhi, I see you are correct about that a0000 write indeed. As I said earlier, I did NOT make any attempt to perform fw_setenv operations in Section e. Particularly e2: -> fw_setenv mtdparts 'xxxxxxxxx' and e3: -> These envs are important to be set if you plan to use uEnv.txt (see section C). Is it OK to reboot anyway? I am a little unclear about how the eby Hilsen - Debian
Hi bodhi, Thanks, all cautions welcomed. The results are the same in any case. I am not going to think about that one too hard... I would have thought the blocks were perhaps already erased/blank, presumably nand write does a read verification and will only write to blocks which are erased ff... /media/usbkey/nsa310/tools/tools # /media.flash/flash_erase /dev/mtd0 0 6 Erasing 128 Kiby Hilsen - Debian
Hi bodhi, Thanks for the continued help! I flashed the uboot and environment img (files renamed for convenience uboot.kwb, newenv.img) That seemed to go well as shown below. Now I pause at editing the environment variables... Is it not necessary to reload the (new updated and default) environment from nand before changing environment variables and resaving the modified environment?by Hilsen - Debian
Hi bodhi, I installed the env tools.. quote: 1. I realized I've missed one package that needs to be installed in order to make fw_printenv and fw_setenv available (these binaries have been moved to package libubootenv-tool in bullseye) . So do this if you want to list or set envs in Debian. apt-get install libubootenv-tool but fw_printenv cannot access the uboot env it seems..by Hilsen - Debian
Network is now up :) I modified /etc/network/interfaces from auto lo eth0 iface lo inet loopback iface eth0 inet dhcp to auto lo enp1s0 iface lo inet loopback iface enp1s0 inet dhcp (found a helpful ref in https://forum.doozan.com/read.php?3,65269,65379#msg-65379) mari8b [ PM ] Re: Boot Debian from USB on Zyxel NSA310 August 16, 2018 05:03AM Registered: 3 years agoby Hilsen - Debian
I did a little more grepping under /etc, but did not come up with anything inspirational (to me!)... root@debian:/etc# grep eth0 * -drecurse avahi/avahi-daemon.conf:#allow-interfaces=eth0 default/dhcpcd:eth0) dhcp/dhclient.conf:# interface "eth0"; dhcp/dhclient.conf:# interface "eth0"; dhcpcd.sh:# $1 = HostInfoFilePath, e.g "/var/lib/dhcpc/dhcpcd-eth0.infby Hilsen - Debian
Hmmh, that is not working. I am rather lost!? root@debian:/# ifconfig -a enp1s0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 00:00:00:00:00:30 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0by Hilsen - Debian
Thanks Bodhi, switched to the original uImage :) That corrected the boot through to the debian shell and root login, though not everything is quite clear in my head at the moment! I notice the network has not come up, not sure why that is? Eth led light but goes out about 13s into kernel boot. Startup dump and dmesg output are below... What would you recommend now? Cheers, Hilsenby Hilsen - Debian
Hi Bodhi, Apologies for stalling before step 3,4 earlier... Did manage to create usb drive with rootfs and boot via KWBOOT and the updated uboot. Debian kernel loaded and started but stopped shortly after 11s with a Kernel Panic as shown below. I see there is an error before kernel execution ** File not found /boot/uEnv.txt ** does that mean there are missing env settings? Thisby Hilsen - Debian
Hello Bodhi, Many thanks for the reply. I succesfully connected a serial port and downloaded the recommended uboot version (initially omitted the -p patch option in kwboot args which had me perplexed for a little while... (renamed file to uboot.kwb for convenience). root@M4A88:/home/tim/Downloads/kwboot-tool# kwboot -b uboot.kwb /dev/ttyUSB0 -t -p Sending boot message. Please reboot tby Hilsen - Debian
Hello, I have an NSA310 which has not had alot of use due to the lack support for SMB1 problem. It has uboot 1.1.4 and Zyxel 4.7 firmware. Was pleased to discover options available here, but after activating the telnet backdoor and checking the NAND chip as recommended, I see there are bad erase blocks: / # dmesg | grep -i 'bad' Scanning device for bad blocks Bad eraseblby Hilsen - Debian