Source:  SMSDI.NLM

Possible Cause:  SMSDI keeps track of what medium it expects to find in the device. It verifies the medium before executing reads or writes. In this instance, the wrong medium was in the device.

Action:  Put the correct medium into the device, or reselect the current medium from the Storage Device Administration menu item.