Help Center/ Cloud Container Engine/ FAQs/ Storage/ Why Does a PV Fail to Be Mounted to a Pod After the PV Is Re-bound to a Released EVS Disk?

Updated on 2025-07-17 GMT+08:00

View PDF

Why Does a PV Fail to Be Mounted to a Pod After the PV Is 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 it 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, resulting in a mounting failure.

Solution

Create a new EVS disk for future use.

Parent Topic: Storage

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot