I got a number of replies to this. All were very useful.
Original question:
I need to create a larger / partition. It's an AdvFS.
What I planned to try is:
1. backup / with vdump
2. boot from the 4.0E install CD
3. select a Custom Install
4. combine the a and b partitions(b is not currently being used).
5. select the UNIX Shell option and restore / with vrestore
Will this work and will I get a bootable AdvFS / partition?
from: josephh_at_cnsdubai.co.ae
Dear Karen,
You can read Chapter 7 of the installation guide v4.0b.The paragraph
name "Restoring advanced file system".It will explain clearly how to
restore root advfs file system
From: A.Mahendra.Rajah_at_Meena.CC.URegina.CA
> 1. backup / with vdump
Before you shutdown the system, save the disklabel info of the system
disk to a file (say, rz0.label) and edit it to suit your requiremnt.
> 2. boot from the 4.0E install CD
disklabel -r -R <raw_system_disk> rz0.label <disk_type>
The above command writes a boot block to the disk as well.
> 5. select the UNIX Shell option and restore / with vrestore
>
> Will this work and will I get a bootable AdvFS / partition?
This would work....
From: crittend_at_storm.simpson.edu
b may be used as your swap partiton, it is on our systems. Otherwise what
you want to do will work. You make the advfs file system by using the
commands mkfdmn and mkfset. I have a set of instructions which Digital
sent me I will include in this message which should help.
Below are the steps necessary to restore your system disk when the
filesystems are AdvFS and not UFS.
STEP 1:
Obtain, through the system console, the location (the unit
number) of your CDROM, your system disk, and the tape
drive that contains your system backup tape. Also
note the system disk's device type. If you need
assistance on doing this, refer to your system's hardware
manuals.
The following is an example on a DEC 3000 Series Processor:
>>> show dev
BOOTDEV ADDR DEVTYPE NUMBYTES RM/FX WP DEVNAM REV
------- ---- ------- -------- ----- -- ------ ---
DKA0 A/0/0 DISK 426.25MB FX RZ25 0700
DKA100 A/1/0 DISK 2.10GB FX RZ28 435E
DKA400 A/4/0 DISK ..... RM WP RRD42 4.3d
MKA500 A/5/0 TAPE RM TZK10 01B4
Here, DKA100 is the system disk and it's type is a RZ28.
DKA400 is the location of the CDROM and MKA500 is the tape device.
STEP 2:
Insert the V3.0 DEC OSF/1 CD into the CDROM and then boot that CD.
The actual boot command will depend on the location (unit number)
of the CDROM and your hardware.
>>> b dka400
Choose the 3rd option on the menu: SYSTEM MANAGEMENT
STEP 3:
Make the special device files for the system disk and the tape drive.
You need to use the unit numbers you saw from the console command
executed in Step 1.
# cd /dev
# MAKEDEV rz1 tz5 (tz# - the number will be the unit no of the tape
device
rz# - the number will be the unit no of your
system disk. NOTE: If your system disk
is on a RAID device, the format will be:
re# )
STEP 4:
Write the disklabel to your system disk and make the root domain and
fileset.
# disklabel -rwt advfs rz1 rz28
(You need to replace rz1 with the device you made
in Step 3 and you must use replace rz28 with
your system disk device type found from Step 1.)
NOTE: If you have a customized disk partition layout on your system
disk, you must now make the needed modifications.
# disklabel -e rz1
# mkfdmn /dev/rz1a root_domain
# mkfset root_domain root
STEP 5:
Mount the root AdvFS filesystem, change directory to its location,
and then issue the restore command to restore your root filesystem.
# mount -t advfs root_domain#root /mnt
# cd /mnt
# vrestore -xf /dev/rmt0h
STEP 6:
When the / (root) filesystem restore is complete, change directories to
root, dismount the AdvFS root filesystem, and halt the system.
# cd /
# umount /mnt
# halt
STEP 7:
Now it depends on whether you need to just restore the root filesystem
or both the root filesystem and /usr. If you only need to restore
root (/), your steps are completed and you can now boot your system
as normally. If you also need to restore /usr, boot to single user mode
and continue with the following:
# boot -fl s
STEP 8:
When you get the # prompt, make the root filesystem read writable and
then remake the usr domain and fileset. You can find out the device and
partition that your /usr is on by looking in the /etc/fdmns/usr_domain
directory. # ls /etc/fdmns/usr_domain
# mount -u /
# mkfdmn /dev/rz1g usr_domain
# mkfset usr_domain usr
# mount -t advfs usr_domain#usr /usr
STEP 9:
Your last step is to now change your directory to /usr and start the
restore. When the restore is completed, you can continue to boot
your system up to multi-user mode.
# cd /usr
# vrestore -x
# init 3
From: tpb_at_doctor.zk3.dec.com Dr. Tom Blinn,
Backup / using vdump; if you can put it someplace else on the system disk, do
so (e.g., if there's enough space in /var or /usr to hold the file, that's an
easier place to get to it than putting it on tape).
Edit the disk label to increase the size of the "a" partition. You should be
able to do this "on line", as long as you don't try to shrink the size of the
partition. AdvFS depends on knowing where the partition begins, but not the
size, once there's a file system in the partition, and anyway, you're going to
be replacing the file domain with a new one. You don't need to change the
boot blocks on the disk, but if you did want to, then use "-t advfs" to get
the AdvFS boot blocks written.
Boot the install CD. Select system management. Do NOT select an "install"
option.
When you get to the system management shell, make any special devices you will
need:
# cd /dev
# ./MAKEDEV rz0
or whatever else disk it is that you're going to work on.
# cd /
# mkdir /etc/fdmns
# mkfdmn /dev/rz0a root_domain
# mkfset root_domain root
If you have an AdvFS /usr file system with your root backup in it, say, you
can set up a directory to mount it from:
# mkdir /etc/fdmns/tmpusr
# cd /etc/fdmns/tmpusr
# ln -s /dev/rz0g
# cd /
# mkdir /tmpusr
# mount tmpusr#usr /tmpusr
>From this point, mount your new root on /mnt and restore your file system:
# mount root_domain#root /mnt
# cd /mnt
# vrestore -xf /tmpusr/var/tmp/vdump.root
or whatever path you need to use to get to the backup copy of your old root
in whereever it is located.
Once you've restored it, you should be able to just unmount the temporary
file systems, halt the system, then boot, and you should be up and running.
Note that restoring the root file system just puts your /etc/fdmns directory
back where it was, so you won't need to muck with it. And your /etc/fstab is
going to be fine, as well.
From: alan.c.davis
Karen,
Stopping an install once it's started is less than comfortable for
most people. Rather that selecting custom install, go to the shell
prompt. You may then :
cd /dev
MAKEDEV rz<whatever>
MAKEDEV tz<whatever>
cd /
disklabel -s /dev/rrz<whatever>a unused
disklabel -e /dev/rrz<whatever>c
The a: partition label is at (if i remember) line 22. Change it's size
entry to the new size required (in 512 byte blocks)
Save the new label.
mkfdmn -r rz<whatever>a root_domain
mkfset root_domain root
mount root_domain#root /mnt
Now restore the backup.
From: bsramsey_at_hti.com
On step 4, make sure you have a swap partition defined (b is the default partion for swap on 4.0b). When you have the
partitions set the way you want them select the commit option and close to return to the installation menu. Don't forget to
set advfs (pull-down option) for the root partition on the installation setup screen. I do not remember having to set
anything to add the boot block.
-Brenda Ramsey
Raytheon Systems Company
From: speno_at_isc.upenn.edu
I recommend a 128MB / partition for all DU systems these days.
You shouldn't need more than that, unless something is really wrong.
> 1. backup / with vdump
> 2. boot from the 4.0E install CD
> 3. select a Custom Install
> 4. combine the a and b partitions(b is not currently being used).
> 5. select the UNIX Shell option and restore / with vrestore
>
> Will this work and will I get a bootable AdvFS / partition?
Probably. But you may have an issue with the bootblocks. Since the disk is
already AdvFS and bootable though, it'll probably be okay. If not, you can
play with disklabel to "fix" it. I usualy play it by ear when that comes
up, so I can say exactly what you'd need to do.
From: henderson_at_unx.dec.com
Karen,
Be sure that your 'b' partition is not being used for swap. It is a quasi
convention for the b partition of the system disk to be the swap partition. I
would use 'diskconfig' to see.
Paul
--
Paul Henderson
DIGITAL Unix Engineering, Compaq Computer Corporation
___________________________________________________________________
Karen Y. Byrd C511 Richards Bldg.
Systems Manager 3700 Hamilton Wlk.
Univ. of Pa. Philadelphia, PA 19104-6062
School of Medicine Voice: 215/898-6865
Information Services Fax: 215/573-7645
and Operations Group
HISD/UPHS byrd_at_mscf.med.upenn.edu
karen_at_mail.med.upenn.edu
Received on Tue Jan 26 1999 - 18:11:24 NZDT