DRBD unconfigured state

Zriouil

New Member
Mar 25, 2015
11
0
1
Hi,
I'm using Proxmox HA with shared storage DRBD.
After turning off my servers, DRBD has become unconfigured.
I tried restarting the service, but no result.

root@ahmed:~# service drbd restart
Stopping all DRBD resources:
Starting DRBD resources:[ d(r0) 0: Failure: (104) Can not open backing device.



root@ahmed:~# service drbd status
drbd driver loaded OK; device status:
version: 8.3.13 (api:88/proto:86-96)
GIT-hash: 83ca112086600faacab2f157bc5a9324f7bd7f77 build by root@sighted, 2012-10-09 12:47:51
m:res cs ro ds p mounted fstype
0:r0 Unconfigured


during setup, I created a physical volume. I caled it drbd0

Before the stop, I had
root@ahmed:~# pvscan
PV ...... /dev/drbd0 ......................lvm2 [20.00 GiB / 12.00 GiB free]
PV ...... /dev/sda3 .......VG pve ...... lvm2 [7.87 GiB / 892.00 MiB free]
Total: 2 [27.87 GiB] / in use: 2 [27.87 GiB] / in no VG: 0 [0 ]


after, I have this:
root@ahmed:~# pvscan
PV ........ /dev/sdb1 ..... VG myvg ......... lvm2 [20.00 GiB / 12.00 GiB free]
PV ........ /dev/sda3 ..... VG pve ............ lvm2 [7.87 GiB / 892.00 MiB free]
Total: 2 [27.87 GiB] / in use: 2 [27.87 GiB] / in no VG: 0 [0 ]

knowing that I added this volume in a volume group that I called myvg. using the command myvg vgcreate /dev/drbd0


here are my configuration files: they are the same in both nodes
----- r0.res
resource r0 {


on ahmed {
device /dev/drbd0;
disk /dev/sdb1;
address 192.168.1.200:7788;
meta-disk internal;
}


on zriouil {
device /dev/drbd0;
disk /dev/sdb1;
address 192.168.1.210:7788;
meta-disk internal;
}
}

-----global_common.conf
global {
usage-count no;
# minor-count dialog-refresh disable-ip-verification
}


common {
protocol C;


startup {
wfc-timeout 0;
degr-wfc-timeout 60;
become-primary-on both;
# wfc-timeout degr-wfc-timeout outdated-wfc-timeout wait-after-sb
}


net {
cram-hmac-alg sha1;
shared-secret "my-secret";
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;


# sndbuf-size rcvbuf-size timeout connect-int ping-int ping-timeout max-buffers
# max-epoch-size ko-count allow-two-primaries cram-hmac-alg shared-secret
# after-sb-0pri after-sb-1pri after-sb-2pri data-integrity-alg no-tcp-cork
}


syncer {
rate 20M;
verify-alg md5;
# rate after al-extents use-rle cpu-mask verify-alg csums-alg
}
}


Best regards,
Thank you in advance
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!