The device is off site and I only had about a hour yesterday. So I can not interrupt the u-boot count down and do printenv, but I think the one here https://forum.doozan.com/read.php?2,26671,42824#msg-42824 should be very close to what I have now: LGE-NAS>> printenv baudrate=115200 loads_echo=0 ipaddr=10.177.190.59 serverip=10.177.191.39 rootpath=/opt/Orion-SDK/armel-2.0/rootfs netby raffe - Debian
Also tried with MODULES=most _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** ** LGE-NAS BOARD: NT1 LE U-Boot 1.1.4 (May 21 2011 - 03:56:55)NT1 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDEE0 Soc: 88F6281 A1 (DDR2) CPU running @ 1000Mhzby raffe - Debian
It stops here: _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** ** LGE-NAS BOARD: NT1 LE U-Boot 1.1.4 (May 21 2011 - 03:56:55)NT1 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDEE0 Soc: 88F6281 A1 (DDR2) CPU running @ 1000Mhz L2 running @by raffe - Debian
Hi! I had some problems a few months ago when I tried to update my LG N1T1 NAS from 6.5.7 to 6.6.3, it would not boot with the new uImage and uInitrd. It stopped just after reading them. After I tried both 6.3.5 and 6.5.7 (the last several times) and got same problems. I also added MODULES=dep to the file /etc/initramfs-tools/initramfs.conf and that setting is still there. Then I got nby raffe - Debian
I did find something strange: The device names for hard drives and USB-drives can switch between boots. This is both from the same device. Just after I have updated from 6.6.2 to 6.7.5, before reboot USB is: sdb1: root@debian:/boot# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 10.9T 0 disk ├─sda1 8:1 1 139.7G 0 part / └─sda2 8:2by raffe - Debian
Naturally it booted up just fine when I had it connected with serial console (and I do not need to disconnect wires to make it work). But I did find something strange: The device names for hard drives and USB-drives can switch between boots. I make a new thread for that...by raffe - Debian
Hi! I tried as I used to do: su - cd /boot mkdir ./backup/2024-03-30/ cp -a uImage uInitrd ./backup/2024-03-30/ cp -a initrd.img-6.6.2-mvebu-tld-1 backup/2024-03-30/ cp -a System.map-6.6.2-mvebu-tld-1 backup/2024-03-30/ cp -a vmlinuz-6.6.2-mvebu-tld-1 backup/2024-03-30/ cp -a config-6.6.2-mvebu-tld-1 backup/2024-03-30/ cp -ra dts/ backup/2024-03-30/dts wget https://bit.ly/3SI4bRv mvby raffe - Debian
Compared to a boot that works OK, after I above disconnect power cable and after ~10 sec connect it again. BootROM - 1.73 Booting from NAND flash General initialization - Version: 1.0.0 Detected Device ID 6810 High speed PHY - Version: 2.0 Init RD NAS topology board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 06by raffe - Debian
Hi! Now when I dug out the NASes and connected via serial, I could check out a boot problem I have had for a while. Sometimes, maybe every second or third boot one NAS freezes while booting and stops with: ... ... [ 22.768595][ T1698] EXT4-fs (sda1): re-mounted 4e7f4895-025a-4c76-99da-7d29674ae6a5 r/w. Quota mode: none. Will now check all file systems. [ 23.317608][ T74] BUG: sby raffe - Debian
I did not have time to fix with a new USB before you released Linux Kernel 6.6.2. So i tried to upgrade to 6.6.2 and now my problems are gone :-)by raffe - Debian
The cat /root/set_persistent_mac_address root@debian:~# cat /root/set_persistent_mac_address #!/bin/bash # # set_persistent_mac_address # # Compare the MAC address in ifconfig with u-boot env ethaddr (persistent MAC for eth0) and reconfig MAC address to ethaddr if necessary. # if [ `/usr/bin/fw_printenv ethaddr ` ]; then UBOOT_MACADDR=`/usr/bin/fw_printenv ethaddr | cut -c9by raffe - Debian
Sticker on bottom of the unit say: 5C648EA53B5E It seems like u-boot-tools do not include fw_printenv anymore, so I downloaded it from here. I also tried to disable IPv6 via /etc/sysctl.conf But after changing "armada-nand:2m" to "pxa3xx_nand-0:2m", I still need to do the ping trick to be able to do anything normally. It seems like both my NAS326 has this freezing problemby raffe - Debian
After last update to Linux Kernel 6.5.7 I got a strange problem. Now I run Linux debian 6.4.11-mvebu-tld-1 as I tried to downgrade to see if it would get better. When I am connected via SSH I can write about 5 seconds, then it freeze for about 10 seconds, then it spits out what I have written and I can write about 5 seconds more before it freezes again. From time to time I get "client_looby raffe - Debian
Well, I got to the site and the two top LEDs had a steady light, but no response with any button. But when I disconnected the power cable, waited 10 seconds, and reconnected the power it just booted up with 6.4.11 as nothing had ever been wrong. So probably just a random glitch or maybe a Gremling on site. Anyhow, now it seems to be happy and everything works :-)by raffe - Debian
I appreciate that bodhi creates new updated versions of "Linux Kernel 6.4.11 Kirkwood package and Debian rootfs" and "Linux Kernel 6.4.11 MVEBU package and Debian armhf rootfs", it has made my NASes so much more useful. But lately I've started thinking about how to make them? Not to replace the versions here, but just to learn and understand. Tried Googling and thinby raffe - Debian
bodhi Wrote: ------------------------------------------------------- > raffe, > > > Ah, you are right. I have a ZyXEL NAS326. So > this > > is wrong thread for me :-) > > Connect serial console, and power up, let it boot > as far as it can. And post the entire serial > console log (from u-boot banner.... everything) > here in a new thread. >by raffe - Debian
I also got problems booting with 6.4.11-mvebu-tld-1. It didn't boot up so I could reach it with SSH or ping it. Tried to wake with WOL, but it didn't help. Not sure if I have Debian-5.13.6-kirkwood-tld-1-rootfs (28 Sept 2021) , but I think I installed Debian on it February 2022 so it should be that one. I am not on site, so I have to check tomorrow what could be wrong. @nsa_by raffe - Debian
bodhi Wrote: ------------------------------------------------------- > rafe. > > QuoteI also got problems booting with > 6.4.11-mvebu-tld-1. > > This kernel > 6.4.11-mvebu-tld-1 is for > the Armada SoC, so can be used on > NAS326. > > This kernel > 6.4.11-kirkwood-tld-1 is > for the Kirkwood SoC, so can be used on > NSA325. > > Pby raffe - Debian
EDIT: Deleted Wrong thread, sorry. Created a new thread for Zyxel 326 here: https://forum.doozan.com/read.php?2,135814by raffe - Debian
Completely unnecessary ;-) But I wanted some visual confirmation when I pushed the buttons. So I did these very simple scripts. /etc/esekeyd.conf #For testing #KEY_116:/usr/bin/logger -s -i "POWER button pushed" #RESTART:/usr/bin/logger -s -i "RESTART button pushed" #KEY_133:/usr/bin/logger -s -i "COPY Button pushed" #The real stuff KEY_116:/root/run_when_by raffe - Debian
@Mijzelf : I did this on NAS326 root@debian:~# date Thu Feb 3 20:03:55 CET 2022 root@debian:~# echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm ; poweroff root@debian:~# Broadcast message from root@debian (pts/0) (Thu Feb 3 20:03:57 2022): The system is going down for system halt NOW! login as: root root@192.168.222.115's password: Linuby raffe - Debian
It still do not want to start with hard disk. NOTE: I have changed the USB disk to a physically smaller one, from 10 cm to 0,5 cm, then it will not be in the way. And I can use the old to boot up OK, while we are trying this. Anyway, I booted it up with the new USB just fine, see Boot4.txt, and did this: root@debian:~# parted -l Model: ATA WDC WD80EFBX-68A (scsi) Disk /dev/sda: 8002GBby raffe - Debian
OK, I did this root@debian:~# whoami root root@debian:~# parted GNU Parted 3.4 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel gpt Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yesby raffe - Debian
QuoteTo verify this, you can create 4 partitions on the 8TB HDD and the first partition is the rootfs. Boot with it. Or create a USB rootfs with GPT partition table to test Do you mean that I could try to make 4 MBR partitions on the 8TB HDD, and the first is the one with the rootfs stuff (as in MBR we can not name partitions)? OK, will try that. I will edit this post when done. QuoteOr in somby raffe - Debian
I found a serial adapter, so this is what it says in the beginning (the whole boot is in attached Boot1.txt) DDR3 Training Sequence - Ver TIP-1.26.0 mvSysEnvGetTopologyUpdateInfo: TWSI Read failed DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR3 Training Sequence - Ended Successfully Not detected suspend to RAM indication BootROM: Image checksum verification PASSEDby raffe - Debian
I have had more time now to compare the attached different fw_printenv FIRST: If I compare the original fw_printenv with when USB worked: New: bootcmd_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi bootcmd_stock_1=run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && boby raffe - Debian
Thanks for the suggestion! I booted up the NAS326 with USB as under B with the fw_setenv stuff there. Then made a 150GB ext3 partition named rootfs on /dev/sda and copied all stuff there, then did the fw_setenv stuff under C. But it wont boot without the USB at all. With USB in it now boots to stock fw. Maybe there are leftovers from the USB fw_setenv stuff, that the hard drive boby raffe - Debian
Hi! I have combined two 8TB disks with jbod to one disk group on my NAS326, and I wonder what is the easiest way to install rootfs Debian on internal HDD without serial console. The disks are new and I have yet not copied any important stuff on them, so I can reformat etc. Do I have to connect the disks to an external Linux PC, or can I do all on the NAS? Here is some info about the NAS:by raffe - Debian
Thank you very much! :-) I still update my LG N1T1 NAS with new Kirkwood versions, and it works great! I have it off location and every night it opens a VPN connection to my home and make a backup of new documents, photos and other important files.Thanks for your work! <3by raffe - Debian
Thanks for the cp option -a info! OK, here is my test log. I start with cd /boot cp -a uImage uInitrd ./backup/2018-03-12/ I try "Boot with DTB file" as you suggest in the post mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.15.2-kirkwood-tld-1 -d vmlinuz-4.15.2-kirkwood-tld-1 uImage I get Image Name: Linux-4.15.2-kirkwood-tld-1 Creaby raffe - Debian