help with missing boot record.

February 16, 2009 at 12:17:50
Specs: Windows XP
I'm not sure but I'm to believe the command fixboot from a recovery console does in fact try to repair the boot record. I could be wrong?

I had to do this with a drive that had a corrupt boot loader. When running fixboot it said something to the fact of "searing for a good boot record" Well It found one and it choose the wrong one. I now have a fat32 instead of a ntfs and my files are obviously gone.

I see the ntfs record with norton utilities ( partition table info ) but I cant for the life of me imagine how I could use the ntfs boot loader that was on that at one point. I could reinstall windows but I want that data.

I'm trying to use restor2000 a program I have used before but during the search its saying " read disk f: at position ( number )_ failed after 10 attempts..." So I dont think its going to allow me access to the files this time around.

two question.

1) does anyone know of a way to fix the boot record?

2) Does anyone think I have a change at getting my data?


See More: help with missing boot record.

Report •

February 16, 2009 at 13:42:20
"I now have a fat32 instead of a ntfs and my files are obviously gone"

Boot record can not change the file structure.

I'd start with getting a live cd and boot to it just to see what files and partitions are on it.

Then decide if you have selected the wrong partition or what when on. Might be you are looking at the recovery partition.

"Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10

Report •

February 16, 2009 at 13:55:01
Actually it seem its not fat32, instead fixboot decided to make it a fat12, is that not for floppy drives?

I have the drive in a second computer.. It is surly messed up, I dont know why fixboot did that. So I guess I need a way to fix the partition that shows fat12..

Report •

February 16, 2009 at 14:09:37
I guess you could try 'Partition Table Doctor'. But I find it hard to believe that Fixboot would change a NTFS MBR to Fat12. I think I would rather tend to believe a hard drive problem.

Report •

Related Solutions

February 16, 2009 at 14:23:19
you and me both. But the fact is it did.

BTW ptd told me right off the boot record was messed up, and I need to do a fix boot, I did that and there was an option to brows the files that it would allow access to, and that is them. But !! now I have to buy in order to fix LOL.

So.. thx this helps ;)

Report •

February 16, 2009 at 15:07:11

Report •

February 16, 2009 at 15:48:10
There are two boot records, the Master Boot Record and the Volume Boot Record. Fixboot fixes the volume boot record where information on the file system is stored. Every Drive/Partition has its own volume boot record which is put there during formatting.

FixMBR fixes the master boot record which among other things stores the partition table information. The Master Boot Record is created/modified during the partitioning process.

There is no way fixboot would make a hard disk partition Fat12 which is for floppy disks and small hard disk with a maximum size of a little over 16 Mbs.

I would suspect a hard disk problem. If the hard disk checks out start suspecting RAM as faulty RAM can cause unexpected disk errors.


Report •

February 17, 2009 at 08:06:07
StuartS, thx for the info.

The drive is back and I found out there was a virus involved.

history in short.

I was trying to do a windows upgraded when if failed. I then got the ntldr error and had to do the upgrade from dos. At that point I figured I could try the fix boot and after it was finished I was no longer able to install windows as it was showing fat12.

So anything could have done it ( possibly the virus )but fixboot made the drive unwritable. Just a messy chain of events.

Report •

Ask Question