What causes a 'Failed Writing!' error in tftp??

I'm replying to this in case anyone else attempts to search here in futility for the answer, as I did.

I don't know what causes it, but I had the exact same program, and opening Raidar (annoying, as, of course, I had the ReadyNAS 600 hooked up to an old system, directly, to do the crap with 192.168.125.1).

My eventual solution, since I couldn't get ANY firmware to work via tftp, was to yank the CF card (I took whole unit apart; I needed have; little plate with two screws near bottom leads directly to it...), toss in a card reader, and use NTRawrite to copy the older firmware to CF card.

Then, with CF card back in ReadyNAS, applied power, with paper clip in 'secret' spot... for way way more than 5 seconds, until the very first steady blink... after which, Raidar (after displaying 'file system check') showed the old version 3, and allowed me to log in.

As I type this, I'm not sure if my data's still there, but at least mine's no longer a brick.

I don't think you can downgrade to RAIDiator 3 without wiping all data the NAS.

chirpa is a good with links to old firmware versions.

I don't know what options there are for writing 3.x to the 600's CF card.

Just experienced this error with my X6 Rev B. Luckily I found this thread, replaced the CF that came with the unit (PN IT19-1-1100-0) originally with a 128MB and that accepted the 4.1.7 Radiator image using an application called Win32DiskImager (which works well with Windows 7)

As background, I had upgraded successfully to 4.1.7 via Web Interface and the system had been working fine for a month. I wanted to eek the last ounce of disk performance from the unit and decided to back everything up and go for a factory restart. All seemed fine. Until I got the 1&3 alternating blinking lights (orange or yellow) and a slow flashing blue power light.
Tried TFTP on the 2nd LED blink which succeeded to transfer but did not reboot (power on/off required). USB Boot 4.1.7 did not work either.

Saw this thread, noticed comments about space and decided to use 128MB SanDisk CF, wrote the image, all tickety boo.

Looks like this problem could occur often for those of us with the older (infrant) Readynas'

I had the same issue and this string saved me...
For the next person here is more info:

I have a Readynas 600
I needed to upgrade the firmware via the CF compact flash card. I am on windows 7.

1) Find applicable FW from Netgear redinass support. Here is a link to FW pages as today: http://www.readynas.com/?cat=8
I used this: Just released – RAIDiator 4.1.8 September 9, 2011
2) Download to your PC
3) Use this program to copy to your CF card: (Image Writer for Windows aka win32discimager): https://launchpad.net/win32-image-writer/+download
4) open Image Writer and browse to location of FW file. In browse dialog box, change file type from ".iso" to "*.*" so it sees the FW file, which is not an ISO file)
5) With CF card in reader on pc, in Image Writer select CF card drive letter as destination
6) Click ok

Image writer will copy RAW FW file to CF card. (Windows will say format CF card DONT DO THAT)
7) Eject CF card from PC and put in ReadyNas
8) Start ReadyNas with at least 1 HDD installed.
9) Locate NAS in RAIDar (From Netgear)
You should see the nas and its status and all should proceed.

Note I think for newer FW, need to have min 256-500 mg CF card. I used 4gig, since its what I had. The existing CF cards w ReadyNas 600 may be too small to hold the FW, which is why if you updated via the NAS, it was not saved to the CF card if you replaced the HDDS or other things.

Hope this helps...

For me, finding the program to copy the FW to the CF card was the issue. Image Writer solved this!!