Cluster /global/devices/node@X mount problem.

Question

Hi,
I have just installed sun cluster 3.2. It is a simple installtion and cluster contains only two servers and one sun storage.
After installation, i realised that the name of the metadevice on tha servers were the same, so only one of them mounted under /global/devices/node@X, and the other were didn't.
Then i re-create metadevice on the second node with another name. After re-creation /global/devices/node@X
fs weren't mounted, when node were rebooted.
there was various error on the console, but i couldn't resolve that problem.
I can mount global/devices/node@X with mount command. But it's not mounted automaticaly in reboot time.
# mount global/devices/node@X is running perfectly.
The error shown in reboot time are as follows;
The /global/.devices/node@2 file system (/dev/rlofi/1) is being checked.
WARNING - Unable to repair the /global/.devices/node@2 filesystem. Run fsck
manually (fsck -F ufs /dev/rlofi/1).
Mar 18 13:35:12 svc.startd[8]: svc:/system/cluster/scmountdev:default: Method "/usr/cluster/lib/svc/method/scmountdev start" failed with exit status 32.
The /global/.devices/node@2 file system (/dev/rlofi/1) is being checked.
WARNING - Unable to repair the /global/.devices/node@2 filesystem. Run fsck
manually (fsck -F ufs /dev/rlofi/1).
Mar 18 13:35:12 svc.startd[8]: svc:/system/cluster/scmountdev:default: Method "/usr/cluster/lib/svc/method/scmountdev start" failed with exit status 32.
The /global/.devices/node@2 file system (/dev/rlofi/1) is being checked.
WARNING - Unable to repair the /global/.devices/node@2 filesystem. Run fsck
manually (fsck -F ufs /dev/rlofi/1).
Mar 18 13:35:12 svc.startd[8]: svc:/system/cluster/scmountdev:default: Method "/usr/cluster/lib/svc/method/scmountdev start" failed with exit status 32.
mount: I/O error
mount: Cannot mount /dev/lofi/126
lofiadm: could not unmap device /dev/lofi/126: No such device or address
mount: I/O error
mount: Cannot mount /dev/lofi/126
lofiadm: could not unmap device /dev/lofi/126: No such device or address
WARNING: Cluster startup could not remove the existing
lofi device associated with /.globaldevices. Try manually
removing the device association. Global devices will
be unavailable until this error is fixed.
Mar 18 13:36:10 tstclstr1 svc.startd[8]: system/cluster/globaldevices:default misconfigured: transitioned to maintenance (see 'svcs -xv' for details)
Mar 18 13:36:10 tstclstr1 Cluster.CCR: /usr/cluster/bin/scgdevs: Filesystem /global/.devices/node@2 is not available in /etc/mnttab.
Mar 18 13:36:10 tstclstr1 last message repeated 1 time
Mar 18 13:38:50 tstclstr1 svc.startd[8]: platform/sun4u/dscp:default failed: transitioned to maintenance (see 'svcs -xv' for details)
The output of the svcs -xv;
root@tstclstr1 # svcs -xv
svc:/system/cluster/globaldevices:default (Suncluster globaldevices service)
State: maintenance since 18 Mart 2010 Perşembe 13:36:10 EET
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-cluster-globaldevices:default.log
Impact: 3 dependent services are not running:
svc:/system/cluster/mountgfs:default
svc:/system/cluster/clusterdata:default
svc:/system/cluster/ql_rgm:default
svc:/application/print/server:default (LP print server)
State: disabled since 18 Mart 2010 Perşembe 13:34:46 EET
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
svc:/system/cluster/scmountdev:default (Sun Cluster scmountdev)
State: maintenance since 18 Mart 2010 Perşembe 13:35:12 EET
Reason: Start method failed repeatedly, last exited with status 32.
See: http://sun.com/msg/SMF-8000-KS
See: /etc/svc/volatile/system-cluster-scmountdev:default.log
Impact: This service is not running.
svc:/system/cluster/scsymon-srv:default (Sun Cluster SyMON Server Daemon)
State: offline since 18 Mart 2010 Perşembe 13:34:49 EET
Reason: Dependency svc:/application/management/sunmcagent:default is absent.
See: http://sun.com/msg/SMF-8000-E2
Impact: This service is not running.
svc:/platform/sun4u/dcs:default (domain configuration server)
State: maintenance since 18 Mart 2010 Perşembe 13:38:51 EET
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/share/man -s 1M dcs
See: /var/svc/log/platform-sun4u-dcs:default.log
Impact: This service is not running.
svc:/platform/sun4u/dscp:default (DSCP Service)
State: maintenance since 18 Mart 2010 Perşembe 13:38:50 EET
Reason: Start method failed repeatedly, last died on Killed (9).
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M prtdscp
See: /var/svc/log/platform-sun4u-dscp:default.log
Impact: This service is not running.
{noformat}root@tstclstr1 #
</pre>{noformat}

Answer 1

Thanks for the reply,
It used to be the same metaset name on the second server, which several folks have run into when installing SC on the 2nd node. So I renamed it when booted into no cluster mode using metarename. I then updated the /etc/vfstab with the new name, this is it in /etc/vfstab:
/dev/md/dsk/d26 /dev/md/rdsk/d26 /global/.devices@2 ufs 2 no global
And yes if I change "global" to "-" then it mounts. When the 2nd node boots up, it cannot mount /global/.devices@2 with it set to global so the boot halts, I do ctrl-D to continue. Then I try a regular mount from root and I get the "no such file or directory" message.
If I do a metastat d26 it shows it to be OK on both submirrors.
The name of the metadisk on the first node is d160. And the 2nd server is able to mount that from the global option on the first server.
Thanks,