NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas Duo V2 - u-boot doesn't boot any more - SOLVED
Hi,
I had a lot of fun with the DuoV2 installing Debian. :D Everything worked well until I tried to modify the u-boot-env to automatically boot my kernel and system.
(I know I void my warranty with doing this. But it's worth it, as it would be a great server. I don't want to do anything evil, I do it just because I like tweaking)
Now u-boot stops at printing "net: egiga [PRIME]"
This text never appears: "Hit any key to stop autoboot:"
So there is no way to get the u-boot console and fix the u-boot-env.
I already succeeded in switching Bootstrap 1.21 into debug-mode or boot-from-uart-mode.
I uploaded the stock u-boot image where I replaced the NAND header with a UART header using your doimage tool.
Well, it booted the same way, since it's the same binary. Stopped just before the autoboot. :(
It was a bunch of work to get to this point. But now I'm stuck. :?
Could you please give a hint on any of these questions?
Thank you very much, you would make me very happy!
JPT
I had a lot of fun with the DuoV2 installing Debian. :D Everything worked well until I tried to modify the u-boot-env to automatically boot my kernel and system.
(I know I void my warranty with doing this. But it's worth it, as it would be a great server. I don't want to do anything evil, I do it just because I like tweaking)
Now u-boot stops at printing "net: egiga [PRIME]"
This text never appears: "Hit any key to stop autoboot:"
So there is no way to get the u-boot console and fix the u-boot-env.
I already succeeded in switching Bootstrap 1.21 into debug-mode or boot-from-uart-mode.
I uploaded the stock u-boot image where I replaced the NAND header with a UART header using your doimage tool.
Well, it booted the same way, since it's the same binary. Stopped just before the autoboot. :(
It was a bunch of work to get to this point. But now I'm stuck. :?
Could you please give a hint on any of these questions?
- Can I use the bootstrap debug console to fix the u-boot-env? How?
- The J1 10 PIN connector. Is it JTAG and what is the pin-out?
- Is there any other way of fixing the u-boot-env?
Thank you very much, you would make me very happy!
JPT
15 Replies
Replies have been turned off for this discussion
chirpa wrote: Does this help at all?
Jepp. It does. Thanks.
At least I am able to get a u-boot console again. But I wasn't able to restore the default boot process yet. Do you have a working uboot.bin?
It boots and writes u-boot-env:Unlocking flash...
Done
Erasing old environment...
Done
Writing environment to /dev/mtd1...
Done
Locking ...
After that it wrote kernel and initrd.
Next boot, still the same problem. I tried to supply uboot.bin as well but it now complains:Searching for internal boot flash device...mtdblock4
Searching for external boot flash device...sda
Writing internal nand flash device...ERROR: flash image checksum does not match!!
The uboot.bin I used was an image I read from /dev/mtd0. It should have the 512 byte nand header but it does not have the 4 byte checksum at the end.
I created another u-boot image by stripping the header and applying again using doimage. this one is 4 byte larger and should have a checksum.
But it still complains about wrong checksum.
Oh no!!! I have to strip the final 4 bytes as well before applying doimage. And I cannot use the image read from /dev/mtd0 because there is a lot of garbage at the end!
I created a UART version from the uboot.bin you provided and successfully uploaded it.
But it only says:...
NAND:128 MB
Switch On !
That's it. Are you sure it should work on the Duo V2? I would like to know before I copy it to the USB drive and burn it into NAND.
BTW: the howto says you have to format the USB drive from linux. this isn't true. I did from WinXP without problems.- What about this u-boot?: https://www.readynas.com/contributed/mdgm/files/arm/5.3/uboot-DUO-1.0.06
This is the u-boot included in 5.3.7.
You would need to rename it e.g. to uboot.bin
The u-boot from the beta would be older. I wouldn't recommend using the beta u-boot. Please also note that this u-boot is just for the Duo v2. The NV+ v2 uses a different u-boot. - Now booted my debian system manually from the USB drive rescue boot console. Read the mtds to disk:
- uboot is a different version than before (V1009 instead of V1008. No idea how this got written)
- the uboot-env still seems to be the same than before. The USB recovery did not write anything to uboot-env. No wonder there are no changes in default boot behavior.
- kernel and initrd are stock. fine.
- jffs2 is completely different. is this the raidiator? - Well, unimportant.
May I write the old uboot-env usingsudo dd if=mtd1.orig of=/dev/mtdblock1
Or should I try to fix it using fw_setenv? - Ok, forget the question. For writing to mtd you have to use mtd-tools.
But I used fw_setenv for now. let's see what happens... - Boots fine into my debian system now.
I restored my 3.8.x kernel into ROM and fixed the uboot-env by manually setting BOOTARGS and BOOTCMD to the correct values.
The USB emergency boot is a fine way to solve more or less ANY boot problems. I'll add it to my guide on installing debian. - Hello,
I have the same problem, but i had the ReadyNas Duo V1 with Sparc CPU. Can you send me the right boot files??
And can you write your steps to, connecting your PC to NAS with Console.
Many Thanks
Nik - What exactly did you do diamond? The Duo v1 is a very different device to the Duo v2. You should not try stuff like this for the v2 on the v1.
- Hello,
I'm honest, I've done with the console on an apt-get update and upgrade. (I think this was not good)
Then I couldn't log on to my NAS-.
I've tried using the Funktions OS-Reinstall, Factore Default, USB boot, TFTP boot, everything reset again but without success. Then I turned off the moment during the current installation.
Now, all LED's don't working anymore, included the LAN. However, I can turn on the NAS with the power button, nothing more, and the fan working on the max. speed.
I have now ordered a TTL-USB converter that comes on Thursday. I hope I can use it to revive the NAS.
I also Install on a other PC an Linux distribution.
My NAS habe following Nummer: ReadyNas Duo, RND2110 (Sparc Prozessor)
Can you help me ?? - If the bootloader was being overwritten when you powered off the NAS you probably bricked it.
If you had asked I would have told you that USB Boot Recovery and especially TFTP Boot Recovery were pointless steps to try to fix your problem. If anything they would only make it worse.
If an OS Re-install didn't fix it, the next thing to try would have been to get remote assistance to fix it.
A factory default should have fixed it but would have wiped all data, settings, everything.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
