Problem
I have installed the Virtual Disk Manager product and mirrored my root disk. My root disk failed. I followed the Release Notes section entitled:
Replacing a mirrored root or parity diskAs instructed I reconfigured the mirrored disk to have the same IDE or SCSI configuration as the root disk. For example, if my root disk was at id=0 on the first adapter and my mirrored disk was at id=1 on my second adapter, I rejumpered it at id=0 and moved it to adapter 0. However, I am unable to boot and may see messages such as:
NO OSorPanic: srmountfun-Error 22 mounting rootdev vdisk(99/1) Cause
The Virtual Disk Manager allows you to configure a mirrored disk with different offsets. The three reserved virtual disks, vdisk1, vdisk2 and vdisk3 are used to mirror the root disk to your mirrored disk. The easiest way to describe and understand the problem is to analyze the resulting /etc/dktab file entries.
/dev/dsk/vdisk1 mirror 2 32
/dev/dsk/0s1 243330 4142330
/dev/dsk/1s1 16002 4142330/dev/dsk/vdisk2 mirror 2 32
/dev/dsk/0s1 46722 196608
/dev/dsk/1s1 4148332 196608/dev/dks/vdisk3 mirror 2 32
/dev/dsk/0s1 16002 30720
/dev/dsk/1s1 4354940 30720The first line of each vdisk describes the virtual disk. Vdisk1 is reserved for mirroring root. The 2 means it consists of two pieces and the 32 is the cluster size (in what size chunks should the data be mirrored).
The next two lines show the configuration for mirroring root, on the root (0s1) and mirrored (1s1) drives. The first number depicts the offset, or at what point the data is to begin. Notice they DO NOT match. The root disk has an offset of 243330, that is, begin the data at this location, while the mirrored disk will begin mirroring the same data at 16002. Since the lengths are the same (4142330) VDM allows this configuration. Vdisk2, reserved for swap, and vdisk 3, reserved for boot, also have the same discrepancies. All is fine until the root disk fails. Upon bootup the /etc/dktab file is read to determine the vdisk configurations. You can see by the vdisk3 entries that 0s1 (root disk) is configured to have its boot information, starting at 16002. When this disk failed, the 1s1 (mirrored disk) is now the boot disk. The /etc/dktab file gets read on bootup and is expecting the boot data to begin at 16002, but from looking at the dktab configuration we can see it will never find it, as the new boot disk has the boot data beginning at 4354940.
If your goal is to mirror your root disk to the second disk that you successfully added to your system, and have the ability to boot from that mirrored drive should your root drive fail, you should have chosen "Continue" when you got to the following menu:
+---------------------------------------------------------------+
| Mirror Root/Swap/Boot |
| |
| +------Select Divisions----------------------------------+ |
| | | |
| | vdisk1 to mirror root: Yes No | |
| | | |
| | vdisk2 to mirror swap Yes No | |
| | | |
| | vdisk3 to mirror boot: Yes No | |
| | | |
| +--------------------------------------------------------+ |
| |
| Continue Cancel Help |
+---------------------------------------------------------------+ Solution
The only possible workaround is to follow emergency recovery procedures and edit the /etc/dktab file. Make the 0s1 offsets look identical to the 1s1 offsets. You should then be able to boot off your mirrored disk.
This has been reported to SCO Engineering.
See also
Virtual Disk Manager Supplement 1.1.0 Release Notes