Thanks to Jean-marc, DAvid, Thomas, Johan, Bruce, Chris, Jason, and Bluejay.
The procedure I used, that worked, was...
- present new root lun from 8100
- hwmgr sc sc
- hwmgr sh sc / hwmgr v d (note Lun # /OSID of new disk)
- disklabel -rw –tadvfs /dev/rdisk/dskxxa (making it bootable)
- start exceed / export display / start diskconfig
- partition a as advfs, and h as swap
- mkfdmn –r /dev/disk/dskxxa root2_domain
- mkfset root2_domain root
- mkdir /root2
- mount –tadvfs root2_domain#root /root2
- shutdown system application
- vdump -0f - / | vrestore -xf - -D /root2
- check /etc/sysconfigtab for swap disks. Remove old ones, put disk part in.
- bring to single user mode(init s)
- add to fstab file so that root2_domain#root mounts to /
- change fstab file so that root_domain#root is renamed to oldroot_domain#root mounted to /oldroot
- mkdir /oldroot
- change root_domain to oldroot_dominan in /etc/fdmns
- halt system (shutdown -h) to SRM prompt, show old boot device
- P00>>> show bootdef_dev (pga...)
- go into wwidmgr and quickset to new lun paths
- P00>>> init
- P00>>> wwidmgr -show wwid (take note of old boot disks)
- P00>>> wwidmgr -clear all
- P00>>> wwidmgr -show wwid (find UDID that matches OSID from lun on 8100)
- P00>>> init
- P00>>> wwidmgr -quickset -udid ## (## is OSID of lun. do for one path from each controller)
- P00>>> init
- P00>>> show dev kgpsa* (find pga* names of devices to boot)
- P00>>> init
- P00>>> set bootdev_dev pga*..., pgb*...
- b -fl s (boot to single user mode)
- If it boots from new disk, continue to multiuser mode (CTRL D)
- df to see that the root2_domain is mounted on /
- ls –lR /etc/fdmns/* - make sure root2_domain is pointing to right disk
----- Original Message ----
From: Rich Glazier <rglazier2002_at_yahoo.com>
To: tru64-unix-managers_at_ornl.gov
Sent: Wednesday, February 4, 2009 7:58:16 PM
Subject: migrating boot disk (root_domain) from one EVA to another
5.1A PK6, DS20E, EVA5000
Managers,
I know that the root domain is the only domain in AdvFS that you can not add a volume to. We are migrating our storage from an old EVA5000 to a new EVA8100, and I've been using addvol/rmvol to accomplish this for the non root domains.
(presented a new lun from the 8100, labeled it, added the volume into the domain (addvol), and removed the
old 5000 volume from the domain (rmvol)).
I can not do this for the bootable root disk; I boot off the SAN. I need to migrate the root_domain another way. Here was my plan. Please see if this seems sounds. If there's a better way to do it, or if anyone has done it, please let me know.
- present new root lun from 8100
- hwmgr sc sc
- hwmgr sh sc / hwmgr v d (note Lun # /OSID of new disk)
- disklabel -rw new disk (making it bootable)
- mkfdmn /dev/disk/dskxx root2_domain
- mkfset root2_domain root
- mkdir /root2
- mount root2_domain#root /root2
- shutdown system application
- vdump -0f - / | vrestore -xf - -D /root2
- change system to not reboot
- consvar -s auto_action HALT
- consvar -l (see that it changed)
- consvar -a (write it to NVRAM)
- bring to single user mode (init s)
- change fstab file so that root2_domain#root mounts to /
- change fstab file- comment out root_domain#root mount
- shutdown system (halt) to SRM prompt, show old boot device
-P00>>> show bootdef_dev (pga...)
- go into wwidmgr and quickset to new lun paths
- P00>>> wwidmgr -show wwid (take not of old boot disks)
- P00>>> init
- P00>>> set mode diag
- P00>>> init
-P00>>> wwidmgr -clear all
-P00>>> init
- P00>>> wwidmgr -show wwid (find UDID that matches OSID from lun on 8100)
- P00>>> init
-P00>>> wwidmgr -quickset -udid ## (## is OSID of lun. do for one path from each controller)
-P00>>> init
-P00>>> show dev kgpsa* (find pga* names of devices to boot)
-P00>>> init
-P00>>> set bootdev_dev pga*..., pgb*...
- Change console from HALT to BOOT
-P00>>> set auto_action boot
- b -fl s (boot to single user mode)
- If it boots from new disk, continue to multiuser mode (CTRL D)
Thanks for the help,
Rich
Received on Tue Feb 10 2009 - 22:41:25 NZDT