PLEASE HELP:->For ROOT Mirroring in Solaris,See Full Information.

jlliagre · 09-10-2013, 10:50 AM

1: where does this fstab content cames from ?

2: read again carefully what you wrote, it is quite obvious there are two disks.

TB0ne · 09-10-2013, 10:52 AM

Quote:

Originally Posted by manalisharmabe

I have some queries:-

Code:

/proc                   -                       /proc   proc    -       no      -
fd                      -                       /dev/fd fd      -       no      -
swap                    -                       /tmp    tmpfs   -       yes     -
#
/dev/dsk/c1t0d0s3       -                       -       swap    -       no      -
/dev/dsk/c1t1d0s3       -                       -       swap    -       no      -
#
#
/dev/dsk/c1t0d0s0               /dev/rdsk/c1t0d0s0              /       ufs     1       no      logging
/dev/dsk/c1t0d0s1               /dev/rdsk/c1t0d0s1              /var    ufs     1       no      logging
/dev/dsk/c1t0d0s4               /dev/rdsk/c1t0d0s4              /u01    ufs     2       yes     logging

Question 1:-
Why swap is shown here 2 times , I mean c1t0d0s3 and c1t1d0s3 ? Is it mirrored ? Well, I have only one disk so I don't think , It's mirrored.

Code:

ash-2.03$ sudo format
Password:
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>  ROOTDSK
          /pci@1c,600000/scsi@2/sd@0,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>  ROOTMIRR
          /pci@1c,600000/scsi@2/sd@1,0
Specify disk (enter its number):

In above information what exactly indicates that there are two disks in system?

is it

1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> ROOTMIRR
/pci@1c,600000/scsi@2/sd@1,0

t1 here or something else, please excuse me for asking this, but I am really confused about the same.

Again, reading the Solaris manuals will tell you the answers. Research first.
http://docs.oracle.com/cd/E19455-01/...680/index.html

Your output is clearly telling you that you have a device called "ROOTMIRR"...and mirroring is what you first posted about doing, isn't it?

manalisharmabe · 09-10-2013, 11:06 AM

Ohh sorry.I forgot to mention

first one is from one system
and second one is from different system, where we have two disks.

Ok so my question is

if c1t0d0s0 and c1t1d0s0 are two different disks, then why beloew it is showing c1t0d0s3 and c1t1d0s3 for swap where we have currently only one disk and another defective disk was removed.

#
/dev/dsk/c1t0d0s3 - - swap - no -
/dev/dsk/c1t1d0s3 - - swap - no -
#
#

Thanks a lot for your replies.

I mean now i am doing freah soalris installation and it is showing below notation for two disks, please see.

jlliagre · 09-10-2013, 11:21 AM

Quote:

Originally Posted by manalisharmabe

if c1t0d0s0 and c1t1d0s0 are two different disks

They are two different slices from two different disks.

Quote:

, then why beloew it is showing c1t0d0s3 and c1t1d0s3 for swap where we have currently only one disk and another defective disk was removed.

#
/dev/dsk/c1t0d0s3 - - swap - no -
/dev/dsk/c1t1d0s3 - - swap - no -
#
#

Probably because when that file was last edited, one of the disks was still functional.

Quote:

I mean now i am doing freah soalris installation and it is showing below notation for two disks, please see.

I'm afraid that with 0MB of available space, you won't be able to install anything.

manalisharmabe · 09-10-2013, 11:34 AM

Ok so you mean to say

/dev/dsk/c1t0d0s3 - - swap - no -
/dev/dsk/c1t1d0s3 - - swap - no - this entry just remain there, even after second disk was removed?

about pic
no see i have space after next steps.
edit:-
So now it clear for that if it is c0t0 and c0t1 that means they are two different disks, right? YES/NO ??

manalisharmabe · 09-10-2013, 11:41 AM

look what I did,

I try to add the same installation as my real scenario server and i gave 32MB for slice7
also took /u01 in action

see pics

manalisharmabe · 09-10-2013, 01:36 PM

Hi Guys,

I have some questions.

1. Do I need to format the new disk when it is inserted in the Server ?

I received this error while doing this:-

Code:

bash-3.00# metadb -afc 2  /dev/dsk/c1t0d0s7 /dev/dsk/c1t1d0s7
metadb: final: c1t1d0s7: device size 0 is too small for metadevice database replica

while installing the OS i had created slice7 on disk 0 as 32MB but did not touch the disk1 at all, but now it is showing above error.
this is what my disk 1 has:-

Code:

partition> p
Current partition table (original):
Total disk cylinders available: 7829 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0 unassigned    wm       0               0         (0/0/0)            0
  1 unassigned    wm       0               0         (0/0/0)            0
  2     backup    wm       0 - 7828       59.97GB    (7829/0/0) 125772885
  3 unassigned    wm       0               0         (0/0/0)            0
  4 unassigned    wm       0               0         (0/0/0)            0
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7 unassigned    wm       0               0         (0/0/0)            0
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

partition>

Do I need to create slice7 of second disk (disk1) also as 32MB?

If YES, then when can I create it when new disk is loaded in Server?

Please guide, I am stuck at this command.

Thanks.

jlliagre · 09-10-2013, 02:51 PM

It looks like you are trying to complete step A2 but have skipped step A1. This isn't going to work.

manalisharmabe · 09-11-2013, 01:10 AM

Thanks jlliagre!

Ok so Step A1 says this:-

Code:

A1) Prepare the partitions of the boot disk (c0t0d0) and the rootmirror disk (c1t0d0)

What actually does this means, what do I need to do here?

Please guide.

Manali

manalisharmabe · 09-11-2013, 09:22 AM

Hi Guys,

This is what the document says:-

Code:

WHAT ACTION DOES THE FIELD ENGINEER/CUSTOMER ADMINISTRATOR NEED TO TAKE:

Follow standard ESD procedures to avoid Electrostatic Discharge

1. Unconfigure the hard drive that you intend to remove. e.g.

# cfgadm -la

# cfgadm -c unconfigure c1::dsk/c1t1d0

2 .Verify that the device is now unconfigured. e.g.

# cfgadm -la

3. Confirm that the hard drive you want to remove from the server is no longer visible to the operating system. e.g.

# format

4. The drive blue LED should now be lit

5. Open front bezel on the server.

6. Slide the catch to the right, remove the drive

7. Slide the catch to the right, install the new drive.

8. Push the metal level until the HDD clicks in place.

9. Close the front bezel.

10. Configure the newly installed hard drive e.g.
# cfgadm -la

# cfgadm -c configure c1::dsk/c1t1d0

11. Confirm that the drive is now connected and configured. e.g.

# cfgadm -la

# format

OBTAIN CUSTOMER ACCEPTANCE

Above is what the document says, but as the faulty drive is already removed i only have to follow step from 7 to 11.

My question is what does this number "10" command cfgadm -c configure c1::dsk/c1t1d0 does to newly installed disk ?

Does it create slice number 7 as 16MB on newly installed disk which is required for mirroring?

Please advise, you people are the only help for me.

Thanks.

TB0ne · 09-11-2013, 10:42 AM

Quote:

Originally Posted by manalisharmabe

Hi Guys,
This is what the document says:-

Code:

WHAT ACTION DOES THE FIELD ENGINEER/CUSTOMER ADMINISTRATOR NEED TO TAKE:

Follow standard ESD procedures to avoid Electrostatic Discharge

1. Unconfigure the hard drive that you intend to remove. e.g.
# cfgadm -la
# cfgadm -c unconfigure c1::dsk/c1t1d0

2 .Verify that the device is now unconfigured. e.g.
# cfgadm -la

3. Confirm that the hard drive you want to remove from the server is no longer visible to the operating system. e.g.
# format

4. The drive blue LED should now be lit
5. Open front bezel on the server.
6. Slide the catch to the right, remove the drive
7. Slide the catch to the right, install the new drive.
8. Push the metal level until the HDD clicks in place.
9. Close the front bezel.
10. Configure the newly installed hard drive e.g.
# cfgadm -la
# cfgadm -c configure c1::dsk/c1t1d0

11. Confirm that the drive is now connected and configured. e.g.
# cfgadm -la
# format
OBTAIN CUSTOMER ACCEPTANCE

Above is what the document says, but as the faulty drive is already removed i only have to follow step from 7 to 11.

My question is what does this number "10" command cfgadm -c configure c1::dsk/c1t1d0 does to newly installed disk ? Does it create slice number 7 as 16MB on newly installed disk which is required for mirroring?

Please advise, you people are the only help for me.

Again, as has been suggested to you before...please RESEARCH things on your own. Can you not read the man page for the cfgadm command? Read about the switches? Find out what they do on your own, rather than asking others to do it for you?

From the Solaris documentation (again):
http://docs.oracle.com/cd/E23824_01/...dm-sbd-1m.html

The "configure" flag will, obviously, CONFIGURE the device for use. The next step is "format"...which will then let you (obviously) FORMAT the disk, and partition it. Go back to where you were given the disk definitions for what the "cxtxdx.." means, and you will then be able to figure out that you're configure the ENTIRE DISK for use, then the format command will let you partition it.

manalisharmabe · 09-11-2013, 01:04 PM

Quote:

Originally Posted by TB0ne

Again, as has been suggested to you before...please RESEARCH things on your own. Can you not read the man page for the cfgadm command? Read about the switches? Find out what they do on your own, rather than asking others to do it for you?

From the Solaris documentation (again):
http://docs.oracle.com/cd/E23824_01/...dm-sbd-1m.html

The "configure" flag will, obviously, CONFIGURE the device for use. The next step is "format"...which will then let you (obviously) FORMAT the disk, and partition it. Go back to where you were given the disk definitions for what the "cxtxdx.." means, and you will then be able to figure out that you're configure the ENTIRE DISK for use, then the format command will let you partition it.

Thanks a lot TBone for reply.

But my question is , when does this partiton gets created on newly inserted second disk?

Code:

partition> p
Volume:  ROOTDSK
Current partition table (original):
Total disk cylinders available: 24620 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       0 -  5807        8.00GB    (5808/0/0)  16779312
  1        var    wm    5808 - 11615        8.00GB    (5808/0/0)  16779312
  2     backup    wm       0 - 24619       33.92GB    (24620/0/0) 71127180
  3       swap    wu   11616 - 14519        4.00GB    (2904/0/0)   8389656
  4 unassigned    wm   14520 - 24607       13.90GB    (10088/0/0) 29144232
  5 unassigned    wm       0                0         (0/0/0)            0
  6 unassigned    wm       0                0         (0/0/0)            0
  7 unassigned    wm   24608 - 24619       16.93MB    (12/0/0)       34668

partition>

-Do we need to create it manually by FORMAT COMMAND ?

As when I am practicing it on my VM I had first encountered the error of no space on slice 7 of second disk, so I manually created slice7 of 100MB on second disk,
and now when I am trying to do with other slices on second disk it is still showing as no space error as below:--

Code:

bash-3.00# metainit -f d10 1 1  c1t0d0s0
d10: Concat/Stripe is setup
bash-3.00# metainit -f d20 1 1  c1t1d0s0
metainit: final: c1t1d0s0: No space left on device

Below is my second disk partition info.

Code:

partition> p
Current partition table (original):
Total disk cylinders available: 7829 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0 unassigned    wm       0               0         (0/0/0)            0
  1 unassigned    wm       0               0         (0/0/0)            0
  2     backup    wm       0 - 7828       59.97GB    (7829/0/0) 125772885
  3 unassigned    wm       0               0         (0/0/0)            0
  4 unassigned    wm       0               0         (0/0/0)            0
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7   reserved    wm     134 -  146      101.98MB    (13/0/0)      208845
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

partition>

So do I need to create partiton same as first disk on second newly inserted disk on Server?
YES/NO? (<<<<--- MAIN QUERY)

I thought

below command will do

Code:

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2
fmthard:  New volume table of contents now in place.

Please suggest.

Thanks a lot.

TB0ne · 09-11-2013, 01:25 PM

Quote:

Originally Posted by manalisharmabe

Thanks a lot TBone for reply.
But my question is , when does this partiton gets created on newly inserted second disk? -Do we need to create it manually by FORMAT COMMAND ?

The partitions get created when you CREATE THEM, don't they? That's why you use the "format" command, right??

Quote:

As when I am practicing it on my VM I had first encountered the error of no space on slice 7 of second disk, so I manually created slice7 of 100MB on second disk, and now when I am trying to do with other slices on second disk it is still showing as no space error as below:--

Below is my second disk partition info.

Code:

partition> p
Current partition table (original):
Total disk cylinders available: 7829 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0 unassigned    wm       0               0         (0/0/0)            0
  1 unassigned    wm       0               0         (0/0/0)            0
  2     backup    wm       0 - 7828       59.97GB    (7829/0/0) 125772885
  3 unassigned    wm       0               0         (0/0/0)            0
  4 unassigned    wm       0               0         (0/0/0)            0
  5 unassigned    wm       0               0         (0/0/0)            0
  6 unassigned    wm       0               0         (0/0/0)            0
  7   reserved    wm     134 -  146      101.98MB    (13/0/0)      208845
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

Do you not see that you have ZERO SIZE for ALL of your partitions??? And again, if you're mirroring, the partition 7 is used for the DB, so you can't use it, right??? Did you not read/understand what's been told to you so far?

So do I need to create partiton same as first disk on second newly inserted disk on Server?
YES/NO? (<<<<--- MAIN QUERY)

See any of the MANY answers you've received before, where things have been explained to you. AGAIN...if you want to MIRROR a disk, you very obviously need them both to be the same.

Quote:

I thought below command will do

Code:

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2
fmthard:  New volume table of contents now in place.

Please suggest.

Did you read what you posted??? You're taking the contents of c1t0d0s2...and putting right back ON THE SAME DEVICE. Why WOULD there be any changes?? You haven't changed ANYTHING.

We will again suggest:

You research things on your own, before posting questions
You pay attention to what you're typing in
You read the man pages for the commands you're using

Unless you begin to do these things, you will never LEARN what you're doing. You'll just be typing in commands with NO IDEA why.

manalisharmabe · 09-11-2013, 02:00 PM

Code:

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2
fmthard:  New volume table of contents now in place.

Ohh my apology.

it should have been

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
fmthard: New volume table of contents now in place.

before this I need to clear this big query, please answer them in yes/No

1st case. c1t0d0 and c1t1d0 are two diffrent disks? yes/no ?

2nd case. c0t0d0 and c1t0d0 are two different disk? yes/no ?

I mean to say, if controller is same (c0,c0) then we should check "t" parameter to make sure whether it is diffrent disk or not, right ? as in first case (t0,t1)
and if controller is different (c0,c1) then even if "t" parameter is same like (t0,t0) then also it suggest that it is different disks as in 2nd case right ?

yes, i got it! that partiton need to be created and i created exactly similar to 1st disk as follow:-

Code:

partition> p
Current partition table (original):
Total disk cylinders available: 7829 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       1 - 2611       20.00GB    (2611/0/0)  41945715
  1        var    wm    2612 - 2873        2.01GB    (262/0/0)    4209030
  2     backup    wm       0 - 7828       59.97GB    (7829/0/0) 125772885
  3       swap    wm    2874 - 3135        2.01GB    (262/0/0)    4209030
  4 unassigned    wm    3136 - 4441       10.00GB    (1306/0/0)  20980890
  5 unassigned    wm    4442 - 4446       39.22MB    (5/0/0)        80325
  6 unassigned    wm    4447 - 4451       39.22MB    (5/0/0)        80325
  7   reserved    wm     134 -  146      101.98MB    (13/0/0)      208845
  8       boot    wu       0 -    0        7.84MB    (1/0/0)        16065
  9 unassigned    wm       0               0         (0/0/0)            0

partition> q

but now when i enter this command i get this error:-

Code:

bash-3.00# metainit -f d20 1 1  c1t1d0s0
metainit: final: c1t1d0s0: overlaps with device in metadevice state database

I need to create like this on 2nd this:-

Code:

bash-2.03$ metastat -p
d0 -m d10 d20 1
d10 1 1 c1t0d0s0
d20 1 1 c1t1d0s0
d1 -m d11 d21 1
d11 1 1 c1t0d0s1
d21 1 1 c1t1d0s1
d2 -m d12 1
d12 1 1 c1t0d0s4
d22 1 1 c1t1d0s4
bash-2.03$

I did not get error when I did this

metainit -f d10 1 1 c1t0d0s0

Thanks you very very much!

TB0ne · 09-11-2013, 02:47 PM

Quote:

Originally Posted by manalisharmabe

Code:

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2
fmthard:  New volume table of contents now in place.

Ohh my apology. it should have been

bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
fmthard: New volume table of contents now in place.

before this I need to clear this big query, please answer them in yes/No

1st case. c1t0d0 and c1t1d0 are two diffrent disks? yes/no ?
2nd case. c0t0d0 and c1t0d0 are two different disk? yes/no ?

I mean to say, if controller is same (c0,c0) then we should check "t" parameter to make sure whether it is diffrent disk or not, right ? as in first case (t0,t1) and if controller is different (c0,c1) then even if "t" parameter is same like (t0,t0) then also it suggest that it is different disks as in 2nd case right ?

And I will AGAIN suggest, that you go back and re-read the documentation that we looked up FOR YOU, and gave you the link to, and try to read/understand it. Those questions are answered, and explained IN DETAIL. Again, unless you start UNDERSTANDING what you're told, you will just be typing in commands. The answers are VERY OBVIOUSLY YES.

Quote:

yes, i got it! that partiton need to be created and i created exactly similar to 1st disk as follow. but now when i enter this command i get this error:-

Code:

bash-3.00# metainit -f d20 1 1  c1t1d0s0
metainit: final: c1t1d0s0: overlaps with device in metadevice state database

I need to create like this on 2nd this:-

Code:

bash-2.03$ metastat -p
d0 -m d10 d20 1
d10 1 1 c1t0d0s0
d20 1 1 c1t1d0s0
d1 -m d11 d21 1
d11 1 1 c1t0d0s1
d21 1 1 c1t1d0s1
d2 -m d12 1
d12 1 1 c1t0d0s4
d22 1 1 c1t1d0s4
bash-2.03$

I did not get error when I did this

metainit -f d10 1 1 c1t0d0s0

Thanks you very very much!

Again, research on your own. You're asking folks here (essentially), to provide you with one-on-one, free technical training. You're running through practice scenarios, in a test environment, and don't seem to want to try to do the research (i.e. 'homework') on your own. From a Google search about that error:
https://forums.oracle.com/thread/1933363
http://www.planetlarg.net/closed%20s...rray-using-sds
http://www.unix.com/solaris/135962-m...e-problem.html