Ignite-UX
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Ignite Warning: Unable to open device to determine unique_name

 
SOLVED
Go to solution
TheJuiceman
Super Advisor

Ignite Warning: Unable to open device to determine unique_name

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.

3 REPLIES 3
Torsten.
Acclaimed Contributor

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!   
TheJuiceman
Super Advisor

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.

Bill Hassell
Honored Contributor
Solution

Re: Ignite Warning: Unable to open device to determine unique_name

One 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