# Cannot recover drdb volume - drbdadm primary --force doesn't work

**URL:** <https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350>\
**Category:** DRBD\
**Tags:** latest, split-brain, drbd\
**Created:** [October 6, 2024, 2:13pm UTC](https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350 "2024-10-06T14:13:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dniasoff](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dniasoff](https://forums.linbit.com/u/dniasoff)\
**Post date:** [October 6, 2024, 2:13pm UTC](https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350/1 "2024-10-06T14:13:50Z")

</div>

I have a drbd volume which won’t come up after a reboot

 ![image](https://canada1.discourse-cdn.com/flex003/uploads/linbit/original/1X/4712e769b29b548dd5ad889c72b818ead43f4d58.png)

I am trying to tell drbd to select the volume on 1 of the nodes as the “source of truth” but I am unable to.

```auto
root@node02.cloud10:~# drbdadm primary --force volume-0eb1b3c1-13d3-4d72-9b07-15ebc5194a3a
volume-0eb1b3c1-13d3-4d72-9b07-15ebc5194a3a: State change failed: (-2) Need access to UpToDate data
Command 'drbdsetup primary volume-0eb1b3c1-13d3-4d72-9b07-15ebc5194a3a --force' terminated with exit code 17

```

How can I recover from this split-brain situation?

---

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [October 7, 2024, 1:41pm UTC](https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350/2 "2024-10-07T13:41:22Z")

</div>

All your nodes are in a `Diskless` state for that resource.

Is the backing storage for the resource present and healthy?

```auto
linstor storage-pool list

```

---

<div class="post-metadata">

**Author:** ![dniasoff](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dniasoff](https://forums.linbit.com/u/dniasoff)\
**Post date:** [October 7, 2024, 5:27pm UTC](https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350/3 "2024-10-07T17:27:47Z")

</div>

Looking OK

```auto
(vqcp) root@node01:# linstor storage-pool list
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ StoragePool ┊ Node ┊ Driver ┊ PoolName ┊ FreeCapacity ┊ TotalCapacity ┊ CanSnapshots ┊ State ┊ SharedName ┊
╞═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ DfltDisklessStorPool ┊ node01.xyz ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node01.xyz;DfltDisklessStorPool ┊
┊ DfltDisklessStorPool ┊ node02.xyz ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node02.xyz;DfltDisklessStorPool ┊
┊ DfltDisklessStorPool ┊ node03.xyz ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node03.xyz;DfltDisklessStorPool ┊
┊ pool1 ┊ node01.xyz ┊ ZFS_THIN ┊ pool1 ┊ 1.22 TiB ┊ 10.47 TiB ┊ True ┊ Ok ┊ node01.xyz;pool1 ┊
┊ pool1 ┊ node02.xyz ┊ ZFS_THIN ┊ pool1 ┊ 1.09 TiB ┊ 10.47 TiB ┊ True ┊ Ok ┊ node02.xyz;pool1 ┊
┊ pool1 ┊ node03.xyz ┊ ZFS_THIN ┊ pool1 ┊ 3.36 TiB ┊ 10.47 TiB ┊ True ┊ Ok ┊ node03.xyz;pool1 ┊
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

```

---

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [October 17, 2024, 6:12pm UTC](https://forums.linbit.com/t/cannot-recover-drdb-volume-drbdadm-primary-force-doesnt-work/350/4 "2024-10-17T18:12:56Z")

</div>

You could try a mass `adjust` on the `resource-group` those resources belong to:

```auto
linstor resource-group adjust <rg-name>

```

Running a `drbdadm adjust all` on `node2` and `node3` might give you more hints as to what’s going on.

Either way, none of your node’s DRBD devices are attached to their local backing storage (all in a `Diskless` state). This isn’t a split-brain based on what’s been shared so far.