I downloaded the file, unzipped and uploaded the file to the NV+... it says the file is good and I clicked on the update button. After it rebooted, it said "Flash verification failed" and it ran up on 4.1.8, which is the last version I have been able to successfully run on. I tried the USB boot with 4.1.12 and 4.1.13, both failed. 4.1.8 seems to be the only version my system likes. I recently took all the data off in preparation for upgrading to 1T drives (yea, behind the curve.. but it's mostly for home use) so I'm not worried about losing any data. I have 4 brand new WD 1T drives, and 4.1.8 seems to work nicely.
I have verified my system to be a NV+ v1 system, thanks to another forum post that showed the back of the system.
Any ideas on how to get a newer firmware version installed? Thanks! Mike
Do a System > Update > Factory Default then try the update via Frontview again.
How much RAM is installed in your NAS? The stock 256MB module or have you replaced it?
I still have the original 256m module installed. I have a Crucial CT12864x335 (1G) module standing by, but wanted to get everything running right before trying the memory upgrade. Since I have all new disks, I'll give the Factory Default thing a try when I get home tomorrow night.
StephenB wrote:
If you have SSH enabled, check the fullness of the OS partition.
If you don't have SSH enabled, then try deleting the logs (backup and system), and then update again from the web UI.
I don't recommend using the USB boot unless you have specific guidance from support, or someone like mdgm. It has some risk.
SSH is not enabled, don't have any logs being kept (that I know of)
Did the "factory default" update, rebooted and tried the update via frontview. The update failed: Problem encountered while updating your ReadyNAS device. It came up on 4.1.8.
I cleared the logs visible on the 'log' page and will try again... have no backup jobs scheduled (or listed) and see no logs there either.
Failed again. The system says the image is valid (Frontveiw > System > Update) but fails to properly install the image. On reboot, I get a flashing 1-4, then 3 and repeat... along with the pulsing power light. SO.. rebooted, USB flash back to 4.1.8
Just doesn't seem to like any other update than 4.1.8 (sigh). 4.1.10 failed (my other post) and 4.1.12 USB flash update also failed, reverted to 4.1.8...
So the 1GB upgraded memory still won't let you update your firmware, or play nicely with anything above 4.1.8? Has anyone gotten 1GB of memory to work with 4.1.13?
So the 1GB upgraded memory still won't let you update your firmware, or play nicely with anything above 4.1.8? Has anyone gotten 1GB of memory to work with 4.1.13?
I haven't upgraded yet, still running the original 256m module. Over the years of working on PCs and Servers, I have learned to not do multiple things to a machine at any given time. My priority was new drives (done), new OS (still having trouble) then upgrade the memory. Don't want to add something else to the mix that might cause the OS upgrade to fail 🙂
Level 3 support tried to update to 4.1.13 and it failed... I'm stuck at 4.1.8... they offered an RMA but I need the original receipt (like that's likely) so looks like I'm outta luck. Time for a new chassis or stay with 4.1.8 until it blows up on me.
My NV+ has 1GB. I had no problem with the 4.1.13 update. I did not add the memory. It was an upgrade package offered by the VAR I bought the unit from 5 years ago (eaegis.com who does not carry readynas anymore).
The problem on paflyer's system is that there are too many bad blocks on the internal flash. 4.1.13 won't fit on the good blocks so when it is written it is always corrupted, but as 4.1.8 is smaller it will fit.
mgdm, How do you determine if the issue is due to the bad blocks with internal flash issue? I have tried several times to upgrade and it always fails. I am on 4.1.12 now, and see issues with TimeMachine and my Mac. Would really like to get this 'fixed'. 😉
It's in the logs. Sent you a PM re a smaller build you could try that Skywalker built and I think worked for paflyer (can't remember for sure now though)
Thanks mdgm. I followed a different tact noted above to actually load the SSH enabler to get to the file system natively.
DF gave me 100% filled for / even though I had already cleared logs...There were two other logs PNP and one other (forgot which one) that were HUGE. No way to purge those logs without logging in via SSH. Once I deleted those logs, I was able to load in the 4.1.13 update.
Now to test and see if the TimeMachine backups are working correctly again.
Thanks again for the PM and response. You might pass along to skywalker that a more complete 'purge logs' button in the GUI would be good for noobs. Something that purges everything but security logs for example (gzips them at a minimum). I can pretty quickly work a UNIX/Linux file system, but I am sure that others are not as adept.
I am certain that overall performance will materially increase with now 67% of my root filesystem available. 😉
