# LVM is not visible **URL:** \ **Category:** SLES Virtualization\ **Created:** [November 29, 2018, 5:30pm UTC](https://forums.suse.com/t/lvm-is-not-visible/33256 "2018-11-29T17:30:00Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Enthalpie](https://avatars.discourse-cdn.com/v4/letter/e/7ba0ec/32.png) [@Enthalpie](https://forums.suse.com/u/Enthalpie)\ **Post date:** [November 29, 2018, 5:30pm UTC](https://forums.suse.com/t/lvm-is-not-visible/33256/1 "2018-11-29T17:30:00Z")
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 ``` ---
**Author:** ![Enthalpie](https://avatars.discourse-cdn.com/v4/letter/e/7ba0ec/32.png) [@Enthalpie](https://forums.suse.com/u/Enthalpie)\ **Post date:** [November 29, 2018, 5:40pm UTC](https://forums.suse.com/t/lvm-is-not-visible/33256/2 "2018-11-29T17:40:11Z")
And the fdisk -l give that : [HTML] Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 \* 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: E527BF47-72CF-4FFF-ADAD-3ABFDEDBE916 Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 4225023 4208640 2G Microsoft basic data /dev/sda3 145756160 976773119 831016960 396.3G Linux LVM /dev/sda4 4225024 145756159 141531136 67.5G Microsoft basic data Partition table entries are not in disk order. [/HTML] with gparted dev/sda4 is my root partition in linux native id 0x83 avec un FS BtrFS ?? ---
**Author:** ![Enthalpie](https://avatars.discourse-cdn.com/v4/letter/e/7ba0ec/32.png) [@Enthalpie](https://forums.suse.com/u/Enthalpie)\ **Post date:** [November 30, 2018, 11:21am UTC](https://forums.suse.com/t/lvm-is-not-visible/33256/3 "2018-11-30T11:21:55Z")
Hi Any idea ? I have update the system to 15 , but i still got the problem when i edit the partition , i see sda3 , linux VM as no mount point is this normal Regards ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 3, 2018, 11:56pm UTC](https://forums.suse.com/t/lvm-is-not-visible/33256/4 "2018-12-03T23:56:16Z")
Hi Enthalpie, 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? Regards, J