Upgrade to small ssd

---

@jphughan wrote:

Fyi your screenshot is sideways, but drive letters in Rescue are unimportant.  They're dynamically assigned by the OS at every boot, whether that OS is full Windows or Windows PE, which is what Rescue Media uses.  There's nothing on a partition that says, "I should always be assigned drive letter D", so the Rescue Media OS doesn't have a way to know which drive letters your normal Windows installation assigns to which partitions.  It will absolutely not make a difference though.  "Full" Windows always assigns the partition it boots from as drive letter C, but when you're in Rescue Media, you didn't boot from your normal C drive, so it doesn't get special treatment there.  Otherwise, Windows assigns subsequent partitions using the next available drive letter unless the user has previously specified a different letter manually, in which case it will assign that if available -- but again that's only because that instance of Windows knows about that.  There's nothing stored on the partition itself that manages this.

Again, I've performed this process MANY times in my IT career, and many times specifically with Reflect.  But if you don't trust my guidance, then you may want to consider reading Reflect's documentation for yourself instead, which incidentally is better than most.  But otherwise, I'm really not what you're worried about here.  Absolute worst case, the restore to your new SSD fails due to some freak issue, and you still have an intact image backup that you just captured and your intact original hard drive.  That's a completely solid contingency position.

By the way, if the first test boot from the new SSD doesn't work, boot back into Rescue Media and run Fix Boot Problems, then try again.

---

I don't doubt about your knowledge about it i doubt myself i'm scared to screw up but that fear is not needed because if something does go wrong i still have the old ssd i'll do it when i get home.

I have tried but face a strange problem my laptop refuses to turn on with the new ssd  when i put back the original the laptop turns on just fine what the f..... is this ??????:Hmm:

---

@jphughan wrote:

Do the undersides of the two SSDs look significantly different?  Are there perhaps contacts on the bottom of the Crucial SSD that don't exist on your original SSD?  My only guess is that some combination of the Crucial SSD and the layout of that system's motherboard is creating a short circuit whereas the design of the original SSD might be different in some way that doesn't create this problem.  That's admittedly a long shot, but I've never heard of an SSD swap causing a system to refuse to even power on, and that's the only possible cause I can think of.

---

Both ssd's look the same sometimes my power button does blink (somtimes)but the screen stays blank the crucial ssd has a B+M key i thought they fit on all motherboards.

Do the undersides of the two SSDs look significantly different?  Are there perhaps contacts on the bottom of the Crucial SSD that don't exist on your original SSD?  My only guess is that some combination of the Crucial SSD and the layout of that system's motherboard is creating a short circuit whereas the design of the original SSD might be different in some way that doesn't create this problem.  That's admittedly a long shot, but I've never heard of an SSD swap causing a system to refuse to even power on, and that's the only possible cause I can think of.

I have  an idea i'll try again  this is the way i do it

1. Loosen the 6 captive screws.
2. Remove the 4 normal screws i put them in a cup so i don't lose them.
3. Take off the base cover.
4. Remove the four screws holding the battery and disconnect the battery from the motherboard(those four screws in another cup so i know what comes from where).
5. Press and hold the power button for 3-5 seconds to discharge residual electricity.
6. Locate the m2 socket and unscrew the ssd  look out the screw doesn't drop between the components..
7. install the new ssd i might be doing this wrong i assume the white label saying "crucial" should be on top though this is not a good "reference point" .
8. reassemble the system.

Step number 7 might cause the problem but i thought motherboards only accepts components one way you can't do it wrong.This is the first time i'm trying to install an ssd.

---

@jphughan wrote:
B+M keys do indeed fit in all motherboards and they can only be inserted one way. Are you making sure to insert the SSD into the slot at a 45-degree angle relative to the motherboard for the SSD connector to fully seat before pressing the top of the SSD down to make it lie flat?

---

Yes the service manual explains this here however in the example in the service manual there is this white label on top saying Micron that's why i assume you have to slide it in that way.It's clear now the crucial ssd can work it's just a problem being caused due to my inexperience the ssd is a component i've never touched before.

Once i get it in right the system should power on then i use the F12 key boot menu to boot from the earlier created rescue media and restore the backup.This is a bit annoying but a good lesson

What did you do differently during installation to make it work? The reason the partition is small is because Reflect by default restores partitions according to their original size on the source. It doesn’t automatically expand anything because it doesn’t assume which partition or partitions you’d want to expand, if any. Depending on the layout of your disk, you may be able to expand the C drive in-place in Administrative Tools > Disk Management. Otherwise, run the restore again, and this time adjust the restored partition size for your Windows partition by changing its properties in the first step of the restore wizard.

---

@jphughan wrote:

What did you do differently during installation to make it work? The reason the partition is small is because Reflect by default restores partitions according to their original size on the source. It doesn’t automatically expand anything because it doesn’t assume which partition or partitions you’d want to expand, if any. Depending on the layout of your disk, you may be able to expand the C drive in-place in Administrative Tools > Disk Management. Otherwise, run the restore again, and this time adjust the restored partition size for your Windows partition by changing its properties in the first step of the restore wizard.

 

 

Like i said before i was assuming the white label saying "crucial" should be on top this was incorrect as soon as i turned over the ssd (white label facing down) it popped in the m2 socket and you have to hold it down with one hand and screw it into place with your other hand.I know i'm verry lucky i didn't damage my m2 socket or the new ssd .

---

I now have a bunch of unallocated space and i don't really understand howto assign that space to the C drive extend volume is greyed out in disk management.

I was inserting the new ssd wrong the white label saying "crucial" must be at the bottom that was causing the problem.I know i'm lucky i didn't damage my m2 socket or the new ssd .

Now there is 346,53 GB of unallocated disc space and i don't understand howto assign that space to the C drive actually i do not like to mess with partitions it can cause trouble....

There is a "extend volume" option within disc management but it is greyed out because there are other partitions in the way.
i have no idea howto get the unallocated  space to the C partition.

that is what the image should be

Found some software called "Nubi partition editor" and got this

Now the "extend volume" option in disc management will enable but i"m scared to click apply doing this wrong can .....

So you had no qualms about using a tool that performs live repartitioning, which involves relocating the data of active partitions on the disk, but now simply extending an existing partition to use unallocated space is the step you're worried about?  For future reference, live repartitioning is a far higher-risk operation than just extending a partition into empty space, because extending a partition just causes the partition table to be updated to say, "This partition is now allowed to use this extra space on disk", with no requirement to rearrange any data on disk.

But now that you've done the repartitioning, there's absolutely nothing to worry about in terms of extending a partition.  And once again, you have a recently captured image of your system, so your worst case scenario is that you just restore that again.  And to state the obvious here, you could also of course keep using Macrium Reflect going forward to capture system images prior to doing things you're worried about, or even just on a regular basis as a data backup solution and/or in case something ever happens unexpectedly, like an update that messes up your system (or a Windows 10 1809 "upgrade" that deletes a bunch of your data, as happened to some users), or of course malware.  You'll find that there's a lot less you need to be worried about if you get into the habit of capturing system images.

But also just for future reference, what I personally would have done in your situation rather than repartition a live disk is simply run the restore again and have Reflect increase the size of the restored C drive as part of its own operation.  The steps for "staging" a partition resize during a restore are outlined here.  The screenshots show a clone, but it works the same way for an image restore.  The trick is that rather than just clicking "Copy selected partitions" in the first step of the wizard, you need to drag and drop the source partitions down to the destination, working left to right, then resize the Windows partition in the Destination row before you drag down the rest.

Problem solved my C drive has now 394 GB space available :Smile: thank you @jphughan

for your advice and patience.