Thanks for the info so far. Now, can SOMEONE post the instructions for REMOVING that partition? I had a nice clean install going with Disk 1 1TB for System, and Disk 2 + 3 at 2TB each for a planned RAID 0 striped volume set under windows 7 - but suddenly
I'm sitting with an extra 100MB partition on one of the volumes I want to use in the RAID0 set. What a crock.
I have 1 Windows Server 2008 R2 machine here with the "desktop experience" turned on - and 2 Windows 7 64-bit machines - all identical Core i7's with 12GB of RAM and 5TB of total disk - but I don't want random 100MB partitions on RAID sets that might get
moved between machines at any time (yes Server can do that).
The instructions at the 'mydigitallife' posting seem to be correct in that pre-partitioning the drives seems to be the solution - I installed Win7 on one machine with all the drives unpartitioned and ended up with this little microsoft mess.
I need a way to remove this partition AFTER install - the windows disk management utility in 'computer management' does not seem to be able to manipulate this partition at all - I'll try boot from CD to WinPE and fry the partition then - but the point IS
NOT that the machine might not boot after removal - it's the hairball that created the partition in the first place - at least ask people if they want extra trash strewn about on their clean disks before putting stuff there - putting something 'extra' on a
RAID set is totally unnacceptable and will now cause wasted time as we reinstall until we get past the stupidity. - 1 idget in redmond wastes 1000's of hours of real peoples time - so typical. QA should catch this stuff. And whoever coded it this way should
spend extra time back in PSS answering phones and emails from needlessly provoked users like me.
thanks for letting me rant. now let's go fix this little amusement.