# Ancient DRBD after Proxmox update until headers are installed manually **URL:** \ **Category:** Proxmox VE\ **Tags:** drbd, linstor, proxmox\ **Created:** [November 23, 2025, 5:51pm UTC](https://forums.linbit.com/t/ancient-drbd-after-proxmox-update-until-headers-are-installed-manually/1069 "2025-11-23T17:51:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sewi](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/sewi/32/279_2.png) [@sewi](https://forums.linbit.com/u/sewi)\ **Post date:** [November 23, 2025, 5:51pm UTC](https://forums.linbit.com/t/ancient-drbd-after-proxmox-update-until-headers-are-installed-manually/1069/1 "2025-11-23T17:51:04Z")
Hey there, This is the second time it happened, and I’m wondering if there’s anything I should be doing. Basically, I’m on a Linbit staff performed install of DRBD/LINSTOR, running Proxmox 9. I update Proxmox (`pveupdate`, `pveupgrade`, `reboot`), and I end up with errors such as `# drbdadm status` `/var/lib/linstor.d/linstor_db.res:14: Parse error: ‘an option keyword’ expected,` `but got ‘auto-promote’` Doing `cat /proc/drbd` I see that somehow a DRBD 8.4.11 has risen from the grave and that’s what I’m running now. (nevermind the fact that `drbd` doesn’t even build with the 6.17 kernel the current Proxmox update ships with, so that’s good to know in advance I guess) So I’d usually have to do an `apt install proxmox-headers-6.xx` with whatever kernel I’m running on, followed by “`dkms autoinstall`”, but I’m wondering if there’s something I’d need to do so the correct `proxmox-headers` are installed automatically. What’s also odd is that right after I reboot, I always see an empty resource list: ```auto # drbdadm status [...lots of empty lines...] –== Thank you for participating in the global usage survey ==– The server’s response is: # No currently configured DRBD found. ``` I have to `drbdadm adjust all` to see them. Is there anything missing on my system? Stefan ---
**Author:** ![rck](https://avatars.discourse-cdn.com/v4/letter/r/c37758/32.png) [@rck](https://forums.linbit.com/u/rck)\ **Post date:** [November 25, 2025, 8:40am UTC](https://forums.linbit.com/t/ancient-drbd-after-proxmox-update-until-headers-are-installed-manually/1069/2 "2025-11-25T08:40:06Z")
> [@sewi](#): > > Basically, I’m on a Linbit staff performed install of DRBD/LINSTOR, running Proxmox 9 then you probably should open a ticket with our our support team > [@sewi](#): > > Doing `cat /proc/drbd` I see that somehow a DRBD 8.4.11 has risen from the grave and that’s what I’m running now. that is the in-tree kernel module shipped with the standard Linux kernel. Usually nowadays a sign that “something went wrong with loading a DRBD 9 module” > [@sewi](#): > > (nevermind the fact that `drbd` doesn’t even build with the 6.17 kernel the current Proxmox update ships with, so that’s good to know in advance I guess) true. a new DRBD kernel module that builds with 6.17 should be out today or tomorrow I guess. We decided to not “backport” anything for just a few days of overlap. sorry for the inconvenience though > [@sewi](#): > > So I’d usually have to do an `apt install proxmox-headers-6.xx` with whatever kernel I’m running on, followed by “`dkms autoinstall`”, but I’m wondering if there’s something I’d need to do so the correct `proxmox-headers` are installed automatically. `apt install -y proxmox-default-headers`should do. > [@sewi](#): > > What’s also odd is that right after I reboot, I always see an empty resource list: I’d say that is a coincidence. Eventually linstor-satellite would have brought up the resources. ---
**Author:** ![sewi](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/sewi/32/279_2.png) [@sewi](https://forums.linbit.com/u/sewi)\ **Post date:** [November 25, 2025, 9:48am UTC](https://forums.linbit.com/t/ancient-drbd-after-proxmox-update-until-headers-are-installed-manually/1069/3 "2025-11-25T09:48:18Z")
> [@rck](#): > > then you probably should open a ticket with our our support team Well, even though we officially pay I’m still a community fan and play the support-ticket-card only when I see no other choice 😉 Community knowledge helps others, which helps the project, which in turn helps me, because I do like DRBD and want to see it strive. The point of mentioning that was merely a “so I didn’t experiment and the install should be correct”. > [@rck](#): > > true. a new DRBD kernel module that builds with 6.17 should be out today or tomorrow I guess. Sounds good, I’ve been waiting for that now. For the time being I boot with the older kernel, but I’ve holding off upgrades to further nodes until the module for the 6.17 is out. > [@rck](#): > > `apt install -y proxmox-default-headers`should do. Thanks, done. > [@rck](#): > > I’d say that is a coincidence. Eventually linstor-satellite would have brought up the resources. Alright, I’ve just been wary rebooting additional nodes until I see the resources all up again, so I don’t lose quorum 😉 ---
**Author:** ![sewi](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/sewi/32/279_2.png) [@sewi](https://forums.linbit.com/u/sewi)\ **Post date:** [November 25, 2025, 8:20pm UTC](https://forums.linbit.com/t/ancient-drbd-after-proxmox-update-until-headers-are-installed-manually/1069/4 "2025-11-25T20:20:21Z")
Also, a small heads up, the 6.17 kernel from Proxmox doesn’t seem to support crct10dif anymore, which my DRBD really liked, so I had to change the verify-alg 😉