Re: Recover from an fsck failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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.

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux