LVM is not found on /dev/sdx "Device /dev/sdx not found (or ignored by filtering)."

Solution Verified - Updated -

Issue

  • LVM disk is not found on local disk /dev/sdb after reboot

  • Booted system into rescue and removed lvm from fstab to allow system to complete boot normally

  • LVM manager is not seeing the LVM information(metadata appears to be missing)

  • pvdisplay, vgdisplay and lvdisplay did not find anything

  • No changes were made to lvm to their knowledge.(Changes were made to the system on the backend. This change may not be apparent.)

  • LVM metadata restore fails with error "Device /dev/sdx not found (or ignored by filtering)."

Environment

  • Red Hat Enterprise Linux 5, 6
  • GPT parted used for partition larger than 2tb
  • LVM created by gui

Troubleshooting

  • System appeared to have lost lvm metadata.
  • When trying to follow the kbases(here and here) for restoring lvm metadata received an error message after the first lvm command:

    # pvcreate --uuid P4ozw7-y8cJ-5Aw4-3RRc-KAXC-u6Fc-xQl66H /dev/sdb
       Device /dev/sdb not found (or ignored by filtering). 
    
  • Verified that lvm.conf was not filtering the device.

  • fdisk -l gave the following:

    #fdisk -l
    
    Disk /dev/sda: 146.1 GB, 146163105792 bytes
    255 heads, 63 sectors/track, 17769 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1         131     1052226   83  Linux
    /dev/sda2             132         784     5245222+  83  Linux
    /dev/sda3             785       14374   109161675   83  Linux
    /dev/sda4           14375       17769    27270337+   5  Extended
    /dev/sda5           14375       16985    20972826   83  Linux
    /dev/sda6           16986       17507     4192933+  82  Linux swap / Solaris
    /dev/sda7           17508       17638     1052226   83  Linux
    /dev/sda8           17639       17769     1052226   83  Linux
    
    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
    
    
    WARNING: The size of this disk is 4.0 TB (3998614552576 bytes).
    DOS partition table format can not be used on drives for volumes
    larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
    partition table format (GPT).
    
    
    Disk /dev/sdb: 3998.6 GB, 3998614552576 bytes
    255 heads, 63 sectors/track, 486137 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1      267350  2147483647+  ee  EFI GPT
    
  • Parted did not see sdb1 and could not remove it:

    (parted) print all
    
    Model: DELL PERC 6/i (scsi)
    Disk /dev/sda: 146GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    
    Number  Start   End     Size    Type      File system  Flags
     1      32.3kB  1078MB  1077MB  primary   ext3         boot
     2      1078MB  6449MB  5371MB  primary   ext3
     3      6449MB  118GB   112GB   primary   ext3
     4      118GB   146GB   27.9GB  extended
     5      118GB   140GB   21.5GB  logical   ext3
     6      140GB   144GB   4294MB  logical   linux-swap
     7      144GB   145GB   1077MB  logical   ext3
     8      145GB   146GB   1077MB  logical   ext3
    
    
    
    Model: DELL PERC 6/i (scsi)
    Disk /dev/sdb: 3999GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    
    Number  Start  End  Size  File system  Name  Flags
    
    
    Error: Unable to open /dev/md0 - unrecognised disk label.
    
  • Found that a GPT partition label was put on top of the lvm metadata.

  • Duplicated the situation in house by creating lvm on /dev/sda in local environment then inserting GPT label.
  • GPT label wrote over lvm metadata and caused the metadata to look like it was missing.
  • When attempted to restore metadata it results in the device not being seen properly and restore fails.
  • Must remove gpt label.  There is no remove label in parted, only make label.
  • Attempting to make a new label WILL destroy data on the device.
  • To restore metadata without losing the contents of the lvm you must follow the steps following Resolution below.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.