- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MSA1000 storage not member of a VG after move to a...
HPE EVA Storage
1753894
Members
7763
Online
108809
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
Discussions
Discussions
Forums
Discussions
back
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
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
11-20-2009 02:11 AM
11-20-2009 02:11 AM
MSA1000 storage not member of a VG after move to active-active
Hi
I have an Itanium blade (HP-UX 11.31) that has been using a single fibre channel / path connection to some MSA1000 storage. Y/day our storage guys upgraded the MSA1000 to become Active / Active thus supporting both HBA's. On bringing the server back on-line the MSA storage is still visible to the Blade at a H/W address level but the volume group information seems to have been lost from the storage and it now just appears as 'unused' storage instead of been a volume group member as it was before.
Is there anything specific I need to do on the server to let it know this storage is now running active / active ? ....even reverting back to single channel hasn't resolved the issue.
Naturally the data will still be on the MSA but i need to recover the Volume group label information etc to allow me to access it again.
Here's how the storage currently appears :-
64000/0xfa00/0x8 /dev/disk/disk5 unused - 1 176.27 HP MSA VOLUME
Any advice greatly appreciated here.
Mike.
I have an Itanium blade (HP-UX 11.31) that has been using a single fibre channel / path connection to some MSA1000 storage. Y/day our storage guys upgraded the MSA1000 to become Active / Active thus supporting both HBA's. On bringing the server back on-line the MSA storage is still visible to the Blade at a H/W address level but the volume group information seems to have been lost from the storage and it now just appears as 'unused' storage instead of been a volume group member as it was before.
Is there anything specific I need to do on the server to let it know this storage is now running active / active ? ....even reverting back to single channel hasn't resolved the issue.
Naturally the data will still be on the MSA but i need to recover the Volume group label information etc to allow me to access it again.
Here's how the storage currently appears :-
64000/0xfa00/0x8 /dev/disk/disk5 unused - 1 176.27 HP MSA VOLUME
Any advice greatly appreciated here.
Mike.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2009 06:41 AM
11-20-2009 06:41 AM
Re: MSA1000 storage not member of a VG after move to active-active
Since the change it appears we are now going through a fibre switch which has changed some of the path details. This would explain why the volume group isn't seeing the disk on the expected hardware path :-
Before
Persistent Device File /dev/disk/disk5
Legacy Device File(s) /dev/dsk/c2t0d6;
Legacy H/W Path(s) 0/3/0/0/0/0.1.0.0.0.0.6
Now
Persistent Device File /dev/disk/disk5
Legacy Device File(s) /dev/dsk/c8t0d6;
Legacy H/W Path(s) 0/3/0/0/0/0.100.0.0.0.0.6 (note the 100)
Can we tell the volume group to look for it's member disk at the new location ?
Before
Persistent Device File /dev/disk/disk5
Legacy Device File(s) /dev/dsk/c2t0d6;
Legacy H/W Path(s) 0/3/0/0/0/0.1.0.0.0.0.6
Now
Persistent Device File /dev/disk/disk5
Legacy Device File(s) /dev/dsk/c8t0d6;
Legacy H/W Path(s) 0/3/0/0/0/0.100.0.0.0.0.6 (note the 100)
Can we tell the volume group to look for it's member disk at the new location ?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP