Video Screencast Help

Win2k3 X64 Media Server LTo4 Drive Problem

Created: 22 Jan 2009 • Updated: 21 May 2010 | 6 comments

Hi

 

I am facing problem in detecting the IBM LTO4 drives by Windows Media Server.

Master Server is 6.5 (Solaris 10)

Media Server is 6.5 (Win2k3 R2 x64 Enterprise Version)

IBM LTO4 Drive vesrion is 6.1.9.9 , I am using the file IBMTape.x64_6199.zip for extracting the Driver.

Applied the patches also , but no success.

In veritas Technote http://seer.entsupport.symantec.com/docs/307868.htm , suggesting driver problem , but I am using the higher version of driver.

Had any body faced such problem

Comments 6 CommentsJump to latest comment

FED_SE's picture

Can the OS see the device(s)? Please send log entry of hardware config.

Brett Hartmann - Federal Account Engineer - DC Metro

Amit Vats's picture

Hi

 

In device Manager I can see the devices , First it comes with yellow mark and after installing the driver , it''s as a normal drive. Media changer also visible.

 

When I run the c:\Program Files\Veritas\volmgr\bin\scan.exe   ----> It shows only the Media Changer , Drives are not visible there. 

FED_SE's picture

Amit,

 

For testing I would back rev the driver the one mentioned in the doc. Are these fiber attached drives. Fiber switch involved? or Direct SCSI connected?  If SCSI check for bent pins/ terminator etc...

 

You'll certainlly want to confirm cabling.

 

Have you logged a case with support?

Brett Hartmann - Federal Account Engineer - DC Metro

Amit Vats's picture

Hi

 

This is a drive from VTL. So , connectivity is not a problem. From same VTL drives are connected to other servers and it's working fine there.

Karthikeyan Sundaram's picture

Did you check by running Configure Storage Devices !

 

 

Thanks, Karthikeyan Sundaram.

Amit Vats's picture

I Had resolved the problem .

Below is the procedure:-

  1. Assigned one drive to the Sstem .
  2. Installed the Latest IBM drivers for X64 win2k3 in non-exclusive Mode.
  3. run the scan using the command line.
  4. Run the device config Wizard at master Server.