Re: rebuild 240v from scratch


"tunla" <lars.tunkrans@xxxxxxxxxxxx> wrote in message
news:1135851810.619907.211780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> Mike Dundas wrote:
>
>> My plan was to partition mirror boot drive on "server b" to
>> match our "server a" and ufsdump/ufsrestore over the network to the
>> mounted mirror boot partitions on "server b". Once I had mirror boot
>> disk bootable, I would boot from it and dd from one disk to the other.
>>
>> Once system restore was complete, I modified the vfstab on mounted
>> mirror drive, /mnt/etc/vfstab, to point to correct disk and installed
>> bootblk. I tried to boot from disk1 and the system failed to boot and
>> panicked rebooting from primary boot disk. I have done some
>> investigation and I think it has to do with the meta devices.
>>
>> boot message:
>>
>> Cannot open mirrored root device, error 19
>> Cannot remount root on /pseudo/md@0:0,0,blk fstype ufs
>>
>> panic[cpu1]/thread=180e000: vfs_mountroot: cannot remount root
>>
>> Any help appreciated,
>>
>> Mike Dundas
>
> If your description of what took place is complete I would say
> that the failure is due to that you did NOT create a new set
> of METADEVICE databases on server b.
>
>
> There is at least three things that must be present for a successful
> volumemanager boot:
>
> /etc/system file must preload the MD devicedrivers and
> the pointer to the metadevice rootfilesystem.
>
> /etc/vfstab must reference the metadevices.
>
> A valid and correct metadabase must exist that translates
> the metadevice root-referens from /etc/system to a physical
> disc/partition number.
>
> The error seems to say that the /etc/system file that you copied
> over from server A with its root metadevice pointer could not
> find a metadb on server B to resolve it to a physical partition.
>
> //Lars
>

I did "not" create a new set of devices, that is correct. I did modify the
newly
restored vfstab to reference the /dev/dsk/cXXXXXXX etc, and commented out
the metadevice references. The reason for this was I am unfamiliar with
metadevices
and most of my systems have a boot drive and a mirror drive that I manually
create/update
every month with a script using the dd command.

Must I therefore modify the /etc/system file. Is this possible by hand?

What is the best practice when trying to restore this box. As it is right
now I am trying to
boot from the mirror drive on a server "B". Should I install Sol 10 copying
partitions to
match server "A", then use volume manager to create the mirror.

The vendor who supplied the system wasn't much help. They had said to
backup server "A"
and restore to server "B". Unfortunatley, our netbackup software isn't
compatable with
Solaris 10 yet and no standalone DLT's avail anymore. I was using
ufsdump/restore across network
but I am having to restore to a mounted mirror drive. This seems rather
convoluted!


thanks for the advice can you now please answer my new questions?

Thanks

Mike Dundas


.

Relevant Pages