Storage Solutions Disk boot error?

Status
Not open for further replies.
A

apsk121

Inactive
Contributor
My mobo had some problems recently and I got it replaced.

I changed nothing on the HDD, but it gives me the disk boot error when I tried to boot from the HDD.
The only thing I did do was connect it to a SATA to USB enclosure to retrieve some data from it. I din't change anything, just copied some data from it...

What could be the problem? Any solutions to fixing the boot record or whatever it is called?
 
FIXBOOT

fixboot drive name:

Use this command to write the new Windows boot sector code on the system partition. In the command syntax, drive name is the drive letter where the boot sector will be written. This command fixes damage in the Windows boot sector. This command overrides the default setting, which writes to the system boot partition. The fixboot command is supported only on x86-based computers.

FIXMBR

fixmbr device name

Use this command to repair the MBR of the boot partition. In the command syntax, device name is an optional device name that specifies the device that requires a new MBR. Use this command if a virus has damaged the MBR and Windows cannot start.

Warning This command can damage your partition tables if a virus is present or if a hardware problem exists. If you use this command, you may create inaccessible partitions. We recommend that you run antivirus software before you use this command.

You can obtain the device name from the output of the map command. If you do not specify a device name, the MBR of the boot device is repaired, for example:

fixmbr \device\harddisk2

If the fixmbr command detects an invalid or non-standard partition table signature, fixmbr command prompts you for permission before rewriting the MBR. The fixmbr command is supported only on x86-based computers.
Click to expand...

Description of the Windows XP Recovery Console

boot from a winxp cd, choose recovery console , and the rest is in the link :)
 
unless the data was stored under bootX (/System/Library/CoreServices/BootX)... it may have copied the bootloader which could have further erased the previous windows bootloader..
but thats again a rare occurence.. this may be a loose connection, try connecting directly to a sata port on the mobo and try again .. otherwise you will have to erase the hard drive and perform the fixmbr command.. let me know whats the outcome :)
 
could it be a bios setting for the sata mode (legacy vs native, and ahci vs ide mode)... ?
 
maybe not as hes trying to connect to a USB .. it doesnt matter if its ahci or sata or ide when it comes to USB from sata ... maybe i m wrong .. :S
 
Status
Not open for further replies.
Top Bottom