Solstice disksuite

Hi Friends,
I started a new work of managing database and backup servers which are running in solaris. Please tell me, through which command i will know like what type of raid is configured in solaris 8 machines using disksuite software......
thanks & regards
VJ.

Hi
Thanks for the reply. I also can able to see metastat and format. But how should we come to conclusion by seeing the output whether the metadevice configuration is stripe/concat (or) Raid 1 (or) Raid 5.
Thanks

Similar Messages

How to backout a Recommended Patch cluster deployment in Solstice disksuite

Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Upgrade from solaris 8 to solaris 9 with sun solstice disksuite

Hi,
I have to upgrade the solaris 8 with Solstice disksuite to Solaris 9 OS. Please let me know the steps for the upgrade.
Regards
chesun

Yep!
See
http://docs.sun.com/db/doc/806-5205/6je7vd5rf?a=view
Lee

Solstice Disksuite 4.2.1

I have recently upgraded to Solaris 8 from 2.6 (and Solstice Disksuite 4.1) and followed the instructions for installing Solstice Disksuite 4.2.1 on to SOlaris 8. I now have a package called SUNWmdg.2. I understand the '.2' indicates a 'duplicate' package. Should I have installed the old packages first? Nowhere in the Disksuite 4.2.1 installation manual did it say to do so. What do I do now?
Thanks
D

Yes, but some versions of VxVM require a 'rootdg' remain. You may or may not prefer to simply use VxVM to mirror root.
The packages are on disk2 of the installation media in the EA folder.
Darren

Solstice DiskSuite Service

Hi,
Under Security, I need to disable Solstice DiskSuite Service in Solaris 8 & 9, after finding out whether its in use or not.
Can anyone help on this
Thanks
Gattu

You can find out if disksuite is in use by running the metastat command.
I'm not sure why you consider it to be a security issue unless your referring to the various
services that ship with it like rpc.metad and rpc.mdcommd.
On solaris 9, all those can be commented out of /etc/inetd.conf without effecting the functioning of disksuite unless your using cluster type functionality.
On solaris 10 they can be shutdown with svcadm.

Solstice DiskSuite 4.2.1 Installation

Hi,
I have a SUN fire 880 system running Solaris 8 and 72GBX10 Disk.
right now 8 disk are configured in Veritas Volume Manager and one disk has root and other file system and one more disk is still free so I am planning to mirror root disk with free disk in ( Solstice DiskSuite 4.2.1) please advice me
My Qustion is
1>Is it possible ???
2>From where I can get Solstice DiskSuite 4.2.1 packages???.
Thanks in advance..
Bhupal

Yes, but some versions of VxVM require a 'rootdg' remain. You may or may not prefer to simply use VxVM to mirror root.
The packages are on disk2 of the installation media in the EA folder.
Darren

SNMP MIB for Solstice DiskSuite 4.2

Hi all,
Does anybody know where I can get the SNMP MIB for Solstice DiskSuite 4.2 ?
Any help will be appreciated,
Thanks,
Simon

Yes, but some versions of VxVM require a 'rootdg' remain. You may or may not prefer to simply use VxVM to mirror root.
The packages are on disk2 of the installation media in the EA folder.
Darren

Solstice DiskSuite in Solaris 8

Hi all,
I was told that DiskSuite is included in Solaris 8, does anybody know where can I find the installation files???
Is there a wizard or something like that???
Do I need a special CD???
I have installed it from the Easy Access Server CD but I don't know how to do it from the files included in Solaris 8 Media
Thanks in advance...
Marissa

had the same prob myself...
cd /cdrom/cdrom0/Solaris_8/EA/products/DiskSuite_4.2.1/sparc

Solstice DiskSuite or Veritas Volume Manager

With regards to Solaris 8,
I plan to use DiskSuite to create a few 0+1 volumes for our new database server. Any reason for me to consider Veritas Volume Manager instead?
We have an E5000 running Solaris 2.6 with Veritas Volume Manager 3.2, we are only using it for 0+1 volumes(vxfs). No snaphosts, fast I/O or any other bells and whilste of VM are being used.

apologies my original post was incorrectly posted to the wrong forum.

How will extend the Filesystem on solstice disksuite

Hi Friends,
In Solstice disk suite one of the filesystem has reached 90%, After doing house keeping finally it has reached 80%.
However we are planned to extend the Filesystem.
We have informed to management to procure 2* 18 Gb Hdd.
I am not familiar in the Solstice disk suite, could you please provide me a procedure to extend the Filesystem on Solstice disk suite,
Please find the following output below:-
/dev/md/dsk/d8 52222754 41701831 9998696 81% /data
# metastat d8
d8: Mirror
Submirror 0: d6
State: Okay
Submirror 1: d7
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 106070958 blocks
d6: Submirror of d8
State: Okay
Size: 106070958 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t8d0s0 0 No Okay
Stripe 1:
Device Start Block Dbase State Hot Spare
c1t9d0s0 3591 No Okay
Stripe 2:
Device Start Block Dbase State Hot Spare
c1t10d0s0 4712 No Okay
Stripe 3:
Device Start Block Dbase State Hot Spare
c1t11d0s0 4712 No Okay
d7: Submirror of d8
State: Okay
Size: 106070958 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c5t0d0s0 0 No Okay
Stripe 1:
Device Start Block Dbase State Hot Spare
c5t1d0s0 3591 No Okay
Stripe 2:
Device Start Block Dbase State Hot Spare
c5t2d0s0 4712 No Okay
Stripe 3:
Device Start Block Dbase State Hot Spare
c5t3d0s0 4712 No Okay
Many Thanks
Karthick

Have a look for a solution here it sounds like your issue http://discussions.apple.com/thread.jspa?threadID=1780505&tstart=0, hope it helps.

Solstice disksuite dual scsi controller

Is there a way to load balance across 2 scsi controllers to a raid unit with solstice? My client won't fork over the money for Veritas.
If I can't get the load balancing, is there a way to failover the controllers? Maybe set up the second controller as a mirror.
System info:
SunFire V480
Dual Sun SCSI controller
Winchester Flashdisk RAID

Sorry rakman2, but your suggestions will not work with that system.
A Sun V20z is Intel Xeon based.
No OBP, and therefore no OBP commands or utilities (such as <i>probe</i>).
Let's just wait for <i>hero</i> to provide more information.
Edit:
Corrected a typo and noticed that it has been three months.
The original poster has not returned.
... and an error about a ROM on a peripheral usually means unqualified 3rd party hardware.

DiskSuite

Hi
I am planning an upgrade from Solaris 2.6 to solaris 8.
I have read sun document "Upgrade Tips and Checklist" which mentions DiskSuite needs to be disabled prior to O/S upgrade.
We have Solstice DiskSuite 4.1 installed.
Q
1. What is this used for
2. How do I dissable it
3. Will this need upgrading to work with Solaris 8. If so How!
Sorry about all the Questions but i am a novice!
Kind Regards
Simon

Your Questions & answers :-
1. What is this used forTo mirror , stripe or concatenate disk partitions for redundency and more capacity.
2. How do I dissable it1. Remove references to root metadevice from /etc/vfstab and putting device name for partitions .You might have an old copy of vfstab or commented entries for these devices.
2. Comment the following lines in /etc/system the
* rootdev:/pseudo/md@0:0,0,blk
* set md:mddb_bootlist1
3. Will this need upgrading to work with Solaris 8.This will work on Solaris 8 also.
If so How!please refer to docs.sun.com for details about Disksuite .
Hemant
http://www.adminschoice.com
Hi
I am planning an upgrade from Solaris 2.6 to solaris
8.
I have read sun document "Upgrade Tips and Checklist"
which mentions DiskSuite needs to be disabled prior to
O/S upgrade.
We have Solstice DiskSuite 4.1 installed.
Q
1. What is this used for
2. How do I dissable it
3. Will this need upgrading to work with Solaris 8.
If so How!
Sorry about all the Questions but i am a novice!
Kind Regards
Simon

Veritas/DiskSuite

I am working on a study on Veritas Volume Manager and Solstice DiskSuite.
Do you have any information on these products : I'd like to have advantages and defaults of each of them. I have link on document on Web but I'd like to have user's point of view.
Thanks in advance for your help.

Hi,
You've already got volume manager, so why not use it? If you install ODS as well as VXVM, you're just complicating the setup of the machine.
You've got veritas already installed, just use this!

Disksuite 4.2.1 wont install via jumpstart on Solaris 8 2/04

Trying to install Disksuite on a Sun Solaris 8 image. The install works on Fujitsu hardware with an even older (2/02) Solaris 8 image for Fujitsu hardware, but for some reason its not working for a Sun V120 with Sun's 2/04 solaris 8 release.
Here's the output from my finish script to install the packages. All other packages install just fine.
==============================================================================
ACI-secure.driver: Finish script: install-disksuite.fin
==============================================================================
Installing DiskSuite
Installing DiskSuite from /a//tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
==============================================================================
Installing Package: SUNWmdr
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdr> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Drivers
(sparc) 4.2.1,REV=1999.12.03.10.00
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdr/install/checkinstall
: /tmp/sh141750: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdr> failed.
No changes were made to the system.
==============================================================================
Installing Package: SUNWmdx
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdx> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Drivers(64-bit)
(sparc) 4.2.1,REV=1999.11.04.18.29
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdx/install/checkinstall
: /tmp/sh142020: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdx> failed.
No changes were made to the system.
==============================================================================
Installing Package: SUNWmdu
Root Directory: /a/
Ask File: /a/tmp/jass-packages/noask_pkgadd
Source Location: /a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages
Options:
==============================================================================
Processing package instance <SUNWmdu> from </a/tmp/jass-packages/DiskSuite_4.2.1
/sparc/Packages>
Solstice DiskSuite Commands
(sparc) 4.2.1,REV=1999.11.04.18.29
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdu/install/checkinstall
: /tmp/sh142290: cannot create
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <SUNWmdu> failed.
No changes were made to the system.

/a/tmp/jass-packages/DiskSuite_4.2.1/sparc/Packages/SUNWmdr/install/checkinstall
: /tmp/sh141750: cannot create
pkgadd: ERROR: checkinstall script did not complete successfullyCheckinstall errors usually suggest that the package cannot be read by the user nobody.
The FAQ mentions this with respect to patches, but it can affect packages as well:
http://www.science.uva.nl/pub/solaris/solaris2.html#q5.59
5.59) Patch installation often fails with "checkinstall" errors.
Darren

How to Delete and Reset a Lost Root Password on a System With a Mirrored ??

hi All,
we are experiencing problem,lost root password on Solaris 10 Sparc T5120, with mirror root,
and we found the solution from Metalink.oracle.com, has anyone have try this??
here list capture the file system :
Filesystem size used avail capacity Mounted on
*/dev/md/dsk/d10 2.0G 349M 1.6G 18% /*
*/dev/md/dsk/d40 9.8G 563M 9.2G 6% /usr*
*/dev/md/dsk/d30 9.8G 1.4G 8.4G 15% /var*
*/dev/md/dsk/d50 7.9G 310M 7.5G 4% /opt*
*/dev/md/dsk/d600 3.8G 4.3M 3.8G 1% /home*
*/dev/md/dsk/d602 471M 20M 404M 5% /app/controlm*
*/dev/md/dsk/d601 471M 251M 173M 60% /app/ctsa*
*/dev/md/dsk/d604 4.9G 1.1G 3.8G 23% /app/oramon*
*/dev/md/dsk/d603 20G 11G 8.2G 58% /app/oracle*
*/dev/md/dsk/d606 39G 10.0G 29G 26% /proj/iprdb01/orafra/iprod01p*
here the step :
Solstice DiskSuite[TM] Software: How to Delete and Reset a Lost Root Password on a System With a Mirrored Root Disk [ID 1010755.1]
Solution
Steps to Follow
How to delete and reset a lost root password on a system with a mirrored root disk.
1) Insert the Solaris[TM] Operating System CD-ROM into the CD-ROM drive.
2) Once the CD-ROM is in the drive, perform a stop-a. This brings the system down to the "ok" prompt.
3) From the "ok" prompt, perform a single-user boot from the Solaris OS CD-ROM.
ok boot cdrom -s4) At the "#" prompt, determine which disk is the system's boot disk (containing the root file system). There are several Oracle architectures and various configurations of systems when it concerns a boot disk. As a general rule, most boot disks are attached to controller 0 (c0). Usually, their SCSI target is
either 3 (t3) or 0 (t0). However, Oracle machines are very flexible, and the boot disk could be at a different location. If you are not sure which disk is your boot disk, perform the following steps to determine the location of the boot device:
a) # eeprom boot-device
The output might appear to be simple, such as "disk" or "disk1" or more complicated, such as a pathname "/iommu/sbus/espdma@4,8400000/...../sd@3,0:a".
b) Make note of the boot-device. If the boot-device is a pathname, it is beyond the scope of this information to provide the location of the customized boot disk. However, for most configurations,
finding the customized boot disk is an easy task. The "Format" command shows all available disks:
#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
(enter its number): c) Enter d to exit format.
Now, you will have an idea what disks are on the system. Therefore, if the boot-device is "disk" and format shows "c0t0d0" (on some systems "c0t3d0") then that is the boot device. If boot-device
shows "disk1" and format shows "c0t1d0," then that is the boot device. If format shows multiple disks, then based on what the "eeprom boot-device" command shows, the system's boot disk would be:
boot-device format
disk c0t0d0 or c0t3d0 (machine dependent)
disk1 c1t0d0
disk2 c0t2d0
disk3 c0t3d0 or c0t0d0 (machine dependent)
and so on ....
5) Because the system was not brought down gracefully (no root password means having to use the Stop-a keystroke to "crash" the system), you need to run "fsck" to clean the root partition (slice). The fsckalso confirms that you selected the proper slice.
# fsck /dev/rdsk/c1t0d0s0
where the X and Y are determined by the previous procedure. It is also possible to have a root partition which is not on slice 0 (s0), but, again, that is not a standard configuration.
The output of "fsck" looks like this:
** /dev/rdsk/c1t0d0s0
** last mounted on /
** Phase 1 .....
The second line in the output of "fsck" ("** Last mounted on /") confirms that this is the correct root filesystem partition. Answer "y" to any questions fsck asks. There shouldn't be too many items
needing repair. If there are, there is a possibility of a corrupted root filesystem. After fsck is finished, mount the root partition:
# mount /dev/dsk/c1t0d0s0 /a
Again, X and Y are the same as for the fsck command.
For example:
# mount /dev/dsk/c1t0d0s0 /a
6) From the root prompt, set the proper TERM type command (such as vt100, dtterm, sun, and so on)
by entering this command:
# TERM=sun; export TERM
7) Use the VI text editor to edit the /etc/shadow file:
# vi /a/etc/shadow
8) The first line of the /etc/shadow file is the one you want to modify.
It looks like this:
root:c3.yAVmYodWsc:6445::::::
9) Delete every character between the first and second colons in the first line of the file. When you finish deleting the characters, the line should look like this:
root::6445::::::
10) Press the Escape key, then enter the following to save the file and exit vi:
:wq!
11) Use the VI text editor to edit the /etc/system file andremove the "rootdev" line shown below:
# vi /a/etc/system
*rootdev:/pseudo/md@0:0,0,blk
Don't comment out the "rootdev" line. Actually remove it.
12) In the /a/etc/vfstab file, replace the lines for the system filesystem meta-devices with their underlying partitions. For example, change lines from
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no -
to
/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
ONLY change the lines for root (/) and the filesystems that were affected by the actions you took in step 1 of this procedure. All other metadevices may stay as is in this file.
13) Unmount root, check the root filesystem, and then stop the system:
# cd /
# umount /a
# fsck /dev/rdsk/c1t0d0s0
# stop-a
14) Boot to single-user mode:
ok boot -swTHIS STEP IS VERY IMPORTANT; YOU MUST BOOT TO SINGLE-USER MODE TO AVOID FILESYSTEM CORRUPTION.
If the system does not boot to single user mode, you might have made a mistake in the previous steps.
15) Because the root password was cleared in an earlier step, press Return when prompted for the the root password. Once you are in single-user mode, you must clear the metamirrors and all the sub-mirrors for the root filesystem. For example, if root (/) is d0, run the following command:
# metaclear -f -r d0
Running the metaclear command not only clears the metamirror but also clears the submirrors that are part of this mirror.
16) When the metamirror is cleared, continue the boot up to multiuser mode by either pressing CTRL-D or by entering the following:
# exit
Now everything should be as it was, except that the system partition is on the underlying partition and isn't mirrored. You will simply need to re-create the metadevices for the root mirror as you had originally.
many thanks

Hi,
Halt your machine.
Boot with fail-safe mode.
format and list out the disks. (You can get the root & mirror disk (c#t#d#) details from /etc/lvm/md.tab of your root or mirror disk. Earlier explorer output may help)
Mount the root disk and remove the password entry in /etc/shadow
umount it.
Mount the mirror disk and remove the password entry in /etc/shadow
umount it.
reboot the server.
Hope this helps!

Solstice disksuite

Similar Messages

Maybe you are looking for