Failed To Create Nodes For Pwwn= Error=10
LinkedIn How to Use this Site ? Storage : "Failed to create nodes for pwwn" error during solaris boot June 18, 2011By RamdevOther Learning Articles that you may like to read Latest ArticlesInformation CentersLinux AdminSolaris AdminVxVM AdminVCS AdminCareer GuidanceScriptingStorage AdminQuick ReferenceLatest Articles Information Centers Linux Admin Solaris 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 continu
Management Converged Platforms Data Protection Infrastructure Management Platform Solutions Security Storage Dell Products for Work Network Servers Education Partners Programs Highlighted Communities Support » Connect » Developers » Partners » Downloads » 日本語コミュニティ EMC Community Dell Community A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor Disk Library DiskXtender Documentum E ECS eRoom G Greenplum H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA S ScaleIO Secure http://unixadminschool.com/blog/2011/06/storage-failed-to-create-nodes-for-pwwn-error-during-solaris-boot/ Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix U Unity V ViPR Controller Product Communities > CLARiiON > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 13 Replies Latest reply: Jan 22, 2010 1:34 PM https://community.emc.com/thread/97665?start=0&tstart=0 by glen Unable to format LUN on Solaris 10 Todd_1215 Jan 22, 2010 6:52 AM Hello - I hope someone here can assist me with this issue. I have been beating my head against the wall over this and have exhausted all possibilities. I have 2 x Sun V480 with an Emulex LP10000-E card connected to a Clariion CX3-10f. I'm using the SUN branded Emulex driver provided with the OS. This server is a new install "no patches" what soever. One server has full access to the LUN that's assigned to it the other can see the LUN device but I am not able to format it nor can I mount it. I'll call the non-working server Server-B and the working server Server-A. Server-A Config ( used fcinfo command to get results ) HBA Port WWN: 10000000c946878a OS Device Name: /dev/cfg/c1 Manufacturer: Emulex Model: LP10000 Firmware Version: 1.91a1 (T2D1.91A1) FCode/BIOS Version: Boot:5.00a7 Fcode:1.41a4 Serial Number: VM51733465 Driver Name: emlxs Driver Version: 2.31p (2008.12.11.10.30) Type: L-port State: online Supported Speeds: 1Gb 2Gb Current Speed: 2Gb Node WWN: 20000000c946878
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/robot-issue-with-OS-system/td-p/217775 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : robot issue with OS system VOX : Backup and Recovery : NetBackup : robot issue with OS system Subscribe to RSS Feed Mark Topic as New failed to Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page robot issue with OS system Manfred_Ratzke Level 4 01-21-2009 03:18 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, after reboot th erobot cannot initialized and I see on the OS systembash host# cfgadm -c configure c4cfgadm: Library error: failed failed to create to create device node: 500104f0006e46a8: I/O errorOperation partially successful. Some failures seenbash host# cfgadm -c unconfigure c4::500104f0006e46a8cfgadm: Library error: remove operation failed: /devices/pci@8,700000/SUNW,qlc@5/fp@0,0/sg@w500104f0006e46a8,0: Inappropriate ioctl for device Labels: 7.1.x and Earlier Backup and Recovery NetBackup 0 Kudos Reply 6 Replies Re: robot issue with OS system Amit_Karia Level 6 01-21-2009 04:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Can you run#luxadm probecommand and send the o/p 0 Kudos Reply Re: robot issue with OS system Manfred_Ratzke Level 4 01-21-2009 05:02 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Let me explain before:when I go and reset the robot and bott the server then all drives are ok and robot initializedwhen I then start backups the first 3 run fine, further more will cause that thesystemmessage"cannot initialize robot"g1bs01 console login: Jan 21 13:06:46 g1bs01 ltid[848]: Request for media ID 000316 is being rejected because it cannot be found in designated slotJan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR, GENERALJan 21 13:07:23 g1bs01 tldcd[1853]: