STATUS CODE: 86, Backup fails with exit status 86 Media Position Error. Problem log shows: ioctl (MTBSF) failed on media id <mediaID>, drive index <drive index number>, Inappropriate ioctl for device (bptm.c.<process id>)

Problem

STATUS CODE: 86, Backup fails with exit status 86 Media Position Error. Problem log shows: ioctl (MTBSF) failed on media id , drive index , Inappropriate ioctl for device (bptm.c.)

Error Message

media position error

Solution

Overview:
The Solaris tape driver has built-in support for many different drive types. There are a number of ways to determine if a drive is supported on the driver. If a drive is not natively supported within the Operating System patch level, then the drive vendor will need to supply the correct configuration settings for the device.

Troubleshooting:
If the drive is NOT natively supported, verify that the data-property-name line in the /kernel/drv/st.conf file has the correct number of entries.  The line syntax should be:
<data-property-name> = <version>, <type>, <bsize>, <options>, <number of densities>, <density> [, <density>*], <default-density>;

For example:
STK9840 = 1,0x36,0,0x1d639,1,0x00,0;
                                  ^
                                  | fields are separated by "," .  The 4th field is options.

The options field is where MTBSF (device support for backspace over EOF marks) is set as well as other device options.  (See the Solaris man page on st for more information on device option settings.)  

Log Files: N/A

Resolution:
Ensure that the st.conf entry for the device is properly formatted and make any necessary corrections.  Whatever value is in the 4th field is interpreted as the device options.  

For example, if the data-property-name in st.conf was:
STK9840 = 1,0x36,0x1d639,1,0x00,0;
then options would be read as 1 which is an "inappropriate ioctl for device" instead of the intended value of 0x1d639.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)