Quote Trond, Please run the same iperf tests as whitepawn did. -bodhi Sure bodhi, $ iperf -n2000M -i 3 -c 192.168.1.128 ------------------------------------------------------------ Client connecting to 192.168.1.128, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.109 port 42516 connected with 192.16by tme - Debian
Hi whitepawn, The RN102 is a file server, so I think the only performance measure that really counts is the bandwidth into and out of the box. For the tests below, both the RN102 and my laptop were cabled to the same gigabit router. I have 2 mirroring 2 TB HDDs in the box (RAID-1). I copied the file 'film.mp4' back and forth. Its size is 1 GB and it contains a 3+ hour movie. Sessionby tme - Debian
Hi bodhi, You are right. I was right about the '/dev/sd?1', but wrong about the LEDs. Here, initially, the only disk is attached to the eSATA connector, then a HHD is hot inserted into slot 1, an then another one into slot 2: root@debian:/tmp# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk `-sda1 8:1 0 149.1G 0 part / mtdblocby tme - Debian
Hi bodhi and whitepawn, Quotemyself 'backup.mtd0' was created by the command nanddump --noecc --omitoob -l 0x80000 -f backup.mtd0 /dev/mtd0 Why isn't this image suited for 'kwboot -p'? Not much of a mystery, actually. The size of the 'mtd0' partition is 1.5 MiB and more that the first 0x80000 B (512 KiB) are used by the U-Boot image: # cat /proc/mtdby tme - Debian
Hi bodhi and whitepawn, Quote Also in u-boot console, attach an HDD to to eSATA port, and try both of these commands, one of them should initialize all the SATA disks in the system. I have modified my eSATAp to SATA adapter cable so that 5 V power is provided from an external power supply. 3.3 V and 12 V pins are unconnected. The disk is powered up before the box. A HGST 1 TB HDD from Aprilby tme - Debian
Hi whitepawn, Quote `Insert happy smile face emoji here.` Great! Congratulation. I will try to reproduce your result. Regards, Trond Melenby tme - Debian
Hi bodhi, Just to experience the expected behavior, I decided to use 'kwboot' to upload the 'mtd0' backup from my second RN102 which still runs stock Netgear firmware: $ kwboot -b backup.mtd0 -p -t /dev/ttyUSB0 Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1by tme - Debian
Quote Yes, it is no e-SATAp, but neither standard 7 pin e-SATA. If you looked connector inside there are also some pins which I think are power pins. My current understanding is that the power pins are there, but unconnected. Can you please verify? Regards, Trond Melenby tme - Debian
Hi whitepawn, Good idea! This is my plan too, but the rear eSATA connector on Netgear ReadyNAS boxes is not eSATAp. Since you are more of a hardware guy, you may try to feed 5 V to the connector. It should preferably have its own 5 V regulator running on 12 V, but maybe there is excess power capacity on an existing 5 V rail? I think SSDs need 5 V only, while HDDs needs 12 V in addition forby tme - Debian
Hi whitepawn, I tried inserting the DDR3 training code from the stock U-Boot using 'kwbimage' and 'mvebuimg'. It kind of works: $ ./kwbimage -x -i backup.mtd0 -o /tmp/ $ mv /tmp/payload /tmp/payload.orig $ ./kwbimage -x -i u-boot.bin -o /tmp/ Invalid image version 20 $ ./mvebuimg -v 1 create -b /tmp/binary.0 -o ubootmodded.bin spi /tmp/payload.orig $ kwboot -b ubootby tme - Debian
Quoterayknight Except ping is not always a good indicator of whether or not a site is available Good point! root@rn102:~# apt install -y binutils root@rn102:~# strings /usr/bin/rnutil | grep netgear https://my.netgear.com/ajax/Update/firmware/firmware?serial_number=%s&model=%s&firmware_version=%s root@rn102:~# rnutil firmware_update name: ReadyNASOS version: 6.10.3 verno:by tme - uBoot
Hi withepawn and bodhi, There is no need to dump the BootROM. It is well documented on page 81 to 98 in the document "88F6710, 88F6707, and 88F6W11 ARMADA ® 370 SoC Functional Specifications – Unrestricted" which is no longer available at www.marvell.com, but may be downloaded from at Arnaud Ebalard's site 'natisbad.org'. For the record, the BootROM starts at 0xFFF0by tme - Debian
Hi whitepawn and bodhi, One way to be able to test my RN102 port of the current mainline U-Boot would be to disassemble BootROM 1.08 to find out what "Header ID"(s) it likes. How do I dump the BootROM content? Using 'md' at the "Marvell>" prompt? Or from inside Debian? Regards, Trond Melenby tme - Debian
Hi whitepawn, > both of them are loaded extremely slowly For me the transfere takes about one minute with a HL-340 based USB-to-RS232 adapter, and not more than, say, 4 minutes by slower means. 'kwboot' is always started first. Kwb-file transfere starts within 3-10 seconds after power on. I have also experienced what appears to be very slow transferes, but I believe this isby tme - Debian
Hi whitepawn, QuoteMaybe ddr code is not working? For some hours earlier today I thought so too. What is similar to your case is that the UART boot drops out early, but my error message is clearly the result of some comparison. My current hypothesis is that Armada's BootROM in both cases puts the kwb-image into SRAM until it's exhausted. Then it initializes DDR3 memory and places tby tme - Debian
Hi whitepawn, We posted in parallel. Warnings from the compiler are to be expected. Gcc has become much better since 2013 at detecting inconsistencies in the code. Ignore the warnings, turn them off with -Wno-unused-const-variable etc. Alternatively, install a Linux distribution from 2013. :-) These are probably real errors, though: nand_base.c:2661:29: error: 'struct nand_chipby tme - Debian
Hi whitepawn and bodhi, I have ported the latest mainline U-Boot release candidate v2020.10-rc5 to Netgear ReadyNAS RN102. My starting point was U-Boot for Synology DS414 which is based on the Marvell Armada XP SoC. Of course, a major part of the port is the device tree credited to bodhi and pulled from his recent kernel. Thanks a lot! Using UART boot to upload U-Boot to the box fails consiby tme - Debian
Quotebodhi U-boot on NAND does not have anything to do with UART booting. UART booting with kwboot works even the NAND is wiped out. Thanks! Quote Most Stora boxes have UART booting capabilty, some don't (different BooROM version). This might be the reason I have not succeed with UART boot. SoC is Kirkwood 88F6281_A0. BootROM version is 1.11, and 1.12 might be required. I see that pby tme - uBoot
Hi bodhi, I want to test my u-boot-v2020.07 on a Netgear MS2110 Stora. Stock u-boot for Netgear MS2110 Stora is U-Boot 1.1.4 (Jul 31 2009 - 10:33:00) Marvell version: 3.4.14 but U-Boot on this box was upgraded some years ago with your then current version U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:45:22 -0700) Netgear-MS2110 To become familiar with 'kwboot' and UART booting, I tby tme - uBoot
Hi K20, Some thoughts: UBIFS sits upon UBI which sits upon '/dev/mtd4'. UBIFS don't care about bad blocks, that's handled by UBI. I imagine that if '/dev/mtd4' is cloned from another box, the status of the blocks from the other box will be applied to the receiving one. That some blocks are marked bad becuse they were bad on the other box is a minor issue, the mby tme - uBoot
Hi K20, Quote I have manage to create a recovery USB. If I understand correctly, the recovery USB was partly successful a few days ago. Did it flash your mtd4/ubifs partition OK? If so, you may step back and use all the experience you've gained to recover from that point. But wait for bodhi's advice and try his recommendation first. Regards, Trond Melenby tme - uBoot
Hi K10, Quote Removed OS HDD The stock firmware needs an unpacked root file system on disk to run. It expects to find this root file system on the first of 3 RAID partitions on an array in the Slots. It uses the second RAID partition as swap media, i.e. to offload the 512 MiB of internal RAM when it runs full. The third RAID partition on the array is by far the largest one and is where youby tme - uBoot
Thanks bodhi, I will try to add support for Netgear ReadyNAS RN102 in the upcoming u-boot-v2020.10 release and will start working on it today. To learn how the bits and pieces fit together, I went for a lower hanging fruit yesterday, and now I have build u-boot-v2020.07 with support for Netgear MS2110 Stora. It's ready for testing on target. The patch is attached. The substance is allby tme - uBoot
Hi K20, Quote E: Unable to locate package y-boot-tools Sorry! I didn't check my spelling carefully enough. There is no such thing as 'y-boot'. Edited in original post: apt install -y mtd-tools u-boot-tools Regards, Trond Melenby tme - uBoot
QuoteK20 'rnutil chroot' command does work which gives me the root access but I cant find nand, ubifs, minirootfs partions for the image to written. Now you may install any tool you like, for instance: apt install -y mtd-utils u-boot-tools Now can do 'cat /proc/mtd', and you have 'writenand'. And if the '/etc/fw_env.config' is set up correctly thenby tme - uBoot
Quotebodhi It is quite easy. Great! Give me a few weeks, and I will verify and report here. Btw, do you have a dts-file for Stora? Or is it so similar to Seagate Goflex Home that the dts-files are the same? Regards, Trond Melenby tme - uBoot
Hi K20, Quote I have checked, the Tech Support mode is completely useless "apt" and "nandwrite" doesn't work, "rnutil chroot" doesn't write anything, "rnutil firmware_update" doest update anything As I wrote, for 'rnutil chroot' to work you must have a disk with the (unpacked) stock firmware on it. Now that you have 2 boxes, you caby tme - uBoot
Hi Stormy, Quote Is it worth it to try to recover the Stora OS? Because a few days ago I read somewhere that in order to get Stora to work it requires some activation on the Netgear servers and the servers dont work anymore. So basically we are stuck with a semi-bricked NAS. What do you recommend? A running Stora runs independantly of Netgear's terminated service, except that one mustby tme - uBoot
Hi AkkJaa, Your RN10400 has its own Netgear product page, but the Product Data Sheet on this page is the same as for RN104, so it seems your box is just an early or late version of RN104. This is consistent with the printed text "RN104_MV_MVT_3.0" on the PCB in your picture. Plus, the same text is printed here, so it is correct that you find the serial console connector behind the whby tme - uBoot
Hi K20, In Tech Support mode you have a root file system in RAM. It includes 'dropbear', so you may use 'ssh' (in stead of 'telnet') for login and 'scp' to copy the binaries to the /tmp directory on the box. The pass word for 'root' in Tech Support mode is 'infr8ntdebug' (without the quotes). In Tech Support mode, most commands areby tme - uBoot