From: Joehnk, John (john.joehnk@scrolltech.com)
Date: Thu Apr 22 2004 - 10:02:00 EDT
Thanks to all that answered it is always a great help!
I have included the basic steps that I followed to create the duplicate drive.
I found an older article the mentioned that to do this, and have it bootable, the LUN of the "new" boot drive needed to be 0.
When I created my new mirrorset with a LUN of 0, it worked.
I have not tried again with a non 0 LUN to verify this, but it seems to be the difference.
These are the steps that I followed
***
Assuming that your new disk is a rz28d and is the rz1 disk
disklabel -wr -t ufs rz1 rz28d
newfs /dev/rz1a
newfs /dev/rz1g
mkdir /root2
mkdir /usr2
shutdown now
mount -u /
mount /dev/rz1a /root2
mount /usr
mount /dev/rz1g /usr2
vdump -0 -f - -D / |vrestore -xf - -D /root2
vdump -0 -f - -D /usr |vrestore -xf - -D /usr2
Some import changes to make to the new root disk.
mount root2_domain#root /root2
1. In the /root2/etc/fstab file change your swap space to the new disk.
change /dev/rz0b swap1 ufs sw 0 2
to /dev/rz1b swap1 ufs sw 0 2
***
-------------------------------------------------------------------------------------
Is it possible to have your boot/system disk in a raid cabinet?
I am testing this on an AlphaServer 1000 running 4.0g connecting to a Raid Cabinet with HSZ40 controllers.
My production system is a 4100 with HSZ70 controllers.
I have used the vdump / vrestore procedures to copy the system. I feel that the drive is partitioned correctly.
I made the changes to the fstab on the "new" system disk. when I reboot and specify that drive it begins reading from the raid array, but at some point during the boot, it seems to change back to the original disk and the boot fails.
I have removed any reference to the internal drives that I can find, but the boot fails.
Any suggestions or thoughts?
Thanks
John Joehnk
Scroll Technologies
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:57 EDT