New
#100
What type Raid did you create. It could very well be that the small disk rules the size - e.g. in Raid 1.
What type Raid did you create. It could very well be that the small disk rules the size - e.g. in Raid 1.
I didn't create a new RAID array due to the drive size discrepancy; the new drives are both 3TB. The old RAID fully used 1TB disks; I wonder how Maingear made that work. I may have to call them.
Edit: RAID 1
I just found the Asus P6T support pages where I found a BIOS update that fixes incorrect drive size display for HDs >2.2TB. I also downloaded the user manual so I can learn how to update the BIOS if my current version is older.
I'm sure glad I'm learning things. This would be so much more tedious if I wasn't.
Well, I flashed the BIOS and found that the update makes Windows 7 recognize the larger drives properly. But Intel Matrix Storage Manager didn't run during the boot because the updated BIOS set SATA HD types to IDE. I changed it to RAID, whereupon IMSM started.... and showed the new drive sizes as 746 GB.
The IMSM in ROM is obviously the problem. It might be possible to update it to Intel Rapid Storage Technology, but the process is too involved, and the results too uncertain, for me to be comfortable with it.
IMSM should properly recognize 2TB drives, so I'll buy a couple of those (which, in retrospect, I should have done in the first place) and save the larger drives for future use. At least I'm booting from the correct drive now.
Hello, I had to change my mobo and CPU, and have cloned one SSD to another (O&O DiskImage), including the 100MB partition. Reinstalling Windows is not an option, and the old SSD is no longer available.
Win 7 works fine on the new SSD, but does not see the extra cores on the new cpu (i7 vs old i5). There are no advanced boot options available in msconfig to change this, apparently because msconfig looks to the 100 MB partition.
It seems like the solution is to move the bootmgr as you have been discussing. When I run the free Easy BCD I get the message "The boot configuration data store could not be opened. The system cannot find the file specified. Would you like to manually load a BCD registry for EasyBCD to manage? ..."
Would I give the 100 MB partition a drive letter so I can point EasyBCD to it, or is that not what it is asking for? If I give the partition a letter, will it mess up the booting process somehow? Thanks!
Here is the SSD:
(Attached, I hope)
Last edited by Vangelas; 28 Dec 2014 at 00:04. Reason: Picture didn't show up
Please post a screenshot of what is telling you that Win7 doesn't see the extra cores in i7. I've never heard of this. Those settings in msconfig are only used for troubleshooting and not to adjust this at all.
What did you use to adjust the Win7 image to the new hardware? It's possible you have older mobo drivers. I would enable Automatically deliver drivers via Windows Update (Step 3)
and install all Important and Optional as there are often important hardware updates and drivers queued in Optional. I'd also scrutinze closely your mobo drivers to see what's installed.
Task manager shows 4 cores instead of 8; utilities like dbpoweramp only show 4 cores when converting files instead of 8, etc. The settings in msconfig are not available at all; I should be able to adjust the number of cores there. From what I have read, this is due to Windows looking at the first partition (100MB) instead of the C: partition.
Nothing was done to adjust the image to the new hardware. All Windows updates are set for automatic.
Automatically deliver drivers via Windows Update (Step 3) is not set in Windows Update. After enabling it then Check for Updates again.
I've asked hardware experts to look at this but it doesn't sound like something that changing boot mgr will remedy, mainly because those settings in msconfig are for troubleshooting purposes only and users have gotten in trouble in the past trying to change them.
The screenshot does not indicate that all cores are not being utilized.
Last edited by gregrocker; 29 Dec 2014 at 12:30.