Possible corruption to the NTFS second boot sector.

[schitzn]

Ok, just thought Id pass this out in case this maybe being caused by MyDefrag.

I recently did a MyDefrag of one of NTFS volumes, and I performed a "CHKDSK /F" on it and noticed a previously non-mentioned error in the report:

"The second NTFS boot sector is unwriteable."

I did a google on this, and I come across one user mentioning that a defrag seemed to be involved with either the implementation or resolve of this issue.

My volume appears intact still, and from what I know about the NTFS file system, it keeps two boot sectors, one at the start and another elsewhere on the disk as a backup.

I just thought Id mention this to see maybe if anyone else gets a similar report after executing MyDefrag just incase its something thats being caused by changes since JKDefrag.

[HolyMan]

I recently did a MyDefrag of one of NTFS volumes, and I performed a "CHKDSK /F" on it and noticed a previously non-mentioned error in the report:

"The second NTFS boot sector is unwriteable."

Did you try to solve the problem by setting the disk as a bootdisk again?
I believe the command is something like setboot or so.

[schitzn]

I recently did a MyDefrag of one of NTFS volumes, and I performed a "CHKDSK /F" on it and noticed a previously non-mentioned error in the report:

"The second NTFS boot sector is unwriteable."

Did you try to solve the problem by setting the disk as a bootdisk again?
I believe the command is something like setboot or so.

Not understanding what your saying on this?  This NTFS volume is a partition on one of my physical SATA hard disks.  The computer boots fine, the drive behaves normally, its only CHKDSK that reports that the second boot sector has since become corrupt to some degree.  I assume because the first boot sector is used primarily, and the 2nd is only a backup used in worst case scenario, but the reason for my bringing this up, is because I have only noticed it since using MyDefrag, in light of the possibility of other users maybe able to see the same issue but like me, not noticing any immediate side effects unless one would look at CHKDSK.  Maybe its just coincidental, but I thought I would bring it up considering my SATA its referring to is under 12months old and due to that I hope to not think its because of defectiveness of hardware.

[HolyMan]

Well, the only remark I can still make is that on my very old IDE laptop drive Mydefrag marks both bootsectors as unmovable. So I would guess that MyDefrag will not do anything with them. But let's wait for the judgement of the wise men.

[jeroen]

just incase its something thats being caused by changes since JKDefrag.

Thanks for testing and for the feedback, I appreciate it! I think you are suspecting a bug in MyDefrag having to do with NTFS. That is not possible. MyDefrag does not know anything about filesystems. It does not modify the MFT itself and does not move things on the disk on a sector or cluster basis. The only thing it does is send "move this file to that location" commands to Windows, and this does not change the content of what is being moved in any way. It is Windows that moves things around on your disk, not MyDefrag.

[schitzn]

just incase its something thats being caused by changes since JKDefrag.

Thanks for testing and for the feedback, I appreciate it! I think you are suspecting a bug in MyDefrag having to do with NTFS. That is not possible. MyDefrag does not know anything about filesystems. It does not modify the MFT itself and does not move things on the disk on a sector or cluster basis. The only thing it does is send "move this file to that location" commands to Windows, and this does not change the content of what is being moved in any way. It is Windows that moves things around on your disk, not MyDefrag.

Understood, however it could also be a glitch caused by the API thats only applicable since changes in MyDefrag.  Just bringing this about to see if anyone else experiences this.