Have you tried the ReScan disk option under "Action" in disk management ?
Is this a MBR disk and possibly already reached the 2 TB limit ?
Although the disk size will increase in Disk Management, the existing partitions will be the same. The extra space will show up as "un-allocated space" in disk management to the right of the existing partitions.
2 TB lmit not a factor. New array size should be around 400 Gb. The raid 5 array is not partitioned. No unallocated space is reported by DOMSA. Thanks for the suggestion of rescan I haven't tied that yet but will.
Did you read this? "Although the disk size will increase in Disk Management, the existing partitions will be the same"
Did you go into Windows Diskmanager ? The VD size in DOMSA is NOT the same as Windows operating system partitions. You need to expand the operating system's partition either in DiskManager or a 3rd party partition manager.
Admin4U
112 Posts
0
July 31st, 2015 19:00
Have you tried the ReScan disk option under "Action" in disk management ?
Is this a MBR disk and possibly already reached the 2 TB limit ?
Although the disk size will increase in Disk Management, the existing partitions will be the same. The extra space will show up as "un-allocated space" in disk management to the right of the existing partitions.
aforby
2 Posts
0
August 1st, 2015 11:00
2 TB lmit not a factor. New array size should be around 400 Gb. The raid 5 array is not partitioned. No unallocated space is reported by DOMSA. Thanks for the suggestion of rescan I haven't tied that yet but will.
pcmeiners
4 Operator
•
1.8K Posts
0
August 1st, 2015 19:00
If you can write to the raid 5, it is partitoned.
Did you read this? "Although the disk size will increase in Disk Management, the existing partitions will be the same"
Did you go into Windows Diskmanager ? The VD size in DOMSA is NOT the same as Windows operating system partitions. You need to expand the operating system's partition either in DiskManager or a 3rd party partition manager.