Your uInitrd has grown too big. 0x1100000 + 11782486 = 0x1C3C956, so that overwrites the fdt on 0x1c00000. You can either create a smaller uInitrd, or change the loadaddress of fdt. (to 0x1D00000 or higher). And of course in the latter case you'll also have to change the boot command to meet the new load address.by Mijzelf - Debian
miazza Wrote: - 1st Question: For this NSA325 I have to follow the > The Marvell Dreamplug box installation procedure > Right ? Nope. From the thread 2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug : "The Marvell Dreamplug box installation procedurby Mijzelf - uBoot
VIRT is virtual memory, in this case that is basically only address space which is reserved. That address space does not have to be shared with other processes, as each process has it's own 4GiB of potential address space. RES (resident) is the actual amount of used memory (+ the size of the binaries in memory). You can detect a memory leak be watching the memory usage over time. If it kby Mijzelf - Debian
Really? How old was that installation? I'm a bit surprised that the command server apparently still works. As far as I could see there was no dns request, so the IP address is hardcoded. I wouldn't expect the command server to be longer than a few days on the same address. But who knows? The reverse dns of tcpdump says the IP address is www.khust.tv, which is Russian. A takedown might bby Mijzelf - uBoot
I tried it (on an immutable system), and believe me, it is executable. So far I have found that it forks itself with an executable stack, as reported by syslog: Mar 8 18:57:46 ks10 kernel: [ 383.871992] process '/home/test/tty6' started with executable stack I *think* it decompresses/decrypts itself to it's stack and executes from there. Then it forks a lot, and it tries to isby Mijzelf - uBoot
The default Armada rootfs has a script /root/set_persistent_mac_address which is called from /etc/rc.local to read the MAC address of the NIC from u-boot environment, and set it to the NIC. Problem is that it is called after the networking is already up, which means the NAS first requests an IP address by DHCP on a random MAC address, and then another time using the 'real' MAC address,by Mijzelf - Debian
Ah thanks. The file has 'obfuscation' written on it. It has an invalid ELF header: $ file tty6 tty6: ELF 32-bit LSB executable, ARM, EABI4 version 1 (GNU/Linux), too many section (65535) It has a very high entropy, it can hardly be compressed. So whatever it is, it's not pure executable code. My first guess was that it is mainly compressed code, and decompresses itself in memorby Mijzelf - uBoot
It appears u-boot in my Shuttle KS10 has a weird GPT implementation. When trying to boot from a 4TB disk, I get this: Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found Device 0 @ 0 0: Model: TOSHIBA HDWD240 Firm: KQ000A Ser#: Z9J1S0I9S5HH Type: Hard Disk Supports 48-bit addressing Capacity: 171829by Mijzelf - uBoot
Are the 5.16.5 kernel modules correctly installed?by Mijzelf - Debian
Yep, that was it. I had to set CONFIG_POWER_RESET_GPIO=y (and so also CONFIG_POWER_RESET=y)by Mijzelf - Debian
Where did you install them? By default Linux only looks in the directories listed in PATH (try 'echo ${PATH}'). If they are elsewhere, you have to specify the path. For instance, when they are in the current directory you can execute it by ./fw_printenvby Mijzelf - uBoot
@bohdi: Do you apply any patches to your kernel regarding power off? I've read linux-5.10.7-mvebu-370xp-tld-1.patch, but as far as I can see it only adds dts files, and a disk led driver. For some reason in OpenWrt I can switch off the box, but I can't switch it on again without powercycling. Tried in both 21.02.1 (Kernel 5.4.154) and master (5.10.90). While your kernel works fine (5.1by Mijzelf - Debian
Ah, so it works! Thanks a lot for testing! I'll put the '326 on my shortlist.by Mijzelf - Debian
@raffe: Could you test for me if the NAS326 supports wake on RTC? In that case the command echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm ; poweroff (run as root) should poweroff the NAS, and after 1 minute it should wakeup again. Thanks in advance.by Mijzelf - Debian
@ehorher: Do you by chance have a copy of /var/run/tty6? The download link is dead, and I'm curious what is inside.by Mijzelf - uBoot
Quote 0:2345:respawn:/tmp/loopd0 This certainly doesn't belong there. And *something* downloads /var/run/tty6 from 202.110.187.205. A google on /tmp/loopd0 gave me this: Quote /tmp/loopd0 was identified as malicious by YARA according to rules: 000 Common Rules Did you execute anything from your raid array after you had mounted it? And what exactly happened to your stock OS? /Ediby Mijzelf - uBoot
What is in /var/run/tty6? And what is in /etc/inittab?by Mijzelf - uBoot
Gnome is a bit heavy, for an 512MiB 500MHz Armv5, I think. But if you are running an Xserver on your client, you can run graphical programs on your NAS, having their in/output on your Xserver. All you have to do is install xauth (and your graphical program) apt install xauth x11-apps Now you can login to your box using ssh -X user@nsa325 and execute for instance xeyes in your shell.by Mijzelf - uBoot
Quotejust wondering if it possible to flash with the original firmware because I wan to see if I can recover the information that I have on the raid. You don't need the original firmware for that. Any decent Linux box can assemble&mount that array, including Debian.by Mijzelf - uBoot
bodhi Wrote: ------------------------------------------------------- > Could you post the kwboot patch? Sure.by Mijzelf - Debian
Quote You could try Willy's recover.bin with the new kwboot. It might boot. It doesn't $ ./kwboot -b recover.bin -t /dev/ttyUSB0 kwboot version 2022.01-00673-g70fe7827f2-dirty Sending boot message. Please reboot the target...| Waiting 2s and flushing tty Sending boot image header (48640 bytes)... 0 % [.....................................................................by Mijzelf - Debian
bodhi Wrote: ------------------------------------------------------- > Also you don't need to change the memory size in > the DTS. It will be detected by u-boot. I was looking further at that patch. It adds a 'ARM_ATAG_DTB_COMPAT_CMDLINE_MANGLE' to Kconfig / .config. And in arch/arm/boot/compressed/atags_to_fdt.c, there is a code block disabled by this config: #ifnby Mijzelf - Debian
Why are you asking that here? The OpenWrt forum seems more appropriate. Anyway, in contrast to Debian OpenWrt is a very minimal OS targeting routers. So any functionality which is not found on a basic router, is not installed. I think you have to install kmod-md-raid0, kmod-md-raid1 and blockd. And then you should be able to assemble the array mdadm --assemble /dev/md0 /dev/sda2 /dev/sby Mijzelf - Debian
OK, this kwboot works: ./kwboot -b spidump -t /dev/ttyUSB0 kwboot version 2022.01-00673-g70fe7827f2-dirty Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target.../ Waiting 2s and flushing tty Sending boot image header (59648 bytes)... 0 % [.....................................................................by Mijzelf - Debian
Quote Nice! it makes sense (with its own battery). Well, there is no visible battery on the board, but I suppose the RTC is that low powered that it can keep the time on a capacitor. Quote This u-boot is too old. Correction: This u-boot is old. It still gets its job done, I just have to wait a little longer. (And yes, a new u-boot with fdt support and everything would be nice, but at tby Mijzelf - Debian
bodhi Wrote: > > While the RN102 uses loadaddr 0x2000000, The > Mirabox uses loadaddr 0x6400000. Perhaps try > 0x6400000 to see it will make any difference. You mean this? Unfortunately it didn't make any difference Using egiga0 device TFTP from server 172.20.172.252; our IP address is 172.20.172.169 Filename 'openwrt-mvebu-cortexa9-globalscale_mirabox-initramby Mijzelf - Debian
Quote Shuttle>> bootm ## Booting kernel from Legacy Image at 02000000 ... Image Name: ARM OpenWrt Linux-5.10.90 Created: 2022-01-13 8:33:29 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5087137 Bytes = 4.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Startingby Mijzelf - Debian
My 2 cents. I think the checksum is to prevent the flasher from flashing a damaged file. And you can ask binwalk what is inside the 16MB backup file.by Mijzelf - uBoot
Does anybody know if wake on RTC works on a NAS326?by Mijzelf - Debian