- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- device file changed for disk
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
тАО07-24-2008 05:43 AM
тАО07-24-2008 05:43 AM
I have changed my storage cabinet on my mc cluster and now in one of the nodes (the secondary one) the HW path has changed from /dev/dsk/c33txdx to /dev/dsk/c23txdx
I have a the map files created with vgexport on the main node. Should a vgimport on the secondary node solve the problem?
Thanks in advance!!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 05:49 AM
тАО07-24-2008 05:49 AM
Re: device file changed for disk
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!
![](https://community.hpe.com/html/assets/select-arrow.png?F89AC8BE8EE85C24E5406B29321738C0)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 06:08 AM
тАО07-24-2008 06:08 AM
Re: device file changed for disk
I hope the issue is clearer now for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 06:14 AM
тАО07-24-2008 06:14 AM
Re: device file changed for disk
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!
![](https://community.hpe.com/html/assets/select-arrow.png?F89AC8BE8EE85C24E5406B29321738C0)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 05:12 AM
тАО07-25-2008 05:12 AM
Solutionyou need to export the volume group from the secondary node and import it back in. That is unless the volume group is the one containing the lock disk. This means that you are redefining the lock disk which cannot usually be done while the cluster is up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 05:14 AM
тАО07-25-2008 05:14 AM
Re: device file changed for disk
Jul 25 14:54:15 seplet6 cmcld: WARNING: Cluster lock disk /dev/dsk/c33t0d0 has failed: I/O error
Jul 25 14:54:15 seplet6 cmcld: Until it is fixed, a single failure could
Jul 25 14:54:15 seplet6 cmcld: cause all nodes in the cluster to crash
Because now the lock disk is c23t0d0. I can't just change it on /etc/cmcluster/cluster.conf with the cluster up?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 05:19 AM
тАО07-25-2008 05:19 AM
Re: device file changed for disk
As for vgimporting the VG, it depends on how to created the new VG on the new array... if you did a bit-for-bit copy of the old VG disks to the new ones, then the new disks will have the same VGID as the old disks. If both the old and new disks are visible to the second server, you won't want to do a vgimport with a map file that contains the VGID at the top... doing so will make LVM discover both old and new disks.
In such a case, you have to use a map file that does not contain a VGID at the top, and specifically identify each disk path in the vgimport command.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2008 12:47 AM
тАО07-27-2008 12:47 AM
Re: device file changed for disk
Please confirm if you are still connecting your old storage box to your nodes or not. If yes, then running vgimport using previously created map file will not work as map file will be having old VGIDs information.
I would suggest you to take complete backup of your existing cluster configuration before you make any changes using new disks comming from new box.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2008 10:36 PM
тАО07-27-2008 10:36 PM
Re: device file changed for disk
My old cabinet is far away from here. But as this is a cluter, I've got the main node working with the new cabinet with no problems. What I did is vgexport on the main node and vgimport on the secondary one. However it is still remaining to solve the lock disk issue. I wonder if I can just change it on the /etc/cmcluster/cluster.conf file and cmapplyconf. Is it correct?
Thanks!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 12:42 AM
тАО07-28-2008 12:42 AM
Re: device file changed for disk
What I understood that one node is able to recognise all the disk devices including lock disk. If this is the case then updating conf file and running cmcheck followed by cmapplyconf should work.
update cluster lock lun for second node e.g.
CLUSTER_LOCK_LUN /dev/dsk/c23txdx
After cmapplyconf
you can run cmrunnode -n second_node_name -v to join cluster ..
This should update cluster lock.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 12:47 AM
тАО07-28-2008 12:47 AM
Re: device file changed for disk
You need to halt cluster to update cluster lock disk in conf file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 12:55 AM
тАО07-28-2008 12:55 AM
Re: device file changed for disk
Now it is clear for me. I will wait for a planned shutdown of the system to update the lock disk on the cluster.
Thanks a lot to all you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 12:55 AM
тАО07-28-2008 12:55 AM