Failed To Create Nodes For Pwwn Error=5
LinkedIn How to Use this Site ? Storage : "Failed to create nodes for pwwn" error during solaris boot cfgadm: library error: report luns failed: June 18, 2011By RamdevOther Learning Articles that you may like to cfgadm: insufficient condition read Latest ArticlesInformation CentersLinux AdminSolaris AdminVxVM AdminVCS AdminCareer GuidanceScriptingStorage AdminQuick ReferenceLatest Articles Information Centers Linux Admin Solaris cfgadm -c configure Admin VxVM Admin VCS Admin Career Guidance Scripting Storage Admin Quick Reference Free Courses We Offer Linux Administration Interview Preparation [Free Email Crash Course] Roles and Responsibilities of System Admin [Free Course] Getting Started with RHEL7 Administration [Free Course] Paid Training Courses we Offer Self Paced CoursesLive WebexSelf Paced CoursesSolaris11 Self Paced Video Learning RHEL7 Self Paced Video Learning VxVM + VCS Self Paced Video Learning Solaris10 Self Paced Video Learning Puppet Automation Self Paced Video Learning Live WebexSolaris 11 Administration Live WebEx Puppet Automation - Live WebEx Veritas ( VCS+VxVM) Live Webex If Fibre Channel devices are not present or turned off, boot errors will occur. Without corrective action, these errors will persist for every re-boot. The boot errors which are linked to this problem, can be found in the /var/adm/messages file, and are formatted as follows: luxadm[90]: [ID 593423 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@8,600000/SUNW,qlc@2,1/fp@0,0:fc::256000c0ffc028e4) in file: /etc/cfg/fp/fabric_WWN_map. I/O error scsi: [ID 243001 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2,1/fp@0,0 (fcp4): Failed to create nodes for pwwn=266000c0ffe028e4; error=5 The reason for these errors is that the device in question cannot be seen by the Solaris[TM] Operating System that is connected to a Fibre Channel Storage Area Network. Solaris[TM] will continue to report this error, every time it boots, until corrective action is taken. This error only pertains to fabric (switch) attached devices, as direct attached devices do not invoke the luxadm command at boot that can error as above. If device has been moved or removed, execute the command: # cfgadm -o force_update -c unconfigure any hitachi array through fibre channel for the first time, the luns will not be visible, Usualy it's problem with HBA card andyou need to restart HBA ports in order to make it visible or reboot the server. To resolve this problem you must perform fallowing procedure. step 1: check current status of the devices [root@localhost:/]# cfgadm -al Ap_Id Type Receptacle Occupant Condition c1 scsi-bus connected configured unknown c1::dsk/c1t0d0 disk connected configured unknown c1::dsk/c1t1d0 disk connected configured unknown c2 http://unixadminschool.com/blog/2011/06/storage-failed-to-create-nodes-for-pwwn-error-during-solaris-boot/ fc-fabric connected configured unknown c2::2100001b320005b0 unknown connected unconfigured unknown c2::2100001b320050af unknown connected unconfigured unknown c2::2100001b320064b0 unknown connected unconfigured unknown c2::2100001b3200a2b1 unknown connected unconfigured unknown c2::2101001b3220ceb0 unknown connected unconfigured unknown c2::210100e08b3f38d8 unknown http://storageengineer.blogspot.com/2013/06/solaris-host-not-able-to-see-hitachi.html connected unconfigured unknown c2::50060e801002b263 unavailable connected unconfigured failed c2::50060e801002b267 unavailable connected unconfigured failed c3 fc-fabric connected configured unknown c3::2100001b320005b0 unknown connected unconfigured unknown c3::2100001b320050af unknown connected unconfigured unknown c3::2100001b320064b0 unknown connected unconfigured unknown c3::2100001b3200a2b1 unknown connected unconfigured unknown c3::2100001b3200ceb0 unknown connected unconfigured unknown c3::210000e08b1f38d8 unknown connected unconfigured unknown c3::50060e801002b263 unavailable connected unconfigured failed c3::50060e801002b267 unavailable connected unconfigured failed c4 scsi-bus connected unconfigured unknown usb0/1 unknown empty unconfigured ok usb0/2 unknown empty unconfigured ok Step 2: Try to reconfigure the controller [root@localhost:/]# cfgadm -c configure c2 cfgadm: Library error: failed to create device node: 50001fe150095928: I/O error report LUNs failed: 50060e801002b263 failed to create device node: 50001fe150095929: I/O error report LUNs failed: 50060e801002b267 failed to create device node: 50001fe15009592d: I/O error Operation partially successful. Some failures seen [root@localhost:/]#cfgadm -c configure c3 cfgadm: Options | Examples | Files | Attributes | See Also | Warnings | Notes Name cfgadm_fp– driver specific commands for cfgadm Synopsis http://docs.oracle.com/cd/E19253-01/816-5166/cfgadm-fp-1m/index.html /usr/sbin/cfgadm [-f] [-n | -y] [-v] [-o hardware_options] -c function ap_id https://adsm.org/lists/html/Networker/2002-10/msg00402.html [ap_id] /usr/sbin/cfgadm [-v] [-a] [-s listing_options] [-o hardware_options] [-l [ap_id]] /usr/sbin/cfgadm [-v] [-o hardware_options] -h [ap_id] Description The fp port driver plug-in /usr/lib/cfgadm/fp.so.1 provides the functionality for Fibre Channel Fabric device node management through cfgadm(1M). cfgadm operates on attachment points. Attachment points are locations failed to in the system where hardware resources can be dynamically reconfigured. Refer to cfgadm(1M) for additional details on attachment points. For Fibre Channel Fabric device node management, each fp port node is represented by an attachment point in the device tree. In addition, each Fibre Channel device is represented by a dynamic attachment point. Attachment points failed to create are named through ap_ids. Two types of ap_ids are defined: logical and physical. The physical ap_id is based on the physical pathname. The logical ap_id is a shorter, more user-friendly name. For fp port nodes, the logical ap_id is the corresponding disk controller number. For example, c0 is a typical logical ap_id. Fibre Channel devices are named with a port World Wide Name (WWN). If a disk device is connected to controller c0, its ap_id can be: c0::50020f2300006077 where 50020f2300006077 identifies the port WWN of a specific Fibre Channel device. Each device on the Fibre Channel private loop port, Fabric port or public loop port is probed and made available to Solaris by default. Devices connected to the Fibre Channel Fabric port or public loop port can be made unavailable to Solaris by initiating an application or an end user operation. The operation is similar to the hot unplugging of devices by way of management user interfaces. Applications or users can use the /usr/lib/cf not see the Tape Driver and the Robot From: Legato_Networker