Device not ready

The technical support forum for Firestreamer (the virtual tape library).
Locked
timr88
Posts: 3
Joined: 16 Jun 2016, 13:22

Device not ready

Post by timr88 » 28 Jun 2016, 16:31

Hi
I have installed Firestreamer 4.0.1 and have created Library 1 with 1 tape drive and 10 storage slots.

In the Media view I can see Element number 1 and have created a file medium and see the .fsrm file listed. It is also shown in the Current State view with a barcode assigned.

i am trying to simulate a backup within Yosemite Server Backup, and I can see the CRSTLINK FirestrmDriver (3.0.1.0) drive listed, but whenever I try to back up to or interact with the drive I get the following error that the tape device is not ready:

Error Description The device is not ready. Make sure that media is properly inserted into the drive. If the error persists, the device may be bad.
Error Code 4038
Date/Time 06/28/2016 5:29:15 PM
CDB Description REWIND/REZERO
CDB 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Data
SCSI Status 02
Sense Code 0x02/0x3a/0x00
Sense Data 70 00 02 00 00 00 00 0a 00 00 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Firestreamer appears to be running and have media inserted so is there a any reason why I cannot access it?

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Re: Device not ready

Post by jsf » 28 Jun 2016, 22:13

Most backup software has a hard-coded list of tape libraries/drives. The result is that to support a new library/drive the backup software vendor needs to release a new version of their product. Yosemite doesn't seem to be an exception.

If you loaded tape into a slot, then most likely Yosemite cannot recognise Firestreamer as a library, and thus cannot move a tape from a slot to a tape drive; hence "device not ready" from a tape drive.

Try loading tapes into all tape drives (as opposed to slots), and see what happens.

In any case, if there still is a problem, we are unlikely to be able to solve it without Yosemite's co-operation.
Best regards,
John Smith
Cristalink Support

timr88
Posts: 3
Joined: 16 Jun 2016, 13:22

Re: Device not ready

Post by timr88 » 29 Jun 2016, 11:11

Thanks for the help so far

I've changed entry from a storage slot to tape drive and this has allowed the drive to be recognised, however both Backup Exec and Yosemite say there is no media in the drive (although they do now recognise it)

I've attached a screen shot of the media library - does it look like a no go from here?

thanks
Attachments
Untitled.png
Untitled.png (26.37 KiB) Viewed 4404 times

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Re: Device not ready

Post by jsf » 29 Jun 2016, 22:24

The other issue may be that the backup software does not issue periodic TEST UNIT READY or similar commands to check the drive status, while Firestreamer relies on those commands to report its state. After loading tape into the tape drive, try starting a backup 3-4 times in a row, to see whether the drive is eventually detected as ready. By the way, are there any warnings or errors in the Activity view of the Firestreamer Snap-In?

We have not tested Firestreamer with Yosemite Server Backup. As to Backup Exec, Symantec refused to cooperate when we approached them some time ago with an offer to make Backup Exec and Firestreamer compatible. If I was an end user, I wouldn't waste time trying to make those two products work with the current version of Firestreamer.
Best regards,
John Smith
Cristalink Support

timr88
Posts: 3
Joined: 16 Jun 2016, 13:22

Re: Device not ready

Post by timr88 » 30 Jun 2016, 09:55

Hi John,

Thanks for your continuing support. As you suggested I re-tried the backup several times in a row with both Yosemite & Backup Exec (though not at the same time), and I get the following in the last command issued by Yosemite#

Also I have attached the Activity view of Firestreamer which does not appear to show any errors

Error Description The device is not ready. Make sure that media is properly inserted into the drive. If the error persists, the device may be bad.
Error Code 4038
Date/Time 06/30/2016 10:50:47 AM
CDB Description TEST UNIT READY
CDB 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Data
SCSI Status 02
Sense Code 0x02/0x3a/0x00
Sense Data 70 00 02 00 00 00 00 0a 00 00 00 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Attachments
Untitled.png
Untitled.png (30.08 KiB) Viewed 4401 times

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Re: Device not ready

Post by jsf » 07 Jul 2016, 12:21

You can try and create a diagnostic log file, though as I pointed out earlier, it is going to be a pointless exercise. We won't be able to resolve compatibility issues without the backup software vendors' participation.
Best regards,
John Smith
Cristalink Support

Locked