This issue occurs when the virtual appliances experience file inconsistencies after being forcefully halted as the result of a storage failure, power failure, or software crash.
To resolve this issue, scan and correct the filesystem by running the fsck
command automatically (preferred) or manually.
- Reboot the virtual appliance, and immediately after the OS starts, press ‘e‘ to open the GNU GRUB Edit Menu.
- Locate the line that begins with the word
linux
.
Option 1
At the end of the line, add fsck.repair=yes
then press F10 to continue booting the appliance. This will force the default filesystem check to auto-resolve any issues. The appliance may silently reboot several times to fix needed issues.
Option 2
At the end of the line, add systemd.unit=emergency.target
then press F10 to continue booting the appliance.
1. Find the filesystems by running the following commands:
$ /bin/sh
$ /bin/mount
$ blkid
2. Run this command against the mount point that has issue:
$ e2fsck -y /dev/<mount>
The -y switch will fix the nodes automatically. Replace <mount> with the mount point experiencing the issue. Ex: $ e2fsck -y /dev/sda3
3. Power OFF the virtual appliance.
4. Power ON the virtual appliance.