Very Computer

I have a problem wich I'm quite unsurtain how to fix atm.
On a Sol7 machine - running mirror of OS disks - one of the main disks got
corrupted. In fact I didnt notice this at first - so by a remote restart it
simply would not boot. I then went to the machine and realized what had
happened - uh ..... I know - I know :-)

But - ok - since I had no replacement disk avail - I swapped the corrupt
disk from the corrupt one (no - I had'nt made dual boot alternatives) -
booted by cdrom into signle-user - commented out the loading of metadisk
from /etc/system and edited the vfstab to use the single disk again. This
went fine - even though I forgot some small things like those files
controlling the metadatabase (mddb.cf, md.tab etc)

Ok - now - I'm in the situation that I've put in the replacement disk - and
have partitioned it like the working one. So - well - since I now have a
more or less "clean" /etc/system file - I thought - well - lets create these
metadb again as if this was the initial setup. Did the "metadb -a -f -c 3
c0t0d0s7" and "metadb -a -c 3 c0t8d0s7". metadb command runs without
hitches. Fine ! - well - not quite. I then started to try to setup the
mirroring ..... and get this error: "metainit: {hostname}: stale databases"

Darn. I'm almost lost from ideas. The only one I'm now considering - but I
feel declined to try since I dont have any test-equip avail atm. is to do
the process ... kind of reversed.

boot single on cdrom.
rename the "backup" of /etc/system so all metadata info is back.
edit /etc/vfstab file to point to /dev/md/xxxx as before .....

But - well - I'm very unsurtain - since I obviously didnt do everything "by
the book" when I needed that system back up fast. (mddb.cf etc....)

Any suggestions ?

Yours, Sverre Larsson

You may be able to remove the old metadb, but if not. Fix it to boot
back off the single slice, and
'dd if=/dev/null bs=1024k of=/dev/rdsk/<metadb slice>'
for all the metadb slices.

Once you start again, it should be good.  BTW, do you have any shared
disks or other data disks that you're using SDS on?

If you don't understand this, then please don't do it. :-)

Ben

Quote:> You may be able to remove the old metadb, but if not. Fix it to boot
> back off the single slice, and
> 'dd if=/dev/null bs=1024k of=/dev/rdsk/<metadb slice>'
> for all the metadb slices.

What I believe you are telling me - is that I should do that for those disks
that I tried to setup - target 0 and 8 from previous thread. Sure - sounds
like a good idea. But, still - I'm a bit unsurtain about the file mddb.cf
.... should I maybe move it so that disksuite dont find it at all - and
simply recreates it ?

Quote:> Once you start again, it should be good.  BTW, do you have any shared
> disks or other data disks that you're using SDS on?

> If you don't understand this, then please don't do it. :-)