Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to set up two machines synchonizing with DRBD. The storage is setup as follows: PV -> LVM -> DRBD -> CLVM -> GFS2.

DRBD is set up in dual primary mode. The first server is set up and running fine in primary mode. The drives on the first server have data on them. I've set up the second server and I'm trying to bring up the DRBD resources. I created all the base LVM's to match the first server. After initializing the resources with ``

drbdadm create-md storage

I'm bringing up the resources by issuing

drbdadm up storage

After issuing that command, I get a kernel panic and the server reboots in 30 seconds. Here's a screen capture.

enter image description here

My configuration is as follows: OS: CentOS 6

uname -a
Linux 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24 01:07:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | grep drbd


cat /etc/drbd.d/global_common.conf

global {
        usage-count yes;
        # minor-count dialog-refresh disable-ip-verification

common {
    handlers {
            pri-on-incon-degr "/usr/lib/drbd/; /usr/lib/drbd/; echo b > /proc/sysrq-trigger ; reboot -f";
            pri-lost-after-sb "/usr/lib/drbd/; /usr/lib/drbd/; echo b > /proc/sysrq-trigger ; reboot -f";
            local-io-error "/usr/lib/drbd/; /usr/lib/drbd/; echo o > /proc/sysrq-trigger ; halt -f";
            # fence-peer "/usr/lib/drbd/";
            # split-brain "/usr/lib/drbd/ root";
            # out-of-sync "/usr/lib/drbd/ root";
            # before-resync-target "/usr/lib/drbd/ -p 15 -- -c 16k";
            # after-resync-target /usr/lib/drbd/;

    startup {
            # wfc-timeout degr-wfc-timeout outdated-wfc-timeout wait-after-sb
            become-primary-on       both;
            wfc-timeout             30;
            degr-wfc-timeout        10;
            outdated-wfc-timeout    10;

    options {
            # cpu-mask on-no-data-accessible

    disk {
            # size max-bio-bvecs on-io-error fencing disk-barrier disk-flushes
            # disk-drain md-flushes resync-rate resync-after al-extents
            # c-plan-ahead c-delay-target c-fill-target c-max-rate
            # c-min-rate disk-timeout


    net {
            # protocol timeout max-epoch-size max-buffers unplug-watermark
            # connect-int ping-int sndbuf-size rcvbuf-size ko-count
            # allow-two-primaries cram-hmac-alg shared-secret after-sb-0pri
            # after-sb-1pri after-sb-2pri always-asbp rr-conflict
            # ping-timeout data-integrity-alg tcp-cork on-congestion
            # congestion-fill congestion-extents csums-alg verify-alg
            # use-rle
            protocol C;
            allow-two-primaries yes;
            after-sb-0pri   discard-zero-changes;
            after-sb-1pri   discard-secondary;
            after-sb-2pri   disconnect;

cat /etc/drbd.d/storage.res

resource storage {
        device          /dev/drbd0;
        meta-disk       internal;

        on {
                disk            /dev/vg_storage/lv_storage;
        on {
                disk            /dev/vg_storage/lv_storage;

/var/log/messages is not logging anything about the crash.

I've been trying to find a cause of this but I've come up with nothing. Can anyone help me out? Thanks.

share|improve this question

Machine check exception is a hardware issue. You can use mcelog to interpret it, if you can boot the system.

The resolution is to replace the failing hardware. Since it looks like you're most likely leasing a server, contact the provider.

share|improve this answer
I've checked the mcelog and it's not coming up with any errors, none when the machine is running and nothing added if I force the crash. Also, just curious, but what led you to think it was a leased server? (it's not btw) – dw.emplod Sep 18 '12 at 15:41
Your KVM-over-IP screenshot looked similar to what I've seen commonly used by server leasing companies for customer use. Anyway, the answer is still to isolate and replace the failing hardware, which it seems you've already done. – Michael Hampton Sep 18 '12 at 15:50

Looks like the kernel panic was caused by the network adapter. The server was set up with a dedicated NIC for the DRBD traffic. When I switched the DRBD traffic onto the onboard NIC's the crashes stopped. I'll report back if I find a better explanation for why this was happening (other traffic over that interface seems to be working fine).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.