- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite-UX
- >
- Re: Ignite Warning: Unable to open device to dete...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-31-2016 10:51 AM
05-31-2016 10:51 AM
I am just curious about an Warning message I am getting when creating an Ignite image.
I am getting the following message:
WARNING: Unable to open device for 255/2/0.0.0 to determine unique_name
What implications does this have on my image and restore abilities? Other than this message, the backup is successful. Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-31-2016 11:16 AM
05-31-2016 11:16 AM
Re: Ignite Warning: Unable to open device to determine unique_name
It could point to USB
example
usbmsvbus 1 255/1 mass_storage CLAIMED VIRTBUS USB Mass Storage
ext_bus 1 255/1/0 usb_ms_scsi CLAIMED INTERFACE USB Mass Storage SCSI
but without an ioscan I cannot tell for sure.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-31-2016 11:41 AM
05-31-2016 11:41 AM
Re: Ignite Warning: Unable to open device to determine unique_name
My apologies for not providing more info. The address refers to an internal DVD device. My concern was how an image restore could be effected by this. It seems to me that there would be no ill effects as the DVD would be found and readded. Thank you for the response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-31-2016 01:14 PM - edited 05-31-2016 01:23 PM
05-31-2016 01:14 PM - edited 05-31-2016 01:23 PM
SolutionOne of the most important features in Ignite is the validation of the hardware and device files. If this path is for a DVD, it sounds as if the device file is missing. You can replace deleted or missing device files with insf. In this case, you can restore the device files with something like:
# insf -H 255/2/0.0.0
Now Ignite can complete with no errors.
The previous backup image will restore without a problem and the missing device file will created automatically.
But since Ignite is usually required in important situations like recovery or deloyment, I want an error free image to be available when I really need it.
Bill Hassell, sysadmin
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP