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

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.

  • DiskSuite and Live Upgrade 2.0

    I have two Solaris 7 boxes running DiskSuite to mirror the O/S disk onto another drive.
    I need to upgrade to Solaris 8. In the past I have used Live Upgrade to do so, when I have enough free disk space to partition an existing disk or to use a unused disk for the Solaris 8 system files.
    In this case, I do not have sufficient free space on the boot disk. So, what is the best approach? It seems that I would have to:
    1. unmirror the file system
    2. install Solaris 8 onto the old mirror drive using LU 2.0
    3. make the old mirror drive the boot drive
    4. re-establish mirroring, being sure that it goes the right way from the Solaris 8 disk to the old boot disk
    Comments, suggestions?

    I recently built a system (specs below) and installed this card (MSI GF4 Ti4200 VTD8X MS8894, 128MB DDR), and when I try to use Live Update 2 (version 3.33.000, from the CD that came with the card), I get the same message:
    "Warning!!! Your Display Card does not support MSI Live Update 2 function.  Note: MSI Live Update 2 supports the Display Cards of MSI only."
    I'm using the drivers/BIOS that came on the CD: Driver version 6.13.10.4107, BIOS version 4.28.20.05.11.  I see on the nVidia site that they have the 4109 drivers out now, should I try those?  ?(
    I have also made sure to do the suggested modifications to IE (and I don't have PC-cillin installed):
    "Note: In order to operate this application properly, please note the following suggests.
    -Set the IE security setting 'Download signed ActiveX controls' to [Enable] or [Prompt]. (System default is [Prompt]).
    -Disable 'WebTrap' of PC-cillin(R) or any web based anti-virus application when executing MSITM Live Update 2TM.
    -Update Microsoft® Windows® Installer"
    I downloaded a newer version of LIveUpdate (3.35.000), and installed it (after completely uninstalling the old version), and got the same results.  Nothing on my system is currently overclocked.
    Help!
    System specs:
    -Soyo SY-KT400 DRAGON Ultra (Platinum Edition) with latest BIOS & Chipset Drivers
    -AMD Athlon XP Thoroughbred 2100+
    -MSI GF4 Ti4200 VTD8X (MS-8894)
    -WD Caviar Special Edition 80 GB HDD, 8 MB Cache
    -512 MB Crucial PC2700 DDR (one stick, in DIMM #1)
    -TDK 40/12/48 CD R/RW
    -Daewoo 905DF Dynaflat 19" Monitor
    -Windows XP Home Edition, SP1/all other updates current
    -On-Board CMedia 6-channel audio
    -On-Board VIA 10/100 Ethernet
    -Altec-Lansing ATP3 Speakers

  • Upgrade solaris 8 to solaris 10 with DiskSuite

    Hello
    After years of not using Solaris I find I have to upgrade a Sun V240 from Solaris 8 to Solaris 10. My concern is that the disks are managed by DiskSuite. Do I have to back DiskSuite out before I do the upgrade and upgrade just on the underlying disks? Or is Solaris clever enough to not have to do this now?
    I have looked around but would just like a definative answer from someone on here.
    Many Thanks
    Darren.

    Hi,
    You can use a IEAK 10 to deploy the installation of IE 10, build your own package, you can add any additional installations or updates you may want to tack onto your Internet Explorer 10 instal.
    This is the download link
    Internet Explorer Administration Kit 10
    http://www.microsoft.com/en-in/download/details.aspx?id=36807
    Detailed instructions are listed in the following link
    Utility Spotlight: Build your own Internet Explorer 10 installation
    http://technet.microsoft.com/en-us/magazine/dn133229.aspx
    Yolanda Zhu
    TechNet Community Support

  • 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

  • Increasing filesystem size in disksuite

    I need to increase the size of a file system on a Solaris 9 server. The filesystem is apparently a metadevice, it shows in /etc/vfstab as:
    /dev/md/dsk/d15 /dev/md/rdsk/d15 /opt/inlum ufs 1 yes -
    metastat:
    d15: Concat/Stripe
    Size: 37749760 blocks (18 GB)
    Stripe 0:
    Device Start Block Dbase Reloc
    emcpower0a 0 No No
    Stripe 1:
    Device Start Block Dbase Reloc
    emcpower0e 0 No No
    Device Relocation Information:
    Device Reloc Device ID
    emcpower0a No -
    emcpower0e No -
    c1t1d0 Yes id1,ssd@w20000004cffb86e8
    c1t0d0 Yes id1,ssd@w20000004cffb84fa
    The filesystem is also has disks allocated to it on an emc san, shows in format as:
    2. c2t0d0 <DGC-RAID5-0099 cyl 40958 alt 2 hd 256 sec 10>
    /pci@8,700000/fibre-channel@3/sd@0,0
    3. emcpower0a <DGC-RAID5-0099 cyl 40958 alt 2 hd 256 sec 10>
    /pseudo/emcp@0
    I'm trying to increase the size of this file system, so I choose #2, used slice 5 because 5 corresponds to "e" in emcpower0e, allocated the rest of the remaining space (25Gb) to that slice through format:
    5 unassigned wm 20482 - 40957 25.00GB (20476/0/0) 52418560
    I really have no background in emc, used disksuite once to mirror filesystems with metatool, so I am really going into this blindly. I think what I need to do now is:
    newfs the slice I just created above with:
    newfs /dev/rdsk/c2t0d0s5
    Now this is where I really don't know where to go, I need to add this slice to the metadevice d15, do I do it with metattach, like:
    metattach d15 /dev/dsk/c2t0d0s5 ?
    and are there other commands I need to do in addtion to this like metainit or metaclear?
    Can the system be used while I'm doing this?
    Once the slice is added to the metadevice, I believe I use growfs like:
    growfs /opt/inlum /dev/md/rdsk/d15
    Is this the correct procedure? Please add any commands I need or corrections to my shot in the dark procedure. Thanks a lot.

    If you want just to add space to a disk through MD, should be pretty easy to do through the SMC.
    Open the existing volume that's controlled MD and add the slice to it. You may have to format the disk to allocate the slice.
    Then run
    #growfs /dev/md/dsk/d<number>

  • 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.

  • 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.

    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!

  • Bad Magic Number in Disk Label & DiskSuite

    Envrionment:
    E450
    Solaris 8
    DiskSuite 4.2.1
    16 disks
    Because of a power failure, after reboot one of the disks has bad magic number in its disk label. The slice was in a mirror. DiskSuite has hot spares and one of them took over the failed slice. I am trying to figure out how to get it back to where it was.
    I think I should use 'format' to recover the disk label from the backup label. However, once the label is recovered, how do I make it stop using the hotspare and have the failed slice join back to the mirror?
    Sorry if this is basic question, I am relatively new to Sun/Solaris and I just took over the E450.
    Thanks,

    Envrionment:
    E450
    Solaris 8
    DiskSuite 4.2.1
    16 disks
    Because of a power failure, after reboot one of the
    disks has bad magic number in its disk label. The
    slice was in a mirror. DiskSuite has hot spares and
    one of them took over the failed slice. I am trying to
    figure out how to get it back to where it was.
    I think I should use 'format' to recover the disk
    label from the backup label. However, once the label
    is recovered, how do I make it stop using the hotspare
    and have the failed slice join back to the mirror?
    Sorry if this is basic question, I am relatively new
    to Sun/Solaris and I just took over the E450.
    Thanks,Since the host spare took over then you're free to repair/replace the bad drive. In this case you could check the drive using format and partition to view the partitions. If the label is bad then I would suspect the drive is still good and a simple format>label and save command would repair the label. Then once this is done if all goes well then the system should rebuild the drive and the hot spare will not longer be used. The system should regonize the drive as a replacement and rebuild it then stop using the hot spare.
    Michael

  • Does Solaris 8 come with Disksuite? If so where is it?

    We have recently purchased a Netra T1 which comes with Solaris 8
    pre-installed (and no CD Roms). I want to be able to configure the 6 SCSI
    drives that we have with this machine as a single device - and I believe that
    the tool I need for this is called 'DiskSuite'.
    However I can't find any of the disksuite commands on our machine, and
    it doesn't look like it is installed.
    Can anybody tell me:
    - Is Disksuite the tool that I need to join multiple disks together into
    a single Raid5 device?
    - If so, is it supplied with Solaris 8
    - And if so, where can I get hold of it?
    Many thanks,
    Chris Allen
    [email protected]

    you can download the software 2 of 2 cd, which has the Disksuite 4.2.1 software on it, from:
    http://wwws.sun.com/software/solaris/binaries/get.html
    The documentation for the disksuite package can be found at docs.sun.com
    ct

  • Installing disksuite 4.2.1

    Hello,
    I am about to install Disksuite 4.2.1 on top of Solaris 8.
    I have FINALLY located some pkgs for this on the Solaris 8 Software CD disk2. I have found the following pkgs on this cd in /cdrom/sol_8_1000_sparc_2/Solaris_8/EA/products/DiskSuite_4.2.1/sparc/Packages -
    SUNWmdg
    SUNWmdja
    SUNWmdnr
    SUNWmdnu
    SUNWmdr
    SUNWmdu
    SUNWmdx
    Going on some notes I have, I am also supposed to have in the same directory, and supposed to install the following -
    SUNWlvma
    SUNWlvmg
    SUNWlvmr
    But I can't see these pkgs in this dir. Do these also need to be installed ??
    Thx
    Trev

    Forget it.
    Don't think I need these pkgs. Have installed all others and will see how I go.
    Cheers

  • 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

  • Will Solaris 10 (Jun/2006) zfs edition consider DiskSuite

    Hi..
    I previously upgraded a Sol8 server to Sol10 (Jan/06 without zfs), but it could not perform a upgrade as the disk array had to be unplugged (which was a metastat configuration). So I had to perform a fresh install, and reconfigure DiskSuite which picked up the data and databases correctly for use after the install. This was all with help from a SUN Support case. Anyways..does anyone know if the zfs version of the O/S is smarter and knows how to deal with metastat during an upgrade? I have a production box that is still on Sol 8, with a complex metastat configuration that I will have to upgrade one day soon. But the test box that I took from Sol 8 to Sol 10 (Jun/2006) O/S was difficult as that version of the upgrade could not deal with the DiskSuite configured 3310 disk array.
    Please email me at [email protected] if anyone has an update or suggestions
    Thanks for reading...Cheers...Roger

    Hi Darren...
    Well I raise CASE: 10815118 with support. On the LIVE Upgrade from Sol 8 to 10 (Jan 2006) attempt and the install_log produced the following...
    =========>
    Error opening file /a/var/sadm/system/admin/CLUSTER.
    getInstalledPkgs: Unable to access /a/var/sadm/pkg
    copyOldClustertoc: could not copy /a/var/sadm/system/admin/.clustertoc to /tmp/clustertocs/.old.clustertoc
    Error:
    Error: ERROR: The specified root and/or boot was not found or was not upgradeable
    Pfinstall failed. Exit stat= java.lang.UNIXProcess@20ca8b 2
    word must be specified if an upgrade with disk space reallocation is required
    Processing profile
    Checking c2t0d0s0 for an upgradeable Solaris image
         Unable to start Solaris Volume Manager for unknown, c2t0d0s0 is not upgradeable
    ERROR: The specified root and/or boot was not found or was not upgradeable
    ===============<
    It seems to look for a disk (controller c2) that did not exist. I copied the DiskSuite files and other system files to another server. the /etc/lvm/md.tab under Sol 8 looked like the following...
    ================>
    # root (on O/S disks 5 GB)
    d0 -m d10
    d10 1 1 c1t0d0s0
    d20 1 1 c1t1d0s0
    # swap (on O/S disks 8 GB)
    d1 -m d11
    d11 1 1 c1t0d0s1
    d21 1 1 c1t1d0s1
    # var (on O/S disks 4 GB)
    d3 -m d13
    d13 1 1 c1t0d0s3
    d23 1 1 c1t1d0s3
    # archive (on O/S disks 5 GB)
    d4 -m d14
    d14 1 1 c1t0d0s4
    d24 1 1 c1t1d0s4
    # usr/openv (on O/S disks 9 GB)
    d6 -m d16
    d16 1 1 c1t0d0s6
    d26 1 1 c1t1d0s6
    # /export/home (on O/S disks 3.7 GB)
    d7 -m d17
    d17 1 1 c1t0d0s7
    d27 1 1 c1t1d0s7
    # array 3310
    # /software ( approx 140 GB)
    d30 -m d40
    d40 1 6 c3t8d0s1 c3t9d0s1 c3t10d0s1 c3t11d0s1 c3t12d0s1 c3t13d0s1 -i 128b
    d50 1 6 c4t8d0s1 c4t9d0s1 c4t10d0s1 c4t11d0s1 c4t12d0s1 c4t13d0s1 -i 128b
    # /databases ( approx 204 GB)
    d31 -m d41
    d41 1 6 c3t8d0s3 c3t9d0s3 c3t10d0s3 c3t11d0s3 c3t12d0s3 c3t13d0s3 -i 128b
    d51 1 6 c4t8d0s3 c4t9d0s3 c4t10d0s3 c4t11d0s3 c4t12d0s3 c4t13d0s3 -i 128b
    # /spare ( approx 92 GB)
    d32 -m d42
    d42 1 6 c3t8d0s4 c3t9d0s4 c3t10d0s4 c3t11d0s4 c3t12d0s4 c3t13d0s4 -i 128b
    d52 1 6 c4t8d0s4 c4t9d0s4 c4t10d0s4 c4t11d0s4 c4t12d0s4 c4t13d0s4 -i 128b
    ===============<
    We had c1 for the O/S disks and c3 & c4 for the 3310 array. Why it was looking for c2 was never determined???
    The Sun support mob under that CASE ID suggested after many attempts to perform an upgrade...
    =================>
    In this situation, I recommend:
    1. Remove Disk Array from Server i.e detach the connecting cable
    2. Please check if Internal Disks are visible at OK prompt.:
    ok probe-scsi-all
    ==================<
    So I unplugged the array, but because there was no spare disk, I had to end up performing a fresh install, then attach and reconfigure the array exactly as before then the data, and more importantly, the Oracle databases and applications where recovered and useable.
    So the question now is ... the server is on sol 10 and I have now rec'd the sol 10 Jun 2006 media...is it possible to perform an upgrade and how will zfs deal with the disksuite defs, because it have real problems under Sol 10 Jan 2006 edition.
    Also, with the SUN engineers, on that CASE ID...we never got to the bottom of the problem with upgrading from sol 8 to 10 with disksuite implemented.
    Cheers...Roger

  • 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

Maybe you are looking for