HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Win 2003 disk manager takes forever to find new vd...
HPE EVA Storage
1833764
Members
2677
Online
110063
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
10-30-2006 03:46 AM
10-30-2006 03:46 AM
Win 2003 disk manager takes forever to find new vdisks
BL25p blades
EVA4000 - XCS 6.0
QLogic HBAs - driver v9.1.0.18
Windows 2003 x64 SP1
MPIO FF 2.00.02
Symptoms:
I create a new vdisk via SSSU or Command View, and present it to host. I log in to that host, and either use "Computer Management/Storage/Disk Management/rescan disks" or the command line "diskpart/rescan" to make the new disk available to the OS. The logical disk manager will hang for five to ten minutes before responding again. Perhaps one time in 20, it will crash. The new disks are always visible when LDM returns.
There are generally no more than ten LUNs available to a given host.
The event log records dozens, sometimes hundreds, of event ID 257 from PlugPlayManager: "Timed out sending notification of target device change to window of LDM Service."
The Microsoft KB says these are harmless, and I see no indication to the contrary, but it seems like it should take much less time for the LDM to recognize new disks. Is this kind of lag normal?
EVA4000 - XCS 6.0
QLogic HBAs - driver v9.1.0.18
Windows 2003 x64 SP1
MPIO FF 2.00.02
Symptoms:
I create a new vdisk via SSSU or Command View, and present it to host. I log in to that host, and either use "Computer Management/Storage/Disk Management/rescan disks" or the command line "diskpart/rescan" to make the new disk available to the OS. The logical disk manager will hang for five to ten minutes before responding again. Perhaps one time in 20, it will crash. The new disks are always visible when LDM returns.
There are generally no more than ten LUNs available to a given host.
The event log records dozens, sometimes hundreds, of event ID 257 from PlugPlayManager: "Timed out sending notification of target device change to window of LDM Service."
The Microsoft KB says these are harmless, and I see no indication to the contrary, but it seems like it should take much less time for the LDM to recognize new disks. Is this kind of lag normal?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2006 03:55 AM
10-30-2006 03:55 AM
Re: Win 2003 disk manager takes forever to find new vdisks
I have found that sometimes there is a lag.
When I go into LDM - if the disks do not appear on the first re-scan then come out of LDM and go back in then try again.
I have never experienced a lag of 10 minutes though.....
When I go into LDM - if the disks do not appear on the first re-scan then come out of LDM and go back in then try again.
I have never experienced a lag of 10 minutes though.....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2006 03:57 AM
10-30-2006 03:57 AM
Re: Win 2003 disk manager takes forever to find new vdisks
Perhaps lag is the wrong term.
The delay is in how long it takes for the LDM front end - be it diskpart or the Computer Management console - to become responsive again after I intitiate the command to rescan for new disks.
The vdisks are generally available instantly; the hold-up seems to be in the OS. I was wondering if this was a common problem, and if any changes to MPIO or anything else might make LDM more responsive.
The delay is in how long it takes for the LDM front end - be it diskpart or the Computer Management console - to become responsive again after I intitiate the command to rescan for new disks.
The vdisks are generally available instantly; the hold-up seems to be in the OS. I was wondering if this was a common problem, and if any changes to MPIO or anything else might make LDM more responsive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2006 11:55 PM
10-30-2006 11:55 PM
Re: Win 2003 disk manager takes forever to find new vdisks
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 2025 Hewlett Packard Enterprise Development LP