User Tools

Site Tools


faq:0001

Q: After a crash, XigmaNAS 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:

  1. Backup your configuration file.
  2. Run fsck from WebGUI Tab> Disks > Mount Point > Fsck. Make sure you selectUnmount disk/partition”, read and understand all notes and warnings on this Tab.
  3. Note or copy / paste any output for future reference.
  4. If you see “ FILE SYSTEM CLEAN ” then you are done, file system corruption should now be fixed, try to mount and use your file system again.
  5. If you get no output, an error or don't see “FILE SYSTEM CLEAN”, and your problem is not solved, try the next procedure.

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.

  1. Make sure you know and understand your XigmaNAS configuration.
  2. Backup your configuration file, then shut down your server.
  3. Remove floppy or USB stick If you are using one to store your configuration file.
  4. Boot system from LiveCD and configure network for temporary access.
  5. Add your disks carefully, make sure you specify how they are already formatted. Under no circumstances should you reformat your disks.
  6. Do not mount any file systems.
  7. If you do not have a RAID array, then from WebGUI Tab> Tools > Execute Command run:
    fsck_ufs -p /dev/YourDrivep1 &
  8. Do this until you see “FILE SYSTEM CLEAN; SKIPPING CHECKS”.
  • If you have a RAID5 array, recreate your array, giving it the original name and the original disks, in the original order, do not check the “Create & initialize” box, then from WebGUI Tab> Tools > Execute Command run:
     fsck_ufs -p /dev/raid5/YourRAIDNamep1 &
  • Do this until you see “FILE SYSTEM CLEAN; SKIPPING CHECKS”.
  • If you have a RAID1 array, recreate your array, giving it the original name and the original disks, in the original order, do not check the “Create & initialize” box, then from WebGUI Tab> Tools > Execute Command run:
     fsck_ufs -p /dev/gmirror/YourRAIDNamep1 &
  • Do this until you see “FILE SYSTEM CLEAN; SKIPPING CHECKS”.

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 ⇒9.0.0.1
faq/0001.txt · Last modified: 2018/08/10 20:56 by zoon01