This video offers a masterclass in digital preservation by turning the abstract threat of bit rot into a manageable maintenance routine. Barnatt’s tool-specific recommendations provide high-value utility for anyone serious about long-term data integrity.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Data Refresh for Long-Term StorageAdded:
[music] >> Welcome to another video from explainingcomputers.com.
This time, I'm going to discuss different methods for refreshing the data on hard drives or SSDs that are left on powered for long periods.
This video is a follow-up to my recent episode on long-term data storage in which I recommended rewriting the data on a long-term storage hard drive every 3 years and reading the data on SSDs every year.
Many people asked how this may be achieved and therefore I'm making this video.
And if you're wondering why we only have to read the data on an SSD to refresh it, it's because reading data forces the controller to assess its integrity and rewrite if required.
Before we begin, it's really important to stress two things.
Firstly, this video is focused entirely on hard drives and SSDs that are left on powered for long periods.
In contrast, if a modern drive is connected to a computer and in regular use, then its controller will be regularly performing housekeeping activities that will refresh the data.
For example, SSDs will constantly perform wear leveling which moves data around to prevent some blocks of flash memory cells wearing out before others.
However, if you have got a hard drive or an SSD in storage for years on end without being connected to a computer, without being powered up, then the controller cannot perform such housekeeping activities and this is what this video is all about.
Secondly, my recommendations for when to undertake data refresh are based on minimum data retention expectations, not the life expectancy of drive media, let alone the average or maximum time that data may be retained.
To be clear, it's perfectly possible that you could save data on a hard drive or on a new TLC SSD and come back to it in 5 or even 10 years and it would still be okay.
But, if every bit of data, and I stress every bit of data, was still intact after 10 years, particularly on an SSD, then you would be beating the odds. And hence, my recommendation is to refresh data after the minimum period it's likely to be retained, as this is the safest option.
With these critical points noted, let's move on to how to refresh data.
And here, three options are available, which are to take advantage of cold storage practicalities, to use specialist applications, or to use operating system utilities.
Right. Here we have two of my five LaCie d2 backup hard drives. And for a couple of reasons on these, I find that I seldom need to use special software or operating system utilities to refresh their data.
And this is because of the way these drives are managed over time, and so I thought it was worth mentioning.
Firstly, as hard drive capacities increase and as the quantity of data I have backed up and archive grows, so my external drives get upgraded.
For example, when When first purchased my LaCie D2s, they had capacities of between 160 and 500 GB.
But, over time, they've all received new internal drives, with this one now containing a 16 TB Toshiba mechanism.
And indeed, over the years, I've made videos about several of my external hard drive upgrades.
A practical implication of upgrading to a larger internal mechanism is that data gets copied from one drive to another.
So, if you upgrade backup hard drives and migrate that data every 3 years or so, you don't have to worry about data refresh.
Secondly, if data refresh is due and a backup or archive drive does not need upgrading, I often find it has enough free capacity to make an on-drive copy, and this is how I often achieve a data refresh.
So, for example, if an 8 TB drive only has 3 TB stored on it, I just duplicate that data on the same drive, making sure that it's verified, as I'll come to in a second. And I then delete the first copy, safe in the knowledge that all data has been rewritten.
And even if a drive is over half full, on-drive duplication can be achieved in stages.
So, for example, if an 8 TB drive contained 5 TB of data, 2.5 TB could be duplicated and verified, and the original deleted, and then the process repeated.
It should be noted that this is likely to lead to data on a hard drive becoming fragmented.
But, on a backup or archive drive, this may not be a concern, and certainly, it doesn't concern me.
And you could always defrag the drive if you wished.
If you rely on either migration to a new drive or an duplication to achieve data refresh, it's wise to make sure that all copies are verified.
In Windows or on a Mac, you can do this using an application called TeraCopy, which is free for personal use and includes copy verification in both its free and pro versions.
So, for example here in Windows, we have got TeraCopy running and we've also got my 16 TB LaCie d2 quadra connected to the computer.
As we can see, it's only got about 5.4 TB of data stored on it and it's also only 22 months since I fitted the drive.
So, a 3-year data refresh is not due.
But, if it were, there would clearly be enough space for an on drive copy. And so, what I do is to open it up and to create a folder into which I copy everything else on the drive. And I do that using TeraCopy. Here it is and I've already set up a test data using just one folder and copying to the new folder we just looked at.
I then go to options and click on verify files after transfer and then click on copy.
As this progresses, let's use the magic of filmmaking to move forward in time until our copy and verification are complete.
And there we go. We can see we've got a green here against verify. Everything is okay and we can also look in the log, which again shows verifying complete with no errors. And so, there we are.
That's how easy it is to do a verified copy in TeraCopy, which as we noted is available for Windows and Mac.
And if you want an alternative that's available for Linux and has a graphical interface, I'd recommend FreeFileSync, which can perform a file copy with verification if appropriately configured.
>> Next, let's look at some specialist applications. And if you search for Drive Refresh Utility, the one that comes up again and again is Disk Fresh from Piriform Software.
This is free to download, works in any version of Windows from XP onwards, and is dedicated to either reading and rewriting each sector of a hard drive or reading each sector of an SSD. And that's all there is to it.
If we scroll down, we can see that the program hasn't been updated since July 2013. And this is not necessarily an issue as if a piece of software does its job, it doesn't need constant updates.
And personally, I've been using Disk Fresh with no issues for many years.
But inevitably, I would caution that you allow a 13-year-old piece of free software to rewrite or read all of the data on a drive at your own risk.
And indeed, in general, note that you should never run any kind of data refresh utility on a drive that contains the only copy of any data.
These points noted, here we have Disk Fresh up and running, and its interface is pretty self-explanatory.
There's a very good help system over here, which includes a nice article all about why data refresh is necessary, but otherwise, it's simply a matter of selecting a drive or partition thereof.
And right now on this particular system, we've got two SSDs physically connected here and here. The second one is formatted for Linux, so Windows can't see it, but the first one has got two NTFS partitions which appear up here.
And then the third physical drive on this system is a test hard drive I've connected for, well, a test. And this again has got two partitions, which as we can see are formatted FAT32. And so, if we wanted to, we could use this fresh either on just this partition, or that partition, or indeed both partitions, or we could select the entire physical hard drive. And I think here, that's what we will do.
By default, DiskFresh will read and then rewrite every sector, which is what is required to refresh a hard disk.
But, there's also this checkbox over here for read-only mode, if you want to refresh an SSD or other flash media.
Although here, we'll leave this unticked, as we're going to refresh a hard drive.
It's then just a matter of which extent of refresh we want to select, where we've got two options. One is refresh range, which you can specify in sectors, which is useful if you want to conduct a refresh in stages. And indeed, as we can see, we can specify sectors as a percentage.
But here, we will cancel, and we'll take the first option of just refresh to do the whole drive. Are we sure we want to continue? Yes, we are. And there we are, the process has started, which inevitably will take a little while. So, let's jump forward in time.
And again.
And again.
Almost finished.
And here we are, the refresh is complete, and the data on our hard drive should be safe from bit rot for at least 3 years.
As this hopefully demonstrates, DiskFresh is very straightforward, and is therefore the application I personally use for hard drive data refresh when I don't rely on data migration or on drive copy.
This said, I must caution that DiskFresh and similar applications, like those we're about to look at, are not ideal for refreshing SMR hard drives, as I'll discuss later in the video.
Moving on, let's return to TeraCopy, as this can perform a file read test, which could be used to refresh the files on an SSD.
And indeed, TeraCopy is my preferred SSD refresh application.
All we need to do is to select our source. I'll go to add folders, and I've got an external SSD now connected to the system, which we could select as our folder. We could do the whole drive, although here, as a quick test, I'm just going to select one folder like that, and select folder. And then, I'll go to options because what TeraCopy is going to do is to read every file in order to create a checksum, and I don't want to save these checksums on the drive, so I'm just checking there are no options ticked to save the checksums. There aren't, so I'll go back to the file list, and click on test.
And as usual, we'll now use the magic of filmmaking to speed on through.
As we do so, I'd note that I find TeraCopy particularly useful if you just want to refresh certain files on an SSD, which is something you cannot do in Disk Fresh.
And remember, the reason we only have to read data to refresh it on an SSD is that this forces the drive's controller to check data integrity and rewrite if required.
Anyway, our test has now completed, and the data we selected on our SSD should now be refreshed.
Moving on again, another option is a program called SpinRite from Gibson Research Corporation.
This costs $89, and has a massive functionality for improving drive performance as well as data refresh.
It's not an application I've used myself, but in recent discussions, two Explaining Computers channel members have told me that they've been using SpinRite successfully for over 20 years to avoid bit rot on hard drives and SSDs.
SpinRite runs from a bootable USB drive and so can be used on most computers regardless of their installed operating system.
A final program I've also not tried myself is Hard Disk Sentinel.
This has a free trial as well as being available in standard, pro, and enterprise versions.
However, as we can see over in this table, the ability to refresh a drive is only available in the professional version. This costs $33 and, like SpinRite, Hard Disk Sentinel offers a massive functionality far beyond data refresh.
As I've said, Hard Disk Sentinel has a good reputation and I did consider getting the pro version to have a look at in this video.
However, as I have no way of knowing if it refreshes data better than DiskFresh or TeraCopy, I thought I'd not muddy the waters and maintain my recommendations of using DiskFresh to refresh hard drives and TeraCopy to refresh SSDs.
Rather than using a graphical application, it's possible to refresh drives using the Windows command prompt or the Linux terminal.
However, this needs to be done with great care.
And, as I've already outlined a range of options for drive refresh in Windows, to be safe, I've decided not to cover any Windows command line alternatives.
For Linux users, SpinRite is a potential option if, with its $89 price tag.
But, as none of the other applications I've talked about run in Linux, let's see how to refresh a hard drive or flash media in the Linux terminal.
Starting with hard drives, we can read and rewrite all data using badblocks with syntax like this.
Here, sudo executes the command with administrator rights, whilst the F flag forces badblocks to run even if the drive is mounted.
B 4096 then sets a reasonable default block size, whilst P1 limits the number of passes to one, so the program does not repeat.
Finally, NSV is critical, with the N parameter making sure that badblocks conducts a non-destructive scan, which does not destroy all data on the drive.
S then enables progress tracking, with V displaying it on the screen.
To try this out, I've got an external hard drive connected to the computer. We can see it over here. And if we do an lsblk list block devices in the terminal, we can see its two partitions are down here, and we can use badblocks either on a whole drive or a partition.
And I think here, we'll choose the former. It'll take slightly less time to run. So, let's clear the screen to make things look tidy. There we go, and then enter our command.
There we go, and always check you've got the N flag to ensure you're doing a non-destructive test. And having checked, let's now press enter.
Where, as usual in Linux when entering a sudo command, we have to enter our password.
And there we are, badblocks is now running a non-destructive read-write test, which, as previously, will take a lot of time. And so, once again, we'll now call on the magic of filmmaking to move forwards in time.
And here we are, over 5 hours later, and we're almost there.
And if we wait a second, yes, a refresh of our hard drive partition is complete.
Next, let's refresh an SSD with a command that will read everything on the drive.
There are many possible ways to achieve this, with a common approach being to copy everything on a drive to null.
However, this can be tricky unless a drive has a totally flat file structure.
And so here, we're going to use this command.
And what this does is to use grep to recursively search every file in a location, which is a nifty way of forcing a read of every bit of data.
For test, I've got a USB SSD connected.
Here it is. And if we go back to the terminal and do an lsblk to list block devices to see where it is. It's actually got two partitions, but the main one is down here. We will refresh the files in this location, so let's copy that mount point like that. And we will uh clear the terminal just to be tidy, and then type the grep minus R to be recursive, our search term. I'm going to use Stanley, but you can use any term you like. It's purely a means to an end.
And then on the end of that, we will put our location. Paste it in like that.
And it's worth noting that unlike bad blocks, grep is happy to be given a mount point rather than a raw drive or partition. And indeed, this could be any folder which contains files you want to refresh on a flash media.
Also note that the only output we're going to see will be any search matches.
And to show this, on the SSD in a docs, and I think it's down in that folder there. Yes, it is. I've already created a test file which contains the word Stanley.
So, with all this noted, let's run this command.
There it goes. And almost immediately, it reports a test file match. But after that, there'll be no indication that anything is happening other than the flashing LED on the drive.
So, let's speed on through until the end.
Here we are, and we've now read every file on the drive, and in doing so, refreshed its data.
Today, there are two methods that hard drives use to lay out their data tracks.
The first is conventional magnetic recording or CMR, where the track pitch is determined by the size of the right head.
And as this has to be larger than the read head, in CMR, there is wasted space between the tracks.
To store more data in the same area, in shingled magnetic recording or SMR, the track pitch is determined by the read head. So, when tracks are laid down by the write head, they are allowed to overlap like shingles.
This still allows data to be read because the read head does not overlap other tracks.
But, data cannot be overwritten without corrupting overlapping tracks.
Because of this, SMR drives organize data into append-only zones to which data can only be added. And when data needs to be changed, it's written to a new location and the previous one marked as obsolete.
SMR drives also have a CMR cache, and I've explained them in more detail in my video on new hard drive technologies.
But, the implication here is that SMR drives are far more difficult to refresh than CMR.
You can use applications like DiskFresh to refresh SMR drives, but they will be very slow indeed and will place excessive wear on the drive mechanism.
On drive copies are therefore more suitable for SMR refresh as they move data around rather than trying to rewrite each sector in turn, which an SMR drive cannot directly do.
And ideally SMR data refresh is best achieved by doing a low-level format and copying data back to the drive from a backup. There really is no ideal refresh method for in situ SMR data.
If you're serious about long-term data storage on unpowered hard drives or SSDs, then you should consider a data refresh strategy.
However, given that everything we've looked at in this video is about either reading or rewriting all of the data on a drive, then I want to stress that everything we've covered is undertaken at your own risk.
In particular, I want to stress yet again that you should never apply a mass data read or rewrite technique to a drive that you don't have a copy of as even a mass read has a small risk of a calamity.
But now that's it for another video. If you've enjoyed what you've seen here, please press that like button. If you haven't subscribed, please subscribe and I hope to talk to you again very soon.
>> [music]
Related Videos
Agentforce NOW AMA: Build with React and Salesforce Multi-Framework
SalesforceDevs
490 views•2026-05-28
How agent o11y differs from traditional o11y — Phil Hetzel, Braintrust
aiDotEngineer
450 views•2026-05-28
WEB TECHNOLOGIES UNIT-2 | Degree 4th sem BCOM Computers web technologies unit-2 full explanation💯✅
LearnwithSahera
1K views•2026-05-29
More tests are always better? How to use AI to identify tests that bring little value
Alliance4Qualification
335 views•2026-05-29
Search Algorithms Explained in 60 Seconds! 🤖💨
samarthtuliofficial
218 views•2026-06-01
People of Game of Thrones using JavaScript DOM
AltCampus
296 views•2026-05-30
Introduction to Problem Solving Part - 1 | Lecture 1 | Intermediate DSA
ascensionix
107 views•2026-05-29
So What's Odin Lang Even Good For
TechOverTea
131 views•2026-06-01











