Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Define\s+path\s+problems\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Define\s+path\s+problems\s*$/: 18 ]

Total 18 documents matching your query.

1. [ADSM-L] define path problems (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Thu, 26 Mar 2009 09:42:02 -0500; TSM server 5.3.4 on windows 2K server. Overland Neo 4100 LTO2 library with 2 x LTO2 drives conected via SCSI 320. We recently replaced both LTO2 drives in the library, as well as the SCSI HBA. The dr; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00409.html (14,852 bytes)
2. Re: [ADSM-L] define path problems (score: 1): Author: "Dennis, Melburn (IT Solutions US)" <melburn.dennis AT SIEMENS DOT COM>; Date: Thu, 26 Mar 2009 10:55:42 -0400; ANR8466E command: Invalid update request for drive drive name in library library name. Explanation: An invalid update request has been made for the given drive. This can occur if a new device name is; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00410.html (16,486 bytes)
3. Re: [ADSM-L] define path problems (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Thu, 26 Mar 2009 10:06:48 -0500; Thank you Mel. Alex ANR8466E command: Invalid update request for drive drive name in library library name. Explanation: An invalid update request has been made for the given drive. This can occur if; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00411.html (16,794 bytes)
4. Re: [ADSM-L] define path problems (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Thu, 26 Mar 2009 11:33:23 -0500; I'm having another problem and could use more help. I've got lots of tapes in the library with lots of data on them, and they do seem to be defined and ready to go: tsm: ITG-TSM>q libv Library Name V; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00412.html (18,880 bytes)
5. Re: [ADSM-L] define path problems (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 26 Mar 2009 14:02:26 -0400; One clue is that since I replaced the drives (delete drives, update library path, define drives, define drive paths) the new drives are showing up as a new device type GENERICTAPE1: That could be a; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00415.html (13,961 bytes)
6. Re: [ADSM-L] define path problems (score: 1): Author: "Dennis, Melburn (IT Solutions US)" <melburn.dennis AT SIEMENS DOT COM>; Date: Thu, 26 Mar 2009 14:07:31 -0400; It looks like you need to reinstall the drivers for the new drives. Your OS is seeing the drives, but TSM needs specific drivers for them to be associated as LTO class devices. If they are IBM drives; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00416.html (21,426 bytes)
7. Re: [ADSM-L] define path problems (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Thu, 26 Mar 2009 14:39:00 -0500; Well, we have HP drives that came with the Overland Neo 4100 library. Any idea where to get the HP drivers for LTO2 drives? I've looked on HP's website and can only find the Windows drivers, not TSM.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00417.html (23,001 bytes)
8. Re: [ADSM-L] define path problems (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Thu, 26 Mar 2009 13:41:11 -0600; You use the IBM TSM driver for HP drives, not the IBM drivers or the HP drivers... Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00418.html (23,870 bytes)
9. Re: [ADSM-L] define path problems (score: 1): Author: Kelly Lipp <lipp AT STORSERVER DOT COM>; Date: Thu, 26 Mar 2009 13:44:12 -0600; When you put the new drives in the library, Device Manager found them. You will need to right click on each drive and update the driver to use the TSM driver. The HP driver probably bound to the driv; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00419.html (24,189 bytes)
10. Re: [ADSM-L] define path problems (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 26 Mar 2009 15:44:00 -0400; Well, we have HP drives that came with the Overland Neo 4100 library. Any idea where to get the HP drivers for LTO2 drives? I've looked on HP's website and can only find the Windows drivers, not TSM; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00420.html (13,351 bytes)
11. Re: [ADSM-L] define path problems (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Fri, 27 Mar 2009 09:27:59 -0500; Totally, this was the problem. In the TSM management interface, I right clicked on the device drivers -> properties, and as Kelly mentioned, TSM was being instructed to use windows drivers. That was; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-03/msg00429.html (23,976 bytes)
12. [ADSM-L] Define path problems (score: 1): Author: Chris McKay <Chris.McKay AT YCDSB DOT CA>; Date: Tue, 12 Jun 2007 08:25:14 -0400; Hi All, I am having problems with replacing a SCSI LTO tape drive in my 3584 library. Usually a routine procedure, but this time I am having major difficulties. Whenever I try to redefine the path fo; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00186.html (12,063 bytes)
13. Re: [ADSM-L] Define path problems (score: 1): Author: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>; Date: Tue, 12 Jun 2007 14:42:06 +0200; Hi, By any change has there been a hardware change? - delete drive from ITSM config, - reboot Windows - define drive serial=autodetect - define path to drive Regards, Karel --Original Message-- From:; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00187.html (12,837 bytes)
14. Re: [ADSM-L] Define path problems (score: 1): Author: Chris McKay <Chris.McKay AT YCDSB DOT CA>; Date: Tue, 12 Jun 2007 08:48:33 -0400; We did recently update the firmware on both the library, and the drives, also updated the changer and tape device drivers on the server as well. ______________________________________________ This me; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00188.html (13,790 bytes)
15. Re: [ADSM-L] Define path problems (score: 1): Author: Doug Fox <dugfox AT GMAIL DOT COM>; Date: Tue, 12 Jun 2007 09:13:41 -0400; It sounds like the serial information to me. Did you try the serial=autodetect when defining it? I had to do this the last time I added some LTO3 drives. We did recently update the firmware on both t; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00191.html (13,880 bytes)
16. Re: [ADSM-L] Define path problems (score: 1): Author: Chris McKay <Chris.McKay AT YCDSB DOT CA>; Date: Tue, 12 Jun 2007 09:15:08 -0400; Yes, I tried both serial and element=autodetect ______________________________________________ This message is for the sole use of the intended recipients and may contain confidential and privileged; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00192.html (15,426 bytes)
17. Re: [ADSM-L] Define path problems (score: 1): Author: Chris McKay <Chris.McKay AT YCDSB DOT CA>; Date: Tue, 12 Jun 2007 14:09:06 -0400; Just an update for this issue. The problem has been resolved. It seems like it was a library firmware issue. The fix was to downgrade the firmware to version 5770. The replaced drive then updated pro; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00207.html (16,170 bytes)
18. Re: [ADSM-L] Define path problems (score: 1): Author: Doug Fox <dugfox AT GMAIL DOT COM>; Date: Tue, 12 Jun 2007 15:47:28 -0400; good to know thanks! Just an update for this issue. The problem has been resolved. It seems like it was a library firmware issue. The fix was to downgrade the firmware to version 5770. The replaced d; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2007-06/msg00209.html (15,862 bytes)

Current List: 1 - 18
Page: [1]