Skip to main content

Newly Cloned SSD Disappears

Thread needs solution

Cloned a 256GB promary SSD to a new 1 TB SSD. The new clone works for about 24 hours and then it simply disappears. I can reclone it from the OEM SSD and it will work for a while again.

I originally cloned through a USB conncetion but then found out I should not have done that way. Now I have cloned through an internal bay. Appears to have worked but it always goes away after about a day. The 1TB drive shows no data on it after it fails to boot.

Any one have any suggestions for this problem?

Jim

0 Users found this helpful

Jim, if you are able to successfully clone from your 256GB drive to the new 1TB SSD and that then works fine for around 24 hours, then this would suggest something other than a problem with the Acronis program used to perform the clone.

When you say that the 1TB SSD drive shows no data on it after failing to boot, how are you checking this?

Is this an actual 1TB SSD drive or is it a hybrid 1TB SSHD drive (mix of SSD and HDD components)?

I have been running my Dell laptop on a 1TB SSHD drive for more than a year since cloning from an older 320GB SATA HDD drive.

This, to me, sounds like the 1TB drive might be faulty and you should consider asking for a RMA from the vendor.

I agree with Steve, your symptoms inidicate hardware failure.  One thing I would suspect first off is a bad connector on the data cable from the motherboard to the drive.  It could also be a failed motherboard connector.  If using a new cable does not help then switch to another port on the motherboard if possible. 

You might also have a flaky controller driver for the SATA devices.  Another possible is that your SSD requires operation in AHCI mode but your bios is set at IDE.

Do some checking and report back.

It is an actual SDD. When it fails to boot, it has not shown up and Windows will not start. 

I don't think it is hardware related except possibly the SSD. The original 256 is as stable as a rock. I was just increasing my space. 

I cannot actually look at the data since I cannot get it to be recognized, so I am surmising that the data is not present.

I read elsewhere (I think it was either here or on Western digital), that if you cloned a drive from a USB port, it would become unbootable.

Well that is what I did. I took it to work and had someone look at it, but I was told there was no data on it.

I retried cloning it from an internal bay vs a USB to sata convertor and while it appears to work fine for a while, it just goes missing from the boot sequence.

Looking at the bios shows nothing where this drive should be, which is in the 0 position.

Jim, the recommended method of cloning drives is to place the new / target drive in place of the existing drive and not connected either internally or externally in any other position.

However, given that the cloned drive will boot and work without issue for upto 24 hours, I stand by my earlier thought that this is a hardware issue with the new SSD drive.  It sounds as if the drive controller / logic board goes 'missing' if the drive cannot even be detected at a BIOS level, either that or it is suffering from some form of over heating issue, especially if the drive can be found again sometime later in order to allow you to clone it again?

I am in a chat queue with Newegg at the moment. I have let it cool off for several hours and it still will not show up.

I dont know if it became unbootable because I originally cloned from a USB port but I thought that reckoning would fix the issue.

It isn't an overheating issue. I am now in the process of getting an RMA from the manufacturer, because of course it was past the reseller's warranty replacement time frame. 

Hopefully, I can get a replacement. 

Jim Holland wrote:

I dont know if it became unbootable because I originally cloned from a USB port but I thought that reckoning would fix the issue.

Jim,

Please let me clarify this...There is nothing wrong with performing the clone the way you did...with the target being connected by USB.  The issue when performing the clone this way is that the drive will not boot when connected by USB.  If order for the drive to boot, it must be disconnected from USB and installed in the computer.  The reason that Acronis recommends to install the target drive in the computer is they were getting a lot of complaints when people would perform the clone like you did, then set their BIOS to boot from USB and the newly cloned drive would not boot while attached via USB.  This is a Windows limitation, not Acronis.

So, I guess what I am saying is performing the clone as you did would not make the disk unbootable.

FtrPilot