Stopped loading centos and doesn't want to mount lvm, what to do?

Question

linux

In the morning, the server gave out that it did not want to work, after the reboot it stopped loading at all with an error:

mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg_libra-lv_root,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.

because The system on a flash drive connected it to a stationary device and decided to mount it, but it doesn’t want to mount it in any one, it gives the same thing.

[email protected]:/home/user# dmesg | tail
[18071.253708] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[18071.253710] sd 10:0:0:0: [sde]
[18071.253711] Sense Key : Data Protect [current]
[18071.253713] Info fld=0x0
[18071.253715] :0:0:0: [sde]
[18071.253716] Add. Sense: Write protected
[18071.253718] sd 10:0:0:0: [sde] CDB:
[18071.253719] Write(10): 2a 00 00 50 99 08 00 00 10 00
[18071.253737] JBD2: recovery failed
[18071.253742] EXT4 -fs (dm-0): error loading journal

pvscan
PV /dev/sde2 VG vg_libra lvm2 [3.25 GiB / 0 free]
Total: 1 [3.25 GiB] / in use: 1 [3.25 GiB] / in no VG: 0 [0 ]
lvscan
ACTIVE ' /dev/vg_libra/lv_root' [2.73 GiB] inherit
ACTIVE '/dev/vg_libra/lv_swap' [528.00 MiB] inherit
blkid
/dev/mapper/vg_libra-lv_root: UUID="f6ef2d43-2ad2-47df-95c7 -45c507ddceaa" TYPE="ext4"
/dev/mapper/vg_libra-lv_swap: UUID="5098012a-83eb-4ea9-9ba5-506962c68f04" TYPE="swap"
fsck.ext4 -f /dev/sde2
e2fsck 1.42.12 (29 -Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sde2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

Answer 1

Apparently, it was necessary to activate the volume and already check it ... and did so, the result was not encouraging again (
2fsck -f -y /dev/mapper/vg_libra-lv_root
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/vg_libra-lv_root: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
run journal anyway? yes
e2fsck: unable to set superblock flags on /dev/mapper/vg_libra-lv_root
/dev/mapper/vg_libra-lv_root: ********** WARNING: Filesystem still has errors ******** **