I'm running an Asus P5Q Pro Turbo and everything is working fine. I\nthink I'll do a Socket 2011 build one of these days, but not now.\nInstead I keep upgrading my current system with things like the 3TB\nSeagate HDD I installed earlier this week.\n\nThe new drive is working fine now, after a little bit of unexpected\nfiddling on my part. My system didn't know what to do with a 3TB drive,\nbut I figured out an inelegant workround. And now I have a question.\n\nFirst some brief background. When I built the system a few years ago I\nwanted to use RAID to join two 1.5TB drives into one big 3TB drive.\nThat meant choosing RAID in BIOS instead of IDE. I accomplished what I\nwanted -\- heck, I successfully joined three 1.5TB drives into a 4.5TB\nRAID drive, but the RAID array fell apart and I lost a lot of work.\n(Nothing I couldn't replace, as I had backups.)\n\nSo I just gave up playing with my MBO's flaky RAID and went back to a\nconfiguration I was more comfortable with. I am currently booting from\na 1TB drive (the largest possible, I think) and using my new 3TB drive\nplus two 1.5TB drives for data storage, video editing, etc.\n\nBut...and this is the root of my question...when building the system I\nhad already begun installing my OS (actually I triple-boot, so it's\nthree OSs) using the RAID controller on my P5Q MBO, and I just left\nthings that way because I discovered that when I set BIOS back to IDE,\nmy already-installed OSs wouldn't boot. (Windows 7 freezes when the\nfireflies begin to appear; use BIOS to set things back to RAID and Win7\nboots just fine.) And if you want to know why I didn't go back to IDE\nwhen I switched from XP to Vista to Win7 over the years, well, I dunno.\nThings were working fine? I didn't know better? Laziness? Take your\npick.\n\nAnyway, for all this time, running under the RAID controller without\nactually having a RAID array hasn't been a problem. I don't see drives\nin my main BIOS screen -\- I have to hit a function key (F10? Maybe,\nsomething like that) to bring up a RAID screen at boot, and from there I\ncan check on my drives. No problem, really. Until this week.\n\nTurns out the RAID controller wouldn't see all 3TBs of the new drive.\nIt would claim the drive was something less than 1TB, I don't remember\nthe size exactly.\n\nSo...I ensured the new drive was initialized GUID, disconnected all HDDs\nfrom the MBO, set BIOS to IDE, connected an empty spare drive, installed\nWin7 64-bit on it, connected the new 3TB drive, and voila! I was seeing\nall 3 terabytes (actually somewhat less, but we all know how that goes).\n\nThen I split the drive into two equal 1.5TB partitions, disconnected the\nspare drive with the new Win7 installation, set BIOS back to RAID,\nre-connected all the drives (including the new 3TB drive), and I was in\nbusiness. The RAID controller had no trouble dealing with a 3TB drive\ndivided into two 1.5TB partitions.\n\nSo all is well...for now. It's just that I am thinking of replacing my\nother two 1.5TB drives with 3TB drives, and I wouldn't want to partition\nthem. I'd want them to remain 3TB.\n\nBut I can't do that under RAID. And I can't simply switch back to IDE\nin BIOS because when I do, my OSs won't boot.\n\nYes, I know I could just rebuild my OSs from scratch under IDE, but\ngolly that would be a lot of work if there's a simpler way.\n\nAnybody know a simple way to make an OS built under RAID operate under\nIDE? Maybe? I hope? Thanks.