Help Center/ Cloud Container Engine/ FAQs/ Storage/ Why Does a PV Fail to Be Mounted to a Pod After Being Re-bound to a Released EVS Disk?
Updated on 2026-01-05 GMT+08:00
View PDF
Share

Why Does a PV Fail to Be Mounted to a Pod After Being Re-bound to a Released EVS Disk?

Symptom

When an EVS volume is mounted to a pod, the error message "wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error" is displayed.

Figure 1 Error message example

Possible Cause

The file system type of the underlying EVS disk must match that of the PV when the PV is first bound to a pod. If a released EVS disk is re-bound to a PV, the PV's file system type must remain consistent with the original PV. If the file system types do not match, CCE detects inconsistencies between the PV file system type and the disk file system type, which results in a mounting failure.

Solution

Create a new EVS disk for future use.

Parent Topic: Storage