SSD + migrating OS

L

LeafMuncher

Well-Known Member
Joined
Dec 29, 2011
Messages
114
Reaction score
0
Location
Cape Town
Hi guys

Basically I have a SSD arriving today (Samsung 840 Evo), and I'm probably going to clone my C: onto it then format the old hard drive. Simple enough, but I also have another old OS drive containing the System flag that won't let me format (almost everything including windows folders deleted from it, using it to backup larger folders from C: to make space before cloning). Would it have any (major) effect on the boot time if I still have the older HDD containing the MBR? If it's a difference of only a couple seconds I'll just leave it as is, otherwise if it will have some noticeable effect I can just do a startup repair.

Does the System (boot sector) only affect the period before the windows logo starts loading? Thanks in advance.

Backstory: Got PC in 2011, only had x86 win7 copy (basic student license or something similar). Upgraded from 4gb ram to 16gb around March this year and installed separate x64 copy (Ultimate) I bought at the same time. Didn't do a format before new install because I had no swap space and didn't want to make partitions on the new drive.

Another question regarding TRIM. Leave it on in Win7 default or let the SSD software/firmware handle it? Found a lot of conflicting advice about it

Also any other advice on type of formatting or anything else I might need to do differently to set it up? (besides setting folder locations to storage drives)

Thanks in advance for any advice :)
 
use diskpart in an Administrative Command Prompt (type 'cmd' in start menu, right click and choose "run as administrator" and then type 'diskpart' followed by enter). You will have to do this while booting from a different drive (which I suspect you will have difficulty with judging from your post).

Remember that boot order is determined by your CMOS menu (pressing 'del' or 'f1-f10', depending on system, just after turning on machine) and by jumper plugs on older IDE drives (on the actual drive). If you edit your CMOS or jumpers you can choose any drive to be the boot drive
 
You misread my post (or I didn't explain properly). I know how to do all of that (diskpart, boot order, etc), I'm asking what effect it would have compared to leaving the MBR on the older drive. I'm only a newbie regarding SSD's and how to treat them.

Drive just arrived, they gave me an 840 Pro when I ordered the Evo ! W00t bonus!
 
LeafMuncher said:
Basically I have a SSD arriving today (Samsung 840 Evo), and I'm probably going to clone my C: onto it then format the old hard drive. Simple enough, but I also have another old OS drive containing the System flag that won't let me format (almost everything including windows folders deleted from it, using it to backup larger folders from C: to make space before cloning). Would it have any (major) effect on the boot time if I still have the older HDD containing the MBR? If it's a difference of only a couple seconds I'll just leave it as is, otherwise if it will have some noticeable effect I can just do a startup repair.
Click to expand...

You will have the issue of waiting for the older HDD to initialise and load up the MBR and then the system will handover to the SSD and you'll boot from there. It'll add on a delay, but we're talking about 2-4s because the MBR is usually tiny.

If you use Macrium Reflect to clone the OS over there is an option somewhere to repair the MBR on the drive, although I may be confusing the functionality between the free and paid versions.

As for Trim, let Windows handle it. Trim will run when the system is idle. Make sure you re-run the WEI assessment when you install the new drive because this lets Windows 7 know it has to optimise itself for a SSD.

Other recommendations are to disable Superfetch and disable indexing on the drive through My Computer>Properties and in Services. Don't worry about defragging and don't worry about wearing out the drive before the warranty's out.

The flash and the controller can easily outlive you.
 
The one thing I miss is not being able to Hibernate the PC using an SSD for the OS. Windows doesn't like it :(

Also noticed the machine gets blue screens of death way too often since changing to the SSD. With my next install of Win7 I will probably revert to my old HDD and only use my SSD to install games on it.
 
@Wesley Thanks, that answered everything I think :)
I was going to use EaseUS backup software for the clone but I'll check out Macrium Reflect instead.

Is the hibernation issue common or just something with Strontium? I tend to hibernate more than shut down :/
 
StrontiumDog said:
The one thing I miss is not being able to Hibernate the PC using an SSD for the OS. Windows doesn't like it :(

Also noticed the machine gets blue screens of death way too often since changing to the SSD. With my next install of Win7 I will probably revert to my old HDD and only use my SSD to install games on it.
Click to expand...

The SSD loves the sleep function. It's also recommended to use the sleep function.

As for your blue screen, it might have nothing to do with the SSD. Memory leaks via RAM is the likely cause.
 
LeafMuncher said:
Is the hibernation issue common or just something with Strontium? I tend to hibernate more than shut down :/
Click to expand...

Windows 7 and 8 work pretty well with hibernation on a SSD and if you'd prefer to use that, it's perfectly fine. SATA3 does this a lot better than older versions of the standard because it was too slow to make a difference. Hibernation is better utilised on notebooks than desktops, but I've made use of it on occasion.
 
Phew... What a headache...

Startup repair after making the clone thought it was a different version of windows, despite being the same disk I installed with...

Bootrec refused to work (found no Windows installation), "upgrade" install wanted me to boot into the detected installation of windows to repair it (kinda hard without BCD working...). Stupid loop right there... "Boot into Windows so you can get Windows to boot" "oh I don't see a Windows install, better Boot into Windows so you can install Windows" *scratches head* WindowsLogic.jpg

Could not edit the current BCD through bootrec command

Eventually changed all hidden/read-only properties of BCD file, deleted BCD. VOILA REPAIR RECOGNISED THE INSTALLATION, created BCD!

*facepalm of note*

Everything working now, thanks for the initial help guys xD
 
funkzar said:
The SSD loves the sleep function. It's also recommended to use the sleep function.

As for your blue screen, it might have nothing to do with the SSD. Memory leaks via RAM is the likely cause.
Click to expand...
Thanks, yeah my BSODs might have just been coincidental as I also tried to install new RAM at the same time (unsuccessfully due to not being compatible with mobo).

Regarding maximizing the life of one's SSD: http://lifehacker.com/5802838/how-to-maximize-the-life-of-your-ssd
 
One reason I hate the sleep function, it seems my PC is more prone to waking up on it's own. Last 2 nights it woke up (and me in the process) at 3am to bug me about Restarting to apply windows updates :mad: :(
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X