Update hard drives

[Strast]

I have a AlphaServer DS20E with Tru64 V5.1A Rev 1885. It currently has three 18GB drives. I have 5 new 36GB drives and I'd like to replace the 3 and add 2.

Is there a step by step document somewhere that will explain the steps to copy the existing system onto the new drives so I can discard the old?

Thanks.

[Steven Schweda]

> Is there a step by step document [...]

I don't remember seeing one, and it's been a
long time since I replaced a boot disk, but
...

First, I'd start with the non-boot disks.
After the usual AdvFS preparation
(initialization, partitioning), I'd expect
that a vdump+vrestore pipeline would be good
for moving the data. Probably in single-user
mode, to help ensure that the file systems
are idle. (Or umount, then mount read-only.)
I'd expect the different device names for the
new disks to cause some trouble, but
adjusting either the contents of "/etc/fstab"
or the directories and links under
"/etc/fdmns" should make the new stuff
available under the old names.

For the boot disk, I'd probably do the
initialization the easy way, but then boot
from a Tru64 installation CD-ROM, and do the
data transfer from there to ensure that the
(normal) boot disk is idle. Escape to a
shell at the first opportunity. Then do
roughly the same steps with that disk as with
the non-boot disks. Again, "/etc/fstab"
and/or "/etc/fdmns" would probably need some
adjustments. Mounting a file system when
booting from a CD-ROM (as I recall) requires
finding a read-write file system where you
can create a mount point -- probably "/tmp".

On the bright side, once the boot disk has
been copied, if you have trouble booting from
the copy, then it should still be possible to
boot from the old boot disk, mount what you
need of the new one, and play with it in a
normal, full, non-single-user environment
before trying it again.

Not exactly step-by-step, I know, but perhaps
that'll give you some things to consider
while you wait for a better procedure to
appear.

[Johan Brusche]

The new root disk will have a new HWID and name. Remember to use "-t AdvFS" in the disklabel command to make the new root-disk bootable . After copying (in single user mode) root, usr and var with a vdump/vrestore pipe you need to mount the new root (eg on /mnt) then goto /mnt/etc/fdmns and change the domain links for root_domain, usr_domain and var_domain for pointing to the new diskname in /dev/disk/.

Also on the copied root_domain you need to edit /etc/sysconfigtab to let the swapdevice point to the new diskname partition-b.

Normally there is no need to change fstab execpt if you mould be using UFS instead of AdvFS.
If the root-disk is configured under LSM then te move becomes somewhat more complicated.
Cheers,

_ JB _

[Strast]

This is great information, however I am unfamiliar with the AdvFS. A fair amount of *nix experience but I'm not recognizing the disk information. Here's the fstab..

root_domain#root / advfs rw 0 1
/proc /proc procfs
usr_domain#usr /usr advfs rw 0 2
usr_domain#var /var advfs rw 0 2
local_dmn#local_fs /usr/local advfs rw 0 2
dsk1_dmn#dsk1_fs /images advfs rw 0 2
dsk2_dmn#dsk2_fs /images/0_dsk2 advfs rw 0 2
Prepstation:/images /images/Prepstatino nfs rw,bg 0 0
Prepstation:/images/0_dsk2 /images/PrepStation/0_dsk2 nfs rw,bg 0 0

[Steven Schweda]

> [...] I am unfamiliar with the AdvFS. [...]

http://h30097.www3.hp.com/docs/pub_page/doc_list.html
http://h30097.www3.hp.com/docs/pub_page/V51A_DOCS/V51A_DOCLIST.HTM
http://h30097.www3.hp.com/docs/advfs_ref/frame.htm
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51A_HTML/ARH96CTE/TITLE.HTM

The "Upkeep" section of the "Advanced File
System Quick Reference" looks interesting.

> [...] Here's the fstab.. [...]

Yes, that looks like a "/etc/fstab" (with
some AdvFS file systems in it). Some of
those domain names are suggestive, but you'll
want more AdvFS-specific info than you'll
find there.

[Strast]

Got the new drives installed and it's working well. Thanks