unable to to create physical volume

[Diablo]

Hi,

When trying to setup DRBD, I get stuck on the following:
(have searched this forum and google but unable to resolve)

Right after editting the LVM.conf file the instructions on the Proxmox VE Wiki say this:

Create the physical volume for LVM

On one node, create the physical volume:
proxmox-105:~# pvcreate /dev/drbd0
Physical volume "/dev/drbd0" successfully created
proxmox-105:~#

When I do this i get the following error:

CENHNS-001:~# pvcreate /dev/drbd0
Device /dev/drbd0 not found (or ignored by filtering).

Any idea why this is happening and how I can resolve this.

I have followed the Proxmox Wiki DRBD instructions to the letter, with the only acception being the physical device being different then the one used in the instructions.

Device in instructions: /dev/sdb
Device in my system: /dev/cciss/c0dx (where x is the number of the physical disk: 0=primary proxmox installation, 1=DRBD disk)

Hope you can help.

 

[tom]

check why you do not have /dev/drbd0 and post your lvm.conf (the part with your custom filter)

 

[Diablo]

Here is the LVM.conf info:

# By default we accept every block device:
filter = [ "r|/dev/cciss/c0d1|", "r|/dev/disk/|", "r|/dev/block/|", "a/.*/" ]

EDIT:

I also found this through the help tekst of the lvm.conf

CENHNS-001:~# vgscan -vvv
Processing: vgscan -vvv
O_DIRECT will be used
Setting global/locking_type to 1
File-based locking selected.
Setting global/locking_dir to /var/lock/lvm
Locking /var/lock/lvm/P_global WB
Wiping cache of LVM-capable devices
...
/dev/cciss/c0d0: Aliased to /dev/block/104:0 in device cache
/dev/cciss/c0d0p1: Already in device cache
/dev/cciss/c0d0p2: Already in device cache
/dev/cciss/c0d1: Aliased to /dev/block/104:16 in device cache
/dev/cciss/c0d1p1: Aliased to /dev/block/104:17 in device cache
...
/dev/drbd0: Aliased to /dev/block/147:0 in device cache (preferred name)
/dev/drbd1: Added to device cache
/dev/drbd10: Added to device cache
/dev/drbd11: Added to device cache
/dev/drbd12: Added to device cache
/dev/drbd13: Added to device cache
/dev/drbd14: Added to device cache
/dev/drbd15: Added to device cache
/dev/drbd2: Added to device cache
/dev/drbd3: Added to device cache
/dev/drbd4: Added to device cache
/dev/drbd5: Added to device cache
/dev/drbd6: Added to device cache
/dev/drbd7: Added to device cache
/dev/drbd8: Added to device cache
/dev/drbd9: Added to device cache
...
/dev/cciss/c0d0: New preferred name
Opened /dev/cciss/c0d0 RO
/dev/cciss/c0d0: size is 976707632 sectors
WARNING: /dev/cciss/c0d0 already opened read-only
/dev/cciss/c0d0: Immediate close attempt while still referenced
Closed /dev/cciss/c0d0
Opened /dev/cciss/c0d0 RW O_DIRECT
/dev/cciss/c0d0: block size is 4096 bytes
/dev/cciss/c0d0: Skipping: Partition table signature found
Closed /dev/cciss/c0d0
Opened /dev/drbd0 RO
/dev/drbd0: size is 1953355528 sectors
WARNING: /dev/drbd0 already opened read-only
/dev/drbd0: Immediate close attempt while still referenced
Closed /dev/drbd0
Opened /dev/drbd0 RW O_DIRECT
/dev/drbd0: block size is 4096 bytes
/dev/drbd0: Skipping: Partition table signature found
Closed /dev/drbd0
...
/dev/cciss/c0d0p1: New preferred name
Opened /dev/cciss/c0d0p1 RO
/dev/cciss/c0d0p1: size is 1048576 sectors
Closed /dev/cciss/c0d0p1
/dev/cciss/c0d0p1: size is 1048576 sectors
Opened /dev/cciss/c0d0p1 RW O_DIRECT
/dev/cciss/c0d0p1: block size is 4096 bytes
Closed /dev/cciss/c0d0p1
Using /dev/cciss/c0d0p1
Opened /dev/cciss/c0d0p1 RW O_DIRECT
/dev/cciss/c0d0p1: block size is 4096 bytes
/dev/cciss/c0d0p1: No label detected
Closed /dev/cciss/c0d0p1
/dev/drbd1: Skipping (sysfs)
...
/dev/cciss/c0d0p2: New preferred name
Opened /dev/cciss/c0d0p2 RO
/dev/cciss/c0d0p2: size is 975654400 sectors
Closed /dev/cciss/c0d0p2
/dev/cciss/c0d0p2: size is 975654400 sectors
Opened /dev/cciss/c0d0p2 RW O_DIRECT
/dev/cciss/c0d0p2: block size is 4096 bytes
Closed /dev/cciss/c0d0p2
Using /dev/cciss/c0d0p2
Opened /dev/cciss/c0d0p2 RW O_DIRECT
/dev/cciss/c0d0p2: block size is 4096 bytes
/dev/cciss/c0d0p2: lvm2 label detected
lvmcache: /dev/cciss/c0d0p2: now in VG #orphans_lvm2 (#orphans_lvm2)
/dev/cciss/c0d0p2: Found metadata at 8192 size 1353 (in area at 4096 size 192512) for pve (til7Bw-npJV-wirk-Uz5r-ERWY-z21V-4xYexl)
lvmcache: /dev/cciss/c0d0p2: now in VG pve with 1 mdas
lvmcache: /dev/cciss/c0d0p2: setting pve VGID to til7BwnpJVwirkUz5rERWYz21V4xYexl
lvmcache: /dev/cciss/c0d0p2: VG pve: Set creation host to proxmox.
Closed /dev/cciss/c0d0p2
/dev/drbd2: Skipping (sysfs)
...
Finding volume group "pve"
Opened /dev/cciss/c0d0p2 RW O_DIRECT
/dev/cciss/c0d0p2: block size is 4096 bytes
/dev/cciss/c0d0p2: lvm2 label detected
lvmcache: /dev/cciss/c0d0p2: now in VG #orphans_lvm2 (#orphans_lvm2) with 1 mdas
/dev/cciss/c0d0p2: Found metadata at 8192 size 1353 (in area at 4096 size 192512) for pve (til7Bw-npJV-wirk-Uz5r-ERWY-z21V-4xYexl)
lvmcache: /dev/cciss/c0d0p2: now in VG pve with 1 mdas
lvmcache: /dev/cciss/c0d0p2: setting pve VGID to til7BwnpJVwirkUz5rERWYz21V4xYexl
lvmcache: /dev/cciss/c0d0p2: VG pve: Set creation host to proxmox.
Using cached label for /dev/cciss/c0d0p2
Read pve metadata (4) from /dev/cciss/c0d0p2 at 8192 size 1353
/dev/cciss/c0d0p2 0: 0 2816: swap(0:0)
/dev/cciss/c0d0p2 1: 2816 24576: root(0:0)
/dev/cciss/c0d0p2 2: 27392 90683: data(0:0)
/dev/cciss/c0d0p2 3: 118075 1023: NULL(0:0)
Found volume group "pve" using metadata type lvm2
Read volume group pve from /etc/lvm/backup/pve
Unlocking /var/lock/lvm/V_pve
Closed /dev/cciss/c0d0p2
Unlocking /var/lock/lvm/P_global
CENHNS-001:~#

Don't know if this is helpfull but I thought I'de post it because it would seem to suggest that there is a /dev/drbd0 defined.

 

[Diablo]

Just wondering if there was any news on this.
I have posted the requested information above, please assist.

 

[Diablo]

Tom,

Could you please help me with this.
I really need to get this up and running as soon as possible.

I have provided the information asked for, kindly assist me in solving this issue.
I have no idea why the device is not found as evindence would suggest otherwise?

Waiting for an answer.

Kind regards.

 

[tom]

I have no more idea whats wrong on your side. if you cannot manage it to work by yourself think of going for a commercial support offering.
http://pve.proxmox.com/wiki/Get_support#Commercial_Support