Acabei de ter o mesmo erro, parece que o endereço IP do segundo nó não estava acessível. Primeiro eu verifiquei o status do serviço:
systemctl status drbd.service
â drbd.service - DRBD -- please disable. Unless you are NOT using a cluster manager.
Loaded: loaded (/usr/lib/systemd/system/drbd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since mar. 2018-04-10 16:21:49 CEST; 5s ago
Process: 3347 ExecStart=/lib/drbd/drbd start (code=exited, status=20)
Main PID: 3347 (code=exited, status=20)
avril 10 16:21:49 GROESSLTCL0B systemd[1]: Starting DRBD -- please disable. Unless you are NOT using a cluster manager....
avril 10 16:21:49 GROESSLTCL0B drbd[3347]: Starting DRBD resources: drbd.d/r0.res:20: in resource r0, on GROESSLTCL0B:
avril 10 16:21:49 GROESSLTCL0B drbd[3347]: IP 192.168.254.2 not found on this host.
avril 10 16:21:49 GROESSLTCL0B systemd[1]: drbd.service: main process exited, code=exited, status=20/n/a
avril 10 16:21:49 GROESSLTCL0B systemd[1]: Failed to start DRBD -- please disable. Unless you are NOT using a cluster manager..
avril 10 16:21:49 GROESSLTCL0B systemd[1]: Unit drbd.service entered failed state.
avril 10 16:21:49 GROESSLTCL0B systemd[1]: drbd.service failed.
Então eu consertei o IP do segundo nó em r0.res, o novo conteúdo é o seguinte:
resource r0 {
protocol "C";
net {
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
}
on GROESSLTCL0A {
device /dev/drbd0;
disk /dev/sdb;
address 163.104.8.108:7789;
meta-disk internal;
}
on GROESSLTCL0B {
device /dev/drbd0;
disk /dev/sdb;
address 163.104.8.107:7789;
meta-disk internal;
}
}
Então eu recriou o recurso:
drbdadm create-md r0
depois disso eu reiniciei o serviço drbd e tudo estava funcionando como esperado.