Technical article 113762

I get the following error message in the boot option of VDM, when I choose "recreate" to recreate the boot partition of the 2nd drive: "Unable to determine the configuration of the recover division on the root partition"

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I get the following error message in the boot option of VDM, when I choose "recreate" to recreate the boot partition of the 2nd drive: "Unable to determine the configuration of the recover division on the root partition"

Cause

This means that the "divvy" table of the root disk does not have a recover area for "fsck" to run in should the root filesystem need to be checked.

Run the "divvy" command below to check:

+-------------------+------------+--------+---+-------------+------------+
| Name              | Type       | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------+
| .boot-vd_save     | EAFS       |  no    | 0 |            0|       19999|
| .swap-vd_save     | NON FS     |  no    | 1 |        20000|      412999|
| .root-vd_save     | HTFS       |  no    | 2 |       413000|     4213246|
|                   | NOT USED   |  no    | 3 |            -|           -|
|                   | NOT USED   |  no    | 4 |            -|           -|
|                   | NOT USED   |  no    | 5 |            -|           -|
|                   | NOT USED   |  no    | 6 |            -|           -|
| hd0a              | WHOLE DISK |  no    | 7 |            0|     4225062|
+-------------------+------------+--------+---+-------------+------------+
4217062 1K blocks for divisions, 8001 1K blocks reserved for the system

If this is the case, VDM will only display this as a warning when it recreates.

This highlights potential problems in the future should your disk
crash and the "root" disk needs to be replaced or boot from the
"mirror" disk.  During this process, the root filesystem will be
"fsck'ed".  If you do not have a "recover" filesystem defined in
"divvy" for "fsck", you are likely to suffer some file corruption
to files that were writing to the disk at the time of the disk
crash.

Solution

In this example, this is how a 4GB root disk could look if the appropriate "fsck" filesystems required:

+-------------------+------------+--------+---+-------------+------------+
| Name              | Type       | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------+
| .boot-vd_save     | EAFS       |  no    | 0 |            0|       19999|
| .swap-vd_save     | NON FS     |  no    | 1 |        20000|      412999|
| .root-vd_save     | HTFS       |  no    | 2 |       413000|     4213246|
|                   | NOT USED   |  no    | 3 |            -|           -|
|                   | NOT USED   |  no    | 4 |            -|           -|
| scratch           | NON FS     |  no    | 5 |      4213247|     4217051|
| recover           | NON FS     |  no    | 6 |      4217052|     4217061|
| hd0a              | WHOLE DISK |  no    | 7 |            0|     4225062|
+-------------------+------------+--------+---+-------------+------------+
4217062 1K blocks for divisions, 8001 1K blocks reserved for the system
NOTE:     There can only be one "recover" filesystem per system.  Additional
          disks will have an area defined for "fsck" on filesystems contained
          on that disk.  This is an automatic process handled by "divvy" when
          the filesystems are originally created.

See also

ta103734, "What is /dev/recover and what is it used for?"
ta104824, "Configuring fsck(ADM) to bypass prompting for scratch file."
ta105734, "How do I configure a MIRROR of Root using the Virtual Disk
           Manager?"
fsck(ADM)

From the Xinuos technical article database, record 113762. Reproduced with permission. The original is at www.sco.com/ta/113762, 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.