Solaris 7 Disk Suite 4.2 on X86

Solaris 7 Disk Suite 4.2 on X86

Post by Joe Salin » Tue, 15 Jun 1999 04:00:00



I feel I must be missing something.
I have an Intel motherboard  with an onboard Symbios Logic
SCSI controller. I have 2 WD SCSI drives attached. Drive 0 has
Solaris installed. I want to mirror drive 0 to drive 1.

I have tried reading the Easy Access documentation. I have searched
docs.sun.com. I just can't grasp the meta* concept. I want to. Badly.

How do I set up a disk with the operating system, allowing space to
add a metadb replica? I set the disk up, leaving unused space in
slice 3 (c0t0d0s3). Metatool will not allow me to use it to store
a DB replica. I reinstalled, leaving space out of the partitions.
Still unable to use. I have been successful at adding two slices
with two replicas each to disk 1, but this seems to useless in event
disk 1 dies.

What do I have to do to disk 1 to allow me to copy the layout of disk 0
onto it? I have formatted it, same size slices as disk 0, no mount
points specified. Trying to copy disk 0 layout and past to disk 1
yields errors like "c0t0d0s9 and c0t1d0s9 both in use and not
compatible". I have low level formatted it, no slice layouts, same
errors.

I am not adverse to reading how to do it, just can't seem to find
where. The Solaris documentation CD tells me to simply select the
slice I want to use, and drag it over to the device I want to use
it in. I have not been successful.

Any help is appreciated. RTFM understood, URL's welcome.

thank you
Joe Saling
Volunteered sys admin

 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by Dennis Clark » Wed, 16 Jun 1999 04:00:00


Whenever I see a message about disksuite frustrations, I feel compelled
to write.  Thus, here I am.  DiskSuite is one of my favorite products
and I mirror everything I can.

First, you task of mirroring two drives with DiskSuite can be done in
under 30 minutes by a seasoned DiskSuite type, be of good cheer, you're
doing fine.   Don't expect to see it as being obvious for a while.  For
all intents and purposes, think of a metadevice as any other disk type
device.  For the most part, you need not know the nitty gritty bits
about how data really gets to the surface of your hard-disk do you?  It
would take years of study in materials physics and computer programming
to really get it.  I don't.  The metadevice is like a 'magic' disk drive
that just happens to distribute data reads and writes to a set of
submirrors.  It is a driver based interface to your actual hardware and
all you really need to know to get things working is HOW to get it
working, not WHY it is working.  Once it is up and running for you, then
you can read the manuals to your hearts content, but for now, let's just
make it work.

Step 1) Install Solstice DiskSuite properly.

OK, well, you happen to be running Solaris 7 for x86.  I have Solaris 7
for Sparc here as well as Solaris 2.5.1 for x86 ( this workstation ) and
both are using DiskSuite ( see above - I mirror everything ) and the
word "everything" is pronounced with a roll of the head and a wave of
the hands for dramatic effect.  You have to read carefully to see that.

Follow the standard package installation process to get SUNWmd
installed.  When done, you should be able to check it with pkginfo -l
SUNWmd :

$ pkginfo -l SUNWmd
   PKGINST:  SUNWmd
      NAME:  Solstice DiskSuite
  CATEGORY:  system
      ARCH:  all
   VERSION:  4.0,REV=1.0
   BASEDIR:  /
    VENDOR:  SunSoft, a Sun Microsystems, Inc. Business
      DESC:  SunSoft's Solstice DiskSuite
    PSTAMP:  airjazz950414160211
  INSTDATE:  Dec 11 1998 13:40
    VSTOCK:  258-4903-10
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:     75 installed pathnames
                41 shared pathnames
                22 directories
                23 executables
              6948 blocks used (approx)

That was the x86 version 4.0 for 2.5.1.  The Sun hardware says the
following :

$ pkginfo -l SUNWmd
   PKGINST:  SUNWmd
      NAME:  Solstice DiskSuite
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  4.2,REV=1998.02.09.12.47.28
   BASEDIR:  /
    VENDOR:  Sun Microsystems, Inc.
      DESC:  Solstice DiskSuite
    PSTAMP:  09/02/98-13:04:05
  INSTDATE:  May 29 1999 00:08
    VSTOCK:  258-6252-11
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:     95 installed pathnames
                22 shared pathnames
                25 directories
                37 executables
             13496 blocks used (approx)

I have no idea why the ARCH tag says 'all' for x86 on 2.5.1 and is
correct with 'sparc' for Solaris 7 on Sparc.  Let's not worry about it,
some Sun SE can answer that sort of minutia.

Step 2 ) Set up your drive slices accordingly  :)

The smile will tell you that you had better see DiskSuite being in your
plan from the beginning because its a bit of a pain if you need to free
up a slice for the metadbs.  Without going to the manual, here are the
next steps ...

Suppose that you have the following disks ...

Example 1) Sun Sparc 20 with dual drives ...

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t1d0 <SUN4.2G cyl 3880 alt 2 hd 16 sec 135>

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0
       1. c0t3d0 <SUN4.2GB cyl 3880 alt 2 hd 16 sec 135>

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0
Specify disk (enter its number):

Then it seems reasonable to mirror these identical drives.  But you
don't need to have identical drives!  You can mirror a 256Mb slice with
a 1Gb slice if you want, I don't recommend it.  DiskSuite will only
mirror 256Mb of the filesystem and ignore the wasted area of the misfit
second submirror slice.  For the sake of seeing a real hack, here is my
x86 workstation made from whatever drives were kicking about at the time
:)

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <DEFAULT cyl 3904 alt 2 hd 5 sec 105>
          /pci@0,0/pci1000,1@1/cmdk@0,0
       1. c0t2d0 <DEFAULT cyl 2992 alt 2 hd 10 sec 140>
          /pci@0,0/pci1000,1@1/cmdk@2,0
       2. c0t3d0 <CONNER-CFP1060S1.05GB-2035 cyl 2312 alt 2 hd 8 sec
112>
          /pci@0,0/pci1000,1@1/cmdk@3,0
Specify disk (enter its number):

Take note that these drives are a real miss-mash of whatever.  With
DiskSuite, it doesn't matter that the drive geometry is different (
actually, for performance, it does, but lets not split hairs for now )
you can mirror any thing with almost anything.  You can concatenate
anything with anything.  Just don't make your submirrors or
sub-components of a concat on the same drive! That will cause incredible
drive thrashing for obvious reasons.

OK, so here is the partition layout of the Sparc20 :

                   Target 1 drive ...
format> curr
Current Disk = c0t1d0
<SUN4.2G cyl 3880 alt 2 hd 16 sec 135>
/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0
<snip>
Current partition table (original):
Total disk cylinders available: 3880 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       0 -  121      128.67MB    (122/0/0)   263520
  1        var    wm     122 -  364      256.29MB    (243/0/0)   524880
  2     backup    wu       0 - 3879        4.00GB    (3880/0/0) 8380800
  3       swap    wu     365 -  607      256.29MB    (243/0/0)   524880
  4 unassigned    wm     608 -  617       10.55MB    (10/0/0)     21600
  5 unassigned    wm     618 - 2559        2.00GB    (1942/0/0) 4194720
  6        usr    wm    2560 - 3818        1.30GB    (1259/0/0) 2719440
  7 unassigned    wm    3819 - 3879       64.34MB    (61/0/0)    131760

                  Target 3 drive ...
format> curr
Current Disk = c0t3d0
<SUN4.2GB cyl 3880 alt 2 hd 16 sec 135>
/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0
<snip>
Current partition table (original):
Total disk cylinders available: 3880 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       0 -  121      128.67MB    (122/0/0)   263520
  1        var    wm     122 -  364      256.29MB    (243/0/0)   524880
  2     backup    wm       0 - 3879        4.00GB    (3880/0/0) 8380800
  3       swap    wu     365 -  607      256.29MB    (243/0/0)   524880
  4 unassigned    wm     608 -  617       10.55MB    (10/0/0)     21600
  5 unassigned    wm     618 - 2559        2.00GB    (1942/0/0) 4194720
  6        usr    wm    2560 - 3818        1.30GB    (1259/0/0) 2719440
  7 unassigned    wm    3819 - 3879       64.34MB    (61/0/0)    131760

PAY PARTICULAR ATTENTION TO SLICE s4 on these identical drives ...

That tiny little slice is where the metadb replica databases are going.

My x86 system is similar but for the moment lets stick with a sane
system that will have identical drives like yours.

Step 3 ) Create the metadb replica databases ...

Because you must have at least two metadb replicas available for the
system to work, I suggect that your chosen slice have two metadb
replicas in it, on each drive.  That way you have four metadbs in total
and you can lose either drive and keep running.

su to root and set up your path for sanity ...

PATH=/usr/sbin:/usr/bin:/usr/opt/SUNWmd/sbin;export PATH

and then create the metadbs in /dev/dsk/c0t1d0s4 and /dev/dsk/c0t3d0s4
and make sure your boot drive has the first metadb replica db ...

# metadb -a -c 2 -f /dev/dsk/c0t3d0s4 /dev/dsk/c0t1d0s4

and that creates the four needed dbs as ( note "-c 2" ) 2 dbs per slice.

Check your /etc/system file and you will see some new stuff at the
bottom :

* Begin MDD database info (do not edit)
set md:mddb_bootlist1="sd:28:16 sd:28:1050 sd:12:16 sd:12:1050"
* End MDD database info (do not edit)

At this point, if you want, you can reboot.  You will see a stack of
WARNING messages, not errors, WARNINGS only ( hand waving again ) about
a stack of failures due to raid this and trans that not loading.  Ignore
this.  Everyone has fits when they see it thinking it means some
catastrophe has happened to their system.  Not yet.  :)  If you use
metadb -i you should see

# metadb -i
        flags           first blk       block count
     a m  p  luo        16              1034          
/dev/dsk/c0t3d0s4
     a    p  luo        1050            1034          
/dev/dsk/c0t3d0s4
     a    p  luo        16              1034          
/dev/dsk/c0t1d0s4
     a    p  luo        1050            1034          
/dev/dsk/c0t1d0s4
 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/opt/SUNWmd/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
#

Step 4 ) Mirror your root filesystem.

Figure out where your root submirror slices are.  Hopefully they are s0
on both drives.

Edit the file /etc/opt/SUNWmd/md.tab and put in the following ...

# root mirror
d10 1 1 /dev/dsk/c0t3d0s0
d0 -m d10
d20 1 1 /dev/dsk/c0t1d0s0

And then save this file.  Don't worry that the manual says you need to
type in /dev/md/dsk/d10 in the place of d10, you don't need it.
Solstice DiskSuite ...

read more »

 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by Joe Salin » Wed, 16 Jun 1999 04:00:00


I can not thank you enough! I followed your directions, and right
now am enjoying the sound of a lot of drive thrashing as my mirrors
sync.

Thank you!
Joe Saling


> Whenever I see a message about disksuite frustrations, I feel compelled
> to write.  Thus, here I am.  DiskSuite is one of my favorite products
> and I mirror everything I can.

 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by J.D. Baldw » Thu, 17 Jun 1999 04:00:00




> Step 1) Install Solstice DiskSuite properly.

> [...]

> Step 2 ) Set up your drive slices accordingly  :)

You forgot step 1.5:  get and install appropriate patches.  (Though
that could reasonably be said to be implied by the last word of
Step 1.)  Particularly in the case of 4.1, that can be a significant
stability enhancer.
--
 From the catapult of J.D. Baldwin  |+| "If anyone disagrees with anything I

 _|70|___:::)=}-  for PGP public    |+| retract it, but also to deny under
 \      /         key information.  |+| oath that I ever said it." --T. Lehrer
***~~~~-----------------------------------------------------------------------
 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by Dennis Clark » Fri, 18 Jun 1999 04:00:00


Ya gotta love all those patches.

Dennis




> > Step 1) Install Solstice DiskSuite properly.

> > [...]

> > Step 2 ) Set up your drive slices accordingly  :)

> You forgot step 1.5:  get and install appropriate patches.  (Though
> that could reasonably be said to be implied by the last word of
> Step 1.)  Particularly in the case of 4.1, that can be a significant
> stability enhancer.
> --
>  From the catapult of J.D. Baldwin  |+| "If anyone disagrees with anything I

>  _|70|___:::)=}-  for PGP public    |+| retract it, but also to deny under
>  \      /         key information.  |+| oath that I ever said it." --T. Lehrer
> ***~~~~-----------------------------------------------------------------------

--
Your computer needs a hobby! Join the distributed RC5-64 decryption!
Go to http://www.distributed.net/ for the fastest computer on earth!

  d.clarke2.vcf
< 1K Download
 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by t.. » Fri, 18 Jun 1999 04:00:00


Great!

btw, can someone throw some light on StorEdge A1000 with
RAID manager software, how it could run in parallel on a
system running DiskSuite driver, or any other suggestions..

Any reply will be appreciated...

-Tom



> I can not thank you enough! I followed your directions, and right
> now am enjoying the sound of a lot of drive thrashing as my mirrors
> sync.

> Thank you!
> Joe Saling


> > Whenever I see a message about disksuite frustrations, I feel
compelled
> > to write.  Thus, here I am.  DiskSuite is one of my favorite
products
> > and I mirror everything I can.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by J.D. Baldw » Sun, 20 Jun 1999 04:00:00




> Ya gotta love all those patches.

And I do!  If this stuff were *trivially* easy to maintain (instead of
merely easy), I wouldn't be the lucky, overpaid, underworked
S.O.B. that I am.
--
 From the catapult of J.D. Baldwin  |+| "If anyone disagrees with anything I

 _|70|___:::)=}-  for PGP public    |+| retract it, but also to deny under
 \      /         key information.  |+| oath that I ever said it." --T. Lehrer
***~~~~-----------------------------------------------------------------------
 
 
 

Solaris 7 Disk Suite 4.2 on X86

Post by Dennis Clark » Mon, 21 Jun 1999 04:00:00


hey ... don't spread that around!  This is back-breaking work!  And I'm
underpaid!




> > Ya gotta love all those patches.

> And I do!  If this stuff were *trivially* easy to maintain (instead of
> merely easy), I wouldn't be the lucky, overpaid, underworked
> S.O.B. that I am.
> --
>  From the catapult of J.D. Baldwin  |+| "If anyone disagrees with anything I

>  _|70|___:::)=}-  for PGP public    |+| retract it, but also to deny under
>  \      /         key information.  |+| oath that I ever said it." --T. Lehrer
> ***~~~~-----------------------------------------------------------------------

--
Your computer needs a hobby! Join the distributed RC5-64 decryption!
Go to http://www.distributed.net/ for the fastest computer on earth!

  d.clarke2.vcf
< 1K Download
 
 
 

1. Solstice Disk Suite 4.2 for Solaris 2.6

Anyone know how I would go about purchasing (presumably used since it's not
listed on the Sun website any more, a legal copy of Solstice Disk Suite v
4.2 for Solaris 2.6.  I need to do some work on an old crusty box, but I'm
having a hard time tracking this down.

Thanks in advance,

                        -John

2. Help Modem not working

3. Disk Suite 4.2

4. Pulled NIC card out, now machine won't boot..

5. Disk Suite 4.2 problem

6. Bootable Tape

7. How can I get Solaris Admin Suite for Solaris 8 (x86)

8. De-frag utility for Unix?

9. SunSSH erratic behaviour after applying SST (Jass) 4.2 to a Solaris 10 x86 box.

10. Solaris 2.6 x86, C++ 4.2, Templates

11. Where to buy Corel WordPerfect (Suite 7) for Solaris 2.5.1 x86 ?

12. Solaris x86 Server Suite Wins LAN Times 'Best Of Show'

13. Solaris 2.6 with Sybase 11.0.3 and Solstice Disk Suite 4.1: Advice/Problems??