Volume Size is Incorrect - But I Can't Change It

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

I hope someone can point me in the right direction with this problem:

I have a RAID 1 (mirror) arrangement. Initially, this consisted of two 160GB drives. One of these failed, so I decided to replace both with larger (500GB) drives. To do this I removed the failed 160GB drive, installed one of the new 500GB drives and then rebuilt the mirror. I then replaced the working 160GB drive with the second new 500GB drive and rebuilt the mirror again. Everything works fine after this, except that the operating system (Windows XP) still thinks the RAID volume is only 160GB. I thought I could fix this by resizing the partition, so I bought Acronis Disk Director for this task. However, Disk Director will only allow me to resize the existing partition (C) at the expense of another partition. I'm stuck at this point, as there is no other partition. As far as Disk Director is concerned, it thinks the 160GB partition fills the entire disk and there is no unallocated space.

What can I do?

Scott

Sat, 11/07/2009 - 19:45
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 45
Comments: 4263

What disk size is reported for the RAID drive setup (160GB or 500GB)?

Does this size differ between DD and Disk Management?

Sat, 11/07/2009 - 21:48
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Disk Management and Disk Director both report the drive as 160GB. The Intel Storage Utility, which I used to build the RAID volume, reports this as 160GB but recognises the individual disk drives as 500GB.

Mon, 11/09/2009 - 19:44
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 45
Comments: 4263

The problem may have been caused because of the method you used to change the drives. I would have created a backup image and then restored that to the new RAID 0 setup.

Does the Intel Storage Utility give you an option to "expand" the configuration to use the additional space on the new drives?

Mon, 11/09/2009 - 20:54
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Yes, it was certainly a mistake to simply rebuild the RAID volume with the bigger drives. I didn't realise at the time that this would result in a volume the same size as the old one. The Intel Storage Utility doesn't provide any means to expand the volume to fill the available space. However, its an old version (v4.5) so maybe there is a newer version available which might be of use. I'm not very hopeful about this, as it seems that even a dedicated partition management tool such as Disk Director can't do it.

Tue, 11/10/2009 - 07:31