"The NTFS in this partition is corrupted"
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I'm trying to backup a Win10 machine with two drives: 500GB M.2 system (C:) drive and a mechanical 2TB data drive (E:).
Backup of the C: completes without issue but ntfsclone complains about the E: drive saying "The NTFS in this partition is corrupted".
It recommends I go into Windows and runk chkdsk /f which I have done several times, but windows does not find any NTFS issues.
Thinks I've tried:
chkdsk /f
chkdsk /r
disabled fast boot
ntfsfix
* rebooting several (3-4) times in a row
Any ideas? patrclone also fails but I don't recall the exact error message...
chkdsk /? gives other options. I think I have had disk results change for different issues that normal check/repair didn't flag/change when a /scan parameter (i think that was the one) made a difference.
Thanks for the suggestion! 'something' worked last night. I added /scan /sdclean and some other options I found from chkdsk /?. Then, after windows finished booting, I 'shut down'. I think before I had been 'restarting' into my USB key. Not sure what fixed it, but my e: drive suddenly became clean and I was able to do the backup.
Hi James
Disabling Windows Fast Startup then running chkdsk c: /f then rebooting Windows twice and then Shutdown the computer is the normal clean up procedure I use before cloning and usually always works for me.
https://help.uaudio.com/hc/en-us/articles/213195423-How-To-Disable-Fast-Startup-in-Windows-10
Glad it worked out though I'd trust restart far more than shut down.
Fastboot started in Win8.0and is a partial hibernation when you turn off the computer through Windows. On next startup some program states are restored to where they were before the shutdown. Though this will not bring back your Word document you had not saved yet, it will bring back Windows's understanding of what files are where on disk without actually looking at the disk. That would be fine as long as nothing happens to the disk between the shutdown and next startup, but dualboot changes that. Windows 7 will allow changing the disk contents while a modern *nix should complain instead of allowing read+write mounting by default. Changes will not be read by win8+ on that next boot by design so if any took place you can expect new changes to not be shown, likely with filesystem corruption as win8+ makes other changes without looking at what it changes first.
Rebooting skips all of that silliness so if a disk will be accessed outside the OS then be sure to reboot win8+ if you do not want to disable fastboot or trust that the settings took. You can shut down the computer during the restart (as BIOS/UEFI steps occur, or go into BIOS/UEFI setup and power off from there. Next boot of Win8+ followed a restart so filesystem will be read from disk instead of referring to a previous memory of it.
I always try to chkdsk before+after any outside OS work with partitions such as repartitioning and cloning, and i want a clean chkdsk report before starting those tasks. Having an unclean chkdsk before leads to odd failures in various programs that handle whole partitions if they interpret its contents instead of blindly copying/restoring all sectors.