Failed To Unconfigure Scsi Device I/o Error
Contents |
Hot-Plugging With the cfgadm Command (Task Map)Next: PCI or PCIe Hot-Plugging With the cfgadm Command (Task Map)SCSI Hot-Plugging With the cfgadm Command This section describes various SCSI hot-plugging procedures that you can perform with the cfgadm command. cfgadm force unconfigure Note – The SCSI framework generally supports hot-plugging of SCSI devices. However, you should cfgadm unconfigure disk consult your hardware documentation to confirm whether hot-plugging is supported for your SCSI devices. These procedures use specific devices as
Cfgadm Command In Solaris
examples to illustrate how to use the cfgadm command to hot-plug SCSI components. The device information that you supply, and that the cfgadm command displays, depends on your system configuration. How to Display Information
Cfgadm: Attachment Point Not Found
About SCSI Devices The following procedure uses SCSI controllers c0 and c1 and the devices that are attached to them in the examples of the type of device configuration information that you can display with the cfgadm command. Note – If the SCSI device is not supported by the cfgadm command, the device does not display in the cfgadm command output. Become superuser. Display information about attachment cfgadm: configuration operation not supported points on the system. # cfgadm -l Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c1 scsi-bus connected configured unknown In this example, c0 and c1 represent two SCSI controllers. Display information about a system's SCSI controllers and their attached devices. # cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 disk connected configured unknown c0::rmt/0 tape connected configured unknown c1 scsi-bus connected configured unknown c1::dsk/c1t3d0 disk connected configured unknown c1::dsk/c1t4d0 unavailable connected unconfigured unknown Note – The cfgadm -l commands displays information about SCSI HBAs but not SCSI devices. Use the cfgadm -al command to display information about SCSI devices such as disk and tapes. How to Unconfigure a SCSI Controller The following procedure uses SCSI controller c1 in the example of unconfiguring a SCSI controller. Become superuser. Unconfigure a SCSI controller. # cfgadm -c unconfigure c1 Verify that the SCSI controller is unconfigured. # cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 disk connected configured unknown c0::rmt/0 tape connected configured unknown c1 scsi-bus connected unconfigured unknown Notice that the Occupant column for c1 specifies unconfigured, indicating that the SCSI bus has no configured occupants. If the unconfigure operat
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z
Cfgadm: Insufficient Condition
Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security luxadm forcelip Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive devfsadm Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training http://docs.oracle.com/cd/E19253-01/817-5093/devconfig2-8/index.html Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support https://support.symantec.com/en_US/article.TECH159840.html Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' The cfgadm unconfigure command fails with "cfgadm: Hardware specific failure: failed to unconfigure SCSI device: I/O error" TECH159840 August 16th, 2011 http://www.symantec.com/docs/TECH159840 Support / The cfgadm unconfigure command fails with "cfgadm: Hardware specific failure: failed to unconfigure SCSI device: I/O error" Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation While trying to remove a device from the OS with cfgadm unconfigure the following error occurs. root# cfgadm -c unconfigure c2::dsk/c2t11d0 cfgadm: Hardware specific failure: failed to unconfigure SCSI device: I/O error root# cfgadm -al|grep c2t11d0 c2::dsk/c2t11d0 disk connected configured unknown Solution First review TECHNOTE312323and follow this recommendation: The cfgadm unconfigure command fails with "Device being used by VxVM". If you are seeingI/O errors instead, you can exclude the the device(s) from dmp.
examples of cfgadm diagnostic messages. (Syntax error messages are not included here.) cfgadm: Configuration administration not supported on this machine cfgadm: hardware component is busy, http://www.shrubbery.net/solaris9ab/SUNWdhshw/806-6783-10/trouble.html try againcfgadm: operation: configuration operation not supported on this machinecfgadm: operation: Data error: error_textcfgadm: operation: Hardware specific failure: error_textcfgadm: operation: Insufficient privilegescfgadm: operation: Operation requires a service interruptioncfgadm: System is busy, http://www.unix.com/unix-for-dummies-questions-and-answers/32609-trying-replace-disk-thats-all.html try againWARNING: Processor number number failed to offline. See the following man pages for additional error message detail: cfgadm(1M) , cfgadm_sbd(1M) , cfgadm_pci(1M) , and config_admin(3X) . Unconfigure Operation failed to Failure An unconfigure operation for a CPU/Memory board or an I/O board can fail if the system is not in a correct state before you begin the operation. CPU/Memory Board Unconfiguration Failures Memory on a board is interleaved across boards before an attempt to unconfigure the board. A process is bound to a CPU before an attempt to unconfigure the CPU. Memory failed to unconfigure remains configured on a system board before you attempt a CPU unconfigure operation on that board. The memory on the board is configured (in use). See Unable to Unconfigure Memory on a Board With Permanent Memory . CPUs on the board cannot be taken off line. See Unable to Unconfigure a CPU . Cannot Unconfigure a Board Whose Memory Is Interleaved Across Boards If you try to unconfigure a system board whose memory is interleaved across system boards, the system displays an error message such as: cfgadm: Hardware specific failure: unconfigure N0.SB2::memory: Memory is interleaved across boards: /ssm@0,0/memory-controller@b,400000 Cannot Unconfigure a CPU to Which a Process is Bound If you try to unconfigure a CPU to which a process is bound, the system displays an error message such as the following: cfgadm: Hardware specific failure: unconfigure N0.SB2::cpu3: Failed to off-line: /ssm@0,0/SUNW,UltraSPARC-III Unbind the process from the CPU and retry the unconfigure operation. Cannot Unconfigure a CPU Before All Memory is Unconfigured All memory on a system board must be unconfigured before you try to unconfigure a CPU. If you try