Question SSD MBS (masterboot sector) issue - permanent or repairable?

Sep 2, 2023
3
0
10
Hi,
I turned my pc on and got a blue screen stating that a boot file could not be found. So I checked the boot options and all my disks are visible. Used a windows CD to chkdsk and the disk wiht the system on it stated "Corrupt master file table. Windows will attemt to recover master file table from disk. Windows cannot recover master file table".

First I tried with bootable windows and
bootrec /fixmbr
bootrec /fixboot
bootrec/fscanos (told me there were 0 windows system found)....
still tried bootrec /rebuildbcd but no success

So I took out an old disk, set new windows on it, hooked up the "damaged disk" to the system and tried
  • Aomei Partition
  • MiniTool Partition
  • EaseUS Partition
to recreate the MBS (not right after each other, but after restarts). All of them said it worked, but i still cannot accesss the drive (not the drive not the data). In windows I see the drive letter, but when I click on it it sates

"F: is not accessible. The disk structure is corrupted and unreadable"

My questions:
1.) Do you think this is a permanent error or is there a way to still fix it?
Reinstall or buy a completly new disk?

Thanks!
 
Last edited:
Hi,
I turned my pc on and got a blue screen stating that a boot file could not be found. So I checked the boot options and all my disks are visible. Used a windows CD to chkdsk and the disk wiht the system on it stated "Corrupt master file table. Windows will attemt to recover master file table from disk. Windows cannot recover master file table".

First I tried with bootable windows and
bootrec /fixmbr
bootrec /fixboot
bootrec/fscanos (told me there were 0 windows system found)....
still tried bootrec /rebuildbcd but no success

So I took out an old disk, set new windows on it, hooked up the "damaged disk" to the system and tried
  • Aomei Partition
  • MiniTool Partition
  • EaseUS Partition
to recreate the MBS (not right after each other, but after restarts). All of them said it worked, but i still cannot accesss the drive (not the drive not the data). In windows I see the drive letter, but when I click on it it sates

"F: is not accessible. The disk structure is corrupted and unreadable"

My questions:
1.) Do you think this is a permanent error or is there a way to still fix it?
Reinstall or buy a completly new disk?

Thanks!
Possibly corrupted control chip firmware, you could try re-flashig it.
 
The $MFT is an NTFS metafile. There is no point in trying to fix the MBR or boot sector, as neither of these are broken.

I would start by obtaining a SMART report from the drive using tools such as CrystalDiskInfo or GSmartControl.

Then examine the drive with DMDE:

https://dmde.com/

In DMDE's Partitions tab, d-click your NTFS volume. Do you see your file/folder tree? If so, r-click and recover your important data to another drive.
 
Hi, I actually gave up, purchased anoter SSD and funny enough, went also with dmde to recover the files. It seems that quite a few of them were actually corrupt. Not sure why and how, but that is life.

@fzabkar : For educational purposes, can you please explain a little more "There is no point in trying to fix the MBR or boot sector, as neither of these are broken."
I have read a few threads and though it could be "just" remapped/rebuild. (obviously in my case it couldnt' :).... )
Thanks
 
The MBR is the code in sector 0. There is also a partition table in this sector. The partition table identifies the locations of the boot sectors of each partition/volume.

The boot sector is the first sector of your NTFS volume. It contains information about the NTFS volume, including the location of the $MFT.

The $MFT is the Master File Table. It contains information (metadata) about all the files and folders in the NTFS volume.

I suspect that DMDE will show an underlined "F" in the Indicators column for that partition. This would be indicative of some kind of corruption in the file system.
 
Hi @fzabkar,
can i reformat the SSD and reuse, or just toss it to be safe. In other words would that be a software problem or a hardware?
Thanks