Unable to create simple volumes on 3TB GPT Hard Disk (Windows 7)
Hi Experts,
I have a new 3TB Hard Disk, in an enclosure connected by USB 3.0 to my Windows 7 Desktop PC.
I have initialized the drive as GPT.
But I cannot create a Simple Volume - as a test I used the default, maximum size.
I get this error:
I've tried all the suggestions in that message, to no avail.
Earlier I used PartMagic to define 3 simple volumes - but my Windows 7 Desktop PC would not recognize any of them (Disk Management console showed the sizes, but not the drive letters).
Interestingly, at that time my Windows 7 laptop recognized all of the volumes.
I wonder if there is an issue with the BIOS on my Desktop PC?
BTW - I have other 3TB drives in USB 3.0 enclosures that work OK with my Desktop PC.
I then decided to wipe the GPT disk using this process:
Open an elevated command prompt, typeed
diskpart [press enter}
list disk
select disk x (if x is the number of the disk in question)
clean
After my latest attempt to create the single Simple Volume, Diskpart gives this output:
Regards,
Leigh
I have a new 3TB Hard Disk, in an enclosure connected by USB 3.0 to my Windows 7 Desktop PC.
I have initialized the drive as GPT.
But I cannot create a Simple Volume - as a test I used the default, maximum size.
I get this error:
The operation failed to complete because the Disk Management console view is not up-to-date. Refresh the view by using the refresh task. If the problem persists close the Disk Management console, then restart Disk Management or restart the computer.
I've tried all the suggestions in that message, to no avail.
Earlier I used PartMagic to define 3 simple volumes - but my Windows 7 Desktop PC would not recognize any of them (Disk Management console showed the sizes, but not the drive letters).
Interestingly, at that time my Windows 7 laptop recognized all of the volumes.
I wonder if there is an issue with the BIOS on my Desktop PC?
BTW - I have other 3TB drives in USB 3.0 enclosures that work OK with my Desktop PC.
I then decided to wipe the GPT disk using this process:
Open an elevated command prompt, typeed
diskpart [press enter}
list disk
select disk x (if x is the number of the disk in question)
clean
After my latest attempt to create the single Simple Volume, Diskpart gives this output:
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 38 GB
Disk 1 Online 465 GB 77 GB
* Disk 2 Online 2794 GB 0 B * <<< this is the troublesome disk Regards,
Leigh
if disk 2 is selected, what is the output of the command create part pri ?
also -i assume you started diskpart from an elevated command prompt?
also -i assume you started diskpart from an elevated command prompt?
ASKER
Hi Nobus:
I ran Diskpart from an elevated command prompt .
See below for the output from "create part pri".
I ran Diskpart from an elevated command prompt .
See below for the output from "create part pri".
DISKPART> select disk 2
Disk 2 is now the selected disk.
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 38 GB
Disk 1 Online 465 GB 77 GB
* Disk 2 Online 2794 GB 0 B *
DISKPART> clean
DiskPart succeeded in cleaning the disk.
DISKPART> create part pri
Virtual Disk Service error:
The operation timed out.
DiskPart has referenced an object which is not up-to-date.
Refresh the object by using the RESCAN command.
If the problem persists exit DiskPart, then restart DiskPart or restart the
computer.
DISKPART>
you first have to run
convert gpt
what was the result from the 'rescan' that diskpart said you had to run?
convert gpt
what was the result from the 'rescan' that diskpart said you had to run?
David, his drive is already GPT as far as I can see from the output.
Looks like it is a problrm of USB box. Does the drive work ok when connected internally?
Looks like it is a problrm of USB box. Does the drive work ok when connected internally?
oops missed the * in the gpt column
ASKER
I have run DiskPart a number of times:
Each time the "create partition primary" command fails, the disk is fully allocated, so I have to do another "clean".
Here's the typical DiskPart sequence:
Each time the "create partition primary" command fails, the disk is fully allocated, so I have to do another "clean".
Here's the typical DiskPart sequence:
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: POTOROO7
DISKPART> select disk 2
Disk 2 is now the selected disk.
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 38 GB
Disk 1 Online 465 GB 77 GB
* Disk 2 Online 2794 GB 0 B *
DISKPART> clean
DiskPart succeeded in cleaning the disk.
DISKPART> create part pri
Virtual Disk Service error:
The operation timed out.
DiskPart has referenced an object which is not up-to-date.
Refresh the object by using the RESCAN command.
If the problem persists exit DiskPart, then restart DiskPart or restart the
computer.
DISKPART> rescan
Please wait while DiskPart scans your configuration...
DiskPart has finished scanning your configuration.
it looks like a bad disk to me - or you have problems with the USB 3 connection
(bad cable? replace it for testing)
i would attach it to a sate cable - not over USB
btw - does the disk have it's own power supply? that often helps also
(bad cable? replace it for testing)
i would attach it to a sate cable - not over USB
btw - does the disk have it's own power supply? that often helps also
Repeating my question: Looks like it is a problrm of USB box. Does the drive work ok when connected internally?
ASKER
As I mentioned in my original post:
>> Earlier I used PartMagic to define 3 simple volumes - but my Windows 7 Desktop PC
>> would not recognize any of them (Disk Management console showed the sizes, but not >> the drive letters).
>> Interestingly, at that time my Windows 7 laptop recognized all of the volumes.
>> I wonder if there is an issue with the BIOS on my Desktop PC?
>> BTW - I have other 3TB drives in USB 3.0 enclosures that work OK with my Desktop PC.
I have just swapped the USB drive enclosure for another one.
The new drive enclosure is working OK because it had another, fully populated 3TB drive in it that was fully recognized by Windows.
When I put the problematic 3TB drive into the new enclosure it gives all the same symptoms as before.
So could the drive be faulty? Even if it worked with my laptop?
Could there be some BIOS settings on my Desktop PC that are relevant?
>> Earlier I used PartMagic to define 3 simple volumes - but my Windows 7 Desktop PC
>> would not recognize any of them (Disk Management console showed the sizes, but not >> the drive letters).
>> Interestingly, at that time my Windows 7 laptop recognized all of the volumes.
>> I wonder if there is an issue with the BIOS on my Desktop PC?
>> BTW - I have other 3TB drives in USB 3.0 enclosures that work OK with my Desktop PC.
I have just swapped the USB drive enclosure for another one.
The new drive enclosure is working OK because it had another, fully populated 3TB drive in it that was fully recognized by Windows.
When I put the problematic 3TB drive into the new enclosure it gives all the same symptoms as before.
So could the drive be faulty? Even if it worked with my laptop?
Could there be some BIOS settings on my Desktop PC that are relevant?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I bought another 3TB drive - same symptoms when connect via USB.
Have tried connecting the 2 drives (one at a time) via SATA cable.
Both drives give the same warning message when booting Windows:
I ran the WD Data LifeGuard Diagnostics on one disk:
It reports the size as 3TB
How do I get Windows to recognize the correct size?
Have tried connecting the 2 drives (one at a time) via SATA cable.
Both drives give the same warning message when booting Windows:
The detected total capacity (746 GB) of the drive is not correct, .......... the capacity should be 2794 GB.
I ran the WD Data LifeGuard Diagnostics on one disk:
Test Option: QUICK TEST
Model Number: WDC WD30EZRX-00D8PB0
Unit Serial Number: WD-WCC4N6CTUPYE
Firmware Number: 80.00A80
Capacity: 3000.59 GB
SMART Status: PASS
Test Result: PASS
Test Time: 15:12:21, November 23, 2015It reports the size as 3TB
How do I get Windows to recognize the correct size?
ASKER
I forgot to mention:
When I first connected one of the drives after I got the Windows warning:
I ran DiskPart and did a Clean on that drive - that did not fix the above issue.
When I first connected one of the drives after I got the Windows warning:
The detected total capacity (746 GB) of the drive is not correct, .......... the capacity should be 2794 GB.
I ran DiskPart and did a Clean on that drive - that did not fix the above issue.
are you running a 32 bit OS? that only detects 2TB max
that is surely why it does not work as expected
click Start>righ click "My computer">select properties
that is surely why it does not work as expected
click Start>righ click "My computer">select properties
ASKER
Hi Nobus,
No, definitely 64 bit OS.
No, definitely 64 bit OS.
after the rescan, did you retry the create disk part ?
According to this discussion the problem is in an Intel driver: http://www.hdsentinel.com/forum/viewtopic.php?f=32&t=1572&start=20
They suggest using proper intel chipset driver. Give it a try.
They suggest using proper intel chipset driver. Give it a try.
ASKER
I identified the intel chipset and downloaded the driver from the Support -> Driver Zone page at www.hdsentinel.com.
Now all hell has broken loose!
All attempts to boot give BSOD.
I have removed all drives (including the 3TB one), just leaving the SSD that has the C: and D: volumes.
The good news is that I can boot WinPE and it sees both C: and D: volumes,
I have run "Check for errors" and both volumes pass OK.
To avoid this topic being drawn out further, I have posted this one:
BSOD attempting to boot Windows 7
Now all hell has broken loose!
All attempts to boot give BSOD.
I have removed all drives (including the 3TB one), just leaving the SSD that has the C: and D: volumes.
The good news is that I can boot WinPE and it sees both C: and D: volumes,
I have run "Check for errors" and both volumes pass OK.
To avoid this topic being drawn out further, I have posted this one:
BSOD attempting to boot Windows 7
Does the Restore to System Restore Point help? Usually the Windows takes automatically restore points before doing system modifications.
ASKER
We have solved this question:
BSOD attempting to boot Windows 7
But I still have a "missing" volume, see: NTFS Volume no longer accessible
BSOD attempting to boot Windows 7
But I still have a "missing" volume, see: NTFS Volume no longer accessible
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, David Johnson, Nobus & Noxcho, for all your help.
I have switched to Windows 10 - and I now have no problems creating and editin volumes!
Regards,
Leigh
I have switched to Windows 10 - and I now have no problems creating and editin volumes!
Regards,
Leigh
from diskmgmt.msc initialize the disk or from diskpart
Convert GPT