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

jlliagre · 09-11-2013, 03:35 PM

Quote:

Originally Posted by manalisharmabe

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

The partition table you posted is broken. Cylinders from 134 to 146 cannot belong to both slice 0 and slice 7.

manalisharmabe · 09-12-2013, 12:31 AM

Quote:

Originally Posted by jlliagre

The partition table you posted is broken. Cylinders from 134 to 146 cannot belong to both slice 0 and slice 7.

Wow Superb answer! Thanks TBOne and jilliagre!

yes, now I recollect, I had first created slice 7 and then when on creating 0 1 3 4 5 6 8.

Today I will again restore my snapshot, I will try again.

(However I would love to have teacher/guide like you both to pay for their knowledge sharing here in my town.:-))

Thanks a lot! I will be very much happy once my task of mirroing disk gets completed, but first i will do it on my VM.

Thanks a lot guys. you people keep my interest Solaris alive.

TB0ne · 09-12-2013, 08:44 AM

Quote:

Originally Posted by manalisharmabe

yes, now I recollect, I had first created slice 7 and then when on creating 0 1 3 4 5 6 8. Today I will again restore my snapshot, I will try again.

Which is why you should have gone back and thought about what you did, and re-read the documentation and what you were posting. The answers were there, but as said..unless YOU start thinking about the steps and KNOWING what things do, you're not learning...just typing commands. Asking others to explain each single step, command, and flag, then asking others to diagnose problems won't teach you ANYTHING, EVER, about ANY subject.

Quote:

However I would love to have teacher/guide like you both to pay for their knowledge sharing here in my town.:-)

There are several online learning courses you can take from anywhere, if your town doesn't have a place for Solaris education. But again, you have access to ALL the information and knowledge you need, but it is YOU that has to take the initiative and look it up. Don't just keep asking others to do it for you.

manalisharmabe · 09-15-2013, 11:44 AM

Hi TBONE and Jilliagre Thanks a lot!

Finally I could do disk mirroring on my server without any problem.
However the disk testing is scheduled in coming weekend from OK prompt.

Well I have some questions will ask soon.

thanks

manalisharmabe · 09-16-2013, 11:15 AM

Hi Guys,

I have setup this mirroring on my VM machine:-

Code:

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

and boot device setup as this:-

Code:

bash-3.00# eeprom boot-device
boot-device=rootdisk0 rootdisk1 net

Now how to check my rootdisk1 without failing rootdisk0 on my VM machine?

Is there any way to find out what disk (rootdisk0 or rootdisk1) I have booted system from ?

Thanks a lot.

manalisharmabe · 09-19-2013, 01:03 PM

Ho w to be sure that my system will fail over to 2nd disk after performing this in OK prompt.

OK boot rootdisk0

init 0

OK boot rootdisk1

Does this mean that , if my system comes come through both disks then all is fine.

and how to find out which disk my server has booted.

Please advice.

TB0ne · 09-19-2013, 01:27 PM

Quote:

Originally Posted by manalisharmabe

Ho w to be sure that my system will fail over to 2nd disk after performing this in OK prompt.

OK boot rootdisk0

init 0

OK boot rootdisk1

Does this mean that , if my system comes come through both disks then all is fine.

and how to find out which disk my server has booted.

Please advice.

We will AGAIN advise you to READ THE DOCUMENTATION:
http://docs.oracle.com/cd/E19637-01/...461019855.html

This is your TEST SYSTEM that you are learning on...it is POINTLESS to ask questions like this, since you are trying to LEARN. In the time it took you to post this question (twice), you could have just attempted the boot, and seen what happened. That attempt would have taught you something. You could have taken that knowledge and researched things further, and learned even more.

Asking to be spoon-fed every single step and not researching/trying things on your own is NOT the way to learn ANYTHING.

manalisharmabe · 09-20-2013, 02:27 AM

Hi Guys,
After setting below paths:

ok nvalias rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
ok nvalias rootmirror /pci@1c,600000/scsi@2/disk@1,0:a
ok nvstore
to check:
ok devalias

devailas does show set path but after reboot

The alias for disks are not getting saved.
I get this error:-

Code:

----------
System is operating in Service Mode.

Rebooting with command: boot rootdisk
Boot device: rootmirror  File and args: rootdisk
Evaluating:

Can't locate boot device

Please advise.

manalisharmabe · 09-20-2013, 02:58 AM

the alias is not getting saved.

however the output of diag-switch is showing false.

{1} ok printenv diag-switch?
diag-switch? = false

TB0ne · 09-20-2013, 08:47 AM

Quote:

Originally Posted by manalisharmabe

Hi Guys,
After setting below paths:

ok nvalias rootdisk /pci@1c,600000/scsi@2/disk@0,0:a
ok nvalias rootmirror /pci@1c,600000/scsi@2/disk@1,0:a
ok nvstore
to check:
ok devalias

devailas does show set path but after reboot The alias for disks are not getting saved. I get this error:-

Code:

----------
System is operating in Service Mode.

Rebooting with command: boot rootdisk
Boot device: rootmirror  File and args: rootdisk
Evaluating:

Can't locate boot device

Please advise.

You have been given advice several times, but you are apparently ignoring it each time. AGAIN:

YOU, PERSONALLY, have to research things on your own, and actually put some EFFORT into learning.
Asking to be spoon-fed each and every single step/command will NOT teach you anything
You have mentioned service mode before, and were given advice. Think hard about what that advice was, and it will answer this current question.

http://docs.oracle.com/cd/E19088-01/...sOn.html#44195
http://docs.oracle.com/cd/E19053-01/.../chapter4.html
http://docs.oracle.com/cd/E23824_01/...ml#SAGDFSgdgsw

And AGAIN, posting the same question more than once doesn't get you an answer any faster.

manalisharmabe · 09-20-2013, 10:38 AM

Hi Guys,

Thanks for reply!

here is my disks info:-

Code:

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):

here is my disks path info:-

Code:

bash-2.03$ ls -l /dev/dsk/c1t0d0s0
lrwxrwxrwx   1 root     root          43 Nov  6  2003 /dev/dsk/c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
bash-2.03$ ls -l /dev/dsk/c1t1d0s0
lrwxrwxrwx   1 root     root          43 Nov  6  2003 /dev/dsk/c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bash-2.03$

this is what I did:-

Code:

nvalias rootdisk /pci@1c,600000/scsi@2/disk@0,0:a

nvalias rootmirror /pci@1c,600000/scsi@2/disk@1,0:a

nvstore

This is my devalias output:-

Code:

{1} ok devalias
rootmirror               /pci@1c,600000/scsi@2/disk@1,0:a
rootdisk                 /pci@1c,600000/scsi@2/disk@0,0:a
rootmirror               /pci@1c,600000/scsi@2/sd@1,0:a
rootdisk                 /pci@1c,600000/scsi@2/sd@0,0:a
xnet2                    /pci@1d,700000/pci@1/SUNW,hme@0,1:dhcp,
xnet1                    /pci@1e,600000/pci@3/SUNW,hme@0,1:dhcp,
xnet                     /pci@1e,600000/pci@2/SUNW,hme@0,1:dhcp,
net3                     /pci@1d,700000/network@2,1
net2                     /pci@1d,700000/network@2
net1                     /pci@1f,700000/network@2,1
net                      /pci@1f,700000/network@2
cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
ide                      /pci@1e,600000/ide@d
disk3                    /pci@1c,600000/scsi@2/disk@3,0
disk2                    /pci@1c,600000/scsi@2/disk@2,0
disk1                    /pci@1c,600000/scsi@2/disk@1,0
disk0                    /pci@1c,600000/scsi@2/disk@0,0
disk                     /pci@1c,600000/scsi@2/disk@0,0
scsi                     /pci@1c,600000/scsi@2
sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
ttya                     /pci@1e,600000/isa@7/serial@0,3f8
name                     aliases
{1} ok

This is my other info:-

Code:

{1} ok printenv boot-device
boot-device =           disk
{1} ok setenv boot-device rootdisk rootmirror
boot-device =           rootdisk rootmirror
{1} ok printenv boot-device
boot-device =           rootdisk rootmirror
{1} ok printenv diag-device
diag-device =           disk
{1} ok setenv diag-device rootdisk rootmirror
diag-device =           rootdisk rootmirror
{1} ok printenv diag-device
diag-device =           rootdisk rootmirror
{1} ok

After setting alises, If I do
OK boot rootdisk ,the system boots

but if I do init 0 and get to OK prompt and do
OK boot

it through below error:-

This is the error which I get:-

Code:

System is operating in Service Mode.

Rebooting with command: boot rootdisk
Boot device: rootmirror  File and args: rootdisk
Evaluating:

Can't locate boot device

{1} ok printenv boot-device
boot-device =           rootdisk rootmirror
{1} ok devalias rootdisk
rootdisk : no such alias
{1} ok devalias rootmirror
rootmirror : no such alias

I also did reset-all after doing nvstore, but still that aliases do NOT get saved.

Please advise.

Thanks,
Manali

TB0ne · 09-20-2013, 01:48 PM

Quote:

Originally Posted by manalisharmabe

Hi Guys,
Thanks for reply!

here is my disks info:-
here is my disks path info:-
this is what I did:-
This is my devalias output:-

This is my other info:-

After setting alises, If I do
OK boot rootdisk ,the system boots but if I do init 0 and get to OK prompt and do
OK boot

it through below error:-
This is the error which I get:-

Code:

System is operating in Service Mode.

I also did reset-all after doing nvstore, but still that aliases do NOT get saved.
Please advise.

AGAIN:

We will advise you actually READ the documentation
We will advise you actually RESEARCH THINGS ON YOUR OWN
We will advise that you pay attention to things you've been told before
We will advise that you read the links you've been sent

If you actually DID any of these things, you'd have been through this tutorial in about an hour. If you did, you'd see the "service mode" mentioned as part of your problem. If you did, you'd see how to check/resolve it.

Sorry, but I'm not spoon-feeding you anymore.

manalisharmabe · 09-21-2013, 07:49 AM

Code:

You have mentioned service mode before, and were given advice.  Think hard about what that advice was, and it will answer this current question.

Thanks a lot TBOne!

I think I should do this to first to make my system come back to NORMAL mode:-

Code:

What to Do

 1. Turn the panel keyswitch to the Normal or Locked position. 

 2. At the ok prompt, type: ok setenv service-mode? false



The system will not actually enter normal mode until the next reset. 

 3. Type: ok reset-all

Than setting alias will work.

I apologize for asking frequently.

Could you please just confirm that, I need to first set system to NORMAL MODE and then proceed with setting aliases ?

THANKS A LOT TBONE.

TB0ne · 09-21-2013, 02:41 PM

Quote:

Originally Posted by manalisharmabe

Thanks a lot TBOne! I think I should do this to first to make my system come back to NORMAL mode:-

Code:

What to Do

 1. Turn the panel keyswitch to the Normal or Locked position. 
 2. At the ok prompt, type: ok setenv service-mode? false

The system will not actually enter normal mode until the next reset. 

 3. Type: ok reset-all

Than setting alias will work. I apologize for asking frequently. Could you please just confirm that, I need to first set system to NORMAL MODE and then proceed with setting aliases ?

No, I will not....you are apparently ignoring/missing the point we've tried to make to you. That is, YOU ARE THE ONE who needs to do research, and you need to stop asking to be spoon-fed EVERY SINGLE STEP. This all has been covered in the links and material you've been given....but you are putting NO EFFORT OF YOUR OWN into reading/understanding it.

AGAIN, this is your TEST system...why don't you just TRY IT?? Learn by DOING.

manalisharmabe · 09-22-2013, 07:59 AM

Quote:

Originally Posted by TB0ne

No, I will not....you are apparently ignoring/missing the point we've tried to make to you. That is, YOU ARE THE ONE who needs to do research, and you need to stop asking to be spoon-fed EVERY SINGLE STEP. This all has been covered in the links and material you've been given....but you are putting NO EFFORT OF YOUR OWN into reading/understanding it.

AGAIN, this is your TEST system...why don't you just TRY IT?? Learn by DOING.

No this is NOT test system. So I can't do much of rnd on it.

Would you please post me the same link again.