Storage : "Failed to create nodes for pwwn" error during solaris boot

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 <c#::wwn>
where <c#::wwn> represents the controller number and World Wide Number(WWN) of the device that has been removed.

To list all the Fabric devices that should be configured, use the command:

# cfgadm -la
The “c#” can also be found in /dev/cfg by doing `ls -l` on the physical path listed in the error message.
In the above example, the designation would be “c3::256000c0ffc028e4”.

To avoid this problem in the future, use the following command before removing the device from the Storage Area Network(SAN):

# cfgadm -c unconfigure <c#::wwn>

If no device has been moved or removed:

forceloading the following drivers during the boot process in /etc/system can resolve the issue.

forceload: drv/qlc
forceload: drv/fctl
forceload: drv/fcp
forceload: drv/fp

If the following drivers are being used by the system it would be worth forceloading these as well.

forceload: drv/ssd
forceload: drv/scsi_vhci





I have started ( aka in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' You can connect me at -

1 Response

  1. you’ve gotten an incredible blog here!

What is in your mind, about this post ? Leave a Reply

  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us