Reboot the machine. Press a key on the " Press any key to see the boot menu " screen. The Check Point Boot Menu now opens. Select the "Start in maintenance mode". Enter the Expert mode credentials. Note: If you detect inconsistencies, ' fsck ' may require the user to remove the '-p' flag from the syntax. Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use. Hallo Forum, vielleicht könnt ihr bei folgendem Problem helfen. Der Bereich unter dev/mapper/pve-root läuft seit einer Zeit stetig voll. -cluster/config.db config.db-wal contains a file system with errors incorrect filetype memdb_open failed run fsck manually unable to open database unable to set wal mode unexpected inconsistency Replies After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into default mode. Then journalctl shows the followings: Raw. systemd-fsck: /dev/sdb1 contains a file system with errors, check forced. systemd-fsck: /dev/sdb1: Inodes that were part of a corrupted orphan How to fix the BusyBox (initramfs) boot problem on Ubuntu or Linux Mint. To resolve the problem, fix the Logical Volume Management (LVM) setting: Enter the root password on the "Give root password for maintenance" prompt. Click image to enlarge. Run "# fsck /dev/mapper/IWSVA-app_data" and answer the prompt with "yes". Wait for the process to complete. Click image to enlarge. Additional help? Ask in Forum run the filesystem check more specifically targeted at the filesystem actually present man e2fsck the -y option will allow you to run it with a response of "yes" to every question after all: you want to repair the filesystem if you don't / if you say "no" … the error will persist of course it will not be corrected because I've solved the issue. Here is how: vagrant up with GUI enabled; As soon as GUI open, keep pressing Right Shift, select "Advanced Options for Ubuntu" and then select "Ubuntu in Recovery mode" To recover a server file system, you will want to use the corresponding version of the CUCM recovery disk. Step 1 Start the system by using the recovery disk Step 2 From the recovery CD menu, select f to run file system check. Step 3 When the file system check completes, select q to quit the recovery CD. MWG appliance is based on a redhat compatible linux distribution. The file system check you saw there is part of the basic operating system. It During the boot, hold down the shift key so that the grub menu is shown. Select the " Advanced options ". Grub Advance Options. Then choose " Recovery mode ". Select Linux Recovery Mode. In the next menu select " fsck ". Select fsck Utility. You will be asked if you wish to have your / filesystem remounted.