Critical EXT4-fs errors on dm-10 after boot — System in Emergency Mode

[RJ-4816]

Hello,
I'm facing a critical issue with my Proxmox VE (node pve01). After a reboot, the system failed to mount local file systems and entered Emergency Mode.
Storage Setup:

• Storage: External SAN (Infortrend) connected via Fibre Channel (FC).
• Configuration: Multipath is enabled.
• Partition: LVM on top of multipath device, formatted as EXT4.
• Target: /mnt/INFTIv01 (mapped to dm-10).

The issue:
The boot screen shows multiple EXT4-fs error (device dm-10) messages and bad block bitmap checksum. I have verified the FC connections and multipath status — everything looks fine on the hardware/transport level.
Current state:
I am in the root shell (emergency mode). I am hesitant to run fsck manually because I am afraid of data loss on this volume.
I have attached a photo of the monitor with the full error trace. What is the safest procedure to recover the filesystem in a Multipath/FC environment? Should I try fsck -n first to see the damage?
Thanks in advance!

---

 

[bbgeek17]

Hi @RJ-4816 , welcome to the forum.

There are two ways to go about this:

a) If available, use your array Snapshot and Clone capabilities to create an identical copy of your LUN's data. Then experiment on it with data recovery.
b) Create a LUN of a similar size, "dd" the data over and experiment with data recovery.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox