IBM Support

fsck error fix instructions

Question & Answer


Question

What is the best practice when I see the  error in a pod ?
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.\n\t(i.e., without -a or -p options)

Answer

=========fsck error fix instructions========
If you get below Error message during POD volume mount, then the Disk is corrupted and can't mount.
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.\n\t(i.e., without -a or -p options)
OPTION1 : FIX Automatically VIA Block-driver
==============================================
1. $ kubectl patch pv PVNAME -p '{"metadata": {"annotations":{"ibm.io/autofix-fsckErr":"true"}}}'
2. $ kubectl get pv PVNAME -o yaml | grep "ibm.io/autofix-fsckErr"
3. Also Try delete and recreate POD and Let the pod go through attach and mount flow again.
4. kubernetes will retry mount operation in few minutes and the block driver will try to autofix based upon this flag.
5. We suggest to remove this Annotation "ibm.io/autofix-fsckErr: true" from the PV after your error gets resolved and POD comes to running state
6. $ kubectl edit pv PVNAME
Remove "ibm.io/autofix-fsckErr: true" under the annotation section and Save
==============================================
Note: The linux command used by block-driver to autofix fsck error is "$ fsck -y DEVICEPATH"
And “-y” option does a accept-all . if User want to manually respond y/n to “fsck”, they can also run this command manually from worker Node.

[{"Line of Business":{"code":"LOB61","label":"IBM Technology Lifecycle Services"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGMV159","label":"IBM Support for Red Hat OpenStack Platform"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
12 August 2021

UID

ibm16365019