Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

testing disksuite failover

Status
Not open for further replies.

csgonan

MIS
May 2, 2007
118
US
I just installed disksuite on a solaris 8 box and I want to force a failover. Anybody have any suggestions or things they have tried?

Thanks
 
I understand that but last time I posted something I got an reply saying "for faster response, this would be better posted in XX group".

Sometimes ya just can't win.
 
Sorry, that was probably me. However, once bitten and all that ;-)

I want to be good, is that not enough?
 
Yeah, that's fine... I got the (possibly incorrect) impression that you were posting subsequent threads in both forums too. No big deal.

Annihilannic.
 
I was testing the removal of the boot disk with the cfgadm command and got the following error. I installed patches 110912-05 and 117702-01 prior to doing this as they were related. Any ideas?? Thanks

Command I entered: cfgadm -c unconfigure c0::dsk/c0t0d0

Error: cfgadm: hardware specific failure: failed to unconfigure SCSI device: I/O error

# cfgadm
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c1 scsi-bus connected unconfigured unknown
# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 disk connected configured unknown
c0::dsk/c0t1d0 disk connected configured unknown
c0::dsk/c0t6d0 CD-ROM connected configured unknown
c1 scsi-bus connected unconfigured unknown

 
I did a little research and saw an article that specifically had this error in it. It indicated:

-------
NOTE: if the message “Hardware specific failure: failed to
unconfigure SCSI device: I/O error” appears, check to make sure that you cleared all replicas and metadevices from the disk, and that the disk is not being accessed
-------

I didn't want to remove all the replicas, etc, since I was just testing. Do you think this is why I couldn't cfgadm? I actually tested by doing an init 0 and reboot (which booted to the second drive, then issue a metareplace for all devices. They seem to be resyncing.

Would the cfgadm -f -s unconfigure worked instead of just the cfgadm -c unconfigure?

Thanks


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top