This is an old revision of the document!
Q: After a crash, NAS4Free stops booting and I see “Run FSCK Manually” on the screen, what do I do?
Q: How can I fix file system damage that prevents me from mounting my UFS formatted drive?
Q: How do I fix the “WARNING: /mnt/MyStuff was not properly dismounted” errors that appear in the logs or at boot time?
A: You need to run FSCK to fix damage done to the file system. If you do not have experience with fsck ( probably true since you are reading this ) try one of these procedures. There are no guarantees, but with luck you will fix the problem.
Procedure #1 - This is the easiest and safest procedure, it is done entirely from the WebGUI, you can only use it if your server boots properly:
Procedure #2 - Is more difficult than the first but is still relatively easy and safe, it is done from the server console and then uses the WebGUI.
fsck_ufs -p /dev/YourDrivep1 &
fsck_ufs -p /dev/raid5/YourRAIDNamep1 &
fsck_ufs -p /dev/gmirror/YourRAIDNamep1 &
With luck, if everything is done right, any damage will be fixed. You should then be able to remove the CD, reboot, mount your drive / array and see your data again, if nothing else is causing the server to crash. If Procedures #1 and #2 do not fix your problem and you still cannot get to your data, it may be necessary to take extra steps or run other utilities only available in the console or CLI. Even experienced users may not have seen all the different circumstances and errors, so we strongly recommend that everyone learn more about fsck before trying to fix file system errors by reading the following:
Helpful, archived topics from old forum:
|Advanced||Basic storage concept||⇒18.104.22.168|