Messed up bootcamp filesystem after partition resize

Question

Level 1

8 points

Messed up bootcamp filesystem after partition resize

Hello,

After trying to resize the bootcamp partition, the filesystem of windows got damaged, the bootcamp partition is visible from the boot menu, but it doesn't boot correctly, instead I am getting the message that Windows could not boot and automatic system repair could not do anything, I am getting the blue troubleshoot screen

I tried everything from this point, the chkdsk x: /f /r /x from the cmd shows that it cannot run on this drive as it is write protected, I don't have any image to be restored as well, so its a dead end.

Tried to fix it somehow from the OS X stand point, tried some commercial recovery software, as I really need to recover important dev flutter repositories(which I didn't back up as well - dumb me - I really hate myself right now) , I don't really care about the whole windows installation.

But through the software (tried disk drill and imyfone any recover) I only achieved half-success as the repositories got recovered only partly, much files didn't recover. So I assume that the bootcamp filesystem got messed up pretty badly.

There comes my question - is there any way to fix the bootcamp filesystem from the OS X, or successfully run the chkdsk on the bootcamp partition to fix bad sectors and filesystem. Im really stuck and depressed as I lost almost a year of work and application development. I can post the testdisk logs if it would be helpful in any way.

Posted on Jul 27, 2021 1:14 AM

Reply

Answer 1

Loner T

Level 9

59,536 points

Jul 29, 2021 5:11 AM in response to sime0ne

You may want to consider removing the current installation and re-installing Windows. In its current state, Testdisk will not recognize the NTFS file system correctly since partition headers were moved by Paragon HDM. Recovery at this point is very unlikely.

Reply

Answer 2

Loner T

Level 9

59,536 points

Jul 27, 2021 12:18 PM in response to sime0ne

sime0ne wrote:

https://discussions.apple.com/content/attachment/a58a0950-4f7d-4a54-bc16-c8db7bee7ae0

So this first partition seems to be the bootcamp one as its size matches.

It may be the same size, but the location is incorrect. If you notice, Testdisk says "the following partitions can't be recovered". At this point, you should scroll down to "Continue" and press Enter/Return to get to the list of viable partitions. Based on the output, your Windows partition should be 213069824 sectors in size.

Reply

Answer 3

Loner T

Level 9

59,536 points

Jul 27, 2021 5:21 AM in response to sime0ne

Can you post the list of viable partitions from Testdisk?

Reply

Answer 4

sime0ne Author

Level 1

8 points

Jul 27, 2021 8:29 AM in response to Loner T

Thanks for the reply! Here is first screen from TestDisk :

Here is first weird thing, as my ssd is only 250 gb, so there should be a partition of bootcamp windows (120 gb), what is weirder I can see it from the finder:

Here is current partition structure of the rdisk0, it has ms data apparently:

Will post result of the scan as soon as it finishes.

Reply

Answer 5

sime0ne Author

Level 1

8 points

Jul 27, 2021 10:09 AM in response to sime0ne

So this first partition seems to be the bootcamp one as its size matches. I don't know where did the linux filesys came from as I never have used any unix system on this MacBook.

Here is the content of that MS Data 109 GB partition

When I try to list files on that 109 GB MS Data section I get this:

Reply

Answer 6

sime0ne Author

Level 1

8 points

Jul 28, 2021 1:45 AM in response to Loner T

Loner T wrote:

At this point, you should scroll down to "Continue" and press Enter/Return to get to the list of viable partitions. Based on the output, your Windows partition should be 213069824 sectors in size.

Sorry, I don't quite understand, there's no possibility to scroll down to continue, whenever I try to scroll down from the last listed partition the pointer comes back up to the first one. I can only choose one of the listed partitions, and enter/return leads me to the content that I have posted above. I see that there is another MS Data partition below that is in fact 213069824 sectors in size(5th in a row). When I try and continue to the content of it I get similar content as from the first one. Few MS Data partitions with 213069824 sectors in size as seen on the screen:

Should I run deep search on any of these?

Reply