Long term problems from hard-cloning HDD to SSD?

Discussion in 'Hardware Components and Aftermarket Upgrades' started by SJLPHI, Oct 17, 2021.

  1. SJLPHI

    SJLPHI Notebook Evangelist

    Reputations:
    7
    Messages:
    383
    Likes Received:
    56
    Trophy Points:
    41
    Hello,
    I recently did a hard-cloning using DD on Linux from a WD Blue HDD to WD Red SSD. I have done similar things have been done many times with different drives and observed no problem for over 4 years.

    Now, question. Is there a long term problem to anticipate from something like this? I am a little bit worried that not only did the cloning clone UUID, it also now reads from Windows as a WD Blue HDD. I thought WD dashboard would pick it up as what it actually is but it still thinks it's a HDD.

    I am thinking about re-initializing the drive and re-cloning using a third storage device and AOMEI Backer upper because this bothers me a little, and I don't even know if it will re-initialize as WD Red SSD.

    Any experience with this?
     
  2. Tech Junky

    Tech Junky Notebook Deity

    Reputations:
    304
    Messages:
    1,262
    Likes Received:
    493
    Trophy Points:
    101
    I wouldn't think much of it. I've done DD, Paragon, clonezilla and a few other methods in the past and never bothered to check name/model post copy.

    I wouldn't' put much thought into it personally. Though it would be in the back of mind as time goes on. Usually the name / model are in the firmware it's odd that it is saying Blue instead of Red on the destination drive. If you run a scan on the Red drive does it pick anything up for corrupt data? Reinitializing it in windows should purge the bad info though and pick up Red in the description. Windows is kind of dumb in comparison but, before you do any of that try reading the disk info with HWINFO and see if it gives you the correct info.
     
  3. SJLPHI

    SJLPHI Notebook Evangelist

    Reputations:
    7
    Messages:
    383
    Likes Received:
    56
    Trophy Points:
    41
    Well, after cloning, everything thinks the WD Red SSD is WD Blue HDD, crystal diskinfo, hwinfo, wd dashboard and etc. I am moving things around right now and I will refit the WD Red for /home drive on my W530. I am going to re-initialize it and see if it realizes that it's a WD Red then.

    I think DD overwrote the GPT table as well as the UUID. I wonder if firmware is intact.
     
  4. SJLPHI

    SJLPHI Notebook Evangelist

    Reputations:
    7
    Messages:
    383
    Likes Received:
    56
    Trophy Points:
    41
    Well, after wiping out all the partition, W10 still picked it up as some sort of no-name brand SSD, then finally WD Dashboard picked it up as WD red, and by erasing everything on the SSD using WD Dashboard and re-initialization the SSD is finally labelled the way it is supposed to be.
     
    tilleroftheearth and Tech Junky like this.
  5. tilleroftheearth

    tilleroftheearth Wisdom listens quietly...

    Reputations:
    5,367
    Messages:
    12,670
    Likes Received:
    2,701
    Trophy Points:
    631
    Cloning: when you really don't care about having an optimal, fully functional, and performant solution.

    Clean install (always!).
     
    pressing, Papusan and Tech Junky like this.
Loading...

Share This Page