cluster boot failure, Urgent HELP needed.

Customer case with 5.1B, where cluster fail to boot, and trouble is that =
I need the disks in the datadg in the SAN to move on.

Boot failure is:

WARNING: cfs_attached_to_devs: LSM not ready on this node yet so can't =
attempt to failover

Waiting for cluster mount to complete
WARNING: cfs_perform_glroot_mount: cfs_mountroot_local failed to mount =
the cluster root fs with error =3D 6


and from both nodes.

Has anybody seen this before and found a solution for it.


The alternative to recover the datadg from the SAN is that I have now =
booted a standalone installation from CD on a local disk.
I can see the disks in the SAN when clearing out after failure first. =
"/usr/sbin/cleanPR clean" helps get rid of the persistant reservations =
the cluster boot has made.

Any help/input , espicially on importing datadg via the "foreign" to =
this boot disk LSM config.

I have also recovered volsave db from the cluster, and trying the road =
of modifying the datadg.d/allvol.* to contain the korrekt disknames. But =
still with no luck.

Localdisk LSM setup :
# lsmsetup -o force dsk29
Initialize vold and the root disk group:
Add disk dsk29 to the root disk group as dsk29:
Addition of disk dsk29 as dsk29 succeeded.
lsm:vold: WARNING: Disk dsk4: Disk rejected as clone
lsm:vold: WARNING: Disk dsk6b names group rootdg, but group ID differs
lsm:vold: WARNING: Disk dsk6g names group rootdg, but group ID differs
lsm:vold: WARNING: Disk dsk6h names group rootdg, but group ID differs
lsm:vold: WARNING: Disk dsk14 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk16 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk9 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk10 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk12 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk17 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk18 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk19 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk20 names group datadg, but group ID differs
lsm:vold: WARNING: Disk dsk26 names group datadg, but group ID differs
lsm:vold: ERROR: Disk group datadg, Disk dsk13: Cannot auto-import =
group:
        No valid log copies in disk group
Initialization of vold and the root disk group was successful.
volwatch daemon started - mail only
#




best regards Martin R=F8nde Andersen, [email protected] , +45 =
53747139 ( I'll return call)