Hello osf-managers,
For this who don't have the time: This is quite a long one and contains quite a bit of detail - you will need
to take a few minutes at least to briefly read through what I've got
to say. I would also advise you print this out for better
referencing (approx 5 Pages).
I have a customer that encounters a problem with the encapsulation
process of the root disk. Here are all the details:
Operating System : Digital Unix 3.2-d
Hardware Platform : Alpha 8200
Reporting Error during root disk encapsulation
Problem
We are trying to provide our client with root disk mirroring. We
completed the steps 1-8 (see the outline of the procedure), and
the process failed on step 9.
The system reported the error during the 2nd reboot. The error was as follows,
starting LSM
Volume Manager : Partitioning rz24 as an encapsulated disk
Volume Manager : Partitioning rz24g as an encapsulated disk
The Volume Manager is now reconfiguring (initialisation phase) ....
Volume Manager : Adding rz24 (rz24) as an encapsulated disk.
Starting all newly created volumes ...
Volume Manager : Adding rz24g (rz24g) as an encapsulated disk.
voimake: Error creating subdisk rz24g-01:
Outside of public partition
The creation of encapsulationd volumes for rz24g failed
Root encapsulation failed.
Please could someone shed some light on what the above error means??
GFIS root disk mirroring Procedure
This procedure will create a mirror of the / (root) filesystem (/dev/rz24a) as well as the swap partition (/dev/rz24g).
Because the root and swap partitions are not contiguous, we need 3 partitions to be free. We have 6 partitions free, so thats fine.
1. Back up whole system
2. Make sure that the target disk is completely empty, and that all partition entries are `unused'. If this is not the case, one can re-label the disk,
disklabel -rw rz34 SYMMETRIX
3. Perform Initial Setup of LSM.
Creates rootdg disk group
Starts LSM daemons
Adds disk devices to disk group
Creates the /etc/vol/volboot file
/sbin/volsetup rz34
4.Check LSM disk status
voldisk list
5. Check status of rootdg diskgroup
volprint -ht
6. Check status of /etc/vol/volboot
voldctl list
7. Check status of vold daemon
voldctl mode
8. Encapsulate the root disk
/usr/sbin/volencap rz24
9. Shutdown the system and reboot,
shutdown -r now
The error takes place in step 9.
10. The system should reboot twice.
11. Watch the system console for any errors, that the encapsulation process might have failed.
12. One can ignore messages of the form,
vm_swap_init: warning /sbin/swapdefault swap device not found
vm_swap_init: in swap over commitment mod
13. Now perform the mirroring of the root disk.
volrootmir rz34
14 Read the disklabel of the target disk, 2 new partitions should be created.
disklabel -r /dev/rrz34c
The root disk should be successfully mirrored at this stage (which we
don't even get this far)
Listing of /etc/fdmns before the failed root encapsulation
$ ls -lR /etc/fdmns
total 48
drwxr-xr-x 2 root system 8192 Dec 12 2022 home_dmn
drwxr-xr-x 2 root system 8192 Dec 12 2022 opt_dmn
drwxr-xr-x 2 root system 8192 Oct 18 1995 root_domain
drwxr-xr-x 2 root system 8192 Dec 12 2022 sybdata_dmn
drwxr-xr-x 2 root system 8192 Dec 12 2022 sybexe_dmn
drwxr-xr-x 2 root system 8192 Dec 12 2022 usr_domain
./home_dmn:
total 0
lrwxr-xr-x 1 root system 9 Dec 12 2022 re3c -> /dev/re3c
./opt_dmn:
total 0
lrwxr-xr-x 1 root system 9 Dec 12 2022 re4c -> /dev/re4c
./root_domain:
total 0
lrwxr-xr-x 1 root system 10 Oct 18 1995 rz24a -> /dev/rz24a
./sybdata_dmn:
total 0
lrwxr-xr-x 1 root system 10 Nov 24 10:57 rz32c -> /dev/rz32c
lrwxr-xr-x 1 root system 10 Nov 24 10:58 rz33c -> /dev/rz33c
./sybexe_dmn:
total 0
lrwxr-xr-x 1 root system 9 Dec 12 2022 re2c -> /dev/re2c
./usr_domain:
total 0
lrwxr-xr-x 1 root system 9 Dec 12 2022 re1c -> /dev/re1c
Listing of /etc/fstab before the root encapsulation
$ cat /etc/fstab
root_domain#root / advfs rw 0 0
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw 0 0
sybexe_dmn#sybase /sybase advfs rw 0 0
sybdata_dmn#sybase /sybase/sybdata advfs rw 0 0
home_dmn#home /home advfs rw 0 0
opt_dmn#opt /opt advfs rw 0 0
/dev/rz24g swap1 ufs sw 0 2
Before the Failed Root Encapsulation
$ disklabel -r rz24
# /dev/rrz24c:
type: SCSI
disk: RZ28M
label:
flags:
bytes/sector: 512
sectors/track: 99
tracks/cylinder: 16
sectors/cylinder: 1584
cylinders: 2595
sectors/unit: 4110480
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 ADVfs # (Cyl. 0 - 82*)
b: 401408 131072 unused 0 0 # (Cyl. 82*- 336*)
c: 4110480 0 unused 1024 8192 # (Cyl. 0 - 2594)
d: 1191936 532480 unused 1024 8192 # (Cyl. 336*- 1088*)
e: 1191936 1724416 unused 1024 8192 # (Cyl. 1088*- 1841*)
f: 194128 2916352 unused 1024 8192 # (Cyl. 1841*- 2594*)
g: 1787904 532480 unused 1024 8192 # (Cyl. 336*- 1464*)
h: 1790096 2320384 unused 0 0 # (Cyl. 1464*- 2594*)
After the Failed Root Encapsulation
$ disklabel -r rz24
# /dev/rrz24a:
type: SCSI
disk: RZ28M
label:
flags:
bytes/sector: 512
sectors/track: 99
tracks/cylinder: 16
sectors/cylinder: 1584
cylinders: 2595
sectors/unit: 4110480
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 ADVfs # (Cyl. 0 - 82*)
b: 401408 131072 unused 0 0 # (Cyl. 82*- 336*)
c: 4110480 0 unused 1024 8192 # (Cyl. 0 - 2594)
d: 1191936 532480 unused 1024 8192 # (Cyl. 336*- 1088*)
e: 16 533008 LSMsimp # (Cyl. 336*- 336*)
f: 131056 16 LSMpubl # (Cyl. 0*- 82*)
g: 1786848 533536 swap # (Cyl. 336*- 1464*)
h: 512 533024 LSMpriv # (Cyl. 336*- 336*)
Note: rz34 is a 4GB disk (RZ29) and rz24 a 2GB (RZ28)
The strange thing is that when I try and simulate the exact same procedure on my Alpha
2000 system, it works perfectly. The only obvious differences are:
1. I am using 2 x RZ28's(rz3 and rz4) with rz3 disklabel
being identical to the rz24 disklabel (root - partition a and swap on
g) and /usr is on a RZ26(rz1c).
2. I am not using RAID on my system (which should be irrelevant)
3. I ran #volinstall before I ran volsetup. (the customer didn't -
they went straight into volsetup)
4. I am running ver 3.2D-2 the customer is running 3.2D-1 (this
shouldn't cause a problem)
5. They are running sybase, I am not running any database on my
system.
6. After the root encapsulation process successfully took place - my
disklabel for rz3(system disk) was slightly different to theirs. The
cylinder numbers/sizes stay the same but some of the partition sizes and
offsets differ??? I don't know if this could be related to the
problem we're having.
Here is a copy of my disklabel for rz3 which you can use to compare
with the customers rz24 disk:
# /dev/rrz3a:
type: SCSI
disk: RZ28D
label:
flags:
bytes/sector: 512
sectors/track: 99
tracks/cylinder: 16
sectors/cylinder: 1584
cylinders: 2595
sectors/unit: 4110480
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 ADVfs # (Cyl. 0 - 82*)
b: 401408 131072 unused 1024 8192 # (Cyl. 82*- 336*)
c: 4110480 0 unused 1024 8192 # (Cyl. 0 - 2594)
d: 1191936 532480 unused 1024 8192 # (Cyl. 336*- 1088*)
e: 16 532480 LSMsimp # (Cyl. 336*- 336*)
f: 131056 16 LSMpubl # (Cyl. 0*- 82*)
g: 1787376 533008 swap # (Cyl. 336*- 1464*)
h: 512 532496 LSMpriv # (Cyl. 336*- 336*)
I thinks thats about it besides handing over the physical system.
Many thanks to those who took the time to read through all this and
who managed to reply. Looking forward to your responses (if I get
any)
Paulo
Received on Fri Feb 14 1997 - 13:07:08 NZDT