Charles,

Maybe this link will help- it suggests  7.0.0.8 HBA firmware ( a little newer 
than yours.)

http://www-01.ibm.com/support/docview.wss?uid=swg21500578

Richard

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Welton, Charles
Sent: Wednesday, March 20, 2013 8:04 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] ANR8939E The adapter for tape drive (\\.\TapeXX) cannot 
handle the block size needed to use the volume

Hello:

Before I begin, here are the hardware specs of our small TSM environment:

TSM SERVER VERSION: 5.4.2.0
TSM SERVER OS VERSION: Windows Server 2003 R2 Standard Edition TSM SERVER TYPE: 
IBM System x3650 (MEMORY: 4096 MB; CPU: Quad 2.33 GHz Intel Xeon) PHYSICAL TAPE 
LIBRARY: IBM 3576 w/ four tape drives (SCSI attached to TSM server) VIRTUAL 
TAPE LIBRARY: DL210 (fiber attached to TSM server) SCSI ADAPTER: Adaptec SCSI 
Card 29320LPE - Ultra320 SCSI (driver version 7.0.0.6)

I'm not sure what else needs to be mentioned from a hardware configuration 
perspective.  But, today we had someone replace some bad memory in our TSM 
server.  When the system was back up and TSM was up, our standard operating 
procedure is to test both virtual and physical tape mounts by running simple 
"MOVE DATA" commands.  When we tested the virtual tape library, no problems at 
all, but when we tested the physical tape library, we received and continue to 
receive the following error for all four tape drives:

03/20/2013 18:18:20   ANR8939E The adapter for tape drive KSFS0203-DRIVE03
                       (\\.\Tape67<file:///\\.\Tape67>) cannot handle  the 
block size needed to use
                       the volume. (SESSION: 341, PROCESS: 3)

HOWEVER, when we run an incremental TSM database backup, which uses a new 
scratch tape, it works without issue.  Absolutely NOTHING has changed from a 
software/firmware perspective in our TSM environment.  In troubleshooting the 
problem, we completely removed the physical tape library and tape drives from 
an OS and TSM perspective, reconfigured them, but still continue to receive the 
errors.

Has anyone run into this issue before?  Does anyone have any suggestions?

Thanks...


Charles Welton
This email contains information which may be PROPRIETARY IN NATURE OR OTHERWISE 
PROTECTED BY LAW FROM DISCLOSURE and is intended only for the use of the 
addresses(s) named above.  If you have received this email in error, please 
contact the sender immediately.