# Proxmox DRBD HA Controller problem

**URL:** <https://forums.linbit.com/t/proxmox-drbd-ha-controller-problem/142>\
**Category:** DRBD\
**Created:** [June 19, 2024, 2:18pm UTC](https://forums.linbit.com/t/proxmox-drbd-ha-controller-problem/142 "2024-06-19T14:18:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![peter.sulan](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@peter.sulan](https://forums.linbit.com/u/peter.sulan)\
**Post date:** [June 19, 2024, 2:18pm UTC](https://forums.linbit.com/t/proxmox-drbd-ha-controller-problem/142/1 "2024-06-19T14:18:39Z")

</div>

Hello, I deleted linstor\_db on node3. How can I safely add linstor\_db again without damaging the system and ensure that linstor\_db does not report as StandAlone?

```auto
root@node1:~# linstor storage-pool list
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ StoragePool ┊ Node ┊ Driver ┊ PoolName ┊ FreeCapacity ┊ TotalCapacity ┊ CanSnapshots ┊ State ┊ SharedName ┊
╞═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ DfltDisklessStorPool ┊ node1 ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node1;DfltDisklessStorPool ┊   
┊ DfltDisklessStorPool ┊ node2 ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node2;DfltDisklessStorPool ┊   
┊ DfltDisklessStorPool ┊ node3 ┊ DISKLESS ┊ ┊ ┊ ┊ False ┊ Ok ┊ node3;DfltDisklessStorPool ┊   
┊ drbd-zfs-sas0 ┊ node1 ┊ ZFS ┊ data_sas0/drbd ┊ 317.33 GiB ┊ 464 GiB ┊ True ┊ Ok ┊ node1;drbd-zfs-sas0 ┊   
┊ drbd-zfs-sas0 ┊ node2 ┊ ZFS ┊ data_sas0/drbd ┊ 317.33 GiB ┊ 464 GiB ┊ True ┊ Ok ┊ node2;drbd-zfs-sas0 ┊   
┊ drbd-zfs-ssd0 ┊ node1 ┊ ZFS ┊ data_ssd0/drbd ┊ 1.68 TiB ┊ 1.73 TiB ┊ True ┊ Ok ┊ node1;drbd-zfs-ssd0 ┊   
┊ drbd-zfs-ssd0 ┊ node2 ┊ ZFS ┊ data_ssd0/drbd ┊ 1.68 TiB ┊ 1.73 TiB ┊ True ┊ Ok ┊ node2;drbd-zfs-ssd0 ┊   
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
root@node1:~# linstor resource list
╭───────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ ResourceName ┊ Node ┊ Port ┊ Usage ┊ Conns ┊ State ┊ CreatedOn ┊
╞═══════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ linstor_db ┊ node1 ┊ 7000 ┊ InUse ┊ StandAlone(node2) ┊ UpToDate ┊ 2024-06-18 15:26:05 ┊
┊ linstor_db ┊ node2 ┊ 7000 ┊ InUse ┊ StandAlone(node1) ┊ UpToDate ┊ 2024-06-18 15:26:05 ┊
┊ pm-0b7a526a ┊ node1 ┊ 7003 ┊ InUse ┊ Ok ┊ UpToDate ┊ 2024-06-18 22:58:44 ┊
┊ pm-0b7a526a ┊ node2 ┊ 7003 ┊ Unused ┊ Ok ┊ UpToDate ┊ 2024-06-18 22:58:49 ┊
┊ pm-c497f25f ┊ node1 ┊ 7004 ┊ InUse ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:07:47 ┊
┊ pm-c497f25f ┊ node2 ┊ 7004 ┊ Unused ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:07:52 ┊
┊ pm-d14f5a7f ┊ node1 ┊ 7006 ┊ InUse ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:27:16 ┊
┊ pm-d14f5a7f ┊ node2 ┊ 7006 ┊ Unused ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:27:23 ┊
┊ pm-ebd55187 ┊ node1 ┊ 7005 ┊ InUse ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:20:18 ┊
┊ pm-ebd55187 ┊ node2 ┊ 7005 ┊ Unused ┊ Ok ┊ UpToDate ┊ 2024-06-18 23:20:25 ┊
╰───────────────────────────────────────────────────────────────────────────────────────────────────────╯
root@node1:~# linstor resource-group list
╭───────────────────────────────────────────────────────────────────────╮
┊ ResourceGroup ┊ SelectFilter ┊ VlmNrs ┊ Description ┊
╞═══════════════════════════════════════════════════════════════════════╡
┊ DfltRscGrp ┊ PlaceCount: 2 ┊ ┊ ┊
╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡
┊ drbd-zfs-sas0 ┊ PlaceCount: 2 ┊ 0 ┊ ┊
┊ ┊ StoragePool(s): drbd-zfs-sas0 ┊ ┊ ┊
╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡
┊ drbd-zfs-ssd0 ┊ PlaceCount: 2 ┊ 0 ┊ ┊
┊ ┊ StoragePool(s): drbd-zfs-ssd0 ┊ ┊ ┊
╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡
┊ linstor-db-grp ┊ PlaceCount: 2 ┊ 0 ┊ ┊
┊ ┊ StoragePool(s): drbd-zfs-sas0 ┊ ┊ ┊
┊ ┊ DisklessOnRemaining: True ┊ ┊ ┊
╰───────────────────────────────────────────────────────────────────────╯

```

---

<div class="post-metadata">

**Author:** ![wanzenbug](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/wanzenbug/32/39_2.png) [@wanzenbug](https://forums.linbit.com/u/wanzenbug)\
**Post date:** [June 20, 2024, 10:49am UTC](https://forums.linbit.com/t/proxmox-drbd-ha-controller-problem/142/2 "2024-06-20T10:49:36Z")

</div>

You will need to:

1. Find the “good” controller instance:

```auto
linstor controller which

```

2. disable the HA configuration **on the other node** : we need to resolve the split brain by discarding the data there.

```auto
drbd-reactorctl disable --now linstor_db
drbdadm disconnect linstor_db
drbdadm secondary linstor_db
drbdadm connect --discard-my-data linstor_db

```

3. Reconnect the resource on the “good” controller:

```auto
drbdadm disconnect linstor_db
drbdadm connect linstor_db
drbdadm status linstor_db

```

The nodes should begin to sync and quickly be back to UpToDate state.
4. Reset the tiebreaker flag:

```auto
linstor resource-definition set-property linstor_db DrbdOptions/auto-add-quorum-tiebreaker
linstor resource list

```

There should now be a diskless tiebreaker resource on `node3`.
5. Re-enable the HA configuration on all nodes

```auto
drbd-reactorctl enable linstor_db

```

---

<div class="post-metadata">

**Author:** ![peter.sulan](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@peter.sulan](https://forums.linbit.com/u/peter.sulan)\
**Post date:** [June 22, 2024, 5:32pm UTC](https://forums.linbit.com/t/proxmox-drbd-ha-controller-problem/142/3 "2024-06-22T17:32:03Z")

</div>

Hi, thank you very much. It saved my situation.

I have one last question: if I wanted to cancel the HA Linstor controller and move the Linstor controller to node3 only, what is the correct procedure?

I am interested in the technical aspect of how I would migrate.
