Saved Bookmarks
| 1. |
Solve : no increase in RAID 1 array volume size after drive replacements!? |
|
Answer» Quote from: pacorod on July 16, 2007, 01:28:31 AM Partition MAGIC is recognizing a 160 GB drive, not a 300 GB drive, even though the 300 GB drive is in use. I see from the manual that Partition Magic only supports partition sizes up to 160 GB. I never knew that before. However Acronis Disk Director Suite includes Partition Expert which supports partitions greater than 160 GB, up to 2 TB I think. *censored*. you're right. i'll get acronis disk director and i'll get back to you. thanks for replying to my problems, by the way.Contrex, I got Acronis Disk Director Suite 10.0. When i start the program it begins by analyzing the partitions, then a window pops up. Under "Disk 1" three partitions are represented by three hard drive icons. ONE is called NTFS (C:), another is FAT 16, and the remaining one is FAT 32. NTFS (C:) has a total size of 145.6 GB, FAT 16 has a total size of 67.72 MB, and FAT 32 has a total size of 3.332 GB, for a grand total of 149 GB...NOT 300 GB. Then, when I try the "Increase Free Space" operation, I select the NTFS (C:) partition as the partition I would like to increase in size, but then it asks me to select a partition from the remaining two (FAT16 and FAT32) from which to extract free space. So, increasing the partition size to near 300 GB is not possible. Please advice. Thank you.Have you got LBA enabled for this disk in the BIOS? I asked you before about 48 bit addressing but you replied about "64 bit technology" so I don't think you understood. You are absolutely sure this is a 300 GB disk? What is the maker and model number? It's a Seagate Barracuda 300 GB Serial ATA/300, 7200 RPM, 16 MB cache, model no. ST3300620AS What is LBA?Sorry if my previous post seemed a bit rude, I was typing in a hurry. Some BIOSes need to have Large Block Addressing enabled to recognise disks greater than about 160 GB. I wonder if that is the reason why you can't resize your partition. If you go into your BIOS and check the hard drive properties, it may give a clue about the problem. Well, 48-bit addressing must be enabled, since I have an additional hard drive, external to the RAID array, that is recognized by the OS as being of 230 GB capacity, and it's about 85% full. So, I would assume LBA is enabled, and I can't find anything related to it in the BIOS. Also, the RAID controller i'm using is Intel's Storage Utility, version 4.0. I've tried deleting the Array, but I get a message ALONG the lines of "this is a system volume that cannot be deleted", and i've tried "Create RAID volume from existing hard drive", but it informs me "There are not enough available non-RAID hard drives to create a volume from existing hard drives", even though I have a non-RAID hard drive in use. So, i'm running out of ideas, and help would be highly appreciated. I see Jephree TOLD you the answer on D-A-L. Alright, so I read Jephree's "solution", and i'm guessing he might be right. The array was set during installation of Windows. BUT!! Listen to this...Intel's Storage Utility (the RAID controller) has a "create RAID volume" function that creates a RAID volume across two hard drives. As I mentioned before, I have two 300 GB hard drives and the original 160 GB hard drive. Now, the 300 GB hard drives contain the same information as the 160 GB hard drive...all three drives are mirrors of each other. This happened when I rebuilt the RAID volume when installing the larger-capacity drives. Now, I could use the "Create RAID volume" function and create a new RAID volume using the 300 GB drives (which implies erasing all data currently on the drives) and then migrating the data from the 160 GB drive to the new RAID array. However, I have no idea how to migrate, or create an image of, the data on the 160 GB drive on the newly-created 300 GB RAID volume. I think this would work, but I need help with the image/migration part... Symantec (Norton) Ghost can image one disk onto another. The RAID volume would appear to Ghost as a single drive. |
|