Solved Make boot drive disk 0 AND set system attribute, remove from H:

[Glaice]

Hello, I have 4 hard disk drives in my system, 3 Seagate (2 320GB, 1TB) and 1 Western Digital (1 160GB). One of the drives (the 160gb) is running very hot constantly (60C on average) and is also labeled as a "System" drive in Disk Management because it was once my original boot drive years ago. I want to take this drive offline because I fear it will eventually die and leave me to unable access Windows 7 without mucking with something.

I want to remove that from the drive and put it on the Boot drive, which is one of the 320GB drives but I also want to make C: (my OS drive) disk 0 but it is disk 1. I cannot format H: (the 160gb WD) yet there is nothing else but an emaciated/gutted XP install with several files which I cannot remove at any cost.

What would I have to do to get myself in working order to my specifics?

 

[VistaKing]

Hi Glaice

You could take a reading at the links below

:ar: http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

:ar: http://www.sevenforums.com/tutorials/681-startup-repair.html

:ar: http://www.sevenforums.com/tutorials/105541-startup-repair-run-3-separate-times.html

To make drive 1 to Drive 0 unplug all the hard drives but the one you want to be drive 0 and do a startup repair for it to be a boot drive.

Can you upload an image of your disk management

Link below will show you how

:ar: http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

 

[Glaice]

Hello, after doing some mucking around I was successful on fixing my boot/system drive designation and got everything all sorted out, despite C: still disk 1

 

[VistaKing]

Which is your Second hard drive . What port on the motherboard is it connected to ?

 

[gregrocker]

It would be best if we see the Disk Mgmt screenshot requested since there may be other complications you're not aware of yet. Disk Management - Post a Screen Capture Image - Windows 7 Forums

The normal way to move the System flag is mark the target partition Active and run Startup Repair - Run up to 3 Separate Times which covers many different parameters whereas other fixes will leave something out like the Repair console on F8 boot tools menu.

 

[Glaice]

I think the problem was that H was in SATA1 while C was in SATA 2 or 3 I had to rearrange things while removing the 160 gig and 120mm fan.

 

[VistaKing]

Is your Drive C now Disk 0 ?

 

[gregrocker]

And is it marked System Active? Let's see the screenshot.

 

[Glaice]

Drive E (320GB) is disk 0, drive C is disk 1 (which is also system and boot which is good ) and the terabyte drive D is disk 2. The two 320s are unmarked and identical so I had to play a guessing game which one had the OS on it. I know the terabyte drive is in SATA3 or SATA4 (DVD drive uses one port methinks)

 

[gregrocker]

As long as Disk0 doesn't get marked Active to derail the System files during a Repair or Reinstall then you can keep it the way it is, tho I'd want Win7 in Disk0 slot, set first to boot in BIOS of course.

Otherwise it looks right. Don't know how you moved the boot files but all of the flags are correct. If you don't have Repair Console on F8 menu then run Startup Repair a few times from DVD or Repair CD.

 

[Glaice]

When I removed H from the system the computer was confused because that drive had System marking on it while the new C had just Boot as it ran fine since I added a terabyte drive in January. I did have to do a repair to fix the boot issues and designated C as Active, System and Boot.

PS: What does "Active" drive flag do anyways?

 

[VistaKing]

Makes the drive bootable

 

[gregrocker]

When I removed H from the system the computer was confused because that drive had System marking on it while the new C had just Boot as it ran fine since I added a terabyte drive in January. I did have to do a repair to fix the boot issues and designated C as Active, System and Boot.

PS: What does "Active" drive flag do anyways?

Active flag is only to designate the drive to boot, but it requires making it bootable by moving the System boot files there and rewriting the bootsector with bootsect /nt60 code.

All of this is automated when you run Startup Repair - Run up to 3 Separate Times