[SSI-devel] Failed to setup drbd on 1.9.0

[Gopalakrishna NM <go...@hp...>]

Hi,
  I tried to setup DRBD on 1.9.0. It could not identify the root device 
/dev/drbd/0 , which is configured as root device in /etc/fstab. This 
device I have created while building mkinitrd since when I install 
openssi-drbd, the device it created was /dev/drbd0, drbd1...drbd10 etc. 
. I ensured that device name and drbd commands (drbdadm, drbdsetup..) 
are available in initrd.
I cut and paste the last part of the error. It could not identify the 
primary(This is expected and documented ) device. Based on instruction 
in the document I ran the command:

  "drbdadm  -- --do-what-I-say primary r0"

This command ran successfully, but upon exiting the shell, system is 
restarting. Soft restart is not working and I had to do power off/on the 
system and same cycle repeates.  But the expectation is after executing 
above command and exit from shell, system should come up with DRBD.

If anybody faced and overcome this problem or if you have any guidance, 
please let me know.

Currently I am debugging this problem.

Thanks and regards,
Gopal.


Name server registered with clms
ipcnameserver ready completed
ipcname_read completed
drbd: module cleanup done.
modprobe -k drbd  minor_count=1
drbd: initialised. Version: 0.7.10 (api:77/proto:74)
drbd: SVN Revision: 1743 build by kvaneesh@node10, 2005-04-26 03:34:15
drbd: registered as block device major 147
Starting DRBD resource:
drbd0: resync bitmap: bits=1220925 words=38154
drbd0: size = 4769 MB (4883697 KB)
drbd0: 4769 MB marked out-of-sync by on disk bit-map.
drbd0: Found 6 transactions (39 active extents) in activity log.
drbd0: Marked additional 0 KB as out-of-sync based on AL.
drbd0: drbdsetup [66083]: cstate Unconfigured --> StandAlone
drbd0: drbdsetup [66086]: cstate StandAlone --> Unconnected
drbd0: drbd0_receiver [66087]: cstate Unconnected --> WFConnection
drbd0: Registering drbd0 with CLMS subsystem

# WARNING: Do not type 'yes' while waiting for DRBD connection
#         unless you know what you are doing!  You have been warned!
#         The only exception is when setting up DRBD first time.
#
***************************************************************
  DRBD's startup script waits for the peer node(s) to appear.
  - In case this node was already a degraded cluster before the
    reboot the timeout is 120 seconds. [degr-wfc-timeout]
  - If the peer was available before the reboot the timeout will
    expire after 0 seconds. [wfc-timeout]
    (These values are for resource 'r0'; 0 sec -> wait forever)
  To abort waiting enter 'yes' [ 119]:
drbd0: Secondary/Unknown --> Primary/Unknown
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.
EXT3-fs: mounted filesystem with ordered data mode.
Running post-root cluster initialization
Starting init
INIT: version 2.86-SSI booting
warning: can't open /proc/mounts: No such file or directory
umount: /initrd: device is busy
findfs: Unable to resolve 'UUID=/dev/drbd/0'
Activating swap.
Adding 2040244k swap on /dev/sda4.  Priority:-1 extents:1
Usage: mountpoint [-q] [-d] [-x] path

The device node  for the root filesystem is missing,
incorrect, or there is no entry for the root filesystem
listed in /etc/fstab.

The system is also unable to create a temporary node in
/dev/shm to use as a work-around.

This means you have to fix this manually.

CONTROL-D will exit from this shell and REBOOT the system.