We have been running MediaStor (5.60.049) successfully since July with a Plasmon M20 jukebox writing to MO media. Since the weekend, (nothing happened except physically moving the server), we haven't been able to bring the Plasmon on line. The message XERR_LIBRARY_DEV_HARDWARE is being returned when attempting this. There is no hardware fault, we have had an engineer confirm this.
The license server is showing as no MediaStor license in use.
We've tried to re-point MediaStor to the license server going through MediaStor set-up, but nothing seems to be working.
Often, hardware vendors hook up their diagnositc utility directly to the hardware, and report that there is no problem. However, this does not take into account the server, the SCSI bus on the server, or the SCSI adapter on the server.
You'll want to check your Windows Event logs, and verify there are no errors for yor SCSI adapter. If you are using an Adaptec 29160, you'll want to look for an error from source 'adpu160m' with an event ID 9, 11 or 15. If you see this, it is an indication that the driver for the SCSI controller needs to be updated.
Fuji - this usually happens becuase of SCSI address. Open Mediastor and view your device and drives. It will show you the scsi assignment next to it. Now, open SCSI Manager (start/programs/mediastor/tools) and see if the addresses match. If not, then you need to add a new plasmon device and assign your drives. Bring it online and see if it appears in DX. If it comes online and your media are available in DX, you can delete your old device listed in Mediastor. Always make sure to backup the registry before doing anything.
Well, that helped...sort of...now Im getting error 16930 (incorrect driver)......I went to dell, got the most recent driver and installed on changer and both drives in device manager....Im kinda lost on the logic now....
mwolfe01
56 Posts
1196
0
Posted October 16th, 2006 07:00
Often, hardware vendors hook up their diagnositc utility directly to the hardware, and report that there is no problem. However, this does not take into account the server, the SCSI bus on the server, or the SCSI adapter on the server.
You'll want to check your Windows Event logs, and verify there are no errors for yor SCSI adapter. If you are using an Adaptec 29160, you'll want to look for an error from source 'adpu160m' with an event ID 9, 11 or 15. If you see this, it is an indication that the driver for the SCSI controller needs to be updated.
Let me know if this helps.
Thanks,
-Mike