HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Virtual Replicator drive letters problem
HPE EVA Storage
1827295
Members
4097
Online
109717
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
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
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
06-10-2004 03:16 AM
06-10-2004 03:16 AM
Virtual Replicator drive letters problem
Hello All.
This question atually relates to the old thread Id=592979, but any new contributions would be most helpful, as I am now running out of ideas! I still have a problem where Virtual Replicator drives are assigned different drive letters after a restart. The msa1000 array has been deleted and recreated so raw disks are definitely not signed by windows. Otto Warlich suggested that applying permanent bindings to the HBAs using lputilnt should fix this behavior, but unfortunately has made no difference (unless I'm not doing it properly!). I had no problem prior to upgrading all firmware and HBA drivers to latest, secure path to 4.0C, OS to win2Ksp4 and VR to 3.0Bsp1. Is there an undocumented problem with this configuration? (incidentally, the recover drives utility appears to run, but does not fix the problem).
Rocky: Did you fix this problem for your customers? if so how?
Any suggestions would be gratefull recieved,
Thanks,
Martin.
This question atually relates to the old thread Id=592979, but any new contributions would be most helpful, as I am now running out of ideas! I still have a problem where Virtual Replicator drives are assigned different drive letters after a restart. The msa1000 array has been deleted and recreated so raw disks are definitely not signed by windows. Otto Warlich suggested that applying permanent bindings to the HBAs using lputilnt should fix this behavior, but unfortunately has made no difference (unless I'm not doing it properly!). I had no problem prior to upgrading all firmware and HBA drivers to latest, secure path to 4.0C, OS to win2Ksp4 and VR to 3.0Bsp1. Is there an undocumented problem with this configuration? (incidentally, the recover drives utility appears to run, but does not fix the problem).
Rocky: Did you fix this problem for your customers? if so how?
Any suggestions would be gratefull recieved,
Thanks,
Martin.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2004 05:21 AM
07-28-2004 05:21 AM
Re: Virtual Replicator drive letters problem
Martin,
I was not able to fix it.
The customer grew tired of the problem and he phased out the VR configuration.
I am maybe scheduled for a new implementation concerning an MSA1k and VR v4.
Hav you tried VR version 4 ?
or is this an upgrade that costs money ?
I have heard (a tip) that unmounting the drives and remounting them in a dos box helps.
I'll get back to you,
rgds,
Rocky
I was not able to fix it.
The customer grew tired of the problem and he phased out the VR configuration.
I am maybe scheduled for a new implementation concerning an MSA1k and VR v4.
Hav you tried VR version 4 ?
or is this an upgrade that costs money ?
I have heard (a tip) that unmounting the drives and remounting them in a dos box helps.
I'll get back to you,
rgds,
Rocky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2004 05:50 PM
07-29-2004 05:50 PM
Re: Virtual Replicator drive letters problem
What is the firmware at on the MSA?
And why are you even using VR? Do you need the snapshot capability? or are you using it for expansion?
Steven
And why are you even using VR? Do you need the snapshot capability? or are you using it for expansion?
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2004 08:35 PM
08-01-2004 08:35 PM
Re: Virtual Replicator drive letters problem
The firmware I am using is version 4.24 as per the support CD version 6.51.
We are using VR primarily for the snapshot capability. (I would like to scrap it personally!)
I am now in the process of downgrading to my previous stable platform of Secure Path V4, Windows sp3 and VR 3.0. I am keeping the current Firmware, even though I was previously at v2.38. This seems to work OK, so I don't think the problem is a firmware issue.
Going to VR v4 is a chargable upgrade, and we are not in a position to purchase this at present. (anyone know if this fixes the problem?)
I am interested in how an unmounted VR drive can be mounted in DOS Have you tried this Rocky?
We are using VR primarily for the snapshot capability. (I would like to scrap it personally!)
I am now in the process of downgrading to my previous stable platform of Secure Path V4, Windows sp3 and VR 3.0. I am keeping the current Firmware, even though I was previously at v2.38. This seems to work OK, so I don't think the problem is a firmware issue.
Going to VR v4 is a chargable upgrade, and we are not in a position to purchase this at present. (anyone know if this fixes the problem?)
I am interested in how an unmounted VR drive can be mounted in DOS Have you tried this Rocky?
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP