drbd doesn't start on boot

Bug #282876 reported by Holger Mauermann on 2008-10-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone
drbd8 (Ubuntu)

Bug Description

The DRBD package is currently mentioned on one of the Ubuntu marketing pages:

DRBD is used in HA clusters to provide a redundant storage device. In Intrepid's current state, DRBD will not start after a reboot. Thus, the underlying storage will become unavailable. This is not the standard behaviour and is due to incorrect LSB headers in the init.d script (it's using redhat style runlevels instead of debian). A fix to the LSB headers will allow the package to correctly start on system boot.

This packaged is fixed in the development branch according to the Launchpad janitor comment below. The relevant section:

This bug was fixed in the package drbd8 - 2:8.3.0-1ubuntu1

  * Modify init script's default runlevels (LP: #282876):
    - start by default on 2, 3, 4 and 5
    - stop by default on 0, 1 and 6

52 days prior I attached a debdiff patch that did the same:

Related branches

Ante Karamatić (ivoks) wrote :

This is a know problem. I've noticed that couple of days ago. I'm just working on a best solution :)

Changed in drbd8:
importance: Undecided → Medium
status: New → In Progress
.:. brainsik (brainsik) wrote :

What's happening is that the /etc/init.d/drbd script is having it's LSB headers parsed by the update-rc.d program. These are the LSB headers:

# Provides: drbd
# Required-Start: $network $syslog sshd
# Required-Stop: $network $syslog sshd
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: Control drbd resources.

The line:

# Default-Start: 3 5

Means update-rc.d will only create start links in rc3.d and rc5.d. This is why not start link appears in rc2.d and why drbd doesn't start at boot.

It seems a simple fix would be to remove the LSB headers from this script as they are breaking the expected function of update-rc.d.

.:. brainsik

.:. brainsik (brainsik) wrote :

Patched. I decided to just change the start/stop lines to match the update-rc.d defaults.

Debdiff attached.

.:. brainsik (brainsik) wrote :

As usual, I've made the patched packages available via my company's apt repository.

Add these lines to your /etc/apt/sources.list:

deb http://packages.devsuki.com/ubuntu/ intrepid main
deb-src http://packages.devsuki.com/ubuntu/ intrepid main

Grab the public signing key:

$ wget http://packages.devsuki.com/devsuki-signing-key.asc

Add it to your apt keychain:

$ sudo apt-key add devsuki-signing-key.asc

Otherwise, you can directly download the packages here:


Launchpad Janitor (janitor) wrote :

This bug was fixed in the package drbd8 - 2:8.3.0-1ubuntu1

drbd8 (2:8.3.0-1ubuntu1) jaunty; urgency=low

  * Closes (LP: #320831)
  * Modify init script's default runlevels (LP: #282876):
    - start by default on 2, 3, 4 and 5
    - stop by default on 0, 1 and 6
  * Merge from debian unstable, remaining changes:
    - Update maintainer according to spec.
    - Made the lsb init script a bit more compliant.
    - Drop the kernel modules since it is apart of linux-ubuntu-modules.
    - Change CN_IDX_DRBD to 0x6 in drbd/linux/drbd.h

 -- Ante Karamatic <email address hidden> Wed, 24 Dec 2008 08:54:58 +0100

Changed in drbd8:
status: In Progress → Fix Released
.:. brainsik (brainsik) wrote :

I see the fixed package is in the current development version of Ubunut (jaunty). Will a fixed package be rolled out to intrepid (or intrepid-updates or intrepid-backports)?

Mathias Gug (mathiaz) wrote :

If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

.:. brainsik (brainsik) wrote :

Steps 1, 2, and 3 are now in the bug description as well.

description: updated
Chuck Short (zulcss) wrote :

Closing this SRU based on the fact that Intrepid has reached EOL.


Changed in drbd8 (Ubuntu Intrepid):
status: New → Won't Fix
Numérigraphe (numerigraphe) wrote :

For your information, a similar bug was introduced in the Lucid cycle and then fixed again in Maverick.
In Lucid thhe default-start and default-sop are empty.

Numérigraphe (numerigraphe) wrote :

Dear SRU team, please would you care to push the fix to Lucid? Being an LTS, I think it's worth it.

Martin Pitt (pitti) wrote :

It was fixed way before, in jaunty. It's supposed to be fixed in lucid.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers