RE: NEC autoloaders
This is the changer with one SCSI ID for the drive and one SCSI ID for the robot. It essentially has 10 slots, if barcode reader is installed then it drops to 9 slots (slot number 10 is used for reading the barcode). For the LTO version it has the same specs as the DLT drive. There is also an SDLT version. mtx should work with the autoloader, although I haven't personally tested this yet. Tien Ton -Original Message- From: Jay Lessert [mailto:[EMAIL PROTECTED] Sent: 10. juni 2003 19:02 To: Tom Brown Cc: [EMAIL PROTECTED] Subject: Re: NEC autoloaders On Tue, Jun 10, 2003 at 04:38:09PM +0100, Tom Brown wrote: > > Has anyone had any experience using LTO autoloaders from NEC and amanda? > > > > Specifically this one > > > > http://www.nec-cebit.com/products/LL0101H.asp > > if nobisy has had any joy with these autoloaders can anyone recommend a LTO > autoloader to work with amanda that has about 8 tapes? Chances are nobody had ever heard of it before, I hadn't. As far as changers go, if it works with mtx, it will work with Amanda (through chg-zd-mtx). Check out the compatibility list at http://mtx.badtux.org/. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Working with multiple tape drives----- Ammended
Reply With History On the library, sometimes due to transportation (and the library was not "Park" properly), the robot arm tends to miscalculate its "Y" position. That is when you need to re-calibrate. By re-calibrate I meant accessing the menu on the library and manually calibrate. On the units that we (Tandberg Data) sell, there is a special menu where you can select to manually calibrate the robot arm. This menu is NOT for normal user use, therefore its need a combinations of keys presses to make it appeared. What I would suggest for you to do is to get the manual for the library you have, maybe there is a section in there that tell you how to recalibrate. If not then you need to contact the support section. Regards Tien
Re: Working with multiple tape drives----- Ammended
Reply With History >From what you described, the problem is to do with the robotic arm. There is a sensor on the robot arm to tell if it has moved to the right position (either the tape drive or the cartridge slot), all you need to do then is to re-calibrate the robotic arm. Then all should be well again. Gene, sorry if the msg was posted to you, something to do with this stupid Lotus Notes Memo Gene Heskett <[EMAIL PROTECTED]> on 11/09/2002 02:25:14 To: "Quinn, Richard C. - Collinsville IT" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc:(bcc: Tien That Ton/TDASA/TDATA) Subject: Re: Working with multiple tape drives- Ammended On Tuesday 10 September 2002 16:36, Quinn, Richard C. - Collinsville IT wrote: >Hi again, > >I think I've narrowed it down just a spell. >Gene was helpfull with some advice regarding the "tapedev" > variable in amanda.conf. >Unfortunately that didn't seem to fix the issue, which I think MAY > be scsi related and not amanda related. > >In a nutshell the problem is this: >I cannot get the robotic arm to take the tapes in and out of one > of my 2 DLT drives. >I will set up chg-scsi to only configure for one drive(the one > that is being ignored by my robotic arm). >I'll send a chg-scsi -resetcommand and get this error: >0 slot 0 move failed > > > >However, upon issuing the chg-scsi command, the tape drive will > rewind and offline itself, and yes, I can do ufsdumps to the > drive. So, if it is a SCSI problem, I am not sure what or how, > AFAIK, ufsdump and mt rew ultimately issue scsi commands don't > they? > >It doesn't seem to be the drive so much as the arm going to the > drive. > >Just before I get this ''move failed'' error, the robotic arm will > move in front of the drive, then move down an inch, then back up > an inch, then down, and THEN, I get the ''move failed'' error. > > > >Here is a snip of the errors I get in >/tmp/amanda-dbg/chg-scsi-#.debug and /var/adm/messages > respectively: > > > >== >== # START LookupElement ># STOP LookupElement (DTE) ># START LookupElement ># STOP LookupElement (STE) >ioctl on 4 failed, errno 5, ret -1 ># START DecodeSense >SCSI_ExecuteCommand:Sense Keys >ErrorCode 1d >Valid 1 >ASC 90 >ASCQ 10 >Sense key 0F >Reserved >== >== > = >=== > > >Sep 10 14:35:06 sun1 unix: WARNING: /pci@1f,4000/scsi@4,1/sst@0,0 >(sst3): >Sep 10 14:35:06 sun1 unix: Error for Command: 0xa5> Error Level: Fatal >Sep 10 14:35:06 sun1 unix: Requested Block: 0 >Error Block: 0 >Sep 10 14:35:06 sun1 unix: Vendor: STK >Serial Number: >Sep 10 14:35:06 sun1 unix: Sense Key: Illegal Request >Sep 10 14:35:06 sun1 unix: ASC: 0x3a (medium not present), > ASCQ: 0x0, FRU: 0x0 >== >== > > > >Any ideas? > > >Does anyone speak SCSI? Not very well I'm afraid. But an idea is beginning to jell in the back of my mind, and it has to do with SOME drives penchant for assigning the robot (s) to the same address as the drive itself, but to a non zero LUN at that address. Now, AFAIK, the lkernel, when initializing itself, does the device scan, it scans all LUNs at each address on the bus, and is the major reason for a noticable pause in the boot proceedings at that point. Such tomfoolery with the bus address and LUN's is normally recorded in /var/log/dmesg, so please post that section of it, probably not more than 20 lines to this list and let us see what was actually detected and recorded by the kernel at your last bootup. It might be cluefull to one of us here. Since I see references to sun1 and unix in that trace above, defining your system to us may also help, I suspect its not middle of the road linux, but may call for some sun/solaris expertise I don't have. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
Re: Documentation
Reply Hi, I did wrote a short doc on how to install amanda on Linux approx. 7 months ago, and I did post it on this listMaybe it got lost a long the way :-) Tien That Ton
Tape partioning problems - request assistance
Memo Please follow the steps below to determine what is going wrong: 1. Rewind the tape: Command Descriptor block: : 01 00 00 00 00 00 2. Run a mode select to partition the tape into two equal sized partitions: Command Descriptor block: : 15 11 00 00 5C 00 : 00 00 10 08 34 00 00 00 00 00 02 00 11 4E 17 01 0010: 30 01 00 00 27 00 FF FF 00 00 00 00 00 00 00 00 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0050: 00 00 00 00 00 00 00 00 00 00 00 00 3. Run a mode sense to check the partitioning Command Descriptor block: : 1A 00 11 00 FF 00 : 5B 73 10 08 34 00 00 00 00 00 02 00 11 4E 17 01 0010: 30 01 00 00 27 0C 27 0C 00 00 00 00 00 00 00 00 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0050: 00 00 00 00 00 00 00 00 00 00 00 00 Below is my interpretation of the data returned by mode select (page 0x11) Mode Sense Header List -- Medium type: 73 Write protect: 0 Buffered mode: 1 Tape speed: 0 Mode Sense Block Descriptor List Tape density code: 34 Block size: 512 Page code: 0x11 Page Definition: Medium Partition page (1) Maximum number of additional partitions: 23 Additional partitions defined: 1 Partition size units (in MB): 2 Partition <0> Size: 9996 Partition <1> Size: 9996 - At this point, it would appear that the tape is correctly partitioned - 4. Use mode sense to check for the active partition: Command Descriptor block: : 1A 00 10 00 FF 00 : 1B 73 10 08 34 00 00 00 00 00 02 00 90 0E 00 00 0010: 00 00 00 00 70 00 18 00 00 00 00 00 Active Partition: 0 5. Write data to active partition (0) cd /directory1 tar cvf /dev/rct0 . 6. Verify tape contents: tar tvf /dev/rct0 < The data verified correctly > 7. Use the locate command to move to partition #1 (from partition 0) Command Descriptor block: : 2B 02 00 00 00 00 00 00 01 00 8. Use mode sense to check for the active partition: Command Descriptor block: : 1A 00 10 00 FF 00 : 1B 73 10 08 34 00 00 00 00 00 02 00 90 0E 00 01 0010: 00 00 00 00 70 00 18 00 00 00 00 00 Active Partition: 1 -- At this point, it would appear that a write would go to partition #1 I understand that you can also use 'mode select to change active partitions, but based on the data above, it looked like the change to partition #1 worked -- 9. Write data to active partition (1) cd /directory2 tar cvf /dev/rct0 . 10. Use mode sense to check for the active partition: Command Descriptor block: : 1A 00 10 00 FF 00 : 1B 73 10 08 34 00 00 00 00 00 02 00 90 0E 00 00 0010: 00 00 00 00 70 00 18 00 00 00 00 00 Active Partition: 0 -- This puzzles me. Why did the partition revert back to 0?? -- 11. Use the locate command to move to partition #1 (from partition 0) Command Descriptor block: : 2B 02 00 00 00 00 00 00 01 00 12. Use mode sense to check for the active partition: Command Descriptor block: : 1A 00 10 00 FF 00 Active Partition: 1 13. Verify the contents of the tape tar tvf /dev/rct0 < The data verified correctly as directory2 > 14. Verify the active partition Command Descriptor block: : 1A 00 10 00 FF 00 Active Partition: 0 This puzzles me again. Why did the partition revert back to 0?? 15. Verify the data tar cvf /dev/rct0 - The data is the contents of directory2 Summary: - Even though it appears that I can create two partitions (see mode sense 0x11 above), and that I can locate to the correct partition (see mode sense 0x10 above), I can't write data to each partition. - I would suspect that the UNIX driver is forcing partition 0 each time and that I never do write to partition #0?
