• Home
  • Disclaimer
  • Contact
  • Archives
  • About
  • Subscribe
  • Support
  • Advertise

Kernel Talks

Unix, Linux, & Cloud!

  • How-to guides
    • Howto
    • Disk management
    • Configurations
    • Troubleshooting
  • OS
    • HPUX
    • Linux
  • Miscellaneous
    • Software & Tools
    • Cloud Services
    • System services
    • Virtualization
  • Certification Preparations
    • AWS Certified Solutions Architect – Associate
    • AWS Certified Solutions Architect – Professional
    • AWS Certified SysOps Administrator – Associate
    • AWS Certified Cloud Practitioner
    • Certified Kubernetes Administrator
    • Hashicorp Certified Terraform Associate
    • Oracle Cloud Infrastructure Foundations 2020 – Associate
  • Tips & Tricks
  • Linux commands
You are here: Home / Troubleshooting Errors

How to resolve 83h/80h error in HPUX

Published: January 8, 2017 | Modified: June 20, 2020



Procedure to resolve Evpd inquiry page 83h/80h error in HPUX. This is LUN related error which may cause non-availability of device.

This post is about 83h/80h error which most of the times seen on HPUX servers. This error is caused by LUNs which are made visible to the server in a place where previously some LUNs were visible.

Normally, when you present a new LUN to HPUX server, after running ioscan -fnCdisk and insf -e commands they should be visible. But in some cases even after running these commands, you don’t see LUNs on the server. Obviously, as a troubleshooting step, you will check syslogs. And you will find below entry :

# tail /var/adm/syslog/syslog.log
May 3 16:46:05 destination vmunix: Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 23) The lun path is

This entry denotes that a new device is made visible on the path which was in use by some other device in the past. To avoid any mishap, the kernel is not accepting this new device by default. Here, you need to manually tell the kernel that this change is accepted and should be taken up into operation.

This can be done with replace_wwid command as suggested in error itself. Command will be :

# scsimgr -v -f replace_wwid -C lunpath -I 69
Binding of LUN path 4/0/5/1/0/4/0.0x5006048452aa4347.0x4034000000000000 with new LUN validated successfully

Note that, here id 69 is used from the error we saw in Syslog. Error log suggests that id 23 is passed known instance and id 69 is a new one. You have to use a new instance id in command.

Once LUN is validated successfully, you will be able to see it on the system after running ioscan and insf commands again!

⇠ Previous article
Building different types of software depots in HPUX
Next article ⇢
How to create tar file in Linux or Unix

Related stuff:

  • How to resolve mount.nfs: Stale file handle error
  • How to unmount NFS when the server is offline
  • mount.nfs: requested NFS version or transport protocol is not supported
  • Failed to mount cd error in Zypper
  • How to resolve the fatal error: curses.h: No such file or directory
  • How to troubleshoot RPC: Port mapper failure – Timed out error
  • Access denied error in NFS for root account
  • Issues while working on ELK stack
  • /bin/bash^M: bad interpreter: No such file or directory
  • How to resolve aclocal: not found error in Ubuntu
  • networker service not starting
  • Space is not released after deleting files in Linux?

Filed Under: Troubleshooting Errors Tagged With: 80h error in HPUX, 83h/80h error, How to resolve 83h/80h, inquiry page 83h/80h failed, New LUN is not visible in HPUX, scsimgr, scsimgr replace_wwid

If you like my tutorials and if they helped you in any way, then

  • Consider buying me a cup of coffee via paypal!
  • Subscribe to our newsletter here!
  • Like KernelTalks Facebook page.
  • Follow us on Twitter.
  • Add our RSS feed to your feed reader.

Share Your Comments & Feedback: Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Get fresh content from KernelTalks

  • Email
  • Facebook
  • RSS
  • Twitter

Get Linux & Unix stuff right into your mailbox. Subscribe now!

* indicates required

This work is licensed under a CC-BY-NC license · Privacy Policy
© Copyright 2016-2023 KernelTalks · All Rights Reserved.
The content is copyrighted to Shrikant Lavhate & can not be reproduced either online or offline without prior permission.