Technical article 104883

Virtual Disk Manager claims no disk space available for configuration

OpenServer 5.0.0

Written · Last revised

Problem

In trying to configure a new virtual disk, this error message occurs:

There is not enough free space available on the system to complete this configuration, it is all being used for divisions and/or vdisk pieces

The configuration then fails.

Cause

There are two possible causes for this error.  Either there
are no available physical disks configured on the system, or
the physical disks that are configured have divvy(ADM) information
written out to them.

Solution

Check to make sure that the kernel recognizes the drives as
being configured.  Run the command "hwconfig -h" and look for
lines similar to:
disk    -   -   -   type=IDA0 unit=1 cyls=1646 hds=16 secs=63
or:
disk    -   -   -   type=S ha=0 id=4 lun=0 bus=0 ht=ad
Sdsk    -   -   -   cyls=525 hds=64 secs=32 fts=sb

You should see listings for all configured disks on the system.

If the disk does not appear there, use the Virtual Disk Manager's
Disk ==> Examine Disk Map option to display the physical disk
mapping.  If the disk does not appear on this chart, you will
need to re-run "mkdev hd" and add the disk into the kernel, reboot
the system, and run "mkdev hd" again to set up the partitions.
When running "mkdev hd" for the second time, DO NOT install
a divvy(ADM) table if it gives you the option.  You will see a
dialogue like this:
The virtual disk driver is installed.

Do not create a division table on partitions which will be used for virtual disk pieces.

Choose one of the following options below or quit

'y' to create a division table on the active partition 'n' to avoid creating a division table

Enter 'y', 'n' or enter 'q' to quit:

Enter "n" at the prompt.  If you are taken directly into
divvy(ADM), then the disk cannot be incorporated into an array
without intermediate processing (see below).
Note: At any point, if you type divvy /dev/hdxa, where 'x' is a
valid disk number other than 0, and a divvy(ADM) table comes up you
will have to follow the procedure outlined below.  If a disk does
NOT have a division table you will see a message like this:

No valid division table. Run divvy with either the -i flag if this device is to be initialized with a new root file system, or the -m flag if it is to be initialized with a number of mountable file systems.

If you see this message, then the disk is ready to be used in a virtual disk array.

If a disk already has a division table written to it, there are
two options: reformat the disk or convert the existing disk
into a "simple" virtual disk.  Reformatting the disk is easily
accomplished by running a destructive scan via badtrk(ADM); see
the badtrk(ADM) man page for more information.  (Note that
scsibadblk(ADM) has been obsoleted and replaced by badtrk(ADM)
in Release 5.0.0)  If you have data on the disk that you need
to save, you will need to do a full backup first.
The final option is to use the Virtual Disk Manager to create
a new disk of type "Simple".  Again, if you have data already
on the disk that you need to save, you will need to do a full
backup first.  Then, unmount the filesystems that are in use
on the disk, start the Virtual Disk Manager and select Disk ==>
New ==> Vdisk type "Simple", and select the disk you need
converted.  The existing division(s) will be deleted once the
Simple virtual disk is assigned, and the drive is ready for
use in a virtual disk array.

If none of these solutions works, contact your support provider for more information.

See also

See the man pages for dktab(F) and dkconfig(ADM); System Administrators Guide, Chapter 8; Other articles in this database on Virtual Disk Manager.

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