RAIDiator Version 4.1.14 (Sparc) Checksum Error

Hello. I have a ReadyNAS NV+ and was trying to install the RAIDiator 4.1.14 update based on the email I received indicating my system needed to be updated.

I tried to use the remote update option--which is how I normally have done updates in the past--However, I received an error that the update cannot access the remote server. I then tried downloading the image and installing locally.

After downloading the file, I tried to complete the upgrade but received the checksum error. Similar to the posting below from MAF1 from last October 19, I then started receiving an error trying to access the NAS shares via windows even though Frontview access remained. I changed and reset the IP address, used Net clear to remove the links and then disabled and re-enabled the CIF access as I figured they might have gotten corrupted somehow. That seemed to correct the access issues as I can now see the shares again via windows. However, I am still getting the checksum error and am still unable to connect to the remote server. The latter issue is odd as the alerts and other network traffic to/from the device seem sound. Too, all configuration items match exactly to what my other ReadyNAS devices have which I recently updated remotely with no problems.

From the notes below I gather one possible issue is that the OS partition may be full. I have cleared the logs but to no avail. Per the comments below, there is apparently no way to clean out other space without doing a system reset. While I have backups on other NAS drives and could complete a rebuild, I am a bit reluctant to do that if there is another option.

While I don't see the update as critical, I would like to try to load it if possible. Hence, any assistance troubleshooting would be appreciated.

Thanks.



Re: RAIDiator Version 4.1.14 (Sparc) Checksum Error

Unread postby maf1 » Sun Oct 19, 2014 3:32 pm

I tried loading the v4.1.14 update and got the same result. Then downloaded the update again and got the same result again, invalid checksum. I now have the problem where I my shares on the NAS are no longer working. Selecting a share from Windows Explorer I get the error message:"The specified network name is no longer available". I am able to ping the NAS drive using both the device name and the IP address, but I can't connect. I am able to access the Admin page, although I'm concerned as the status logs only shows the entries from when I tried to update the new firmware.

do you have ssh enabled?

Yes. I have Cygwin installed.

beichst wrote:
Yes. I have Cygwin installed.

I think you misunderstood.

I was asking if you have ssh enabled on the ReadyNAS.

Sorry. My misunderstanding :-) No, I don't have SSH enabled on my ReadyNAS. I have never had a need to use root access or anything other than Frontview to complete what I have needed to do.

One option is to contact Netgear support. They will charge, but should be able to clean out the OS partition remotely.

You could try installing the enablerootssh addon, and see if that takes. If so, you can then use putty (or terminal on the mac) to connect to the NAS. If it is a full OS partition, it can easily be fixed at that point.

StephenB wrote:
One option is to contact Netgear support. They will charge, but should be able to clean out the OS partition remotely. You could try installing the enablerootssh addon, and see if that takes. If so, you can then use putty (or terminal on the mac) to connect to the NAS. If it is a full OS partition, it can easily be fixed at that point.

I am a bit concerned about installing the add-on as I understand ReadyNas may withdraw support. Is that correct? However, I have rooted other devices before so am familiar with the general process. If I do proceed with that process, you have indicated I should be able to clear the full partition. How would I know what to look for in cleaning it?

Too, I am assuming once I install it, it is not simply going to be in the installed add-ons tab. How would I remove it?

Thanks.

Technically they can, (and they likely would if you deleted stuff in the OS partition that you shouldn't). They've said here that they won't deny support unless there is evidence that you did damage with ssh. If you purchased on your join date, your NAS is out of warranty, so support might not be an issue anyway.

Uninstall information is in this old thread: https://www.readynas.com/forum/viewtopi ... 36&t=57594

Once installed (assuming success, which is not guaranteed in your case) you can look for large log files, and delete them. If you have ReadyDLNA installed on the NAS, you can disable that, and also check with ssh that the database has been deleted. Note there is is a separate add-on that will move the ReadyDLNA database to the C drive in order to prevent it from taking up precious OS partition.

If you aren't sure that something is safe to delete, just post back here.

Thanks StephenB.

Yes, it would have been my join date. Hence, you are probably right about the support being gone anyhow :D So you are indicating pretty much any large file in the log area can be deleted? interesting. I would assume anything that is prior to this year would also be considered removeable? I will have to keep that in mind.

Too, thank you for the uninstall information. However, as some good news (to me at least :D ) I will not be needing it at this point. After getting the error again, I tried doing a shutdown/reboot with a full disk quote and share check. It didn't find any errors. However, I then also changed the IP again and cleared all network cache on both my server and my router, did a reboot and restart. Finally, I disabled all services on the system and rebooted the system one more time. I then tried the online update and voila, was able to get that to work. The system is now showing in RAIDArray as updated to Radiator 4.1.14 with the new IP address. I am also still able to see all data shared. I am currently in process of re-enabling all my services (e.g. DLNA). Once that is done, I should be pretty much back to status quo but on current Radiator.

From your notes below about disabling DLNA, I am guessing that it was the DLNA service that might have been the issue in taking up space. You have indicated there is an add-on which can move the DLNA DB to the C drive. Would that be: ReadyDLNA_1.1.1.2.bin? If so, I might try implementing that as well so that the next time I need to complete a firmware upgrade I won't have this problem.

Thanks again for all the advice/help. I really appreciate the time.

beichst wrote:
From your notes below about disabling DLNA, I am guessing that it was the DLNA service that might have been the issue in taking up space. You have indicated there is an add-on which can move the DLNA DB to the C drive. Would that be: ReadyDLNA_1.1.1.2.bin?

No, its the cachedir add on here: https://www.readynas.com/forum/viewtopi ... 15#p392371

ReadyDLNA logs can also get quite large.