6 replies
by dimbulb Accepted solution
by thechas Accepted solution
What you are really asking is how many write cycles can you perform on a hard drive. Basically, what is the write cycle Mean Time To Failure.
Plus, how reliable is your source media.
Most mechanical hard drives are going to have a MTTF in the 1000's of write cycles, if not in the millions as per their test data. However, these tests usually do not account for the effects of system crashes and power issues.
My general rule of thumb is if I even suspect a physical failure of the hard drive, I replace the drive.
In my work environment, we run many computers 24/7. Most of our hard drives run for years with the original software load. Some are well past 10 years of running. We tend to have small bursts of failures on these systems after a power outage. They have been running for so long that the bearings in the drives and fans have worn out and will not spin up from a cold condition.
My point is that you are not apt to wear out a drive by repeatedly restoring an image. However, once you have bad sectors or problems with one of the heads, the ability to successfully restore an image and have the system run for any length of time is lost.
Chas
by seanferd Accepted solution
Odds are you'll have a mechanical failure before the platter "wears out". Sure, you lose magnetic domains occasionally, but you get blocks marked as bad, and then they are not used.
On a "solid state" drive, yeah, I wouldn't re-image it constantly.
by oh smeg Accepted solution
It all depends on the drive and quite honestly the most likely issue to be had is that the method of Connection the Master Image will introduce potential problems not related to the HDD Image.
But the reality is that the Data stored on a HDD is all Digital so it's what is mistakenly called either a 1 or a O.
Not quite correct as you can never get exactly the same value when you overwrite so you will get a 0 with a bit of Drift or a 1 with a bit of drift form that actual Value. The way that Forensic Recovery Works is to read those Differences and rebuild the data that was written to the drive with that level of drift from the Supposed Design Values.
As stated above there is no actual limit to the number of times you can reimage the drive unless you exceed it's Design Life which should run for at least 5 years 24/7/365 if not considerably longer.
As these are a Digital Image if you where to constantly reimage to another drive and be constantly deploying a modified Image even that should make no difference provided that the Data Connections where in good condition and did not introduce any failures.
All Digital Copies should be an [b]Exact Copy[/b] of what it came from so there should be no differences or degrading of the original image.
Of course if you use substandard data connectors and constantly abuse them you will have problems related to the failure of those components. ;)
Col
by dimbulb Accepted solution
by thechas Accepted solution
I guess I can see where you might run into a problem if you made and restored successive images. But, I cannot make any case for drive failure or wear when restoring a base image multiple times.
However, as these are mobile systems and see hard use, an argument could be made that by the third time you re-image a drive because of a corrupt file that the drive should be replaced. In that case, Panasonic is being looser than my one strike rule for file errors on any critical drive.
If you are restoring a base image because of mal-ware or other soft errors, I would not count that against the drive hardware. If you are restoring because of suspected physical file corruption, definitely count that against the drive.
Chas
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending