changing out old ssd for new and bigger

[gemm85]

What problems will I face removing old ssd for new and bigger ssd

 

[ignatzatsonic]

What problems will I face removing old ssd for new and bigger ssd

None if you do it right and the hardware is not defective.

Do you intend to do a clean install to the new SSD?

Or do you want to transfer the existing installation on the old SSD to the new SSD? If yes, then how?

Or?

 

[ben946210]

If you are simply migrating to a larger drive, you could use EaseUS Todo Backup or Acronis which both a clone feature on them. I have personally used EaseUS before in the past.

 

[Boozad]

A Macrium image would be another option.

 

[whs]

I would make a clone with free Macrium or free AOMEI Backupper. That's the easiest. If you go the image route, you have to watch the alignment. Macrium keeps the alignment if you do it right. Read the rules under 'Advanced Topics': Reflect_v5

 

[BugOutMachine]

If you are simply migrating to a larger drive, you could use EaseUS Todo Backup or Acronis which both a clone feature on them. I have personally used EaseUS before in the past.

Agreed! You can't go wrong with either solution and switching drives will be smooth.

 

[gemm85]

Thanks guys--think I will try the Macrium clone. when it comes to software I'm like an old college roommate who used to say--" I don't understand all I know about this", I was a mechanic and holding things in my hand is easier than holding them in my head.

 

[whs]

When you are done with the clone, you will have a lot of unallocated space on the new SSD because it is bigger than the old one. Just right click on C (in disk management) and extend C to include that space.

 

[ignatzatsonic]

Thanks guys--think I will try the Macrium clone. when it comes to software I'm like an old college roommate who used to say--" I don't understand all I know about this", I was a mechanic and holding things in my hand is easier than holding them in my head.

Be aware that Macrium gives you 2 methods to transfer a system to another drive: cloning and imaging.

I'd probably try imaging even though cloning may work---if for no other reason than that you should familiarize yourself with Macrium imaging and continue to use it in the future to backup your existing Windows installation---which cloning does not do.

 

[whs]

I think for his case, cloning is easier. It takes a little longer than making an image but then it is only a one stop shop. But you are correct to point out the importance of frequent images.

 

[Layback Bear]

Okay ignatzatsonic and whs; so I and others might understand better could you give the plus and minus using a image or a clone?

 

[whs]

A clone is a one step operation and in case of to and from SSDs, you don't have to worry about alignment. You do, however, have to fix the alignment when you clone from a HDD to a SSD.

If you use an image, you have 2 steps - the imaging and the restore. A good imaging program has the option of preserving the alignment in the case of SSD to SSD. But if the image comes from a HDD, you also have to fix the alignment or you have to restore the image(s) into predefined, aligned primary active partition(s). But there are plenty of programs that help to fix the alignment in 20/20 hindsight.

Either method is fine as long as you know what you are doing.

 

[Layback Bear]

Thank you Wolfgang.

 

[ignatzatsonic]

Okay ignatzatsonic and whs; so I and others might understand better could you give the plus and minus using a image or a clone?

For the simple purposes of moving an existing and healthy system from drive A to drive B, they both can work and both can fail. Cloning is simpler for that purpose when it works. If the cloning fails, try imaging.

For purposes other than moving a system to another drive (backup as normally understood), there isn't much comparison. Cloning has shortcomings as a backup plan when compared with imaging.

For a one-shot deal to move a system, cloning can be a reasonable choice. Regardless, I'd think any conscientious person want to become familiar with imaging for purposes unrelated to moving systems between drives. Cloning is pretty much a one-trick pony.

 

[whs]

Thank you Wolfgang.

You are welcome Jack. I like the "One trick pony" of Ignatz, LOL.

 

[Layback Bear]

Thank you ignatzatsonic. I also like simple. I'm guessing because I'm simple.

 

[Lady Fitzgerald]

A clone is a one step operation and in case of to and from SSDs, you don't have to worry about alignment. You do, however, have to fix the alignment when you clone from a HDD to a SSD...

Curious. I've never had to fix the alignment when cloning from an HDD to an SSD. Must be living right.

 

[Lady Fitzgerald]

Okay ignatzatsonic and whs; so I and others might understand better could you give the plus and minus using a image or a clone?

For the simple purposes of moving an existing and healthy system from drive A to drive B, they both can work and both can fail. Cloning is simpler for that purpose when it works. If the cloning fails, try imaging.

For purposes other than moving a system to another drive (backup as normally understood), there isn't much comparison. Cloning has shortcomings as a backup plan when compared with imaging.

For a one-shot deal to move a system, cloning can be a reasonable choice. Regardless, I'd think any conscientious person want to become familiar with imaging for purposes unrelated to moving systems between drives. Cloning is pretty much a one-trick pony.

Thank you Wolfgang.

You are welcome Jack. I like the "One trick pony" of Ignatz, LOL.

I also like it. It perfectly describes when to use cloning.

 

[whs]

LF, that is unusual. Since a clone is a pure iron copy, it should not be aligned when coming from a HDD. Maybe there was a partition in front that gave the alignment.

 

[Lady Fitzgerald]

LF, that is unusual. Since a clone is a pure iron copy, it should not be aligned when coming from a HDD. Maybe there was a partition in front that gave the alignment.

Good point. I do format the SSD first. Also, I use smart sector cloning (the default setting) in Macrium Reflect, which copies over only the sectors with data on them. That can be much faster than forensic cloning, which is an exact duplicate, including empty sectors.