Support Center > Search Results > SecureKnowledge Details
How to check the hard drive integrity in Gaia/SecurePlatform OS with the 'fsck' command Technical Level
Solution

Check the hard drive/partition integrity if you see an error that indicates:

  • Possible corruption of data on the hard drive
  • Failure of the hard drive partition (example: message "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY")
  • The partition's becoming read-only (check with "cat /proc/mounts" command)

Note: In kernel 3.10, Check Point supports EXT3 and XFS file systems,
Before proceeding to the next steps, check the file system type on your computer by running this command in expert mode:

# df -T

You will find the file system type in /dev/mapper/vg_splat-lv_current (below the "Type" column).

Note: XFS is a journaling file system. It does a self file system check on each boot. If needed, it repairs and fixes possible disk corruptions automatically.

However, if you wish to check/repair the XFS file system manually, follow the steps below, but mind steps 7-8 accordingly.

Note: During the boot process, you will see a screen with this message:

Press any key to see the boot menu [Booting in 5 seconds]

Be ready to press a key! If you do not press a key, the system will require a full boot-up and another reboot.

 

To check the integrity of a hard drive in the Gaia/SecurePlatform OS:

  1. Connect to the machine over console (serial).

  2. Reboot the machine.

  3. Press a key on the "Press any key to see the boot menu" screen. The Check Point Boot Menu now opens.

  4. Select the "Start in maintenance mode".

  5. Enter the Expert mode credentials.

  6. Unmount the file system:

    # umount -a

  7. For the EXT3 file system, run the applicable 'fsck' commands (skip this step if you have a XFS file system):

    1. Check and update the bad block list, but do NOT repair:

      # fsck -f -n -C -v

    2. Repair automatically:

      # fsck -f -p -C -v

      Note: If you detect inconsistencies, 'fsck' may require the user to remove the '-p' flag from the syntax. In such a case, use the 'fsck -f -y' command instead to assume 'yes' to all questions.

      # fsck -f -C -v -y
  8. For the XFS file system, run the relevant 'xfs_repair' commands (skip this step if you have an EXT3 file system):

    A.Determine which file system you want to check/repair:

    # df -T

    You must specify the selected file system in the next sub step.

    B. Check and update bad block list, but do NOT repair:

    # xfs_repair -n /dev/mapper/vg_splat-lv_log

    (replace "/dev/mapper/vg_splat-lv_log" with the desired file system)

    C. Repair automatically:

    # xfs_repair /dev/mapper/vg_splat-lv_log

    (replace "/dev/mapper/vg_splat-lv_log" with the desired file system)

     
    Important Note
    Running xfs_repair on mounted file system (such of lv_current) is not recommended, and may result in unexpected behavior. Make sure you back up the data present in the filesystem before you repair the mounted filesystem.
    If you wish to proceed on a mounted file system, specify the "-d" flag:
    # xfs_repair -d /dev/mapper/vg_splat-lv_log

9. Synchronize data on disk with memory and reboot the machine:

      # sync ; sync ; reboot

 

Related solutions:

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment