Technical article 105820

The Virtual Disk Manager displays vdisk2 with Bad Parity.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

I am mirroring my root disk to another disk using the Virtual Disk
Manager. My system crashed and upon reboot the Virtual Disk Manager
restored parity on vdisk1 and vdisk3 automatically. I am also seeing
error messages on bootup that /dev/dsk/vdisk2 is disabled.  When I
go into the Virtual Disk Manager GUI it shows:
/dev/dsk/vdisk2            BAD PARITY

If I click on Disk Maintenance==>Repair Parity I get the following:

/etc/dkconfig restore operation on /dev/dsk/vdisk2 configuration is disabled

Cause

The virtual disks vdisk1, vdisk2, and vdisk3 are reserved by the Virtual Disk Manager for root, swap, and boot respectively.

NOTE: The Virtual Disk Manager Release Supplement 1.1.0 added the ability to mirror boot, which allows you to boot off a mirrored drive. SCO OpenServer Release 5.0.2 and 5.0.4 come with this supplement installed. OpenServer Release 5.0.0 came with Virtual Disk Manager Release 1.0.0, so vdisk3 was not reserved for boot. The Supplement 1.1.0 can be downloaded from the Supplements/vdm110 directory on SCO's website.

A restore operation for swap is by default turned off, as a restore for swap is not needed. This saves the system time as the start-up scripts for the Virtual Disk Manager will blindly try to run a restore on each virtual disk after such a crash. This is why you are unable to generate a restore operation from the Disk==> Maintenance screen.

The cause of the Bad Parity error on /dev/dsk/vdisk2 is unknown, but the following workaround will resolve the problem.

Solution

Log in as root and run the following commands from the command line:

# dkconfig -e /dev/dsk/vdisk2

This will enable the array and mirror restore functionality on vdisk2.

# dkconfig -R /dev/dsk/vdisk2

This will restore the parity data on the array.

# dkconfig -d /dev/dsk/vdisk2

This will disable the array and mirror restore functionality as configured by default.

Now shut down and reboot the system to multiuser mode. The /dev/dsk/vdisk2 should not give any error messages on bootup and the Bad Parity message should be gone.

From the Xinuos technical article database, record 105820. Reproduced with permission. The original is at www.sco.com/ta/105820, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.