NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 214 data corruption issue
I am seeing a very strange behaviour that results in corrupted files. My NAS (ReadyNAS 214) has been stable for years, until recently I found a single file had an error revealed via the logs followin...
I have been having the same issues, RN204 corrupting excel and word docs, you guys seem way more techie than me, does anyone have a fix, or a recovery option? everything i have tried has not repaired the files.
this is what i get...
You should store your files on an additional device for now, i.e. your PC local drive.
I found existing files already on my NAS in general did not get corrupted, only files edited or newly added. I did find copying a file within the same directory on the NAS also corrupted both the source and copy, so avoid that action.
Once a file is corrupted, you will need to go back to a previous good copy from another device. The corrupted files appear unrecoverable. Luckily I did have a backup, and I noticed this problem within a day or two, so could recreate what I needed.
Which version of the OS are you running, i.e. have you recently upgraded?
Have you changed anything else recently?
I decided to rebuild my NAS from factory defaults, and now I'm restoring files - around 7.5TB, so it will take a few days. My NAS seems stable since clearing it, not ideal, and for sure there may still be an underlying issue that I've not seen yet on the rebuild.
While I have no solution, I have an idea of where to look for the problem. Excel (and all Microsoft Office products) create a temporary file in the directory (and thus on the device) from which they were opened. Further, when saving a modified file, they concatenate (not combine) changes with the original, saving an original plus changes instead of a modifed original. So if something happens to that temporary file (which is set as invisible and starts with a tilde (~), at least on a Windows machine, which may or may not be pertinent), the end result can be a corrupted file. Or. if the last part of the saved file, which has the changes, is not properly saved, the entire document can also be corrupted.
This would not seem to explain the issue with "newly created" Excel files, but if you save as you go (manually or automatically), it could still have the original plus changes format.
This experiment might help get to the bottom of it: Copy a file that was created on a local drive to the NAS. Open and make a minor modification to the file on the NAS and save. If you then find the modified file to be corrupt, do a binary compare of the original on the local device to the corrupt one on the NAS.
As a not-so-great work-around, I believe using "save as" always creates a new original, not an original plus changes. (I know it used to, but I've not checked recently).
Sandshark wrote:
While I have no solution, I have an idea of where to look for the problem. Excel (and all Microsoft Office products) create a temporary file in the directory (and thus on the device) from which they were opened. Further, when saving a modified file, they concatenate (not combine) changes with the original, saving an original plus changes instead of a modifed original. So if something happens to that temporary file (which is set as invisible and starts with a tilde (~), at least on a Windows machine, which may or may not be pertinent), the end result can be a corrupted file. Or. if the last part of the saved file, which has the changes, is not properly saved, the entire document can also be corrupted.
If I remember correctly, there have been similar symptoms with some Macs related to the use of "apple fruit"
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
