me@work wrote:I would like to suggest to go route 2b:
Create a new disk group with the new two 300GB disks, initialize a RAID-1 on this disk group, then dd the complete partition data from the old group to the new one, and finally set the new Virtual Drive as Boot VD.
Ok tnx, but isn't this the same as a array rebuild on larger drives ?
VD-1 = 70gb.
VD-2 = 300gb.
Copy (dd) vd-1 to vd-2, the array size will still be the same, 70gb, or do you get the option to expand vd-2 after the copy because vd-2 was initialized as raid-1 / 300gb ? in other words if the array was created with a Y size you can copy a smaller array X onto array Y, where my concern is being able to expand X sitting on a larger Y and also 'who/what', ea. array software, bios, dd option, etc...
me@work wrote:Where do you conclude that the previous two 73GB disks were run in a RAID-1? Perhaps someone recently increased the available space by migrating from the initially installed RAID-1 to a RAID-0 (which, in fact, can be done, and results in doubling the usable space, while giving up redundancy, of course).
When you look at picture 3 you see a raid-0 definition with 2 'segment 1' disks each of 67gb and a total array size of 67gb which tells me this is a raid-1 setup and not a raid-0 as the screens would make you believe.
This conclusion is backed-up when we swapped the original 67gb disks with 300gb disks one by one and the array being rebuild twice. So it is definitely a raid-1 but the software is 'seeing' a raid-0.