Let’s talk about docs and guides.
My question from above:
What are the recommended packages to install via apt on a raspi as a diskless node? (The raspi should only serve as a quorum)
Hint: I don’t have any other third node, only the raspi.
You convinced me to go with DRBD Reactor and said I should follow the linked blog. This blog leads to https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-proxmox-installing-from-linbit-public-repos, which might not be the correct install guide, for I’m not using a 3rd PVE node, well no PVE on the raspi at all. Yes, the raspi is running as Proxmox Corosync qDevice, but here we are focussing on DRBD and what I have understood is, that I just need to setup a 3rd LINSTOR/DRBD diskless node as a DRBD (not PVE) quorum.
OK, let’s go with the above guide for installing anyway. Here is the trail (after getting the keyring):
root@raspi-1:~# PVERS=8 && echo "deb [signed-by=/etc/apt/trusted.gpg.d/linbit-keyring.gpg] \
http://packages.linbit.com/public/ proxmox-$PVERS drbd-9" > /etc/apt/sources.list.d/linbit.list
root@raspi-1:~# apt update
Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:5 http://deb.debian.org/debian bookworm-updates InRelease
Get:3 https://packages.linbit.com/public proxmox-8 InRelease [2,793 B]
Fetched 2,793 B in 1s (2,437 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Then
root@raspi-1:~# apt -y install drbd-dkms drbd-utils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package drbd-dkms
Different approach - the overall installation in the LINSTOR guide (not Proxmox-related).
2.2.2. Using a Script to Manage LINBIT Cluster Nodes
If you are a LINBIT® customer, you can download a LINBIT created helper script and run it on your nodes to:...
Alas, I am not a paying customer. This is for home use. At work we are currently and still with VMware and I try possible future routes at home.
A little bit further down on topic 2.2.2:
If you want to be able to use LINSTOR to create DRBD replicated storage, you will need to install the required DRBD packages. Depending on the Linux distribution that you are running on your node, install the DRBD-related packages that the helper script suggested. If you need to review the script’s suggested packages and installation commands, you can enter:
# ./linbit-manage-node.py --hints
Ah, the script may also help free users. Let’s try:
root@raspi-1:~# ./linbit-manage-node.py --hints
Looks like you executed the script on a GENERIC system.
Enter "apt update" to update your LINBIT repositories.
If this is an SDS controller node you might want to install:
apt install linbit-sds-controller
You can configure a highly available controller later via:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-linstor_ha
If this is an SDS satellite node you might want to install:
apt install linbit-sds-satellite drbd-module-6.6.62+rpt-rpi-v8 # or drbd-dkms
If you don't intend to run an SDS satellite or controller, a useful set is:
apt install drbd-utils drbd-module-6.6.62+rpt-rpi-v8 # or drbd-dkms
For documentation see:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#p-administration
Is the raspi going to be a satellite node? Guess so from the blog I still follow.
So it should be the line (for package drbd-dkms is not there - see above)
root@raspi-1:~# apt install linbit-sds-satellite drbd-module-6.6.62+rpt-rpi-v8
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linbit-sds-satellite
E: Unable to locate package drbd-module-6.6.62+rpt-rpi-v8
E: Couldn't find any package by glob 'drbd-module-6.6.62+rpt-rpi-v8'
One more thing: I also tried to change to
root@raspi-1:~# echo "deb [signed-by=/etc/apt/trusted.gpg.d/linbit-keyring.gpg] \
http://packages.linbit.com/public/ bookworm misc" > /etc/apt/sources.list.d/linbit.list"
Outcome is the same. Pretty stuck here, despite all your help.
maybe there was just a name change recently that I’m remembering. Either way, dealing with kernels and kernel modules can be confusing at first, but once you understand the relationship it isn’t so bad, I promise.