Hi
On a Suse entreprise server , after update the LVM is not visible in the libvirt manager
commande pvscan give that
[HTML]
PV /dev/sda3 VG XSLocalEXT-1cd2eec0-d9ab-c8b4-64f5-08a6f99e3633 lvm2 [396.25 GiB / 396.25 GiB free]
Total: 1 [396.25 GiB] / in use: 1 [396.25 GiB] / in no VG: 0 [0 ]
[/HTML]
command lvs return nothing
I have try and vgchange without success
and commande e2fsck said i have bad block , but it is normal , this is not a partition with ext4
[HTML]
linux-udsf:~ # e2fsck /dev/sda3
e2fsck 1.42.11 (09-Jul-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks…
e2fsck: Bad magic number in super-block while trying to open /dev/sda3
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
[/HTML]
could you help me ?
edit : i did'nt see any entry in fstab for this
I could not yet see what the actual error is - you wrote “after update the LVM is not visible in the libvirt manager”. Could you please be a bit more specific on what you’re trying to do, what you expected and what you got instead?
Your actions on /dev/sda3 don’t seem to get you anywhere - running fsck on a PV is not helpful and might even harm things, had it decided to try to “correct” things. How much are you into details of LVM? I’d have expected you to run “lvs” to see a summary of available logical volumes, which are the “block devices” that you’d use to i.e. put file system on.
But again - what’s it you expected to see in virt-manager that’s you found missing or wrong?