Solved Creating system image of HDD for re-image to SSD

[Roo Boy]

thanks WHS
How do i know that TRIM is working? Is it automatically activated under windows 7? There were no driver updates or anything like that when i rebooted for the first time after instal but i thought this may have been all done by the intel installation software that came with the SSD

 

[whs]

The command is:

fsutil behavior query DisableDeleteNotify​

If the result is '0' TRIM is enabled.​

 

[Britton30]

Read this:
http://www.sevenforums.com/hardware-devices/186212-trim-question.html#post1575860
Ooops, posted same time as whs.

 

[whs]

Gary, have to be fast around here,

 

[Roo Boy]

thanks again guys. It shows "0" so all good

I just downloaded AS SSD benchmark tool and ran a test.

Can you guys have a look at the result and see if this looks right? I thought the SEQ Read Write should be faster.

http://img197.imageshack.us/img197/8513/ssdbench.JPG

Thanks in advance

p.s. this is running off a SATAII board

 

[whs]

Hmm, you want the thruth and nothing but the truth ==> the scores are low to medium.

The scores to focus on are 4k R/W and Access time.

 

[Roo Boy]

any suggestions as to why on a brand new Intel 520 SSD??

surely its not bottlenecked that much by sata2

 

[whs]

Sata2 should not be the problem. All those nums are well within Sata2 capability. Suggest to run Atto and see what that yields.

http://www.attotech.com/products/product.php?sku=Disk_Benchmark

 

[Roo Boy]

what would i be looking for with the results of that program or do you just want me to post the pic?

edit:

Here are the results of ATTO - doesnt look any more impressive

http://img515.imageshack.us/img515/7356/attobench.jpg

why would this be?

 

[whs]

That looks better. As I said, for the OS you have to focus on the 4K numbers (and the Access time). The bigger blocks are hardly or never used by the OS and are therefore only of academic interest.

The average access time is around 0.1ms - some are half of that.

Here are Atto numbers of my old M4. Although it is not that great with the large blocks (which is anyhow irrelevant), the 4K nums are OK.

 

[Roo Boy]

i was expecting to see read and writes in the 3-400's like ive seen from other peoples bench results.
do you think running it in a laptop that uses an i3 390 is affecting it?

 

[whs]

Nah, the CPU should not have any bearing on it. And again, focus on the 4K R/W, the rest is pretty irrelevant.

 

[chev65]

1. If e.g. the bootmgr sits on another partition, many people forget to image that partition (because it is hidden and they never look into Disk Management) or copy the bootmgr to C.

2. Depending on the imaging program you use, you may get your SSD aligned or not. That's why it is always prudent to predefine an aligned primary active partition into which you can dump the image.

3. When you install an OS to a SSD via an image, there is no installer that makes the settings for you. E.g. you will have to disable defrag yourself and maybe make a few other settings to optimize the space on the SSD.

4. Windows 7 imaging works or it doesn't. In my experience it did not work many times.

I think I had it backwards, I was taking my image from my SSD and saving it to a regular HDD, using that same image back to my SSD never a problem there. I'm pretty sure this is how everyone is doing it these days.

But creating an image of a regular HDD then putting that onto an SSD would be more problematic as you suggested, because the image was made from a regular HDD. Although that may be problematic no matter which imaging software was being used.

So the clean install would be the way to go there.

 

[Britton30]

Windows backup does at it wishes, no adjustments possible, you use it or not. The free Macrium is quite flexible and does a great job, even, say, restore a bigger partition to a smaller one and vice versa. (Ex. 500GB with 100GB data to a 128GB drive.)
I admit I haven't done it a lot, only 15-20, but Macrium has alway been spot on! I can even image a system with, say, two drives to two drives.
Ahh, you edited the post, thanks. As for a HDD image restored to a SSD I think is what causes many people problems.

Why bootmgr ends up on anther drive? People do odd things trying to do odd things.

 

[whs]

Rob, I never had problems moving systems with Macrium images from Hdds to SSDs. The only things you have to make sure is that you move the bootmgr also and that the data fits on the SSD. I never move the 100MB partition because I alway copy the bootmgr to C. http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html