sun cluster3.2, d3 and d8 are shown as failed


 
Thread Tools Search this Thread
Operating Systems Solaris sun cluster3.2, d3 and d8 are shown as failed
# 8  
Old 07-15-2009
It looks like you have problem with device drivers... Or maybe there are some broken links to physical devices... Please provide the output of the following commands:
Code:
devfsadm -Csv
ls -l /dev/rdsk/c0d0s2

Also this device can be not supported by SC your version...
# 9  
Old 07-15-2009
Quote:
Originally Posted by Sapfeer
It looks like you have problem with device drivers... Or maybe there are some broken links to physical devices... Please provide the output of the following commands:
Code:
devfsadm -Csv
ls -l /dev/rdsk/c0d0s2

Also this device can be not supported by SC your version...
OK,

@tommy_sun1

Quote:
-bash-3.00# devfsadm -Csv
devfsadm[1686]: verbose: removing file: /dev/term/a
devfsadm[1686]: verbose: removing file: /dev/cua/a
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s0
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s1
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s2
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s3
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s4
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s5
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s6
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s7
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s8
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s9
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s10
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s11
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s12
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s13
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s14
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1s15
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1p0
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1p1
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1p2
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1p3
devfsadm[1686]: verbose: removing file: /dev/dsk/c1d1p4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s5
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s6
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s8
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s9
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s10
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s11
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s12
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s13
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s14
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0s15
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0p0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0p1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0p2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0p3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t5d0p4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s5
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s6
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s8
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s9
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s10
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s11
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s12
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s13
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s14
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0s15
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0p0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0p1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0p2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0p3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t6d0p4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s4
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s5
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s6
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s7
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s8
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s9
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s10
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s11
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s12
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s13
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s14
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0s15
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0p0
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0p1
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0p2
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0p3
devfsadm[1686]: verbose: removing file: /dev/dsk/c2t7d0p4
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s0
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s1
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s2
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s3
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s4
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s5
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s6
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s7
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s8
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s9
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s10
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s11
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s12
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s13
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s14
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0s15
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0p0
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0p1
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0p2
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0p3
devfsadm[1686]: verbose: removing file: /dev/dsk/c3t4d0p4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s5
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s6
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s7
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s8
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s9
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s10
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s11
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s12
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s13
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s14
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1s15
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1p0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1p1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1p2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1p3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c1d1p4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s5
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s6
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s8
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s9
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s10
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s11
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s12
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s13
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s14
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0s15
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0p0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0p1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0p2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0p3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t5d0p4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s5
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s6
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s8
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s9
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s10
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s11
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s12
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s13
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s14
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0s15
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0p0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0p1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0p2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0p3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t6d0p4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s5
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s6
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s7
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s8
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s9
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s10
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s11
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s12
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s13
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s14
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0s15
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0p0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0p1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0p2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0p3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c2t7d0p4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s4
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s5
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s6
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s7
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s8
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s9
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s10
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s11
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s12
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s13
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s14
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0s15
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0p0
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0p1
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0p2
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0p3
devfsadm[1686]: verbose: removing file: /dev/rdsk/c3t4d0p4
devfsadm[1686]: verbose: removing file: /dev/usb/hub0
devfsadm[1686]: verbose: removing file: /dev/usb/hub1
bash-3.00# ls -l /dev/rdsk/c0d0s2
Quote:
lrwxrwxrwx 1 root root 54 Feb 12 10:55 /dev/rdsk/c0d0s2 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:c,raw
-bash-3.00# ls -l /dev/rdsk/c0d1s2
Quote:
lrwxrwxrwx 1 root root 54 Feb 27 10:08 /dev/rdsk/c0d1s2 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@1,0:c,raw
Thank you!

---------- Post updated at 01:52 PM ---------- Previous update was at 01:49 PM ----------

d1 tommy_sun1:/dev/rdsk/c0d0
d3 tommy_sun1:/dev/rdsk/c0d1
d6 tommy_sun:/dev/rdsk/c0d0
d8 tommy_sun:/dev/rdsk/c0d1

Actually d1 d6 are shown OK and d3 and d8 are of the same type (as that of d1 and d6) but shown failed. Smilie Smilie

---------- Post updated at 02:33 PM ---------- Previous update was at 01:52 PM ----------




SOLVED,

I did on both nodes,

Quote:
format -e, selected c0d1 (failed disk in cldev)

format> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Warning: This disk has an SMI label. Changing to EFI label will erase all
current partitions.
Continue? y
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
8 - change '8' partition
9 - change `9' partition
partition> p
Current partition table (default):
Total disk sectors available: 1212334 + 16384 (reserved sectors)

Part Tag Flag First Sector Size Last Sector
0 usr wm 34 591.94MB 1212334
1 unassigned wm 0 0 0
2 unassigned wm 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 unassigned wm 0 0 0
7 unassigned wm 0 0 0
8 reserved wm 1212335 8.00MB 1228718
partition> q

on both nodes ->
-bash-3.00# newfs /dev/rdsk/c0d1s0
newfs: construct a new file system /dev/rdsk/c0d1s0: (y/n)? y
Warning: 4212 sector(s) in last cylinder unallocated
/dev/rdsk/c0d1s0: 1212300 sectors in 198 cylinders of 48 tracks, 128 sectors
591.9MB in 15 cyl groups (14 c/g, 42.00MB/g, 20160 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 86176, 172320, 258464, 344608, 430752, 516896, 603040, 689184, 775328,
861472, 947616, 1033760, 1119904, 1206048

edited /etc/vfstab on both nodes to point to slice 0 (s0) on c0d1
node1 ->
/dev/did/dsk/d3s0 /dev/did/rdsk/d3s0 /global/.devices/node@1 ufs 2 no global

node2 ->
/dev/did/dsk/d8s0 /dev/did/rdsk/d8s0 /global/.devices/node@1 ufs 2 no global

on one node,

scshutdown -y i0

after both nodes were up,

cldev status

=== Cluster DID Devices ===

Device Instance Node Status
--------------- ---- ------
/dev/did/rdsk/d1 tommy_sun1 Ok

/dev/did/rdsk/d3 tommy_sun1 Ok

/dev/did/rdsk/d4 tommy_sun Ok
tommy_sun1 Ok

/dev/did/rdsk/d5 tommy_sun Ok
tommy_sun1 Ok

/dev/did/rdsk/d6 tommy_sun Ok

/dev/did/rdsk/d8 tommy_sun Ok

Last edited by upengan78; 07-15-2009 at 04:52 PM..
# 10  
Old 07-16-2009
Glad to you! Smilie
# 11  
Old 07-16-2009
Quote:
Originally Posted by Sapfeer
Glad to you! Smilie
Thank you for your timely help! appreciate it.Smilie

One more thing I'd like to add that I did but not sure if this also helped solving my issue.
Quote:
cldevice set -p default_fencing=nofencing d3
cldevice set -p default_fencing=nofencing d8
it was set to Global earlier (by default)
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Can we add Oracle ASM in sun cluster3.3 or 4.0 in failover mode

Hi I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies

2. Solaris

Need suggestion:- Failed HTTPS transfer to https://supportfiles.sun.com/curl

Hi Guys, I have recently started reciving below Error message Failed HTTPS transfer to https://supportfiles.sun.com/curl whenever I run /usr/local/bin/sudo /opt/SUNWexplo/bin/explorer -P -q -v from all Servers. Looks like the SSL certificate as Expired. Whenever I type... (4 Replies)
Discussion started by: manalisharmabe
4 Replies

3. Solaris

Patching failed on Sun T2000

Hi folks, I was patching Sun server (SunOS suns121 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Fire-T200) with the lateset bundle. It was completed with no errors. Server was restarted with shutdown command (/usr/sbin/shutdown -y -i6 -g0) after patching was complete. However, after that,... (3 Replies)
Discussion started by: zulu1
3 Replies

4. Solaris

SUN 6540 Array with failed controller battery

Can someone point me to a procedure detailing the replacement of a failed battery in a SUN 6540 controller. Or describe the procedure. Thanks (1 Reply)
Discussion started by: USFE
1 Replies

5. Solaris

Failed to recover root password in Solaris 10 on Sparc CPU Sun Ultra10

Failed to recover lost root password for Solaris SunSparc (On Sun Ultra10 - SPARC CPU Hardware, not x86 Intel CPU nor x64 AMD CPU) This Sun Ultra10 workstation comes with an old 6-in wafer probing station purchased from a Surplus equipment vendor. Computer: Sun Ultra 5/10 UPA/PCI... (21 Replies)
Discussion started by: fromtexas0
21 Replies

6. Solaris

Sun Cluster3.2 And Oracle10g

I want to configure Sun Cluster3.2 with Oracle10g ... i created 4 resources namely , logical host, sotrage, oracle -server & Listener .. all work fine butoracle resource does not come up .. though i can bring up the oracle outside sun cluster. node1:/>clrg online ora-rg clrg: (C450598) On... (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

Global device issue in sun cluster3.2

In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ? VM1:/>cd /dev/global -bash: cd: /dev/global: No... (1 Reply)
Discussion started by: fugitive
1 Replies

8. Virtualization and Cloud Computing

Sun Cluster3.2 on Vmware Server2.0

I'm trying to configure sun cluster 3.2 on vmware server 2.0 on windows xp host with solaris 10x86 guests VM3 and VM4 and i 'm running scinstall from VM4 .. it fails with following error Initializing cluster name to "laptop" ... done Initializing authentication options ... done Initializing... (0 Replies)
Discussion started by: fugitive
0 Replies

9. Solaris

Please help me.. connection failed between OpenSSH-3.8.1 to Sun SSH-1.1

hi All, We tried to establish a connection from OpenSSH3.8.1 running on Windows Box to SunSSH-1.1 running on Solaris 10. Please see the debug statements. C:\Documents and Settings\sadmin\.ssh>ssh sadmin@10.4.3.8 -v -v -v OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading... (2 Replies)
Discussion started by: venusunil
2 Replies

10. Solaris

what FS is shown in df -kh

Hi, On solaris 10, t5120, I don't understand what are the last 2 file systems so last 2 file systems what are they, why are they getting shown and also confused why the swap is shown so many times and different size when I set it to 16 G at the time of installing solaris 10. ( rest... (3 Replies)
Discussion started by: upengan78
3 Replies
Login or Register to Ask a Question