1833685 Members
3542 Online
110062 Solutions
New Discussion

NO_HW

 
Stephen Tanner
Occasional Advisor

NO_HW

I have exchanged two tape libraries connected via SAN, which has of course cause NO_HW output in ioscan. I was able to remove all the devices with rmsf, except for two on each machine.

ext_bus 60 1/0/12/0/0.1.35.255.11 fcpdev NO_HW INTERFACE FCP Device Interface

These four devices are all of the type listed above. When I attempt to remove these, I get the error:
rmsf: Specified hardware path has no devices

Is there a way for me to remove these from the list, without rebooting the machine?
8 REPLIES 8
Geoff Wild
Honored Contributor

Re: NO_HW

Did you try:

ioscan -fn
and insf -e

Then try to remove them?

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Stephen Tanner
Occasional Advisor

Re: NO_HW

I did indeed.
Fabio Ettore
Honored Contributor

Re: NO_HW

Hi Stephen,

try

rmsf -k -H 1/0/12/0/0.1.35.255.11

Best regards,
Fabio
WISH? IMPROVEMENT!
Stephen Tanner
Occasional Advisor

Re: NO_HW

I receive the same error.

rmsf: Specified hardware path has no devices

There are no special device files for these particular hardware paths. Although, it perplexes me that rmsf cannot remove the hardware path from the list.
Charles Holland
Trusted Contributor

Re: NO_HW

From time to time when we have to boot our systems as a nPar instead of into vPar status we wind up with device files for hardware that is not assigned to the system when it is in vPar status. In other words when we boot into the nPar status it picks up all the hardware from all the other vPars and creates files for them. When we boot back into the vPar status we then have /dev files that are bogus. ie NO_HW status.

Attached is a script that we use to resolve this problem. Please review. After running it will create a file that contains rmsf commands. chmod 744 the file (devfiles_without_hardware) and then run it.

It works for us, hope it answers your request for help.

Regards
"Not everything that can be counted counts, and not everything that counts can be counted" A. Einstein
Stephen Tanner
Occasional Advisor

Re: NO_HW

My problem is the exact opposite. I have hardware without /dev files. This hardware is in a NO_HW state, and I cannot seem to remove it from the list. I thought that I had made this clear in the initial, and subsequent post. If not, I hope everything is clear now. The error I receive is entirely correct, I do not have devices files for the hardware that shows NO_HW. I was able to remove all the hardware in this state that did have devices. What I am now looking for, is a way to remove the hardware that has no devices, because rmsf is giving me the error stated. I would like to do this without a reboot. I hope this has clarified my situation.
Geoff Wild
Honored Contributor

Re: NO_HW

Well...it sounds like a reboot is going to be the only way.

If you have a support contract, you could give HP a call and see what they have another way.

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Sameer_Nirmal
Honored Contributor

Re: NO_HW

Hi,

As you see in the "ioscan" output, the h/w type is "INTERFACE" . Hence it won't be associated with any device files. A hardware with type "DEVICE" beneath it would have a device file like a controller etc.

Are you using the FC HBA associated with the h/w path?

Can you post the "ioscan" output for h/w path "1/0/12/0/0" tree ( below it)?