From: Dustin Marquess (dmarquess@gmail.com)
Date: Tue Mar 11 2008 - 23:10:40 EST
All,
Sorry about the long delay in the summary. I had to source the disk
and schedule a time to do the work.
After playing with the system a little, it appears that I'm going to
have to add the new drive to the system (using an SCA adapator since
the bays are full) and use volevac (per John Brusche) to make the
system happy.
Below are the replies I received. I want to say thank you to
everybody who replied.
-Dustin
==============
Jeffrey Hummel
==============
I never tried that. I always used RAID 1 with LSM so I was able to use
the commands to build a replacement and migrate it. If you use dd,
you will need to specify the c partition. Beyond that, the only
problems I can think of are:
1. When booting from the cd, it will try to read the device database
on your disk
2. There is a boot driver that dd will not touch and might not be the
same as the other disks. I don't know if this will be a problem
because I'm not sure how the stripe is touched when the system is
booted.
I can't wait to hear what you hear from the rest of the community.
===========
John Lanier
===========
Since this is a striped volume, this will require:
a. Removing the stripe (RAID0; no redundancy)
b. Recreating the stripe
c. Restoring the /var data from backup
I don't have the exact steps, but they should be detailed here:
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/ARH9BDTE/TITLE.HTM
...
Section 4.3.4 "Creating LSM Volumes with a Single Striped Plex"
...
Since this is the "/var" filesystem, this can be done while either
booted from CD or in single-user mode.
============
John Brusche
============
Please consider using
/usr/sbin/volevac [-g diskgroup] medianame [new_medianame...]
Breaking a LSM stripe without involving LSM is a very bad idea.
Insert disk equal or larger size.
Boot into single user from normal bootdef_dev
>>> b -fl s
Tru64 discovers new disk -->> dskxx
# mountroot
# mount /usr
# disklabel -rw dskxx
# /usr/sbin/voldiskadd dskxx
# /usr/sbin/volevac -g rootdg oldmedia newmedia
Above is from memory, so check manpages...
=============
Richard Loken
=============
Personally, I would not use dd to copy a drive under most circumstances
but rather dump and restore because I think the drive will be cleaner that
way: there will be less disk fragmentation, few sparse directory files, etc.
You would have to disklabel the device and build the partitions like the old
one, mark it as bootable if that is appropriate but not of those steps
take very long.
Your procedure is identical to what I would do.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:37 EDT