Answer the question
In order to leave comments, you need to log in
What is the best way to restore mbr after magic partitions?
A physical disk with logical ones: C, D. I wanted to split D into D and E. On the C drive, wine 7. Through the partichen I assigned what to do, the computer, as expected, went to reboot. Then there was a jamb, the picture on the monitor began to be displayed outside the monitor, I saw only a strip along the right edge, then reboot (it would be better to sit and wait in the dark - whether operations are being performed).
After that, Windows stopped loading.
Then I ran Linux Mint 18.1 from a flash drive. Folders on drives C and D are opened, files are copied. As far as I understood, only the boot sector flew off.
I tried the following methods through system restore (nothing helped):
1) restore the boot sector in automatic mode
2) through manual mode, I didn’t understand a bit. Found out via Diskpart that my C became F.
The instructions said:
"After entering the commands, you should see a list of available disks, you need to find the letter that is assigned to the disk from which you booted, for example, it will be the letter E.
Exit the Diskpart utility - to do this, write exit on the command line and press Enter
Now you need to go to the disk from which we booted, for this we write on the command line:
E: and press Enter ..."
Why does the author write about drive E? Booting from a flash drive is carried out from disk X, after exiting Diskpart, we automatically find ourselves again on disk X. Or in my case, do I need to register disk F?
3) The commands "bootrec.exe /FixMbr" and "bootrec.exe /FixBoot" are executed successfully, but the system does not start.
4) bootrec.exe /RebuildBcd - did not help. Finds system F:\Windows, but then writes: "The requested system device cannote be found".
5) bcdboot.exe f:\windows - did not help. Writes "Failure when attempting to copy boot files"
6) Disk commander. After analyzing the disk, I displayed a list of lost sectors (?), but when I tried to restore them, I gave errors.
7) Hiren's Boot CD was written to the flash drive:
7.1) Paragon Hard Disk Manager 12 via DOS (alternatives) - gives an error when creating a Ram disk: "The name of the command or file is incorrect."
Paragon Hard Disk Manager 12 in the main menu - starts but gives out: "Restart operation required - the previous session was not completed correctly. Restart is required ...". I press "Yes", but this cat appears again and again. There is no correct output. When exiting via Alt + F4, black screen and blinking underscore in the top left corner. Then restart.
7.1) Acronis Disk Director Server 10 - no hard drives found.
7.2) Mini Windows XP - blue screen of death
8. Live CD didn't start from flash drive.
Now I'm dealing with Smart Boot Manager 3.7.1, until I figured out how to use it.
PS: Not so long ago I upgraded the hardware to the Skylike generation, and until I got used to the features of the new BIOS on UEFI, I used to cut it down, like now. In CSM - the parameters of boot devices were set to "Only Legacy OPROM".
Answer the question
In order to leave comments, you need to log in
Perhaps the reason is that you disabled UEFI and deleted its boot partition - a hidden system partition, 100...300 MB in size. I do this too, because I don't like " UEFI features " either , I'm more used to the good old MBR. But after that, you need to assign the boot partition that contains the OS (by any advanced partition manager), and then restore the bootloader. The easiest way to repair the bootloader is to launch any LiveDVD/LiveUSB containing the well-known utility package 2k10, which has a "Recovery Boot" section. There are a dozen utilities in this section - one of them will help you, as it helped me.
By the way, there is no 2k10 package in Hiren's Boot CD, EMNIP. I use MultiBoot instead of Hiren's Boot CDom is a completely universal tool for all occasions of computer life.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question