I hope someone can help me here, I have an AMD 1700+ running Suse 9.0 professional. I boot of IDE drives, but I have a Adaptec 29160 Scsi card. The only thing connected is a Quantum DLT4500 5 slot mini dlt tape unit.
I'm using mtx to control the device. mtx -f /dev/sg1 unload mtx -f /dev/sg1 status etc. All the commands work except for one: mtx -f /dev/sg1 load 3 The tape loads and rewinds but sends back an error :; Destination Element 16 already full. and the scsi bus resets. I have posted in quite a few news groups but no success yet, changed cards, change lead, terminators etc. I can read and write to the tape drive no problem... Someone suggested that its the current build of the kernel and the re-complied a new one, but I got scared off at this. Any suggestions: Thanks Dean
Hi Dean, I don't know if you've got the documentation already, but if you Google for "dlt4000_dlt4500_dlt_7000_manual.pdf" (exactly as spelled here) you should find a comprehensive manual for that library subsystem.
From your short description, it seems that if you can read/write to the integrated tape drive, itself, but are having problems with the library functions, this could be something as simple as verifying the SCSI ID of the robotics controller -- which (I think) is separate from the tape drive controller.
HTH
- Carl Thanks, I have the manual but doesn't help me, The device is seen as one scsi id "5" but the drive is lun 0 and the changer is lun 1 I altered the scsi bios to enable multiluns but didn't work. Thanks Dean
Hi Dean, I Googled your error message and came up with the following: ----- "Diagnostics These SCSI sense error messages may display on the console. See messages(M) for general information about kernel error messages, including a list of generic device driver errors. NOTICE: Sjk: Destination Element Full A data medium could not be placed in a given element because that element was already occupied. " [from http://osr5doc.ca.sco.com:457/cgi-bin/man/man?jukebox+HW] ----- - Could it be a physical impediment to the proper placement of the tape cartridge in the desired slot? Sometimes - for safety's sake - only a tiny bit of resistance will cause the robotics to interpret an empty slot as "full." - Could it be a bad/dirty sensor making the unit *think* that "Destination Element 16" is already occupied? And, focusing on this a bit more, why does the error message identify the "full" element as number "16" when this is a five slot library? Parallel to this line of inquiry, why is it calling itself a "barcode" device instead of a tape library? - Does the subsystem successfully pass it's own POST? Somehow, this is starting to look like a configuration/driver issue or, possibly, an isolated fault within the subsystem itself. It certainly looks like you've covered all the h/w basics from the adapter through to the terminator. regards, - Carl - - - - - - - - - - - - - - - - - - - - - - - - - - - C. E. Hartung Business Development & Support Services Dover Foxcroft, Maine, USA http://www. cehartung.com