Can I undo a "fixboot" command during a recovery attempt ?

  • Thread starter Thread starter Dave Patrick
  • Start date Start date
D

Dave Patrick

You can run;
fixboot D:
or any other drive letter to mark it as active and write the boot sector to
it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Hi,
|
| Long story, but tried a fixboot from a command prompt while trying to
| get a cloned HD to boot. This apparent hosed a different partition on
| the same drive.
|
| Windows complained I had a non-standard MBR. Which is apparent true.
|
| The partition is the 4th and last on an 80gig Seagate according to
| PartitionMagic. When running the MAP from the command prompt it was
| listed as a 36G Partition 1.
|
| This explains my problem booting (the system partition was listed as
| partition 2).
|
| The drive is now mounted as a slave - and I need to repair that
| partition somehow. Disk size/used/unused info is incorrect now, and
| it doesn'thave a serial number anymore.
|
| Any pointers on where to start/ how to proceed ?
|
| Thanks,
|
| L.
|
|
 
You can run;
fixboot D:
or any other drive letter to mark it as active and write the boot sector to
it.
Click to expand...

Thanks Dave,

But I think the <fixboot> is what caused the problem.
Perhaps I don't understand what <fixboot> does exactly.

More info :

Was cloning a Win2kSP4 install to a new 80G HD. (Drive1)

A)
Created 4 partitions with PartitionMagic8
Used DriveImage7 to mirror 3 partitions from Drive0 to Drive1
Loaded 12Gs of backup files to the 4th partition.
There were no errrors and all the files were accessible from the OS.

B)
Swapped cables tried to boot and got ntoskrnl.exe error.
Boot to Win2k CDROM; <map> showed my 4gig system partition as
Partition2 instead of 1 and the 4th partition (a 36 gig storage) as
Partition1 instead of 4.

C)
Ran <fixboot> from the command prompt. Reboot. No joy.
Reboot ran <fixmbr> and aborted when warned of a "non standard MBR"
Modified "boot.ini" to boot to partition2 and the system booted.

But the storage partition is now a "12bit FAT" and of course has
incorrect properties/free space/ etc and no visible files.

The Win2k disk management console shows the partition as a "healthy"
36 gig FAT vol but "properties" shows a 10 Mb vol with 3 Mb free.

Obviously the <fixboot> hosed the partition information.

Where should I go from here ? It seems a repair should be possible
somehow. Could it be a simple as changing the partition type to Fat32
?


I am not shure wht the <fixboot> cmd does or did to a MBR.

A good partition recovery utility to reccomend ?

Thanks,
L.
 
Fixboot only marks the specified partition as active and writes a boot
sector to it. If no drive letter is specified then C:\ is assumed. Fixboot
in of itself shouldn't have caused any partition damage.

This article may also help.
http://support.microsoft.com/default.aspx?kbid=266745

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks Dave,
|
| But I think the <fixboot> is what caused the problem.
| Perhaps I don't understand what <fixboot> does exactly.
|
| More info :
|
| Was cloning a Win2kSP4 install to a new 80G HD. (Drive1)
|
| A)
| Created 4 partitions with PartitionMagic8
| Used DriveImage7 to mirror 3 partitions from Drive0 to Drive1
| Loaded 12Gs of backup files to the 4th partition.
| There were no errrors and all the files were accessible from the OS.
|
| B)
| Swapped cables tried to boot and got ntoskrnl.exe error.
| Boot to Win2k CDROM; <map> showed my 4gig system partition as
| Partition2 instead of 1 and the 4th partition (a 36 gig storage) as
| Partition1 instead of 4.
|
| C)
| Ran <fixboot> from the command prompt. Reboot. No joy.
| Reboot ran <fixmbr> and aborted when warned of a "non standard MBR"
| Modified "boot.ini" to boot to partition2 and the system booted.
|
| But the storage partition is now a "12bit FAT" and of course has
| incorrect properties/free space/ etc and no visible files.
|
| The Win2k disk management console shows the partition as a "healthy"
| 36 gig FAT vol but "properties" shows a 10 Mb vol with 3 Mb free.
|
| Obviously the <fixboot> hosed the partition information.
|
| Where should I go from here ? It seems a repair should be possible
| somehow. Could it be a simple as changing the partition type to Fat32
| ?
|
|
| I am not shure wht the <fixboot> cmd does or did to a MBR.
|
| A good partition recovery utility to reccomend ?
|
| Thanks,
| L.
|
 
Fixboot only marks the specified partition as active and writes a boot
sector to it. If no drive letter is specified then C:\ is assumed. Fixboot
in of itself shouldn't have caused any partition damage.

This article may also help.
http://support.microsoft.com/default.aspx?kbid=266745

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Thanks Dave,
|
| But I think the <fixboot> is what caused the problem.
| Perhaps I don't understand what <fixboot> does exactly.
|
| More info :
|
| Was cloning a Win2kSP4 install to a new 80G HD. (Drive1)
Click to expand...

Snip

Thanks again - a google on "fixboot fat16" or "fixboot fat12" showed
me that this is not unheard of. The fix is rather complicated so
rather than try and edit partition tables and really mess things up -
I'll fire up the cd burner and recover the files by hand.

(Winternals Disk Commander can see the files in the lost partition)

thanks,
L.
 
Hi,

Long story, but tried a fixboot from a command prompt while trying to
get a cloned HD to boot. This apparent hosed a different partition on
the same drive.

Windows complained I had a non-standard MBR. Which is apparent true.

The partition is the 4th and last on an 80gig Seagate according to
PartitionMagic. When running the MAP from the command prompt it was
listed as a 36G Partition 1.

This explains my problem booting (the system partition was listed as
partition 2).

The drive is now mounted as a slave - and I need to repair that
partition somehow. Disk size/used/unused info is incorrect now, and
it doesn'thave a serial number anymore.

Any pointers on where to start/ how to proceed ?

Thanks,

L.
 
Back
Top