TruCluster
Showing results for 
Search instead for 
Do you mean 

clu_bdmgr -h : Disk device is not configured to be a members boot disk

Regular Advisor

clu_bdmgr -h : Disk device is not configured to be a members boot disk

Hi to all,
This weekend I was migrating TruCluster 5.1 (GS80, two nodes, Tru64 5.1 + PK6) from Symmetrix 8830 to DMX-3.
After successful dumping of content of "a" partition of boot disk from old to new storage I;ve tried to recover the cnx partition, but no success:

root# clu_bdmgr -h dsk90h /targetmnt/etc/clu_bdmgr.conf

*** Error ***
Disk device is not configured to be a members boot disk.

Error: clu_bdmgr : Failed to meet requirements


Configuration of the disk (clu_bdmgr -c) went ok:

root# clu_bdmgr -c dsk90 3

Error: Disk 'dsk90' has at least one partition that is in use.
The partition in use is open as an Advfs Domain.
Domain root3_domain already exists for member 3. If you continue this
domain will be removed and a new domain, of the same name, will
be created.

Do you want to continue creating this boot disk? [yes]:

*** Error ***
Bad disk label.
rmfdmn: domain root3_domain removed.

Creating AdvFS domains:
Creating AdvFS domain 'root3_domain#root' on partition '/dev/disk/dsk90a'.


Any idea why "clu_bdgmr -h" fails ??

Few days ago I did the same successfully on a single node cluster (ES45 with 5.1A + PK6).

NOt to mention that your time and effort will be appreciated :) !

Regards
9 REPLIES
Honored Contributor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

1) Did you try 'clu_bdmgr -h' again after 'clu_bdmgr -c' succeeded?

2) Can you post the output of 'showfdmn root3_domain' and 'disklabel dsk90c'?
Regular Advisor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

1) sure that I did, if I didn't make "clu_bdmgr -c" then I couldn't dump "a" partition :). so first "clu_bdmgr -c", then vdump/vrestore, then "clu_bdmgr -h".

2)
root# disklabel -r dsk90
# /dev/rdisk/dsk90c:
type: SCSI
disk: SYMMETRIX
label: clu_member
flags:
bytes/sector: 512
sectors/track: 128
tracks/cylinder: 15
sectors/cylinder: 1920
cylinders: 46450
sectors/unit: 89184000
rpm: 5400
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE: values not exact
a: 262144 0 AdvFS # (Cyl. 0 - 136*)
b: 16777216 262144 swap # (Cyl. 136*- 8874*)
c: 89184000 0 unused 0 0 # (Cyl. 0 - 46449)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 44395392 393216 unused 0 0 # (Cyl. 204*- 23327*)
h: 2048 17039360 cnx # (Cyl. 8874*- 8875*)
root# showfdmn root3_domain

Id Date Created LogPgs Version Domain Name
446f96bb.0101cb86 Sun May 21 00:22:51 2006 512 4 root3_domain

Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 262144 89056 66% on 256 256 /dev/disk/dsk90a

Honored Contributor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

I see that 'h' partition is already marked as 'cnx'. Was that from previous configuration? Note sure if that's causing the problem.

If you want to see exactly where the 'clu_bdmgr' script fails, you could add a 'x' to the end of the first line of /usr/sbin/clu_bdmgr and run the command.
Honored Contributor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

Hello Aco
First, you can do what BL said.
Take a look at some previous thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=930469&admit=-682735245+1148389799511+28353475
What I would do is:
1. clear label of disk (# disklabel -z )
2. do clu_bdmgr stuff
3. edit disklabel and restore "a" partition
Regards
In vino veritas, in VMS cluster
Regular Advisor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

Yes Vladimir,

I;ve done that procedure, and to mention again that procedure worked on a 5.1A single cluster.

clu_bdmgr fails on function "clu_bdmgr_init".

I suspect that this has to do something with 5.1 (because on 5.1A it worked).

Thanks again guys,
maybe some with similar problem will respond
Honored Contributor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

Could you try,
root# clu_bdmgr -h dsk90 /targetmnt/etc/clu_bdmgr.conf ;specify disk name without 'h' letter.


Regular Advisor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

That's the way I've done it (without 'h'), and I think that's the only way...
Honored Contributor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

You still have addvol/rmvol option if othing other helps.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=993314
In vino veritas, in VMS cluster
Regular Advisor

Re: clu_bdmgr -h : Disk device is not configured to be a members boot disk

Yes, I am aware of that option also.
However we prefer this method in case failback to be needed...

Thank you Vladimir
//Add this to "OnDomLoad" event