pvcreate /dev/sdb1 Device /dev/sdb1 not found (or ignored by filtering).

[Riccardo Zambon]

Dear All,
I'm using Intel Modular Server and ProxmoxVe 4.4. I created a shared lun for all the server and setup the multipath as showed in the wiki: https://pve.proxmox.com/wiki/Intel_Modular_Server#Configure_Multi-Path_for_ProxMox_4.x

I am trying now to be able to use the shared volume to install Vm but when I try to create the pv I receive this result:

root@proxmox01:~# pvcreate /dev/sdb1
Device /dev/sdb1 not found (or ignored by filtering).

What in your opinion could I do to fix the problem? Thanks for the help.

 

[dcsapak]

do you have any filters defined in /etc/lvm/lvm.conf?

grep filter /etc/lvm/lvm.conf

 

[Riccardo Zambon]

Hi, thank you for your reply. That's what I have in /etc/lvm/lvm.conf

# such information is used to drive LVM2 filtering like MD component
# A filter that tells LVM2 to only use a restricted set of devices.
# The filter consists of an array of regular expressions. These
# Don't have more than one filter line active at once: only one gets used.
# If lvmetad is used, then see "A note about device filtering while
global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" ]
# filter = [ "a/.*/" ]
# filter = [ "r|/dev/cdrom|" ]
# filter = [ "a/loop/", "r/.*/" ]
# filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
# filter = [ "a|^/dev/hda8$|", "r/.*/" ]
# Since "filter" is often overridden from command line, it is not suitable
# for system-wide device filtering (udev rules, lvmetad). To hide devices
# global_filter. The syntax is the same as for normal "filter"
# above. Devices that fail the global_filter are not even opened by LVM.
# global_filter = []
# The results of the filtering are cached on disk to avoid
# A note about device filtering while lvmetad is used:
# directly by a pvscan --cache <device> call), devices/filter is ignored and
# all devices are scanned by default -- lvmetad always keeps unfiltered
# command does the filtering based on devices/filter setting itself. This
# does not apply to non-regexp filters though: component filters such as
# lvmetad, devices/global_filter must be used.
# mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]

 

[Riccardo Zambon]

do you have any filters defined in /etc/lvm/lvm.conf?

grep filter /etc/lvm/lvm.conf

Hi, thank you for your reply. That's what I have in /etc/lvm/lvm.conf

# such information is used to drive LVM2 filtering like MD component
# A filter that tells LVM2 to only use a restricted set of devices.
# The filter consists of an array of regular expressions. These
# Don't have more than one filter line active at once: only one gets used.
# If lvmetad is used, then see "A note about device filtering while
global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" ]
# filter = [ "a/.*/" ]
# filter = [ "r|/dev/cdrom|" ]
# filter = [ "a/loop/", "r/.*/" ]
# filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
# filter = [ "a|^/dev/hda8$|", "r/.*/" ]
# Since "filter" is often overridden from command line, it is not suitable
# for system-wide device filtering (udev rules, lvmetad). To hide devices
# global_filter. The syntax is the same as for normal "filter"
# above. Devices that fail the global_filter are not even opened by LVM.
# global_filter = []
# The results of the filtering are cached on disk to avoid
# A note about device filtering while lvmetad is used:
# directly by a pvscan --cache <device> call), devices/filter is ignored and
# all devices are scanned by default -- lvmetad always keeps unfiltered
# command does the filtering based on devices/filter setting itself. This
# does not apply to non-regexp filters though: component filters such as
# lvmetad, devices/global_filter must be used.
# mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]

 

[dcsapak]

hmm looks normal, are you sure that /dev/sdb1 is the correct device?

 

[Riccardo Zambon]

hmm looks normal, are you sure that /dev/sdb1 is the correct device?

I found out that the problem was that I had to create the PV before installing the multipath drivers for the Intel Modular Server. I did that and I was able to proceed normally. Thank you for you help.

 

[kipishio]

Hello podskzhite that it is necessary to do at me the same problem

root@pve:~# vgcreate kipi /dev/sdb /dev/sdc
Device /dev/sdb not found (or ignored by filtering).
Device /dev/sdc not found (or ignored by filtering).

 

[kipishio]

root@pve:~# grep filter /etc/lvm/lvm.conf
# is used to drive LVM filtering like MD component detection, multipath
# Configuration option devices/filter.
# Run vgscan after changing the filter to regenerate the cache.
# See the use_lvmetad comment for a special case regarding filters.
global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" ]
# filter = [ "a|.*/|" ]
# filter = [ "r|/dev/cdrom|" ]
# filter = [ "a|loop|", "r|.*|" ]
# filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
# filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
# filter = [ "a|.*/|" ]
# Configuration option devices/global_filter.
# Because devices/filter may be overridden from the command line, it is
# not suitable for system-wide device filtering, e.g. udev and lvmetad.
# Use global_filter to hide devices from these LVM system components.
# The syntax is the same as devices/filter. Devices rejected by
# global_filter are not opened by LVM.
# global_filter = [ "a|.*/|" ]
# The results of filtering are cached on disk to avoid rescanning dud
# This is a quick way of filtering out block devices that are not
# by pvscan --cache), devices/filter is ignored and all devices are
# scanned by default. lvmetad always keeps unfiltered information
# which is provided to LVM commands. Each LVM command then filters
# based on devices/filter. This does not apply to other, non-regexp,
# filtering settings: component filters such as multipath and MD
# are checked during pvscan --cache. To filter a device and prevent
# devices/global_filter.
# Configuration option activation/mlock_filter.
# mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]

 

[Ackros]

did you find a solution for this?