2019 16" MacBook Pro - Catalina 10.15.7 with a NVMe SSD
BOOTCAMP Volume with Windows 10 (21H1) installed via Boot Camp Assistant
Would like to clone the BOOTCAMP volume with WinClone 9
Two Canoes / WinClone insist that we need to run chkdsk /b prior to cloning to check at the block level for errors on the BOOTCAMP volume.
With a fresh Win10 install -- chkdsk (without any parameters) reports no errors.....
I get one of 3 results when running chkdsk /b on the BOOTCAMP volume on this SSD. (I've started this over several times while troubleshooting....)
ONE: chkdsk /b appears to complete and when Windows attempts to restart I get a BSOD of death with a:
"Stop code: BAD_SYSTEM_CONFIG_INFO" error
TWO: chkdsk /b seems to complete but it marks more than 90% of the BOOTCAMP Volume as bad sectors.
THREE: chkdsk /b appears to complete, Windows restarts but chkdsk now reports;
“The master file table’s (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.”
Running chkdsk /scan reports no errors.
Restart Windows and chkdsk once again reports the MFT error.
If I start by running chkdsk /f, it appears to complete but subsequently running chkdsk (no parameters) reports the MFT error.
Once I have the MFT error no combination of chkdsk parameters appears to have the ability to repair the MFT error. Every time I run chkdsk /scan it reports not errors.
Searching online it appears that it is not advised to run chkdsk /r (chkdsk /b include the functionality of /r) as it has been know to mark many "sectors" on an SSD as bad when in fact the SSD is fine and furthermore, the SSD controller takes care of marking errors on the SSD.
I know from past experience (2014 MacBook Pro - PCI SSD - El Capitan - WindClone 5) that running chkdsk /b used to work just fine on a SSD volume... (of course at that time a block level clone was the ONLY option in WinClone)
Anyone else run into anything similar. I find precious little info regarding MFT errors on line and almost all of the article that do talk abut this MFT error suggest that running chkdsk /scan and restarting should clear the MFT error???
I've posted on the Two Canoes forums (posted there because they re the ones insisting chkdsk /b should be run prior to cloning with WindClone) but so far not a single peep from anyone there....
Thanks
John
BOOTCAMP Volume with Windows 10 (21H1) installed via Boot Camp Assistant
Would like to clone the BOOTCAMP volume with WinClone 9
Two Canoes / WinClone insist that we need to run chkdsk /b prior to cloning to check at the block level for errors on the BOOTCAMP volume.
With a fresh Win10 install -- chkdsk (without any parameters) reports no errors.....
I get one of 3 results when running chkdsk /b on the BOOTCAMP volume on this SSD. (I've started this over several times while troubleshooting....)
ONE: chkdsk /b appears to complete and when Windows attempts to restart I get a BSOD of death with a:
"Stop code: BAD_SYSTEM_CONFIG_INFO" error
TWO: chkdsk /b seems to complete but it marks more than 90% of the BOOTCAMP Volume as bad sectors.
THREE: chkdsk /b appears to complete, Windows restarts but chkdsk now reports;
“The master file table’s (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.”
Running chkdsk /scan reports no errors.
Restart Windows and chkdsk once again reports the MFT error.
If I start by running chkdsk /f, it appears to complete but subsequently running chkdsk (no parameters) reports the MFT error.
Once I have the MFT error no combination of chkdsk parameters appears to have the ability to repair the MFT error. Every time I run chkdsk /scan it reports not errors.
Searching online it appears that it is not advised to run chkdsk /r (chkdsk /b include the functionality of /r) as it has been know to mark many "sectors" on an SSD as bad when in fact the SSD is fine and furthermore, the SSD controller takes care of marking errors on the SSD.
I know from past experience (2014 MacBook Pro - PCI SSD - El Capitan - WindClone 5) that running chkdsk /b used to work just fine on a SSD volume... (of course at that time a block level clone was the ONLY option in WinClone)
Anyone else run into anything similar. I find precious little info regarding MFT errors on line and almost all of the article that do talk abut this MFT error suggest that running chkdsk /scan and restarting should clear the MFT error???
I've posted on the Two Canoes forums (posted there because they re the ones insisting chkdsk /b should be run prior to cloning with WindClone) but so far not a single peep from anyone there....
Thanks
John
Last edited: