File system errors can be caused by power outages and disconnects that prevent the file system from completely writing the data to the RAID array. It can also be caused by problems with hardware, system crashes and drivers. This will result in file system being left in an inconsistent state. With the file system in this state you can see a variety of issues ie: Loss of all shares, slow data transfer and if not repaired, it could result in a loss of data.
Running file system repair will resolve these issues. Linux does perform a file system check on startup system performs a check at each bootup, however it is rather perfunctory.
In order to run file system repair you must run a memory test on your system to determine if you have any memory errors. If you run the FS repair without knowing you have memory errors, the repair can damage your data. If the memory test comes up clean, you can then run the File system repair.
To run the memory test, restart your 3945N LSS with keyboard, mouse and monitor connected. Then, right after the system performs POST, hit ‘Esc’ and you’ll get options to run the test. It’s best to let the memory test run until it’s completed.
To run the FS repair, go to the Console Extended Tools after the system has booted to the main screen below showing its IP Address(es):…
Hit Ctrl-Alt-X to open the Extended Tools Menu, then select Repair File System on LV (Logical Volumes)
After the process is finished reboot your machine.
NOTE: When running file system repair the volumes will be unmounted and the shares not available for use. Increasing the amount of RAM will increase the speed of the file system repair.
NOTE: You can run RFS (Repair File System) only on NAS volumes.
NOTE: RFS (Repair File System) may move some of your files to lost+found folder. You may access this folder by creating a share that is pointing to the root of LV.