Solaris

hi, i am new to Unix. I was try to do a mirror on solaris 8 with Solstice DiskSuite. Unfortunately I have missed the metaroot command and reboot system. The system unable to boot up.

May i know what should I do to bring the system up? Pls help.

thks and regards,
ann

I would not expect that to render the system unbootable. Instead, the system should just boot up on the original slices. My guess is that some other error rendered the box unbootable.

But I think you can boot the install cd into single user mode and mount the root disk as /mnt. The instuctions for doing can be found in our faq section in the "lost root password" article. Once it is mounted, I think, that you can run metaroot with the -R option. I have never done that though.

Boot into single user from cdrom, mount your / partition to /a or /mnt. Edit /a/etc/system and /a/etc/vfstab. Remove any SDS info in /a/etc/system and comment out meta devices in vfstab (add in normal partitions back in - whatever your original vfstab contained). Save files, remove the config files for Disksuite (/a/etc/lvm/*.cf), umount /a, fsck that partition, halt and boot from original disk.

hi thanks in advance.
But i have original vfstab(as shown below) before I create replica. Mean it already have some replicas before I create the d3. of course these was not create by me.

And then I create d3 and forgot to issue metaroot. How am i go back this this original setup without removing all metadevices. Really need your advice here.

#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/md/dsk/d1 - - swap - no -
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no logging
/dev/md/dsk/d2 /dev/md/rdsk/d2 /home ufs 2 yes logging
swap - /tmp tmpfs - yes -

Metaroot is the command to issue when adding the / partition. It sets up the system files for root (/) metadevice. IF that is your original vfstab you posted, then it shows the following:

/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no logging

If that is an original entry, then the d3 that you were trying to add doesn't require a metaroot command (unless you were doing something more than adding in a new parition into DiskSuite).

What partition/mount point are you trying to add with the d3? Please explain the original state of filesystems and what you were trying to add (including mount points).

hi,
yes, posted was my original vfstab. ..

the original filesystenm was:
d0 - d10, d11 - c0t0d0s0,c0t1d0s0
d1 - d12, d13 - c0t0d0s1,c0t1d0s1
d2 - d14, d15 - c0t0d0s6,c0t1d0s6


These are the step I have done to my system:

I make a partition c0t0d0s7 and c0t1d0s7 with 30G each
try to mount it to /export/home/oracle but failed.

so guess it may need to mirror it before mount. so I did these.

metainit -f d16 1 1 c0t0d0s7
metainit -f d17 1 1 c0t1d0s7
metainit d3 -m d16
metattach d3 d17

mount /dev/md/dsk/d3 /export/home/oracle

then reboot ( and it keeps reset/sebooting )

Well, there is no standard but in my experience, the metadb is usually placed on slice 7. If you have overwritten the metadb information, then you have toasted the old set up.

See if you can find where the metadb were stored - if it was slice 7, then I don't know if those can be restored or not but it certainly sounds like this is what you have done (would cause server not to boot).

Was there some space reserved on slice 7 before you changed it? Do you have the output of the metadb command (which would show which partition the database was on)?