This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
old firmware manually updated to newest now stuck in booting
I picked up an old ReadyNAS running firmware 6.1.9. I wasn't able to connect to the internet with it so I downloaded the latest firmware and did a manual update. I failed to see the note saying it should be a stepped update to certain firmware versions first. Now the unit seems to be stuck at 'booting'. It says not to load older FW versions, so I'm not sure where to go from here. Any help would be appreciated.
Re: old firmware manually updated to newest now stuck in booting
In most cases, the warning about going backwards only means for retaining an active volume. If you don't mind starting over, you can usually go backwards without an issue by first doing a USB recovery then a factory default without allowing the NAS to boot in between.
But, the reason for the warnings on those specific updates is not known to me, and I can't recommend you try it. If those updates also mess around with the U-Boot, then it's not the usual case.
Re: old firmware manually updated to newest now stuck in booting
In most cases, the warning about going backwards only means for retaining an active volume. If you don't mind starting over, you can usually go backwards without an issue by first doing a USB recovery then a factory default without allowing the NAS to boot in between.
But, the reason for the warnings on those specific updates is not known to me, and I can't recommend you try it. If those updates also mess around with the U-Boot, then it's not the usual case.
Re: old firmware manually updated to newest now stuck in booting
Thank you for the reply. I was able to get it to boot back on the 6.1.9 and factory reset it. Still can't connect to the internet but I can take it from here. Thanks again.
Re: old firmware manually updated to newest now stuck in booting
Not connecting to the internet probably means that the DNS settings are not set correctly. If you set a static I.P. you need to make sure that DNS servers are specified correctly.
