Salta al contenuto principale

While cloning SSD to SSD I get a high pitched "scream" (high C#) from the mother board

Thread needs solution

I'm using an Intell Core i7-3770K CPU@3.50 GHz, 7.97 RAM 64bit OS Mother Board.  

When cloning between two 118gb SSD's I get a screaming warning from the MB - it is a high C#.  

It occurs just after the source and destination are identified and ACRONIS is "PREPARING.... something".   

It stops when the system is rebooted.  

The cloned SSD appears to work as expected EXCEPT the NEW boot drive has 66.1gb free (of 118) and the OLD system had 66.1gb.  I'm guess that some cleaning up was done by Acronis.

A 128gb SSD "safety clone" shows 50.7gb free of 118gb

 I'm guess that some cleaning up was done by Acronis.   I haven't found any information about that in the documentation.

0 Users found this helpful

Stephen, welcome to these user forums.

How exactly were you performing the Clone between these two SSD drives?

There should be no 'cleaning' done as part of the clone process - cloning is a 1 to 1 direct copy from one drive to the other at a sector / block level where the end result should be two identical drives.

Please see post: 128231: [IMPORTANT] CLONING - How NOT to do this!!! for guidance on cloning.

Assuming you are correct about the noise coming from the motherboard, is there also a error message appearig. On my motherboard whenever there is an auibile error sound there is also an error number displayed.

Ian

Steve Smith:  Thanks for the excellent article.  I've 'cloned' for years with no problem.  I'll use Acronis Backup and Restore from now on.

I was doing a 'routine' clone following the automated rather than the manual method.  Afer I identified Source and Destination, I received a notification that it was "Preparing...." .  The alarm started immediately. 

IanL-S:  No error message.  No chance to get a Blue Screen report.  It completed the process and turned off the machine.  It started up on destination SSD after moving wires.

Now that you mention it, the message, if any, could have been 'under' the Acronis in process information message.

Previously the primary had been cloned to an ADATA 128gb with no incident.

 

-- Thank you both for responding. 

Stephen, thanks for the update - strange about the alarm / screaming from the computer, especially if this is a process you have performed on other occasions without any similar sounds being given!

I've trying to think of what I did to the system since I last cloned (using this machine).  I can only guess that I've upgraded it to W10 and caught up on all the releases.

Other than jangled nerves, Acronis cloned the drive. 

Where (within the bios) would I look for a warning text/indication when I do it again? One would think that the system would maintain a log someplace.

I'll use your alternate method this weekend.  I suspect that will not make the bios complain.

Stephen, I can only suggest taking a look at the Windows Event Logs if the clone was done entirely within Windows but if it was done either on a reboot or using the Rescue Media, then there are unlikely to be any logs you can look at for this issue.

BIOS is firmware and as such there are very few options for storing log data unless your specific computer version of the BIOS provides an option to do so, but you would need to consult the documentation for either the computer or the motherboard / BIOS or any diagnostic logs held etc.

Thanks Steve,

Good points and info.  We'll find out as I sweep out all the dusty crannies on the MB.  I didn't see anything on the event log when I was poking around there.   In the process Acronis reboots twice - at beginning and end.

I think my best solution is do as you suggested and not 'clone' anything.

Again thanks for your time and help.

Steve.