Solstice DiskSuite 4.2.1 Reference Guide

Appendix A DiskSuite Error Messages

Introduction

The first part of this appendix, "DiskSuite Tool Messages", contains the status, error, and log messages displayed by DiskSuite's graphical user interface, DiskSuite Tool. The second part of this appendix, "DiskSuite Command Line Messages", contains the error and log messages displayed by the command line utilities.

Use the following table to locate DiskSuite Tool status, error, and log information.

Use the following table to locate DiskSuite command line error and log information.

DiskSuite Tool Messages

This part of this appendix contains the status, error, and log messages displayed by DiskSuite's graphical user interface, DiskSuite Tool.

State Information Terms

The dialog boxes shown in DiskSuite Tool use the following terms when the state of the components is reported.

OK - The component is operating properly.
Resyncing - The component is in the process of resyncing (copying) the data.
Erred - The slice has encountered an I/O error or an open error. All reads and writes to and from this slice have been discontinued. See the Solstice DiskSuite 4.2.1 User's Guide for information on slice replacement.
Last erred - The slice has encountered an I/O error or an open error. However, the data is not replicated elsewhere due to another slice failure. I/O is still performed on the slice. If I/O errors result, the mirror or RAID5 I/O will fail. See the Solstice DiskSuite 4.2.1 User's Guide for information on slice replacement.

Metadevice Editor Messages

The Metadevice Editor has a message line at the bottom of the window that displays information about objects and actions. There are two types of feedback displayed:

When you are pointing the cursor at an object, the message line has the following format:
object_type object_name: attribute=value,...
When you are dragging an object that is not yet populated, the message line has the form:
Drop requirement comp_type into new_object_type new_object_name
Once the object is sufficiently populated, the message line has the form:
Drop comp_type into new_object_type new_object_name or commit

Dialog Box Error Messages

DiskSuite displays the following messages in Error dialog boxes. When these messages are displayed, the only choice on the dialog box is OK. The action you attempted will not be performed. Use the information here to correct the error.

A RAID can only have one operation that causes a resync per commit

You have tried to commit two separate changes to a RAID device at the same time. While the changes may be valid, only one can be performed at a time. For example, if you replace a slice and add a new slice, this message is displayed. You must perform one change and click on the Commit button, then perform the other change and click on the Commit button.

Concat dn has no stripes

You have tried to commit a concatenation that has no stripes. You must add stripes to the concatenation.

You cannot delete a metadevice that is in use.

You have tried to delete a metadevice that contains a mounted file system, is being swapped on, or is open as a raw device.

dn has no components.

You have tried to commit a Concat/Stripe template that has no slices. You must add slices to the object before clicking on the Commit button.

Mirror dn has no submirrors

You have tried to commit a mirror that has no submirrors. You must add submirrors before clicking on Commit.

RAID dn must have at least three slices.

You have tried to commit a RAID metadevice that has fewer than three slices. Add the necessary slices and commit the RAID metadevice.

Slices added to a RAID device must be at least
as large as the smallest original slice.

You have tried to add a slice to a RAID device that is smaller than the slices that are already part of the RAID device.

Slice slice is mounted. You cannot add it to Concat/Stripe dn, it
is not the first mounted slice to be added.

You have tried to add a slice that has a mounted file system to a Concat/Stripe and there is already at least one slice in the Concat/Stripe. The slice with the mounted file system must be the first one added to the Concat/Stripe.

Slice slice is mounted. You cannot add it to dn, it already has a
mounted slice.

You have tried to add a slice that contains a mounted file system to a Concat/Stripe template. The slice that contains the mounted file system must be the first slice added.

Slice slice is mounted. You cannot add a mounted slice to a RAID
device, doing so would corrupt the file system.

You have tried to add a slice that contains a mounted file system to a RAID template. Choose another slice that does not contain any data.

Slice slice is too small to be used in a RAID device.

You have tried to add a slice that is too small. The slice being added is either smaller than the slices already in the RAID device or is too small to be used in a RAID device.

Submirror dn has a mounted file system, it should be the first
submirror added.

You have tried to add a submirror that contains a mounted file system to an existing mirror. To mirror this file system, create a one-way mirror using this submirror then attach another submirror that does not contain data.

Submirror dn is too small.

You have tried to add a new submirror that is smaller than the current size of the Mirror. The submirror must be as large as the existing submirror.

Mirror dn has a component with a file system mounted. You cannot
add another submirror.

You have tried to add a submirror that contains a mounted file system and the Mirror already has a mounted file system on the other submirror. You must add an unassigned slice.

The root file system may not be mounted on
a concat with more than one stripe.

You have tried to drop the slice that contains the root file system into a Concat/Stripe template. Remove one of the existing stripes.

The root file system may not be mounted on a trans device.

You have tried to drop the slice that contains the root file system into a Trans device template. The root file system cannot be placed in a Trans device.

Trans dn has no master

You have tried to commit a Trans device that has no master device. Add the master device and commit the device.

You cannot add device to a RAID device while it is initializing

You have tried to add a slice or hot spare pool to a RAID device that has been committed and is initializing. Wait until the device is initialized.

You cannot replace a slice in a RAID device while it is
initializing.

You have tried to add a slice to a RAID device that has been committed and is initializing. Wait until the device is initialized.

The value you entered value is too large.
You should use a value less than new value, which is the
maximum possible device size.

You tried to enter an unacceptably large value in one of the Slice Filter window`s size fields.

Your attempt to change the name of Hot Spare Pool hspnnn
to hspnnn failed for the following reason:

You tried to change the name of a hot spare pool to a name that already exists, or the name is not valid.

RAID component component is not the same size as component
component. Extra space on the larger component will be wasted.

You tried to add a slice to a RAID5 metadevice that is not the same size as the existing slices in the RAID device.

You cannot change the hot spare pool for a RAID device while it
is initializing.

You tried to change the current hot spare pool for a RAID5 metadevice during its initialization. Wait for the initialization to complete before attempting to change the hot spare pool again.

The RAID device has failed to initialize. It cannot be repaired
and should be deleted.

There was an error when trying to initialize the RAID5 metadevice. The only recourse left is to delete the device and recreate it, after repairing any errored slices.

A slice in a created stripe may not be replaced unless the stripe
is part of a submirror with redundancy.

You can only replace a slices if data redundancy exists.

A slice in a stripe may not be enabled unless the stripe is part
of a submirror with redundancy.

You can only enable slices if data redundancy exists.

The metadevice state database has not been committed since slice
slice was added. You cannot restore replicas on the slice.

You need to commit the MetaDB object before enabling any broken slices.

There is no device with a mounted file system which matches
the path name path.

You tried to drag a file name from Storage Manager to the Metadevice Editor canvas and DiskSuite Tool could not locate the device containing the file system.

Disk Set Released
host no longer owns the setname disk set.
setname cannot continue; you must exit.

Disk Set Changed
An external change has occurred to the setname disk set.

Disk Set Load Failed
Unable to load disk set setname.

The above three messages indicate that changes were made to the diskset from the command line while DiskSuite Tool was running on that diskset.

Statistics sheets are not available for controllers, trays or
slices.

You tried to display the Device Statistics window for a controller, tray, or slice. The Device Statistics window is only available for metadevices or disks.

Sync NVRAM is only available for SPARCstorage Array controllers,
trays and disks with working batteries.

You tried to sync NVRAM on a non-SPARCstorage Array device, or you tried to sync NVRAM on a SPARCstorage Array whose battery has failed.

Fast Write is only available for SPARCstorage Array controllers,
trays and disks with working batteries.

You tried to enable Fast Write on a SPARCstorage Array device whose battery has failed.

Reserve Disks is only available for SPARCstorage Array
controllers, trays and disks.

You tried to perform a disk reservation on a non-SPARCstorage Array device.

Release Disks is only available for SPARCstorage Array
controllers, trays and disks.

You tried to release a disk reservation on a non-SPARCstorage Array device.

Start Disks is not available for slices.

Slices by themselves cannot be started, only disks.

Stop Disks is not available for slices.

Slices by themselves cannot be stopped, only disks.

You may not detach a submirror while it is resyncing.

You cannot detach a submirror in the process of resyncing.

Error while trying to reserve lock for metaset setname.

The lock for setname could not be acquired. Either another instance of DiskSuite Tool or the command line currently has the lock.

Interlace value is out of range.

You entered an invalid interlace value for the striped metadevice or RAID5 metadevice.

Failed trying to exchange metadevices dn and dn.

You cannot exchange metadevice names of a metadevice that is in use.

Failure trying to rename dn to dn.

You cannot rename a metadevice that is in-use, nor can you rename a metadevice to a name that already exists.

Metadevice name not in range dn - dn.

You tried to give a name to a metadevice outside the current defined range. If necessary, increase the value of nmd in the /kernel/drv/md.conf file.

The hot spare pool name not in the range hsp000 - hsp999.

Hot spare pools must be named hspnnn, where nnn is a number between 000 and 999.

The hot spare pool hspnnn already exists.

You tried to create a hot spare pool with an existing hot spare pool's name.

You cannot delete a mounted trans device that has an attached
logging device.

To delete a trans metadevice, first detach the logging device.

The metadevice dn is currently either opened, swapped on, or
mounted. Deleting it will cause the name to be pushed down.

The mirror or trans metadevice you are trying to delete is currently in-use. The deleted device name will be switched with one of its subdevices names. In the case of a mirror, the mirror name is switched with one of its submirror names. In the case of a trans metadevice, the trans name and the master device name are switched.

You cannot delete a mounted mirror with more than one submirror.

To delete the mirror, make it into a one-way mirror.

You cannot delete a mounted trans device whose master is not a
metadevice.

You are attempting to delete a mounted trans device whose master device is a slice. Unmount the trans metadevice to be able to delete it.

Cannot purge the NVRAM for device. Disk is reserved by another host.

Cannot sync the NVRAM for device. Disk is reserved by another host.

Cannot reserve device. Disk is reserved by another host.

Cannot release device. Disk is reserved by another host.

Cannot start device. Disk is reserved by another host.

Cannot stop device. Disk is reserved by another host.

Cannot disable fast write for device. Disk is reserved by another
host.

Cannot enable fast write for device. Disk is reserved by another
host.

Cannot enable fast write for synchronous writes for device. Disk
is reserved by another host.

The above messages indicate that another host has a reservation on device. To perform the desired action, first release the reservation.

You cannot detach an existing submirror while a replace, enable
or attach is pending.

You tried to detach a submirror that is currently be replaced, enabled, or attached. Wait for the operation to complete before attempting the detach again.

You cannot enable a slice in a mirror while the mirror is
resyncing.

You tried to enable a slice in a submirror while the mirror is being resynced. Wait for the operation to complete before attempting the enable again.

Dialog Box Warning Messages

DiskSuite displays the following messages in Warning Dialog Boxes. When these messages are displayed you can either continue or undo the action. The information here will help you determine which action to select.

All of the state database replicas are on the same controller.

You have populated the MetaDB template with slices that are all attached to the same controller. If the controller fails, you will not have access to any of the metadevices.

The new Concat/Stripe device dn has a slice with a mounted file
system. If an entry for its file system exists in
"/etc/vfstab" it will be updated when the Concat/Stripe is
committed so that the next mount of the file system will use the
new device. The system must be rebooted for this device mount to
take effect.

You have tried to add a slice that contains a mounted file system to a Concat/Stripe template. The slice that contains the mounted file system must be the first slice added. You cannot add a mounted file system to a RAID device.

Metadevice device_type dn will be deleted.
Data could be lost.
Really delete it?

This message displays when you attempt to delete any committed metadevice. You should continue only if you are sure your data is protected.

Stripe component dn is not the same size as component
dn. Extra space on the larger component will be wasted.

You have tried to add slices to a Concat/Stripe (stripe) that are a different size than the slices already in the stripe. Adding slices of a different sizes to a stripe causes wasted space.

Slice dn is on the same controller as slice dn.It is not advisable
to have slices from multiple submirrors on the same controller.

You have tried to create a Mirror with submirrors that are made up of slices attached to the same controller. If the controller fails, the mirror will not protect against lost data.

Slice dn is on the same disk as slice dn.It is not advisable to
have slices from multiple submirrors on the same disk.

You have tried to create a Mirror with submirrors that are made up of slices from the same disk. If the disk fails, the mirror will not protect against lost data.

Submirror dn is not the same size as submirror dn.
Extra space on the larger submirror will be wasted.

You have tried to create a Mirror that has differently sized submirrors. The extra space on the larger submirror cannot be used.

Submirror dn has an erred component.
Its data will not be valid after it is detached.

You have tried to detach or offline a submirror that has a slice reporting errors.

The file system mounted on metadevice dn has
been unmounted since the last status update.

You have tried to delete a metadevice that was unmounted. The device does not display the unmounted information. Select Rescan Configuration from the Metadevice Editor window's File menu to update this information.

The following components are in the erred state: dn
You may not replace RAID component dn until they are fixed.

You are replacing a component of a RAID metadevice that has reported errors (in the last-errored state). This cannot be performed if there are any other components in the RAID metadevice that have reported errors.

The following components are in the erred state: dn
The data for the component replacing RAID component dn may be
compromised.

You are replacing or enabling a RAID component that has reported errors. This action is dangerous if there is another component that has reported errors (in the last-errored state). The data on the new component may not be completely accurate.

The following components are in the last_erred state: dn
The data for RAID component dn may be compromised.

You are replacing or enabling a RAID component that is reporting errors. This action is dangerous if there is another component that has reported errors (in the last-errored state). The data on the new component may not be completely accurate.

The following components have erred: dn
The data for RAID component dn WILL NOT BE RESYNCED.

You have tried to replace a component in a RAID metadevice and there are two or more components reporting errors. It is not possible to replace the components because there is no way to recreate the data. If you proceed with the replacement, you must obtain the data from a backup copy.

The format of disk dn has changed.
You must restart metatool to incorporate the changes.

You have reformatted a disk that used to have a metadevice, file system, or database replica and selected the Rescan Configuration option from the Metadevice Editor window's File menu. If the disk is not being used, the new information is read by DiskSuite and displayed in the appropriate windows (for example, Slice Browser and Disk View).

The log device for Trans dn cannot be detached until
the Trans is unmounted or the system is rebooted.

You have tried to detach a log and commit the Trans object. The detach will not be performed as long as the log master is mounted. The Trans device is actually in a "detach pending state."

The master device dn for Trans dn has a mounted file system.

In order for logging of
this file system to be activated, the file
/etc/vfstab must be updated with the
new device name and the system rebooted.

Committing Trans dn will update
/etc/vfstab automatically if an entry exists
for the file system.

You have tried to add a metadevice that has a mounted file system to a Trans master. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The master device dn for Trans dn has a mounted file system.

If an entry for its file system exists in "/etc/vfstab," it will
be updated with the new device to mount for the file system.

The system must be rebooted for this
device mount to take effect.

You have tried to add a master device that has a mounted file system to a Trans. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The metadevice dn has been removed as a swap device
since the last status update.

You have tried to delete a device that is the swap device. The device still says it is swap. To update the device's status, select Rescan Configuration from the Metadevice Editor window's File menu.

The new Mirror device dn
has a submirror with a mounted file system.

If an entry for its file system exists in /etc/vfstab, it will
be updated with the new device to mount for the file system.

The system must be rebooted for this
device mount to take effect.

You have tried to add a Concat/Stripe that has a mounted file system to a Mirror. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The state database will have no replicas.
If the system reboots, all metadevices will
be corrupted.

You have tried to remove the state database and all replicas from the MetaDB template. If you commit, you will not have access to any metadevices after the next reboot.

The submirror dn has a slice with a mounted
file system.

In order for mirroring of
this file system to be activated, the file
/etc/vfstab must be updated with the
new device name and the system rebooted.

Committing Mirror dn will update
/etc/vfstab automatically if an entry exists
for the file system.

You have tried to add a submirror that has a mounted file system to a Mirror. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

This log is not mirrored. It is recommended that you mirror logs
whenever possible to avoid single points of failure.

You have tried to create a Trans device with a log that is not mirrored. If the log is not mirrored, the data could be lost or unavailable.

Trans dn has no log device.

You have tried to commit a Trans device that has no Trans log. You should add the log before committing the device. Until you add the log, the logging feature is disabled.

Dialog Box Information Messages

DiskSuite displays the following messages in information dialog boxes. These messages tell you a common mistake has been made or provide a helpful message. These dialog boxes appear with a large "i" on the left side of the message. There is only one button on the bottom of this dialog: OK.

You added additional capacity to the metadevice metadevice_type on
which file system file_system is mounted. You have the
option of growing this file system to take advantage of
this additional space either now or later (by hand).
If you choose to grow it now, the application will be
disabled until the growth process completes.

The command that will be run is:

    "growfs -M file_system /dev/md/rdsk/dn"

Do you want to grow the metadevice now or later?

You have tried to add slices to a Concat/Stripe metadevice. Following a commit, you can expand the file system, as documented in the Solstice DiskSuite 4.2.1 User's Guide.

The file system file_system mounted on metadevice dn
is now being grown.

You are growing a file system.

Statistic sheets are not available for the Metastate
database (metadb), Hot Spare Pools or slices.

You cannot display a Device Statistics window for the metadevice state database, hot spare pools, or slices.

Metadevice Editor Window Messages

The following messages are displayed when you are pointing to an object inside the Metadevice Editor window. An explanation of the message follows the sample output.

Click or drag to create a new object device

You are pointing at any of the five Template icons. object is either Trans, RAID, Mirror, Concat/Stripe, or Hot Spare Pool.

component_type dn: size=size, use=use, status=status

You are pointing at an object (component_type) on the canvas. The component_type is either Trans, RAID, Mirror, Concat/Stripe, or Hot Spare. The metadevice name is reported as dn, where the default size for n is a number in the range 0 to 127. The size is the capacity of the metadevice (for example, 500 Mbytes). The use is either Unassigned, Submirror, or /filesystem. The status is reported as OK, Attention, Urgent, or Critical.

Drag objects into this work area to look at or modify them...

You are pointing at an empty canvas or the device list in the Metadevice Editor window.

hspnnn: status=status

You are pointing at a Hot Spare Pool on the canvas. The Hot Spare Pool name is reported as hspnnn, where nnn is a number in the range 000 to 999. The status is reported as OK, Attention, Urgent, or Critical.

Slice cntndnsn: size=size, use=use, status=status

You are pointing at a disk slice on the canvas. The name of the slice appears in the format, cntndnsn. The size is the capacity of the slice (for example, 5 Mbytes). The use is either Unassigned or Component. The status is reported as OK, Attention, Urgent, or Critical.

Use Button2 to pan the viewport over the work area ...

You are pointing at the Panner. By pressing the middle button and moving the cursor, you move the canvas to a new view area.

Messages Displayed When Dragging an Object

The following messages are displayed when you are dragging an object inside the Metadevice Editor window. An explanation of the message follows the sample output.

Concatenations must be part of a mirror
for hot spare pools to function

You are dragging a Hot Spare Pool over a concatenation. This message is telling you that the Concat/Stripe must be part of a Mirror or the Hot Spare Pool you are dropping will not work.

Drop a concatenation into mirror dn

You are dragging a Concat/Stripe over the specified Mirror. If you drop the Concat/Stripe, it will become part of that Mirror.

Drop a concatenation to replace submirror dn

You are dragging a Concat/Stripe over the specified submirror. Drop the Concat/Stripe inside the rectangle that contains the submirror to make the replacement.

Drop a hot spare pool to assign it to concatenation dn

You are dragging a Hot Spare Pool over the specified concatenation. By dropping the Hot Spare Pool into the Concat/Stripe, it becomes associated with that concatenation.

Drop here to associate a hot spare pool with this RAID

You are dragging a Hot Spare Pool over the specified RAID device. If you drop the Hot Spare Pool, it will become associated with the RAID device.

Drop a metadevice or slice into trans log

You are dragging a metadevice or slice over a Trans device. If you drop the metadevice or slice, it will become part of the Trans device.

Drop a metadevice or slice into master

You are dragging a metadevice or slice over the Master of a Trans device. Drop the object into the Master to add it to the device.

Drop a slice into hot spare pool dn

You are dragging a slice over the specified Hot Spare Pool. Drop the slice to add it to the Hot Spare Pool.

Drop a slice into RAID dn

You are dragging an unused slice over the specified RAID device. If you drop the slice, it will become part of the RAID device.

Drop a slice of the same size to replace the current slice

You are dragging a slice either over a committed RAID device or over a submirror that has more than one submirror. You can drop the new slice on the existing slice to make a replacement.

Drop a slice to replace current slice

You are dragging an unused slice over a Concat/Stripe, RAID, or Trans device. To replace the slice you are over, release the middle button and drop the slice.

Drop a slice into stripe dn or commit

You are dragging an unused slice over a Concat/Stripe that has one or more slices. You can populate the Concat/Stripe with additional slices or select the Concat/Stripe (stripe) and execute a commit.

Drop a slice to add new replicas; you should have at least
three replicas.

You are dragging a slice over the MetaDB object. Drop the slice to create another replica. DiskSuite requires the configuration have a minimum of three slices in the MetaDB object.

Drop at least one concatenation into mirror dn

You are dragging a Concat/Stripe over the specified Mirror. You must drop a minimum of one Concat/Stripe into the specified Mirror.

Drop at least one slice into stripe dn

You are dragging an unused slice over a Concat/Stripe that has zero slices. You must populate the Concat/Stripe (stripe) with a minimum of one slice.

Drop at least three to create the RAID parity group

You are dragging an unused slice over the specified RAID device. You must drop a minimum of three slices into the RAID device.

Drop a slice to add a new replica.

You are dragging a slice over the MetaDB object. Drop the slice to create another replica.

You cannot add more concatenations;
mirror dn already has three submirrors

You are dragging a Concat/Stripe over the specified Mirror. You cannot add another Concat/Stripe (submirror) to a Mirror that already has three submirrors.

You cannot add slices to committed stripe dn

You are dragging an unused slice over a committed Concat/Stripe. DiskSuite does not permit you to add slices to a committed Concat/Stripe (stripe).

You cannot replace in-use slices in a hot spare pool

You are dragging an unused slice over a slice that is in use in a committed Hot Spare Pool. You cannot drop the new slice on a slice in a Hot Spare Pool that is currently in use.

You cannot replace objects in committed RAID dn

You are dragging an object over the specified RAID device. Because the device is committed, you cannot make replacements.

You cannot replace slices in a committed stripe unless
it is part of a submirror

You are dragging a slice over a a committed Concat/Stripe. You cannot make changes to this metadevice, unless it is part of a submirror.

You cannot replace submirror dn when
mirror dn has only one submirror

You are dragging a submirror over the specified submirror. You cannot drop the submirror into the Mirror when there is only one submirror present.

You cannot replace slices in a committed trans device

You are dragging an unused slice over a slice that is in use as a Trans master or log. You cannot replace slices in a committed Trans device.

Disk View Window Messages

The Disk View window has a message line at the bottom that displays information about objects and actions. There are two types of message line feedback displayed:

When you are pointing the cursor at an object, the message line has the following format:
object_type object_name: attribute=value,...
If you are pointing at a disk or slice that has a status problem, the message has the form:
object_type object_name: problem_description, affected_device
When you are pointing the cursor at an empty portion of the canvas, the following message displays:
Drop object onto color drop sites to show mappings
You can select a disk or slice and drag it to the color map at the bottom of the Disk View window. On a color monitor, you have four colors available as drop sites. On a monochrome monitor, you have one color drop site.

Messages Displayed When Pointing at an Object

The following messages are displayed when you are pointing to an object inside the Disk View window:

Slice cntndnsn: size=size, use=use, status=status

You are pointing at a disk slice on the canvas. The name of the slice appears in the format, cntndnsn. The size is the capacity of the slice (for example, 5 Mbytes). The use is either Unassigned, Component, Hot Spare, MetaDB Replica, Reserve, mount_point, swap, Trans Log, or Overlap. The status is reported as OK, Attention, Urgent, or Critical.

Messages Displayed When Dragging an Object

The following messages are displayed when you are dragging an object inside the Disk View window.

Drag slices onto object templates in the metadevice editor canvas

You are dragging an object from the Disk View window. You can drop the slices inside an object or on the canvas of the Metadevice Editor window.

Log Messages

Log messages are those passed by syslog(3) to the syslogd(1M). These messages are appended to a file and written to the console window. These messages will not appear in any DiskSuite error or problem list.

The log messages are divided into the following categories:

Notice log messages
Warning log messages
Panic log messages

The log messages displayed by DiskSuite are listed in alphabetical order below. Each message is always preceded with md: The variables in these messages indicate the following:

dev is a device name.
dnum is a metadevice name.
num is a number.
state is a Trans device state.
trans is either "logging" or "master."

Note -

When the initial portion of a message begins with a variable, the message is alphabetized by the first word following the variable.

Notice Log Messages

Could not load misc /dev

The named misc module is not loadable. It is possibly missing, or something else has been copied over it.

db: Parsing error on `dev'

The set command in /etc/system for the mddb.bootlist<number> is not in the correct format. Run metadb -p to place the correct set commands into the /etc/system file.

dnum: Hotspared device dev with dev

The first device name listed has been hot spare replaced with the second device name listed.

dnum: Hotspared device dev(num, num) with dev(num, num)

The first device number listed has been hot spare replaced with the second device number listed.

dnum: no mem for property dev

Memory could not be allocated in the prop_op entry point.

Warning Log Messages

dnum: not configurable, check /kernel/drv/md.conf

This error occurs when the number of metadevices as specified by the nmd parameter in the /kernel/drv/md.conf file is lower than the number of configured metadevices on the system. It can also occur if the md_nsets parameter for disksets is lower than the number of configured disksets on the system. To fix this problem, examine the md.conf file and increase the value of either nmd or md_nsets as needed.

dnum: Cannot load dev driver

The underlying named driver module is not loadable (for example, sd, id, or a third-party driver). This could indicate that the driver module has been removed.

Open error of hotspare dev
Open error of hotspare dev(num, num)

The named hot spare cannot be opened, or the underlying driver is not loadable.

dnum: read error on dev
dnum: write error on dev

A read or write error has occurred on the specified metadevice at the specified device name. This happens if any read or write errors occur on a metadevice.

dnum: read error on dev(num, num)
dnum: write error on dev(num, num)

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.

dnum: read error on dnum
dnum: write error on dnum

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.

State database commit failed
State database delete failed

These messages occur when there have been device errors on components where the state database replicas reside. These errors only occur when more than half of the replicas have had errors returned to them. For example, if you have three components with state database replicas and two of the components report errors, these errors may occur. The state database commit or delete is retried periodically. If a replica is added, the commit or delete will finish and the system will be operational. Otherwise, the system will time out and panic.

State database is stale

This message occurs when there are not enough usable replicas for the state database to be able to update records in the database. All accesses to the metadevice driver will fail. To fix this problem, add more replicas or delete inaccessible replicas.

trans device: read error on dnum
trans device: write error on dnum

A read or write error has occurred on the specified logging or master device at the specified metadevice. This happens if any read or write errors occur on a logging or master device.

trans device: read error on dev
trans device: write error on dev

A read or write error has occurred on the specified logging or master device at the specified device name. This happens if any read or write errors occur on a logging or master device.

trans device: read error on dev(num, num)
trans device: write error on dev(num, num)

A read or write error has occurred on the specified logging or master device at the specified device number. This happens if any read or write errors occur on a logging or master device.

logging device: dnum changed state to state
logging device: dev changed state to state
logging device: dev(num, num) changed state to state

The logging device and its associated master device(s) have changed to the specified state(s).

Panic Log Messages

State database problem

A failed metadevice state database commit or deletion has been retried the default 100 times.

dnum: Unknown close type
dnum: Unknown open type

A metadevice is being opened/closed with an unknown open type (OTYP).

DiskSuite Command Line Messages

This part of this appendix contains the error and log messages displayed by the command-line metadevice utilities of DiskSuite.

Errors that deal with command usage and other simple error messages are not documented in this appendix. All DiskSuite command line error messages are displayed in the following format:

program name:    host:    [optional1:]    name:    [optional2]:
error message...

where:

program name: is the name of the application name and version being used (for example, DiskSuite 4.2.1).
host: is the host name of the machine on which the error occurred (for example, blue).
[optional1]: is an optional field containing contextual information for the specific error displayed for example. mountpoint or which daemon returned the error).
name: is the command name which generated the error message (for example, metainit).
[optional2]: is a second optional field containing additional contextual information for the specific error displayed
error message... is the error message itself (as listed in this appendix).

For the purpose of this appendix, only the final portion (error message...) of each error message is listed.

The log messages listed near the back of this appendix are divided into three categories:

Notice log messages
Warning log messages
Panic log messages

Error Messages

The command line error messages displayed by DiskSuite are listed in alphabetical order below. The message is preceded by some or all of the variables described in the previous section. Other variables included in these messages indicate the following:

nodename is the name of a specific host.
drivename is the name of a specific drive.
metadevice is the number of a specific metadevice device or hot spare pool.
setname is the name of a specific diskset.
num is a number.

add or replace failed, hot spare is already in use

The hot spare that is being added or replaced is already in the hot spare pool.

administrator host nodename can't be deleted, other hosts still in
set. Use -f to override

The host which owns the diskset cannot be deleted from the diskset without using the -f option to override this restriction. When the -f option is used, all knowledge of the diskset is removed from the local host. Other hosts within the diskset are unaware of this change.

administrator host nodename deletion disallowed in one host admin
mode

The administrator host is the host which has executed the command. This host cannot be deleted from the diskset if one or more host in the diskset are unreachable.

already has log

The specified trans metadevice already has an attached logging device.

already used in metadevice

The specified component is currently being used in the metadevice.

attempt to detach last running submirror

An attempt was made to detach the last submirror. The operation would result in an unusable mirror. DiskSuite does not allow a metadetach to be performed on the last submirror.

attempt an operation on a submirror that has erred components

An attempt was made to take a submirror offline or detach a submirror that contains the data. The other submirrors have erred components. If this operation were allowed, the mirror would be unusable.

attempt an operation on a submirror in illegal state

An attempt was made to take a submirror offline that is not in the OKAY state or to online a submirror that is not in the offlined state. Use the -f option if you really need to offline a submirror that is in a state other than OKAY.

attempt to replace a component on the last running submirror

An attempt was made to replace a component in a one-way mirror.

attempted to clear mirror with submirror(s) in invalid state

The user attempted to use the metaclear command on a metamirror that contained submirrors that weren't in the OKAY state (Needs maintenance state). If the metamirror must be cleared, the submirrors must also be cleared. Use -r (recursive) to clear all the submirrors, or use -f (force) to clear a metamirror containing submirrors in the Needs maintenance state.

can't attach labeled submirror to unlabeled mirror

An attempt was made to attach a labeled submirror to an unlabeled mirror. A labeled metadevice is a device whose first component starts at cylinder 0. To prevent the submirror's label from being corrupted, DiskSuite does not allow labeled submirrors to be attached to unlabeled mirrors.

can't find component in unit

An attempt was made to replace or enable a component that did not exist in the specified metadevice.

can't find submirror in mirror

An attempt was made to either metaonline(1M), metaoffline(1M), or metadetach(1M) the submirror, dnum. The submirror is not currently attached to the specified metamirror causing the command to fail.

can't include device dev, it already exists in dnum

An attempt was made to use the device dev in a new metadevice and it already is used in the metadevice dnum.

can't include device dev, it overlaps with a device in dnum

The user has attempted to use device dev in a new metadevice which overlaps an underlying device in the metadevice, dnum.

cannot delete the last database replica in the diskset

An attempt was made to delete the last database replica in a diskset. To remove all database replicas from a diskset, delete all drives from the diskset.

cannot enable hotspared device

An attempt was made to perform a metareplace -e (enable) on an underlying device which is currently hot spared. Try enabling the hot spare component instead.

can't modify hot spare pool, hot spare in use

An attempt was made to modify the associated hot spare pool of a submirror, but the submirror is currently using a hot spare contained within the pool.

checksum error in mddb.cf file

The /etc/lvm/mddb.cf file has probably been corrupted or user-edited. The checksum this file contains is currently invalid. To remedy this situation: delete the mddb.cf file, delete a database replica, and add back the database replica.

component in invalid state to replace \
     - replace "Maintenance" components first

An attempt was made to replace a component that contains the only copy of the data. The other submirrors have erred components. If this operation were allowed, the mirror would be unusable.

data not returned correctly from disk

After a replica of the state database is first created, it is read to make sure it was created correctly. If the data read does not equal the data written this message is returned. This results from unreported device errors.

device not in set

An attempt was made to use a component for a shared metadevice or shared hot spare pool whose drive is not contained within the diskset.

device in shared set

An attempt was made to use a component for a local metadevice or local hot spare pool whose drive is contained within the diskset. The drives in the local diskset are all those which are not in any shared disksets.

device is too small

A component (dev) in stripe num is smaller than the interlace size specified with the -i flag in the md.tab file.

device size num is too small for metadevice database replica

An attempt was made to put a database replica on a partition that is not large enough to contain it.

devices were not RAIDed previously or are specified in the wrong
order

An attempt was made to metainit a RAID device using the -k option. Either some of the devices were not a part of this RAID device, or the devices were specified in a different order than they were originally specified.

drive drivename is in set setname

An attempt was made to add the drive drivename to a diskset which is already contained in the diskset setname.

drive drivename is in use

An attempt was made to add the drive drivename to a diskset, however a slice on the drive is in use.

drive drivename is not common with host nodename

An attempt was made to add the drive drivename to a diskset, however, the device name or device number is not identical on the local host and the specified nodename; or the drive is not physically connected to both hosts.

drive drivename is not in set

An attempt was made to delete the drive drivename from a diskset and the diskset does contain the specified drive.

drive drivename is specified more than once

The same drive (drivename) was specified more than once in the command line.

driver version mismatch

The utilities and the drivers are from different versions of the DiskSuite package. It is possible that either the last DiskSuite package added did not get fully installed (try running pkgchk(1M)), or the system on which DiskSuite was recently installed has not been rebooted since the installation.

failed to take ownership of a majority of the drives

Reservation of a majority of the drives was unsuccessful. It is possible that more than one host was concurrently attempting to take ownership of the same diskset. One host will succeed, and the other will receive this message.

growing of metadevice delayed

The attempted growth of a submirror has been delayed until a mirror resync finishes. The metamirror will be grown automatically upon completion of the resync operation.

has a metadevice database replica

An attempt was made to use a component (i.e., for a hot spare) which contains a database replica.

host nodename already has a set numbered setnumber

An attempt was made to add a host nodename to a diskset which has a conflicting setnumber. Either create a new diskset with both hosts in the diskset, or delete one of the conflicting disksets.

host nodename already has set

An attempt was made to add a host nodename to a diskset which has a different diskset using the same name. Delete one of the disksets and recreate the diskset using a different name.

host nodename does not have set

An attempt was made to delete a host or drive from a set, but the host nodename has an inconsistent view of the diskset. This host should probably be forcibly (-f) deleted.

host nodename is already in the set

An attempt was made to add a host nodename which already exists within the diskset.

host nodename is modifying set - try later or restart rpc.metad

Either an attempt was made to perform an operation on a diskset at the same time as someone else, or a previous operation dropped core and the rpc.metad daemon should be restarted on host nodename.

host nodename is not in the set

An attempt was made to delete the host nodename from a diskset which does not contain the host.

host nodename is specified more than once

The same host (nodename) was specified more than once in the command line.

host name nodename is too long

The name used for the host nodename is longer than DiskSuite accepts.

hotspare doesn't exist

An attempt was made to perform an operation on the hot spare dev and the specified hot spare does not exist.

hotspare in use

An attempt was made to perform an operation on the hot spare dev and the specified hot spare is in use.

hotspare isn't broken, can't enable

An attempt was made to enable a hot spare that is not in the broken state.

hotspare database create failure

An attempt to create a hot spare record in the metadevice state database failed. Run metadb -i to determine the cause of the failure.

hotspare pool database create failure

An attempt to create a hot spare pool record in the metadevice state database failed. Run metadb -i to determine the cause of the failure.

hotspare pool is busy

An attempt was made to delete the hot spare pool hspnnn before removing all the hot spares associated with the specified hot spare pool.

hotspare pool is referenced

An attempt was made to delete the hot spare pool, hspnnn, that is associated with a metadevice.

hotspare pool in use

An attempt was made to metaclear(1M) a hotspare pool without first removing its association with metadevices.

hotspare pool is already setup

An attempt was made to create a hot spare pool which already exists.

illegal option

An attempt was made to use an option which is not valid in the context of the specified metadevice or command.

in Last Erred state, errored components must be replaced

An attempt was made to replace or enable a component of a mirror in the "Last Erred" state when other components are in the "Erred" state. You must first replace or enable all of the components in the "Erred" state.

invalid RAID configuration

An invalid RAID device configuration entry was supplied to metainit, either from the command line or via the md.tab file.

invalid argument

An attempt was made to use an argument which is not valid in the context of the specified metadevice or command.

invalid column count

An invalid RAID configuration entry was supplied to metainit, either from the command line or via the md.tab file. Specifically, an invalid argument was provided with the -o option.

invalid interlace

An unsupported interlace value follows the -i option on a metadevice configuration line. The -i specifies the interlace size. The interlace size is a number (8, 16, 32) followed by either -k for kilobytes, -m for megabytes, or -b for blocks. The units can be either uppercase or lowercase. This message will also appear if the interlace size specified is greater than 100 Mbytes.

invalid mirror configuration

An invalid mirror configuration entry was supplied to metainit, either from the command line or via the md.tab file.

invalid pass number

An attempt was made to use a pass number for a mirror that is not within the 0 - 9 range.

invalid stripe configuration

An invalid stripe configuration entry was supplied to metainit, either from the command line or via the md.tab file.

invalid trans configuration

An invalid trans configuration entry was supplied to metainit, either from the command line or via the md.tab file.

invalid write option

An attempt was made to change the write option on a mirror using an invalid option. The legal strings are "serial" and "parallel."

invalid hotspare pool

The metadevice configuration entry in the md.tab file has a -h hspnnn and a metainit has not been performed on the hot spare pool.

invalid read option

The user has specified both the -r and -g options on the same metamirror.

invalid unit

The metadevice (submirror) passed to metattach is already a submirror. The metadevice may already be a submirror for another metamirror.

is a metadevice

The device dev being used is a metadevice and it should be a physical component.

is mounted on

The device dev in the metadevice configuration has a file system mounted on it.

hostname is not a nodename, but a network name

An attempt was made to add a host to a diskset without using the nodename found in the /etc/nodename file.

is swapped on

The device in the metadevice configuration is currently being used as a swap device.

maximum number of nodenames exceeded

An attempt was made to add more nodenames than DiskSuite allows in a diskset.

maxtransfer is too small

An attempt was made to add a component to a RAID device whose maxtransfer is smaller than the other components in the RAID device.

metadevice in use

An attempt was made to metaclear(1M) a submirror without first running metaclear on the metamirror in which it is contained.

metadevice is open

The metadevice (submirror) passed to metattach is already open (in use) as a metadevice.

num1 metadevice database replicas is too many; the maximum is num2

An attempt was made to add more databases (num1) than the maximum allowed (num2).

metadevice database has too few replicas, can't create new
records

An attempt to create a metadevice record in the metadevice state database failed. Run metadb -a to add more database replicas.

metadevice database is full, can't create new records

An attempt to create a metadevice record in the metadevice state database failed. Run metadb -a (and -s) to add larger database replicas. Then delete the smaller replicas.

metadevice database replica exists on device

An attempt was made to use a component (that is, for a hot spare) which contains a database replica.

metadevice is temporarily too busy for renames

An attempt was made to rename a metadevice that is open. An open metadevice is either mounted on, swapped on, or being used as the raw device by an application or database. To rename the metadevice, first make sure it is not open. This error can also appear if the -f option is not used when switching trans metadevice members, or when trying to switch trans metadevice members with a logging device still attached.

mirror has maximum number of submirrors

An attempt was made to attach more than the supported number of submirrors. The maximum supported number of submirrors is three.

must be owner of the set for this command

An attempt was made to perform an operation on a diskset or a shared metadevice on a host which is not the owner of the diskset.

must have at least 2 databases (-f overrides)

An attempt was made to delete database replicas, reducing the number of database replicas to a number less than two. To override this restriction, use the -f option.

must replace errored component first

no available set numbers

An attempt was made to create more disksets than DiskSuite allows.

no hotspare pools found

An metahs operation was attempted using the "-all" argument when no hot spare pools meet the criteria for the operation.

no metadevice database replica on device

An attempt was made to delete non-existent database replicas.

no such set

An attempt was made to perform an operation on a diskset or a shared metadevice using a non-existent set name.

nodename of host nodename creating the set must be included

An attempt was made to create a diskset on the local host without adding the name of the local host to the diskset.

not a disk device

The component name specified is not a disk device name. For example, a CD-ROM device doesn't have the characteristics of a disk device.

not enough components specified

An invalid stripe configuration entry was supplied to metainit, either from the command line or via the md.tab file.

not enough stripes specified

Invalid stripe configuration entry was supplied to metainit, either from the command line or via the md.tab file.

not enough submirrors specified

Invalid mirror configuration entry was supplied to metainit, either from the command line or via the md.tab file.

not in local set

An attempt was made to create a local metadevice or local hot spare pool with a component whose drive is contained in a shared diskset.

not a metadevice

The specified device is not a metadevice. DiskSuite expected a metadevice name.

only slice 7 is usable for a diskset database replica

An attempt was made to add a database replica for a shared diskset on a component other than Slice 7.

only the current owner nodename may operate on this set

An attempt was made to perform an operation on a diskset or a shared metadevice on a host which is not the owner of the diskset.

only valid action is metaclear

The initialization of a RAID device has failed. Use the metaclear command to clear the RAID device.

operation would result in no readable submirrors

An operation was attempted on a component or submirror that contains the only copy of the data. The other submirrors have erred components. If this operation were allowed, the mirror would be unusable.

operation requires -f (force) flag

Due to the components within the RAID device being in the "Maintenance" or "Last Erred" state, the force flag (-f) is required to complete the operation.

overlaps with device in metadevice

Overlapping slices are not allowed in metadevices or hot spare pools.

replace failure, new component is too small

An attempt to use metareplace failed because the new component is too small to replace the old component.

reserved by another host

An attempt was made to add a currently reserved drive to a diskset.

resync in progress

The mirror operation failed because a resync is being performed on the specified metamirror. Retry this operation when the resync is finished.

rpc.metad: permission denied

The user does not have permission to run a remote process on the other systems in the diskset. The remote access permissions need to be set up.

set setname is out of date - cleaning up - take failed

The diskset setname is out of data with respect to the other host's view. This error should occur only after one-host administration.

set lock failed - bad key

Either another DiskSuite command is running and has locked the diskset or a DiskSuite command has aborted without unlocking the diskset on one of the hosts in the diskset. Check to see if there are other DiskSuite commands running on the hosts in the diskset. Check all the hosts and allow other commands to complete on all hosts before retrying the failed command. If the error message appears when no other DiskSuite commands are running, kill and restart rpc.metad on all the hosts in the diskset. Make sure rpc.metad is running on all the hosts before trying the command again.

set name contains invalid characters

An attempt was made to use illegal characters to name a diskset.

set name is in-use or invalid on host nodename

The diskset name selected is already in use on host nodename or contains characters not considered valid in a diskset name.

set name is too long

An attempt was made to create a diskset using more characters in the diskset name than DiskSuite will accept.

set unlock failed - bad key

The diskset is locked and the user does not have the key. Either another DiskSuite command is running and has locked the diskset or a DiskSuite command has aborted without unlocking the diskset on one of the hosts in the diskset. Check to see if there are other DiskSuite commands running on the hosts in the diskset. Check all the hosts and allow other commands to complete before retrying the failed command. If the error message appears when no other DiskSuite commands are running, kill and restart rpc.metad on all the hosts in the diskset. Make sure rpc.metad is running on all the hosts before trying the command again.

side information missing for host nodename

The diskset is incomplete. Kill rpc.metad on all hosts and then retry the operation.

slice 7 is not usable as a metadevice component

An attempt was made to use Slice 7 in a shared metadevice or shared hot spare pool. Slice 7 is reserved for database replicas only.

submirror too small to attach

The metadevice passed to metattach is smaller than the metamirror to which it is being attached.

stale databases

The user attempted to modify the configuration of a metadevice when at least half the metadevice state database replicas were not accessible.

syntax error

An invalid metadevice configuration entry was provided to metainit from the command line or via the md.tab file.

target metadevice is not able to be renamed

An attempt was made to switch metadevices that do not have a child-parent relationship. For example, you cannot rename a trans metadevice with a stripe that is part of a mirrored master device for the trans.

there are no existing databases

To create any metadevices or hot spare pools, database replicas must exist. See metadb(1M) for information on the creation of database replicas.

unable to delete set, it still has drives

An attempt was made to delete the last remaining host from a diskset while drives still exist in the diskset.

unit already set up

The user requested that a metadevice dnum be initialized when dnum is already set up.

unit is not a concat/stripe

An attempt was made to perform a concat/stripe specific operation on a metadevice that is not a concat/stripe.

unit is not a mirror

An attempt was made to perform a mirror specific operation on a metadevice that is not a mirror.

unit is not a RAID

An attempt was made to perform a RAID specific operation on a metadevice that is not a RAID device.

unit is not a trans

An attempt was made to perform a metatrans specific operation on a metadevice that is not a metatrans device.

unit not found

An attempt was made to perform an operation on a non-existent metadevice.

unit not set up

An attempt was made to perform an operation on a non-existent metadevice.

waiting on /tmp/.mdlock

Some other metadevice utility is currently in progress and the lock cannot be accessed at this time. DiskSuite utilities are serialized using the /tmp/.mdlock file as a lock. If you determine that there are no other utilities currently running, you may want to remove this lock file.

Log Messages

The command line log messages displayed by DiskSuite are listed in alphabetical order below. Each message is always preceded with "md:" The variables in these messages indicate the following:

dev is a device name.
dnum is a metadevice name.
num is a number.
state is a metatrans device state.
trans is either "logging" or "master."

Note -

When the initial portion of a message begins with a variable, the message is alphabetized by the first word following the variable.

Notice Log Messages

Could not load misc /dev

The named misc module is not loadable. It is possibly missing, or something else has been copied over it.

db: Parsing error on `dev'

The set command in /etc/system for the mddb.bootlist<number> is not in the correct format. Run metadb -p to place the correct set commands into the /etc/system file.

dnum: Hotspared device dev with dev

The first device name listed has been hot spare replaced with the second device name listed.

dnum: Hotspared device dev(num, num) with dev(num, num)

The first device number listed has been hot spare replaced with the second device number listed.

dnum: no mem for property dev

Memory could not be allocated in the prop_op entry point.

Warning Log Messages

dnum: Cannot load dev driver

The underlying named driver module is not loadable (for example, sd, id, xy, or a third-party driver). This could indicate that the driver module has been removed.

Open error of hotspare dev
Open error of hotspare dev(num, num)

The named hot spare is not openable, or the underlying driver is not loadable.

dnum: read error on dev
dnum: write error on dev

A read or write error has occurred on the specified metadevice at the specified device name. This happens if any read or write errors occur on a metadevice.

dnum: read error on dev(num, num)
dnum: write error on dev(num, num)

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.

dnum: read error on dnum
dnum: write error on dnum

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.

State database commit failed
State database delete failed

These messages occur when there have been device errors on components where the state database replicas reside. These errors only occur when more than half of the replicas have had errors returned to them. For example, if you have three components with state database replicas and two of the components report errors, than these errors may occur. The state database commit or delete is retried periodically. If the replica is added, the commit or delete will finish and the system will be operational. Otherwise, the system will time out and panic.

State database is stale

trans device: read error on dnum
trans device: write error on dnum

A read or write error has occurred on the specified logging or master device at the specified metadevice. This happens if any read or write errors occur on a logging or master device.

trans device: read error on dev
trans device: write error on dev

A read or write error has occurred on the specified logging or master device at the specified device name. This happens if any read or write errors occur on a logging or master device.

trans device: read error on dev(num, num)
trans device: write error on dev(num, num)

A read or write error has occurred on the specified logging or master device at the specified device number. This happens if any read or write errors occur on a logging or master device.

logging device: dnum changed state to state
logging device: dev changed state to state
logging device: dev(num, num) changed state to state

The logging device and its associated master device(s) have changed to the specified state(s).

Panic Log Messages

State database problem

A failed metadevice state database commit or deletion has been retried the default 100 times.

dnum: Unknown close type
dnum: Unknown open type

A metadevice is being opened/closed with an unknown open type (OTYP).