Reference Guide

Dell - Internal Use - Confidential
Confidential Page 9 5/10/2016
Release Notes— Fluid Cache for SAN for Linux Systems
File Systems Table (fstab) Settings Prevent Server from Starting
ISSUE: The server can fail to boot because of errors related to setting non-zero fs_passno field
in the /etc/fstab file. Setting the force fsck option causes the system boot to fail. This is because
the devices do not exist at boot time when fstab is processed. When the error occurs, the
following message is displayed:
/dev/fldc0 is mounted. e2fsck: Cannot continue, aborting.
/dev/fldc1 is mounted. e2fsck: Cannot continue, aborting.
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
The sixth field (fsck option) is used by the fsck (8) program to determine the order in which file
system checks are done at reboot time. If the sixth field is set to zero, these system check errors
do not occur during reboot. Therefore it is recommended that for any fldc-related user entry in
/etc/fstab, the fifth field (dump option) and the sixth field (fsck option) are both set to zero. In
case the sixth field is not zero, it is very likely the above Linux error message occurs during
reboot.
WORKAROUND: Remount the root file system as read/write (mount -n -o remount, rw /) and
then comment out the Fluid Cache disk device entries from fstab, as shown:
#/dev/fldc0 /root/fldc/mnt ext2 defaults 1 3
Then change:
/dev/fldc1 /root/fldc/mnt2 ext2 defaults 1 4
either to:
/dev/fldc1 /root/fldc/mnt2 ext2 defaults 1 0
or to:
#/dev/fldc1 /root/fldc/mnt2 ext2 defaults 1 4