I've actually found on some platforms that only bouncing TSm doesn't resolve this. I end up having to reboot to server machine, too. Seems that the OS doesn't scan the SCSI bus and when TSm queries for devices you are getting the 'cached' information from the last bus scan. When I added capacity to a 3583 library, I had to reboot the server to get it recognized. Now when I make changes like that, drive additions/changes, firmware upgrades,... I reboot.
Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Tom Kauffman Sent: Tuesday, August 12, 2003 5:06 PM To: [EMAIL PROTECTED] Subject: Re: 3584 Library issues If you haven't already done so, stop and restart the TSM server. You may also need to run an audit library afterward. Tom Kauffman NIBCO Inc. -----Original Message----- From: Bradberry, Kenneth [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 3:08 PM To: [EMAIL PROTECTED] Subject: 3584 Library issues IBM added two extra drives, since I associated them with the zone on the SAN I have been getting the error below. IBM did have to take slots out of the library to install the two additional drives. Any ideas on how to resolve this issue? Thanks. Ken. ANR8441E Initialization failed for SCSI library LTO1. ANR1404W Scratch volume mount request denied - mount failed. ANR8478W Invalid home slot address in inventory for library LTO1; volume = 00009;slot = 1288. ANR9999D mmsscsi.c(6867): ThreadId<18> Unable to build active slot records for library LTO1. CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
