RAIDiator Version 4.1.14 (Sparc) Checksum Error

surreyalan it appears that one of your disks is bad.

As instructed, I removed Disc 2 where 5 ATA errors were showing, and rebooted. Radar still shows NAS as Booting, and in the Drives sector, two green dots show both drives, even though Drive 2 has been removed from the NAS and is sitting on my desk!

Rebooting the NAS now. It should hopefully update to 4.1.14.

I did see some weird things on your OS partition.

You had a huge 152MB /var/log/leafp2p.log (though that hadn't been changed since February 2012 so I emptied it) and you had a lost+found directory of 558MB on the OS partition.

What would have caused those things? Anyhow, the NAS has now booted and all is well. I will back up all my vital data and then put a new drive into the now empty Bay2, and let the system rebuild itself. Thanks again mdgm for all your assistance. I use my NAS as a backup device to my destop pc and two laptops. I suppose one can't have too many backups. It is a great relief to have access to all my data once again. BRILLIANT SUPPORT, THANKS!

You're welcome surreyalan

The first one could have been caused by lots of messages in a short space of time for ReadyNAS Remote, though it is odd that it wasn't pruned.

The second suggests filesystem issues with the OS partition.

If you have a good backup it may be prudent after you have done a backup and verified your backup is good to start afresh with a factory default (wipes all data, settings, everything) with two good disks.

Tried updating the firmware remotely, but was told that v4.1.13 was the latest version. Was able to update to v4.1.14 using a local copy of the downloaded firmware.

Thanks for the assistance provided.

That is odd. I guess your NAS must have cached the update check info from the update server.

vandermerwe wrote:
Have you downloaded the zip file again? Have you unzipped the file?

Yup, tried re-downloading. Same issue. Looking for a mirror perhaps to download from.

Spunk wrote:
Recommended practice - after unzipping the update, run an MD5 checker on the extracted update file. The zip includes an MD5 file that shows what it should be. Suggestion - use Nullriver's freeware WinMD5Sum.

Thanks for the link to the freeware!! Checksum checks out prior to upload to the 1100. Then upload works but once the update process starts and it does its own checksum check, it fails the check by the OS.

gheatly there are reasons this can happen. Sent you a PM.