[Problem Description]
A customer's host breaks down for unknown reasons. After the host is restarted, the system reports a super block access failure and a read/write error when accessing the VG. In this case, the storage system needs to analyze the cause.
[Symptom Description]
The following figure shows the error information reported by the host.
[Cause]
Faults on the host side are not described here. Generally, the cause is that the VG is not activated successfully.
[Location Method] and [Solution]
1. No I/O error is found in storage logs, which is irrelevant to storage.
2. Run the vgchange –an vgname command on the host to hibernate the VG.
3. Run the vgchange –ay vgname command to reactivate the VG.
4. The VG is successfully mounted.
[Post-Recovery Check]
Check whether upper-layer services are normal.
