Uninstalled Linux OS dual boot with Windows 7 now boot issue.

whs · 25 Dec 2014

If bootmgr is located on C: in the 100Mb system partition

You are again confusing things. The bootmgr is in the system partition. That is an independent partition and not C.

When C was F that means that C was not the running OS at that moment but some other OS was running (or perceived as running). C is always the currently running OS.

For the G partition do what Greg suggested. But there is no need to make it a primary, can be a logical partition. On your whole installation only one single primary partition is a must - and that is the system partition. Only the partition that contains the bootmgr must be a primary. All other primaries are kind of 'optional' and do not really serve a purpose. They could all be logical partitions and would function just as well. But you can leave it as is - no harm done on your configuration.

GARoss · 26 Dec 2014

whs said:

If bootmgr is located on C: in the 100Mb system partition

You are again confusing things. The bootmgr is in the system partition. That is an independent partition and not C.

When C was F that means that C was not the running OS at that moment but some other OS was running (or perceived as running). C is always the currently running OS.

For the G partition do what Greg suggested. But there is no need to make it a primary, can be a logical partition. On your whole installation only one single primary partition is a must - and that is the system partition. Only the partition that contains the bootmgr must be a primary. All other primaries are kind of 'optional' and do not really serve a purpose. They could all be logical partitions and would function just as well. But you can leave it as is - no harm done on your configuration.

Thanks, I'll do that. My terminology is all wrong. I meant to say that system reserve & C driver were on the same hard drive.

GARoss · 26 Dec 2014

Success!

As a precaution I moved all data to another drive then processed. All went without a glitch. Thanks!

gregrocker · 26 Dec 2014

Looks fine but If possible I'd swap cables between Disks 0 and 1 so that Win7 HD is in Disk0 position, otherwise during Repairs or Reinstall it may derail the System flag to the first-in-order Primary partition. Make sure Win7 drive remains set first to boot in BIOS setup.

whs · 26 Dec 2014

The OS may be on Port 0. Disk Management does not map the ports correctly. And Port 0 may not be the fastest port anyhow. On some mobos, the Sata III ports are ports 2 and 3 or the last two.

Disk drive numbers may not correspond to the SATA channel numbers when you install Windows on a computer that has multiple SATA or RAID disks

gregrocker · 26 Dec 2014

Yes I am aware of that. But most are able to make this switch easily enough, avoiding the risk of Primary partitions preceding Win7.

whs · 26 Dec 2014

Agree if the Sata III port is port 0 - which is rarely the case. And a primary partition that is not active can preced Win7 - no harm done.

GARoss · 27 Dec 2014

I think it was important to return G: to Basic because eventually I'll have to upgrade to Windows 10 which I don't believe to be compatible with Dynamic drives.

I think I understand now why G: became a "Dynamic" drive. After deleting the Linux & swap partitions, I Expanded G: without formatting these to NTFS first. All appeared OK but 21Gb of data space was in purgatory, so to speak

. I discovered this when moving data off G: as a precaution while converting G: to Basic. File info indicated 21Gb of additional data remained on G: even after everything had been copied to another drive.

It easy enough to move C: to Port 0. Thanks again!

whs · 27 Dec 2014

Hopefully your port 0 is a 6Gb port - else you may lose SSD speed.

GARoss · 27 Dec 2014

Attachment 344404

whs said:

Hopefully your port 0 is a 6Gb port - else you may lose SSD speed.

Motherboard is Gigabyte GA-P67-UD3-B3_v1.1 . According to the manual, if I'm reading it correctly (see bottom attachment) , 0-1 are 6Gb while 2-6 are 3GB. CDM indicates C: is on port 1.