VMware Cloud Community
ChesterB
Contributor
Contributor

The device, \Device\Scsi\vmscsi1, is not ready for access yet.

Good Day Experts!

I have a Guest Windows 2003 Box running Backup Exec 2010. Backup up to an HP Autoloader (HP 1/8 Ultrium 960 Tape Autoloader). This is on ESXi 3.5 Host. I am having issues with backups in that if i use verification on the jobs they will fail. I have removed verify now and have a different issue in that one or two jobs may run ok but randomly they will start to fail.

After the job fails and theres nothing running the media will still be "In Use" under devices. Even though on the Autoloader itself its "ready". Only way i can get it to reset the status is to reboot the server. Once the server comes up i get the following errors popping up in the windows event log:

Event Type: Error

Event Source: vmscsi

Event Category: None

Event ID: 15

Date: 24/06/2010

Time: 16:16:23

User: N/A

Computer: SERVER_NAME

Description:

The device, \Device\Scsi\vmscsi1, is not ready for access yet.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 0f 15 18 00 01 00 6e 00 ......n.

0008: 00 00 00 00 0f 00 04 c0 .......À

0010: 03 01 00 00 a3 00 00 c0 ....£..À

0018: dd 0d 00 00 00 00 00 00 Ý.......

0020: 00 00 00 00 00 00 00 00 ........

0028: 00 00 00 00 02 00 00 00 ........

0030: 00 00 00 00 28 00 00 00 ....(...

0038: 07 00 00 00 04 00 00 00 ........

Now, I have read conflicting things around the BUSLogic and LSI SCSI - But which one should i be using? The SCSI Controller is connected to the Autoloader only. See Attachment. Could this be causing the above issue?

Tags (1)
Reply
0 Kudos
1 Reply
FranckRookie
Leadership
Leadership

Hi Chester,

It is recommended to use LSI disk controller for a Windows 2003 server on ESX 3.5.

To check if it can solve your problem (before changing the controller model), you can try to add a second controller and attach your physical autoloader to it.

Hope it helps

Regards

Franck

Reply
0 Kudos