Xen, OpenSSI and DRBD

Hi all,

I have a working OpenSSI cluster of Xen virtual machines with DRBD (all
on Debian Sarge). I'm trying to create another cluster, but I'm hitting
a problem with failover that I never had the first time round.......

On my working cluster, the ramdisk was created with drbd devices
labelled as /dev/drbd/X in the usual places. This was then changed to
/dev/drbdX everywhere except /etc/fstab and all works fine. On my new
cluster, I've done exactly the same, but when the init node fails, I
get:

drbd0: drbd_nodedown: Signaling receiver thread.
drbd0: drbd_set_state: (mdev->this_bdev->bd_contains == 0) in
drivers/block/d/drbd_fs.c:702
drbd0: Secondary/Unknown --> Primary/Unknown
drbd0: Doing CLMS nodedown callback for service 9
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
write handler down off 600000 len 10000
EXT3-fs: mounted filesystem with ordered data mode.
fsck 1.35 (28-Feb-2004)
ERROR: Couldn't open /dev/null (No such file or direct)
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: No such file or directory while trying to open /dev/drbd0
The superblock could not be read or does not describe a correct ext2
filesystem If the device is valid and it really contains an ext2
filesystem (and not swar ufs or something else), then the superblock
 is corrupt, and you might try rung e2fsck with an alternate superblock:
 e2fsck -b 8193 <device>

I've also tried modifying the contents of the ramdisk (by mounting it on
a loop device) to remove all traces of /dev/drbd/ but this had not
effect.

Any ideas?

Owen