ProLiant Servers (ML,DL,SL)
1748112 Members
3506 Online
108758 Solutions
New Discussion юеВ

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

 
Ayman Altounji
Valued Contributor

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

My 4 Servers: DL360 2 X 800 P-III, 1.5 Gb RAM, 2X 9 Gb HD, WIN2000 Server ( 5.0.2195 + SP1 Build 2195).
The error in System event viewer is:
Source: cpqarry2, Event ID: 15, Description:
The device, \Device\Scsi\cpqarry21, is not ready for access yet.
:-((
12 REPLIES 12
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

There is no resolution at this time. Please call the Customer Support Center and have a case opened for possible escalation .
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

I am having this same problem. Has this issue been resolved to date? Are there any settings that can be configured in the array utility software that will prevent this error?
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

Hi , i am also having the same problem.. is there any updates from Compaq..?
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

......Also the same problem. Please can you give feedback of the status of the problem?
Tx
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

Any new news on this error?
Ayman Altounji
Valued Contributor

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

is it fixed?
Ra├║l Salcedo
New Member

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

I'm having same problem, some solution at this time?
Rob Meyer
New Member

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

please escalate!
Michael D. Davis
New Member

Re: The device, \Device\Scsi\cpqarry21, is not ready for access yet.

I am also having this issue. Is anyone working on resolving this issue?