Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on the environment.
fsck
command automatically (preferred) or manually.
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.
By running pam_tally2 -u root via SSH on each node after we were able to get logged in, we determined that the Lockouts were coming from Solar Winds.
service loginsight stop; umount /storage/core; umount /storage/var
e2fsck -y /dev/mapper/data-var
e2fsck -y /dev/mapper/data-core