printenv Marvell>> printenv AC_Power_fail_detect=open CASset=min HW_version=MVT MALLOC_len=5 Manufacturer=NETGEAR NANDboot=nand read.e 0x2000000 0x200000 0x400000;nand read.e 0x1000000 0x7e00000 0x20000;nand read.e 0x3000000 0x800000 0x400000;bootz 0x2000000 0x3000000 0x1000000 Product=ReadyNAS 104 SKUNum=RN104 Startup=Normal USBboot=fatload usb 0:1 0x2000000 /zImage-recoveby K20 - uBoot
Also is there anyway I can write the root.tlz file to the UBIFS partition root@nas-36-66-02:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149G 0 disk ├─sda1 8:1 0 4G 0 part │ └─md0 9:0 0 4G 0 raid1 / ├─sda2 8:2 0 512M 0 part │ └─md1 9:1 0 511.4M 0 raid1 └─sda3 8:3 0 144.5Gby K20 - uBoot
Is there anyway I can manually create UBIFS as I have manage to extract root.tlz file from FW QuoteDid you try reflashing stock mtd3 and mtd4? and how did you do that? i.e. usually ubifs need to be flashed with different command, not nand write. If root.tlz is an mtd4 nanddump, then flash with nand write. But if it is a rootfs backup, you would need to create UBIFS volume, write it ,.... inby K20 - uBoot
Quotei am going to try recreating the UBIFS Hi alxvt, Did you manage to create UBIFS? Thanksby K20 - uBoot
Thanks for your message bodhi. I have tried ./nandwrite --noecc on last 2 partitions but I still got ubi_io_read errors. Then I also tired 1st partitions "mtd0" from the backup but NAS failed to boot uboot and now there is no point checking permission issue for mtd1 as flashing method not working. I am totally lost now, I dont know what to do,by K20 - uBoot
Thanks bodhi for your reply. Quotesince you can log in stock OS with the HDD rootfs, why not let stock OS reinstall the FW for you? there must be a way to do that. I have tried many ways to write the OS to flash via GUI, for example: Restore to default= NAS reboots and give error "Error: could not mount the boot flash" and removes the OS from the HDD Firmware update= NAS rebby K20 - uBoot
Removed OS HDD Booted kwboot Write 0, 1, 2 partition old way. Write 3, 4 as you have instructed. Serial output as follows: __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_by K20 - uBoot
Quotethen in the bricked box, do the same when you execute nandwrite Thanks bodhi for your replay, I have followed your instructions and manage to extract the partitions 3 and 4 from the good NAS and wrote to nand via following command: ./nandwrite /dev/mtd3 mtd3.minirootfs.rn104 ./nandwrite /dev/mtd4 mtd4.ubifs.rn104 Broken NAS still cant find the OS from the flash/nand Installedby K20 - uBoot
Thanks Trond for your reply QuoteNow you may install any tool you like, for instance: apt install -y mtd-utils y-boot-tools I am unable to get the package and NAS is connected to the internet root@nas-36-66-02:~# apt install -y mtd-utils y-boot-tools Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package y-boot-toolsby K20 - uBoot
QuoteI just did above. -bodhi Thanks bodhi for your replay, I am really happy with what I have manage to archive so far with no linux knowledge/background and I had my first linux OS install 3 days ago to run kwboot, so much more to learn. This website is so awesome and everyone here has so much knowledge :) Back to the issue: NAS OS doesn't have "nanddump" "nandwby K20 - uBoot
Thanks for your reply Trond. I have followed your instructions and logged on to "Tech Support mode" and 'rnutil chroot' command does work which gives me the root access but I cant find nand, ubifs, minirootfs partions for the image to written. Following portions are not visible and I think the sits on the top of uboot not the readynas kernel 0: u-boot 0by K20 - uBoot
OK, I have tried to restore the NAS to its default settings and update the firmare but its still not copying the FW to the nand. Potentially I need to create UBIFS partition, which I am working on now. I ran a command on working NAS "ubi info" but there is no partition table. I don't now which partition to write the img to and how too... 0: u-boot 0x0000by K20 - uBoot
Now I cant login to the OS yet with default credentials as I need to load boot flash image. So, I have used my working readynas, I have inserted a blank disk and went to the GUI and restored the readynas to its default setting. This way boot flash image was loaded into the blank HDD. I have now inserted this HDD to non working NAS and while booting it picked up the image from the HDD. (likeby K20 - uBoot
So I did this way: nand erase.chip Marvell>> setenv serverip 192.168.1.3 Marvell>> setenv ipaddr 192.168.1.2 Marvell>> setenv gatewayip 192.168.1.1 Marvell>> tftpboot 0x000000000000 uboot.bin Using egiga0 device TFTP from server 192.168.1.3; our IP address is 192.168.1.2 Filename 'uboot.bin'. Load address: 0x0 Loading: ######################by K20 - uBoot
Thanks for the replay all, 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 I have bought another NAS (same model) and connected to the console and to see hows everything runs and try to replicate. I dont knoby K20 - uBoot
Thanks bodhi for your replay, The only recovery procedure they have got is to copy all the files to USB put the USB to front port and hold backup button while power on, the device this should automatically complete the recovery (firmware update) which I am doing from many hours with no success. I have found on netgear forum that this is a very common problem which happened to many users afby K20 - uBoot
Also I was wondering the way I wrote the uboot to the nand is correct? tftpboot 0x000000000000 uboot.bin nand write 0x000000000000 0 0x000000180000 The reason why I have asked you is that when I try to write below to other partitions in nand it just write to 0x0 which stopped the uboot boot on the next reboot and then I have to kwboot => nand erase.chip => tftpboot and then nand wby K20 - uBoot
Also I can get following files from ReadyNASOS-6.10.3-arm FW which is for my NAS model. csums.md5 initrd.gz kernel.arm u-boot-rn104-2.0.img initrd-recovery.gz uImage-recovery I think root.tlz is the FW itself which is 58.2MBby K20 - uBoot
Thanks a lot for your help bodhi , I really appreciate it :) Outputs are as follows: printenv Marvell>> printenv AC_Power_fail_detect=open CASset=min HW_version=MVT MALLOC_len=5 Manufacturer=NETGEAR NANDboot=nand read.e 0x2000000 0x200000 0x400000;nand read.e 0x1000000 0x7e00000 0x20000;nand read.e 0x3000000 0x800000 0x400000;bootz 0x2000000 0x3000000 0x1000000 Product=Reaby K20 - uBoot
I have no idea what to do next to restore it to OS6. Could someone please helpby K20 - uBoot
Good news :) I have manage to write the uboot to the Nand and now am currently able to boot from nand every time I power on Marvell>> setenv serverip 192.168.1.3 Marvell>> setenv ipaddr 192.168.1.2 Marvell>> setenv gatewayip 192.168.1.1 Marvell>> tftpboot 0x000000000000 uboot.bin egiga1 wait for link ....... no link (wait 6000 ms) egiga0 wait for link .Done -by K20 - uBoot
Also ran following commands for you to understand where I am currently. arvell>> mtdparts device nand0 <armada-nand>, # parts = 5 #: name size offset mask_flags 0: u-boot 0x000000180000 0x000000000000 0 1: u-boot-env 0x000000020000 0x000000180000 0 2: uImage 0x000000600000 0x000000200000 0 3: minirootfs 0x00000040000by K20 - uBoot
I have followed this https://forum.doozan.com/read.php?3,95249 I can't find any info on how to copy and write into mtd0 the original uboot from netgearby K20 - uBoot
Ran the following command on my Ubuntu machine kwboot -t /dev/ttyUSB0 -b ./uboot.bin -B 115200 -p Manage to load the uboot via kwboot now I don't know how to save uboot to nand so whenever NAS powers on it reads the uboot from nand instead of me booting up from kwboot Sending boot message. Please reboot the target...| Sending boot image... 0 % [............................by K20 - uBoot
Hi All, I hope someone can help me with restoring my NAS to its default readynas OS 6 The previous seller has installed Debian on it and I wanted to restore the NAS to its sock OS 6 and while I was doing that I have erase the entire nand chip by command: nand erase.chip Now whenever I power on my NAS I am getting following BootROM 1.20 Booting from NAND flash BootROM: Bad header atby K20 - uBoot