- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Bogus Physical Volumes
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Report Inappropriate Content
тАО11-09-2009 06:45 AM
тАО11-09-2009 06:45 AM
We're running an HPUX 11.00 (yes, we still have one due to openspool :( ) and I'm seeing some 'ghost disks'. When I read the syslog.log, a lot of messages like the next are spawning.
Nov 9 13:56:16 %system% EMS [12311]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_4_0_0.80.7.0.0.0.1" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 806813824 -r /storage/events/disks/default/0_4_0_0.80.7.0.0.0.1 -n 806813771 -a
When I execute the command, it always refers to a disk we had connected the server to on SAN. Today this connection is completely gone (no zoning anymore to the SAN).
When I use ioscan, I can still see the disks comming up. When I use pvdisplay on such a disk, I get this output:
# pvdisplay /dev/dsk/c48t0d0
pvdisplay: Couldn't find the volume group to which
physical volume "/dev/dsk/c48t0d0" belongs.
pvdisplay: Cannot display physical volume "/dev/dsk/c48t0d0".
A pvremove doesn't change a thing:
# pvremove /dev/rdsk/c48t0d0
Warning: Cannot determine block size of Physical Volume "/dev/rdsk/c48t0d0".
Assuming a default value of 1024 bytes. Continuing.
pvremove: Physical Volume "/dev/rdsk/c48t0d0" contains no LVM information
Normally we do a procedure to get luns visable we made on SAN:
ioscan
ioscan
insf -e
powermt config
powermt check
With powermt nothing is visible however.
Can I somehow remove these disks?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 06:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 07:04 AM
тАО11-09-2009 07:04 AM
Re: Bogus Physical Volumes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 07:15 AM
тАО11-09-2009 07:15 AM
Re: Bogus Physical Volumes
/var/stm/data/tools/monitor/disabled_instances
(IIRC the file is self documenting)
That may stop the EMS errors being reported, I'm aware of no way to get rid of the NO_HW entries on ioscan without reboot though...
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 07:35 AM
тАО11-09-2009 07:35 AM
Re: Bogus Physical Volumes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 07:35 AM
тАО11-09-2009 07:35 AM
Re: Bogus Physical Volumes
the ioconfig file resides in /etc/ioconfig and /stand/ioconfig.
you can rename the files and reboot. the system will stop while trying to boot with a prompt saying ioconfig file not found.
A that point you can run ioinit -c to recreate a new ioconfig file without all the stale entries from the previous disks.
ofcourse this is a bi risky since some hardware mapping may change. If yo have a lot of SAN disks connected at some point in time, it would be beneficial to do it, otherwise i wont recommend it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 07:05 AM
тАО11-10-2009 07:05 AM
Re: Bogus Physical Volumes
- Kevin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-10-2009 07:10 AM
тАО11-10-2009 07:10 AM