Question Cloned SSD dependant on old HDD filesystem?

[labyrinthine]

In july i bought a new 2tb SSD to replace my 2tb HDD. cloned the hdd to my ssd using macrium & everything seemed to work fine, but i procrastinated taking the hdd out. today i finally decided to take it out, but when i booted it had reset all my user settings, couldnt log in to microsoft, and said the user folder was corrupted along with having none of my files, but was still showing some game installs from my game drive on my desktop. i didnt test but some programs seemed to still be installed also. when i put the hdd back in, everything was fine again. both discs have the same partitions, and i know the ssd has its own files because they are not present when booting from the old hdd.

whats the problem?? is there any way to fix this before redoing everything? im considering copying important files and re-cloning onto the ssd, and then removing the hdd immediately afterwards (the first time i cloned a drive i had no problems with it, but took the old drive out immediately afterwards, but it was hdd to hdd). i know the best solution is to do a clean install but i have a lot of stuff i dont want to reinstall (9 years of stuff basically), and had issues accessing my game drive when i tried a clean install at first.

UPDATE: spent the day copying important files with the intent to reset windows on my SSD, took my HDD out so there would be no issues with the windows install, and then windows launched completely fine with no problems from my SSD. no idea what the problem was yesterday but it seems to have fixed itself, and now i have extra backups of my important files just in case i suppose!

 

[Lutfij]

Welcome to the forums, newcomer!

I would personally backup any and/or all data that's mission critical off of the 2TB SSD and start afresh with the cloning process.

Would also help if you made sure your platform was on the latest BIOS version before proceeding forward.

 

[Lafong]

I don't entirely follow your first paragraph, but I generally agree with your idea of starting over.

Can you better describe what problems you have NOW if you try to operate with ONLY the SSD connected?

Why do you currently need the HDD at all?

A clone should generally result in "everything" on Drive 1 being copied to Drive 2, as of the moment the clone finished. Do you think that did NOT happen?

There's nothing sacred about a clone. An image file followed by an image file restoration would accomplish the same thing as a clone.

But neither a clone nor an image file is going to save you if your source drive is fouled in some way. Is it?

 

[labyrinthine]

I don't entirely follow your first paragraph, but I generally agree with your idea of starting over.

Can you better describe what problems you have NOW if you try to operate with ONLY the SSD connected?

Why do you currently need the HDD at all?

A clone should generally result in "everything" on Drive 1 being copied to Drive 2, as of the moment the clone finished. Do you think that did NOT happen?

There's nothing sacred about a clone. An image file followed by an image file restoration would accomplish the same thing as a clone.

But neither a clone nor an image file is going to save you if your source drive is fouled in some way. Is it?

sorry for not being clear, the source drive is completely fine and still works great other than being a bit slow due to being an hdd. the clone to drive 2 (ssd) seemingly worked fine until yesterday when i tried taking the source drive out, and could no longer access anything that was cloned to the ssd (except for, seemingly, some program installs that were still in my taskbar). i have no idea why that would happen other than possibly filesystem dependencies remaining on the hdd from not taking it out until now.

 

[labyrinthine]

Welcome to the forums, newcomer!

I would personally backup any and/or all data that's mission critical off of the 2TB SSD and start afresh with the cloning process.

Would also help if you made sure your platform was on the latest BIOS version before proceeding forward.

backing up stuff now, will hopefully check bios version & clone today and see how it goes!

 

[JackrumMadthing]

Your problem is very likely to do with Boot Partitions.

Unless you have manually set the old HDD to NOT be the primary Boot, it will still think it is.

You can fix this very simply....by moving the SATA cable that was in the "old" drive to the new one, or move the drives around in your BIOS boot order.


You don't NEEED to remove the bootable partition setting on the old drive, but it is neater. You can even completely delete and recreate the partitions, on the old drive, but I'm presuming you want to keep a backup for a while.