Jump to content

jetdog9

Members
  • Content count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jetdog9

  • Rank
    Occasional Forum Poster
  1. It may be worth it to plug the thing into Windows, install HP's Tape Library tools (should be on their website), and see if there is a newer firmware if you believe firmware is the issue here. Aside from that, as the technology is a bit old, it may be worth looking into other hardware options as well.
  2. As noted by people's replies, the fix is in RDU 6.1.14.101. But just FYI it seems there was a strange bug where amount of RAM could cause the auto configuration tool to hang. An odd one, but it is now fixed.
  3. Some info from an HP Autoloader manual: Step 1: Check the SCSI ID Check the autoloader’s SCSI ID on the SCSI ID switch on the rear panel (the number switch on the left). If necessary change it from the default of 5 by pressing the indented + or - buttons above and below the SCSI ID number. Use a ball-point pen or similar pointed object. To prevent particle contamination, do not use a pencil. <4 or 5 should be fine> Step 2: Check the Option Switch Value Check the option switch on the back of the autoloader (the number switch on the right). If connecting to a Sun workstation, change the switch to 5. For any other system, the default setting of 7 is correct. Step 3: Set the Configuration Switches (UNIX Systems Only) page 1-9 Check the UNIX configuration switches in the bottom of the autoloader. Change the switch settings if necessary. This should definitely be working, so if it continues to fail, we'd want to look at a SCSI debug log (that may require contacting support).
  4. Please note also that there was a bug in RDU 7.5.10 through 7.5.13 which may cause DVD-R media to work improperly. This was fixed in RDU 7.5.14.102, which was released 04/01/08.
  5. Here's a fun tidbit: "MATSHITA" is short for Matsushita (pronounced "Matshsushta"), which is essentially the real Japanese company name for Panasonic. They have to abbreviate in the SCSI inquiry string because there's only 8 characters reserved for the Vendor ID string.
  6. Please try the new RDU, version 6.1.14.101 (posted 04/01/08). It fixes bugs related to custom configuration, DVD+RW media, and DVD-R media.
  7. jetdog9

    LTO-2 SCSI Performance

    You should not need to uninstall. Just point to the Adaptec ones. I don't know if you'll get the Windows message about drivers not being signed, etc, but go ahead and proceed even if you do.
  8. Please try RDU 6.1.14.101 which was just released 04/01/08.
  9. jetdog9

    LTO-2 SCSI Performance

    Have you tried drivers from Adaptec's website, not from the Windows CD or Windows Update? This may make a *substantial* difference.
  10. The Optiarc drive is now officially supported (get rid of any rdi file in the Retrospect preferences folder created during custom configuration), and the Pioneer drive should work fine again, with the the new RDU 6.1.14.101 (released 04/01/08). Give that a try.
  11. Getting back to the technical issue at hand, please try the latest RDU, version 6.1.14.101, which was just released. Among other things, it fixes: -an issue where custom configuration may hang -an issue where DVD-R discs cannot be written to -an issue where DVD+RW discs cannot be erased Also I believe the Pioneer DVR-115 is not listed as officially supported, but with the latest RDU you can still try to use the drive without using custom configuration. Get rid of any existing rdi files in the Retrospect Preferences folder, make sure you are using the new RDU, and give either drive (112 or 115) a shot.
  12. As this is not an officially supported drive and you need to run through custom configuration, the drive still might not work. However, RDU 6.1.14.101 which was just released, fixes an issue where custom configuration may hang, and it also fixes an issue where DVD-R media may not work. So try again with the latest RDU (released 04/01/08).
  13. This drive is supported with RDU 6.1.14.101. I would do the following: 1. Remove and rdi files in the Retrospect Preferences folder. 2. Install RDU 6.1.14.101 3. Check to see the drive is recognized without any custom configuration needed
  14. Some bugs regarding DVD-R, DVD-RW, and DVD+RW (DVD+R was always working) have been fixed in RDU 6.1.14.101. DVD drive users should update to this RDU.
  15. For those who are more technically inclined than average users, most times when an error -206 is reported, there is sense data that triggered the error in the operations log. So when the log says: Sense > 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 Byte 2 is the sense key, in this case 05h corresponds to "illegal request" Bytes 12 and 13 are the ASC/ASCQ (additional sense code and additional sense code qualifier), in this case 24h 00h is "invalid field in CDB" So basically 05-24-00 is "illegal request, invalid field in CDB". Translation is basically a command that's not supported was sent. But in the case of hardware failures with optical drives, you'll often see something like 03-11-00 which translates to "medium error, unrecovered read error". Unfortunately, as in this case, the error the drive is reporting is still pretty vague. So you can see why the Retrospect error isn't any clearer. Sense keys and standard ASC/ASCQ errors can be found a www.t10.org.
×