Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 366
  • Last Modified:

Can't configure DiskSuite ( Solaris 8/ Intel )


I am trying to configure DiskSuite Tool.

Before you can use DiskSuite, you must create at least 3 state database replicas. You can do it either from the command line or through the DiskSuite.

As suggested in documentation, i created a slice ( through the format command ) to hold these state databases ( c0d0s5)


Then I opened DiskSuite ( metatool & ) , from the Objects list, dragged the MetaDB object onto the canvas , clicked Disk View to display the Disk View window, selected View All Controllers from the View menu in the Disk View window....

There were no any controllers, disks, and slices. The "Disk View" window was empty.

2) I also tried to create initial State database replicas through the command line.


Here is an example from the User's guide :

Example -- Creating Initial State Database Replicas on a System With Three Disks
metadb -a -f -c 2 c0t1d0s3 c1t1d0s3 c2t1d0s3

By spreading the state database replicas across controllers, you can increase metadevice performance and reliability.


I have 2 disks ( c0d0 and c0d1 )

Here is a copy from my server :




c0d0p0 c0d0s11 c0d0s5 c0d1p3 c0d1s14 c0d1s8
c1t0d0s1 c1t0d0s3 c0d0p1 c0d0s12 c0d0s6
c0d1p4 c0d1s15 c0d1s9 c1t0d0s10 c1t0d0s4
c0d0p2 c0d0s13 c0d0s7 c0d1s0 c0d1s2
c1t0d0p0 c1t0d0s11 c1t0d0s5 c0d0p3 c0d0s14
c0d0s8 c0d1s1 c0d1s3 c1t0d0p1 c1t0d0s12
c1t0d0s6 c0d0p4 c0d0s15 c0d0s9 c0d1s10
c0d1s4 c1t0d0p2 c1t0d0s13 c1t0d0s7 c0d0s0
c0d0s2 c0d1p0 c0d1s11 c0d1s5 c1t0d0p3
c1t0d0s14 c1t0d0s8 c0d0s1 c0d0s3 c0d1p1
c0d1s12 c0d1s6 c1t0d0p4 c1t0d0s15 c1t0d0s9
c0d0s10 c0d0s4 c0d1p2 c0d1s13 c0d1s7
c1t0d0s0 c1t0d0s2 core

While i created c0d0s5 to hold these databases , i should give the following command :

metadb -a -f -c 2 c0d0s5 c1d0s5

But i don't have c1d0s5 in /dev/dsk dir

I also tried to put databases on c0d0s5 and c1t0d0s5 : metadb -a -f -c 2 c0d0s5 c1t0d0s5 ( i knew that it was wrong)

and i got error : /dev/dsk/c1t0d0s5 is busy.

Then i tried to put all databases on c0d0s5 only: metadb -a -f -c 3 c0d0s5

After i did it, i opened DiskSuite tool, from the Objects list, dragged the MetaDB object onto the canvas.

It shows that status for MetaDB is critical and in a couple of minutes DiskSuite Tool is closing and i am getting error : Segmentation Fault.
I guess it was not the right way to do it.

Can someone tell me what i am doing wrong and why it is not working ?

Thanks in advance.

1 Solution
Some basics:
each meta db must be in its own partition.  The partition should either be dedicated, or the metadb must be created before anything is put in the partition (after the newfs, I think, but I'd have to check).

Your /dev/dsk is confusing.  You say your disks are c0d0 and c0d1.  Are they IDE disks?  I am used to seeing c0t1d0 and c0t2d0, but that is SCSI.  The /dev/dsk also shows c1d0, which I presume is the cdrom drive, so of course you cannot put a state database there.  Your /dev/dsk also lists values up to ...s14, which is some kind of extended partitioning that I have only seen in Unixware (which is IDE, so that might confirm my conjecture).

You need to create three new partitions, I think they reccomend 5 MB, though you can get away with a somewhat less, probably 2 on the primary drive and 1 on the secondary if possible, assuming you cannot boot the system without the first drive.

you should do a metastat, then delete all the databases defined and start over.  It might help to do a "touch reconfigure" from root on the root slice and reboot (to make sure your /dev/dsk is complete), but that is probably not your problem.

It would not surprise me if the meta databases had to be in 'primary' partitions rather than extended ones, so do that if possible.
innessaAuthor Commented:
Thank you very much for your response.
Yes, I am using IDE disks and i think that's the problem.

Thanks allot.


Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now