Missing physical LVM2 devices from SAN due to failed devices on Red Hat Enterprise Linux
Issue
- While rebooting received error
fsck.ext3 No such file or directory while trying to open /dev/VolGroup01/LogVol00 The superblock could not be read or does not describe a correct ext2 filesystem. If device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternative superblock- Commented them out of the fstab so the server would come up and discovered that the server cannot see the physical volumes:
# pvdisplay -v Couldn't find device with uuid 9Z4CcL-acBD-juK0-Ostu-M5LG-mwqj-g4DPd2. Couldn't find device with uuid rjexwE-ClWN-0h7w-cMK2-BdTl-ZodB-O2Kh9j. PV unknown device VG VolGroup01 lvm2 [50.00 GB / 45.00 GB free] PV unknown device VG VolGroup01 lvm2 [50.00 GB / 40.00 GB free]
- Commented them out of the fstab so the server would come up and discovered that the server cannot see the physical volumes:
Environment
-
Red Hat Enterprise Linux
-
SAN-provided storage from an Enterprise-grade SAN via fibre channel.
-
device-mapper-multipath running on SAN volumes
- LVM physical volumes on multipath devices
- LVM volumes mounted at boot time via /etc/fstab entries
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.