# Pacemaker DRDB

**URL:** <https://forums.suse.com/t/pacemaker-drdb/27384>\
**Category:** SUSE OpenStack Cloud\
**Created:** [August 27, 2015, 10:12pm UTC](https://forums.suse.com/t/pacemaker-drdb/27384 "2015-08-27T22:12:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vneuhauss](https://avatars.discourse-cdn.com/v4/letter/v/59ef9b/32.png) [@vneuhauss](https://forums.suse.com/u/vneuhauss)\
**Post date:** [August 27, 2015, 10:12pm UTC](https://forums.suse.com/t/pacemaker-drdb/27384/1 "2015-08-27T22:12:45Z")

</div>

my environment is:  
1-adminNode  
2-ControlNodes

I added to my admin node 1 new disk with 10GB, i formatted as ext4 and created a lvm mounted in /cloud , in this directory i create a sbd.img using “dd” and shared this .img file using iscsi to my 2 control nodes.  
In my two control nodes i enable the softdog module and installed the sbd package using “zypper in sbd” and executed sbd -d /dev/disk/by-path/ip… create, and after sbd -d /dev/disk/by-path/ip… dump , this two commands don’t returns any error, but when i try use the “list” option don’t return my nodes information.  
I tried create the pacemaker cluster using the crowbar interface but returns me the followed error There is no suitable disk for LVM for DRBD

---

<div class="post-metadata">

**Author:** ![maikcat](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@maikcat](https://forums.suse.com/u/maikcat)\
**Post date:** [August 28, 2015, 9:18am UTC](https://forums.suse.com/t/pacemaker-drdb/27384/2 "2015-08-28T09:18:57Z")

</div>

i havent use sbd fencing mech so far, but i am familiar with drbd,  
can you please post your drbd config used?

also what cat /proc/drbd shows?

Michael.

---

<div class="post-metadata">

**Author:** ![vuntz](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@vuntz](https://forums.suse.com/u/vuntz)\
**Post date:** [September 3, 2015, 12:02pm UTC](https://forums.suse.com/t/pacemaker-drdb/27384/3 "2015-09-03T12:02:30Z")

</div>

You need at least one unused disk on each member of the cluster where you want DRBD. It seems this is not the case, and that’s what the error is saying. (You’re mentioning sbd, but that bit seems to have gone well)