[CentOS] Recover from an fsck failure

Thu May 28 23:38:14 UTC 2020
Robert Nichols <rnicholsNOSPAM at comcast.net>

On 5/28/20 1:33 PM, James B. Byrne via CentOS wrote:
> /dev/mapper/vg_voinet01-lv_log
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the 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 alternate superblock:
>    e2fsk -b 8193 <device>

What output do you get from:

     file -s /dev/mapper/vg_voinet01-lv_log
     lsblk -f /dev/mapper/vg_voinet01-lv_log

Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.