- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Drive expansion succeeded Windows directory si...
ProLiant Servers (ML,DL,SL)
1753480
Members
4770
Online
108794
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
12-12-2005 08:53 AM
12-12-2005 08:53 AM
Drive expansion succeeded Windows directory size shows unchanged
We have 2 Proliant servers in a Cluster configuration attached to an MSA1000, We swapped all the 72 gig drives with 145 gig drives on at a time and let them rebuild, next we did an expansion and then made the changes in the Windows OS.
This process was done on sets of drives.
Both look successful in ACU, Diskpart, and the disk administrator Grapical discription of the drive, however doing a directory of the drive in dos, or in windows shows the orrriginal 67 gigs of space.
Has anyone seen this and is there a fix?
This process was done on sets of drives.
Both look successful in ACU, Diskpart, and the disk administrator Grapical discription of the drive, however doing a directory of the drive in dos, or in windows shows the orrriginal 67 gigs of space.
Has anyone seen this and is there a fix?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2006 09:21 AM
01-31-2006 09:21 AM
Re: Drive expansion succeeded Windows directory size shows unchanged
Robert:
Are you running Windows 2000? If so, which service pack are you at?
There is a known issue with diskpart pre Windows 2000 SP4. There is a hotfix available to prevent the issue from happening, but you need to call Microsoft to get a walkthorugh on how to fix the actual disk that has the issue already. There are a few threads on the subject. I will post links as I run across them again.
I believe the same can happen if you don't use the correct version of diskpart.exe on your Windows Box. There are 3 different versions. 1 for XP, 1 for 2000 and 1 for 2003. i believe I read somewhere that using the 2003 version on 2000 can cause the same or similar issue. (or perhaps the 2000 version on Windows 2003, something like that).
Steven
Are you running Windows 2000? If so, which service pack are you at?
There is a known issue with diskpart pre Windows 2000 SP4. There is a hotfix available to prevent the issue from happening, but you need to call Microsoft to get a walkthorugh on how to fix the actual disk that has the issue already. There are a few threads on the subject. I will post links as I run across them again.
I believe the same can happen if you don't use the correct version of diskpart.exe on your Windows Box. There are 3 different versions. 1 for XP, 1 for 2000 and 1 for 2003. i believe I read somewhere that using the 2003 version on 2000 can cause the same or similar issue. (or perhaps the 2000 version on Windows 2003, something like that).
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)
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