- Community Home
- >
- Servers and Operating Systems
- >
- Server Clustering
- >
- Windows 2003 Cluster, disk shown as empty in disk ...
Server Clustering
1753797
Members
7917
Online
108805
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-17-2008 03:36 AM
11-17-2008 03:36 AM
Windows 2003 Cluster, disk shown as empty in disk management
We have a two node Windows 2003 cluster, which uses EVA4000 as shared disk space. EVA has two disk groups, one for online and one for near-online disks. Last week we transferred few cluster disks to near-online group. We did this via mirrorclone with following steps:
1. create mirrorclone
2. shutdown both cluster nodes
3. unpresent original disks from cluster nodes
4. fracture mirror to make mirrored disk into two independent virtual disks
5. present mirrors with same lun id from near-online group
6. startup cluster nodes
Everything worked almost fine (only thing was little delay in problematic disk to bring back its original name), except yesterday when we tried to extend one of those disks. EVA extends the disk fine and it is even shown in disk management as free space. Diskpart is missing the whole volume and in upper window of disk management it says that disk is empty and the filesystem column is empty for problem disk. If I check from disk properties it says that the disk is raw. Anyhow, the disk is still usable for read and write through explorer and only thing that is missing is the disk name. Now the disk is named as "Local disk" instead of it's original name.
We took snapclone from the disk and presented clone to another server which couldn't mount the disk at all. I changed automount enabled with diskpart and unpresented/presented the disk back and then it was mounted but shown as empty in disk management. In explorer disk is usable and even the disk name has appeared to be the original one.
Tools chkdsk, chkntfs, fsinfo shows that NTFS is and the disk itself is ok.
Does anyone ever had similar problem and how was it repaired?
BR,
Jani
PS. I posted this message originally to Windows Server 2003 forum http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1286352
1. create mirrorclone
2. shutdown both cluster nodes
3. unpresent original disks from cluster nodes
4. fracture mirror to make mirrored disk into two independent virtual disks
5. present mirrors with same lun id from near-online group
6. startup cluster nodes
Everything worked almost fine (only thing was little delay in problematic disk to bring back its original name), except yesterday when we tried to extend one of those disks. EVA extends the disk fine and it is even shown in disk management as free space. Diskpart is missing the whole volume and in upper window of disk management it says that disk is empty and the filesystem column is empty for problem disk. If I check from disk properties it says that the disk is raw. Anyhow, the disk is still usable for read and write through explorer and only thing that is missing is the disk name. Now the disk is named as "Local disk" instead of it's original name.
We took snapclone from the disk and presented clone to another server which couldn't mount the disk at all. I changed automount enabled with diskpart and unpresented/presented the disk back and then it was mounted but shown as empty in disk management. In explorer disk is usable and even the disk name has appeared to be the original one.
Tools chkdsk, chkntfs, fsinfo shows that NTFS is and the disk itself is ok.
Does anyone ever had similar problem and how was it repaired?
BR,
Jani
PS. I posted this message originally to Windows Server 2003 forum http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1286352
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