Skip to main content

TI 2020 constant Check Disk

Thread needs solution

I have a friend who also uses TI 2020, as do I. His TI 2020 won't execute a backup job. It looks like it starts OK, then says 'disk error found. Aborting. Consider running Check Disk.'

This we have done multiple times. The first time we ran it, it legitimately did find an error which it quickly fixed. Since then, every time we run CHKDSK it says there is 'no error found, no action needed'. We've run this on EVERY disk in his PC. No discernable check disk errors, and yet TI still fails with the same message.

FYI - Windows 10 and Acronis are both running with all the latest patches and/or bug fixes as of this writing date.

HELP!!! Any advice or assistance is helpful.  TIA

 

0 Users found this helpful

Keith, welcome to these public User Forums.

The key limitation of CHKDSK is that it can only be used to check disks / partitions which have been allocated a drive letter, i.e. CHKDSK C: /F - the issue here is that there is probably a disk error on a hidden / system partition on your friend's PC.

Dedicated diagnostic utilities from the disk manufacturers take the longest time to complete the checks, but provide the most accurate methods of checking whether the disk is good or needs replacement:

 - Western Digital drives: Data Lifeguard Diagnostic for Windows

 - Seagate disks: SeaTools for Windows

 - HGST disks: HGST Windows Drive Fitness Test (WinDFT)

 - Intel SSDs: Intel Solid State Drive Toolbox

 - Samsung drives: Samsung Magician

 - ADATA drives: ADATA SSD ToolBox

 - Kingston SSDs: Kingston SSD Toolbox, Kingston SSD Manager

 - Transcend SSDs: Transcend SSD Scope

 - Silicon Power disks: SP ToolBox

 - Toshiba disks: Toshiba PC Diagnostic Tool Utility

- Crucial disks: Crucial Storage Executive

Steve, thanks for your response. Full disclosure, I'm 30+ years in IT.

It's a Dell Inspiron system with a SanDisk SSD Plus 1TB drive. It's being backed up to a WD external USB 2TB drive.

I ran CHKDSK C: /F from an elevated prompt and got the reboot scan clean. I was beginning to suspect it might be on the non-lettered partition(s). Is there any way to check and correct the issue? Any utilities to try?

TIA

 

One more thing. I do have the SanDisk Dashboard app loaded. And I've run Crystal Disk Info multiple times. Both say the SSD is 100% clean and healthy. 0 errors reported anywhere.

 

Kieth,

Use diskpart to assign drive letters temporarily to all unlettered partition on your disk, then run chkdsk with the /f switch on each of them.  After chkdsk runs use diskpart to remove the temp letters.