GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Disk device files deletion
Operating System - HP-UX
1849822
Members
3440
Online
104044
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
05-16-2004 06:11 PM
05-16-2004 06:11 PM
Disk device files deletion
On one of our HP-UX 11i system, all disk device files like /dev/dsk/c5t5d0 are accidently deleted. Therefore 'vgdisplay' command produces the following error.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t6d0":
The specified path does not correspond to physical volume attached to
this volume group
/etc/lvmtab file has the correct volume group information and LV information on physical volume should also be clean and intact. So there shouldn't be a need of vgsacn and vgcfgrestore. System is also running fine so far. Should we just create disk device files using mknod command? Raw device files /dev/rdsk/c5t5d0 are still intact, so minor number for device files can be determined.
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t6d0":
The specified path does not correspond to physical volume attached to
this volume group
/etc/lvmtab file has the correct volume group information and LV information on physical volume should also be clean and intact. So there shouldn't be a need of vgsacn and vgcfgrestore. System is also running fine so far. Should we just create disk device files using mknod command? Raw device files /dev/rdsk/c5t5d0 are still intact, so minor number for device files can be determined.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2004 06:19 PM
05-16-2004 06:19 PM
Re: Disk device files deletion
If they were removed like this:
# rm /dev/dsk/cxtydz
You may be able to re-create them with
# insf -e
Do they still appear in the ioscan output?
# ioscan -fnC disk
Or were they removed using a different method?
# rm /dev/dsk/cxtydz
You may be able to re-create them with
# insf -e
Do they still appear in the ioscan output?
# ioscan -fnC disk
Or were they removed using a different method?
Anyone for a Mutiny ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2004 06:50 PM
05-16-2004 06:50 PM
Re: Disk device files deletion
insf -e
as stated in prev comment ... I wonder u may need to
mv /etc/lvmtab /etc/lvmtab.old
vgscan
As the device filenames may get changed if the order in which they are searched are diffrent from the original config.
Kaps
as stated in prev comment ... I wonder u may need to
mv /etc/lvmtab /etc/lvmtab.old
vgscan
As the device filenames may get changed if the order in which they are searched are diffrent from the original config.
Kaps
Nothing is impossible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2004 01:25 AM
05-18-2004 01:25 AM
Re: Disk device files deletion
I assume that since you only assigned 5 points to the other replies that 'insf -e' did not work.
Did 'ioscan -fnCdisk' show the disks as CLAIMED or maybe NO_HW? What does 'diskinfo /dev/rdsk/c#t#d#' report?
If these are SAN fabric attached devices then perhaps someone moved the storage port (e.g. storage was connected to switch/director at port X and was moved to port Y). This will change the controller number and show up on the server as new device files. The old ones will then no longer be used (unless the storage port is moved back to its original location). If this is the case then you will have some cleanup to do.
David
Did 'ioscan -fnCdisk' show the disks as CLAIMED or maybe NO_HW? What does 'diskinfo /dev/rdsk/c#t#d#' report?
If these are SAN fabric attached devices then perhaps someone moved the storage port (e.g. storage was connected to switch/director at port X and was moved to port Y). This will change the controller number and show up on the server as new device files. The old ones will then no longer be used (unless the storage port is moved back to its original location). If this is the case then you will have some cleanup to do.
David
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP