the Internet Windows Android

How to find out which disk partition table. How to find out what GPT or MBR drive is used in your computer? Problems of working with the new standard and their decision

The situation is as follows. There is a screw at 160GB. On it 2 sections - 40GB and 120GB. In order to install Ubunti as the second system, a breakdown was made 120GB -\u003e 100 + 10 + 2 + 8.
RESULTS
1. When loading the system, the message MBR Helper Not Found is displayed;
2. FDISK shows one large 160GB disk.

Fool is clear that this is the beginning of a fun night.
Next, under the cut, solving the issue.

1. Restore partition table

1.1. Parted Magic.
This LiveCD \\ USB distribution, 100MB in size carries a huge bunch of software, to work with disks. From breakdown, before recovery.
Of these, all we need will be gpart., testdisk., fDISK. and mS-SYS..
1.2. Gpart.
gPart is a utility scanning a sector disk for sections that are present on a carrier, but not in the table. In his work, she ignores already existing table (if present). The program is raised by the German programmer Michail Brzitwa and no longer supported. The sluggish development is conducted by Fedora and Debian teams. Current version - 0.1h.

The utility allows you to quickly and easily restore the partition table, but it carries several drawbacks. First, the development was long abandoned, secondly, it sometimes does not quite correctly define sections.

GPart can work in 2 modes. This is a quick analysis and detailed scanning. In some cases, the first mode is sufficient. We will look at the second.

GPART -IF / DEV / SDA

-I. - Interactive mode. A question will be asked for each found partition, save it or skip it.
-f. - Full disk scan.

After, quite a long time, a report will be created with possible partitions. Its one must necessarily look at the recording as closely as possible.
Example of the report (not mine):

Begin Scan ...
Possible Partition (DOS Fat), Size (1907MB), Offset (0MB)
Possible Partition (SGI XFS FileSystem), Size (5730MB), Offset (1907MB)
End Scan.
Checking Partitions ...
Partition (DOS or Windows 95 WITH 32 Bit Fat, LBA): Primary
Partition (Linux Ext2 Filesystem): Primary
OK.
Guessed PRIMARY PARTITION TABLE:
PRIMARY PARTITION (1)
Type: 012 (0x0c) (DOS O Windows 95 WITH 32 BIT FAT, LBA)
Size: 1907MB #S (3906544) s (16-3906559)
CHS: (0/1/1) - (1023/19/16) D (0/1/1) - (12207/19/16) R
PRIMARY PARTITION (2)
Type: 131 (0x83) (Linux Ext2 FileSystem)
Size: 5730MB #S (11736000) S (3906560-15642559)
CHS: (1023/19/16) - (1023/19/16) D (12208/0/1) - (48882/19/16) R
PRIMARY PARTITION (3)
Type: 000 (0x00) (Unused)
Size: 0MB #S (0) S (0-0)

PRIMARY PARTITION (4)
Type: 000 (0x00) (Unused)
Size: 0MB #S (0) S (0-0)
CHS: (0/0/0) - (0/0/0) D (0/0/0) - (0/0/0) R

If everything is OK, then agree to the entry in the partition table, we cross your fingers and reboot.
In my case, the program identified sections that were before breaking (40 and 120), which did not fit and forced to look for alternative methods Recovery.

1.3. Testdisk.
Note: More This utility is described in this post, I will not repeat here.

This utility is similar to the previous one, but has a number of advantages:
1. Fresh and actively supported;
2. Subjectively, it works much faster;
3. Functional;
4. There is a simple console interface based on Ncurses.

Go!
1. In the first window, select CREATE A NEW Log File;
2. Choose disc (/ dev / sda) -\u003e proceed;
3. We note the type of sections as Intel;
4. Select Analyse Current Partition Structure and Search for Lost Partitions;
5. If the found partitions are correct, click Backup and go to step 6, it is possible to quickly retell the disk if somewhere (Quick Search);
6. There is already a green list with sections. If OK, then write, otherwise launch Deep Search.;

In my case, the result was similar to the result of GPART, which is incorrect.
Running Deep Search, waiting about 40 minutes. I received a response from which the soul was sad enough.
A few partitions were found, which were superimposed by one to another (these were the initial (to manipulation) 120GB and the new, 100GB). Noting unnecessary, as a remote, I recorded the table on the disk and rebooted. Fortunately, everything turned out and the computer returned to the state, which was initially, and I could go to bed with a clean conscience.

3. Restoration of MBR

For this task, we have a MS-SYS Tulza in the arsenal.
First we learn that with our MBR.

MS-SYS / DEV / SDA
/ Dev / SDA HAS AN x86 boot sector
IT IS Unknown Boot Sector

Now it is clear that there is no boot sector on this disk.
The utility can work with MBR of various operating systems. The list can be obtained by running the program without aggregates. In my case, it was necessary from Windows 7.
Record MBR to disk:

MS-SYS -7 / DEV / SDA
Windows 7 Master Boot Record SuccessFully Written To / Dev / SDA

Check:

MS-SYS / DEV / SDA
IT IS Microsof 7 Master Boot Record, Like The One This
PROGRAM CREATES WITH THE SWITCH -7 ON A HARD DISK DEVICE.

That's all, the necessary MBR is installed and can be rebooted.

3. Outro.

This post is an example of how from an empty place you can create a problem and midnight do not do what it is necessary. But it gave an invaluable experience that I tried to set out here.
Perhaps someone is useful. After all, it is not very difficult to get into this situation, but there is no particular manual.

If you have ever made a disk marking or even more, tried to install Linux on a laptop with pre-installed Windows 8 or more new version, Most likely met with such concepts as a partition table, GPT and MBR. Even if you erased Windows, you still probably wondered what the MBR differs from GPT, which table partitions is better, what are the advantages of the GPT from the MBR. In this article we will answer all these questions and after reading it you will already know exactly what partition table you need, but first a little theory.

As you know, hDD Not a whole substance to which the system is installed. We can divide it into several sections to set one system to one another, and leave the third, and the third is generally left under the files. This separation was both in Windows - this is a disk with :, D:, there is both in Linux - SDA1, SDA2, SDA3.

But the question is how the system recognizes the structure of the hard disk? In fact, the hard disk is a huge address space in which you can write data. To know how many sections exist, what size they are, on which cell begin and on which one you run out somewhere to store this data somewhere. Here you already need a MBR or GPT partition table. Or how they decrypt Master Boot Record and GUID Partition Table. Despite the fact that they differ in architecture, they perform the same work. The difference between MBR and GPT will be better understood if we look at them in turn.

MBR (Master Boot Record)

MBR is an old standard partition table, but it is still widely used by many people. This partition table was developed during the DOS times, in 1983, and therefore contains many relevant restrictions.

The MBR is at the very beginning of the disk, if more precisely, it takes the first 512 bytes. It contains information about what logic and extended sections are on this device. In addition, the MBR is the executable code that can scan sections in search operating system, as well as initiate the loading of the operating system. For Windows is windows bootloaderIn Linux there is a GRUB initialization code. Since there are very few places there, usually this code is used only to initialize the main bootloader located somewhere on the disk.

Very uncomfortable MBR restriction, this is what you can have only four disk partitions. This is associated with a limited amount of memory allocated under the partition table. So it was from the very beginning, but then the developers found a solution. The usual sections began to be called primary (Primary), and also added extended (extended) and logical (Logical). One advanced section may contain several logical, so you can create the required number of sections.

In addition, the MBR uses a 32-bit space addressing, so you can only work with disks of up to two terabytes. Of course, over time, there were ways to maintain large volumes, but it will not work with them. Another minus is that the MBR is located only at the beginning of the disk and if you randomly scold it, then the disk will be fully unreadable. Plus, the MBR can be called full compatibility with many operating systems including Windows, including old versions, Linux and MacOS.

GPT (GUID PARTITION TABLE)

GPT is a modern standard for managing hard disk partitions. This is part of the EFI standard (Extensible Firmware Interface) designed in Intel to replace the outdated BIOS.

The very first difference is the use of a completely different disk addressing. The MBR used addressing dependent on the disk geometry. The address consisted of three head values, cylinder and sector (for example 0.0.0). GPT uses LBA addressing. This block addressing, each block has its own number, such as LBA1, LBA2, LBA3, and so on, with the MBR addresses are automatically broadcast in LBA, for example, the LBA1 will have address 0.0.1 and so on.

GPT does not contain the bootloader code, it expects what will be engaged in EFI, only the partition table is posted here. In the LBA0 block is MBR, it is done to protect against GPT to the old work disks, and the GPT itself begins with the block (LBA1). Under the partition table, 16,384 memory bytes is redundant, 512 per unit, and this is 32 blocks, so the first partitions will begin with the LBA34 block (32 + 1MRB + 1GPT).

An important advantage is that the number of sections is not limited. More precisely limited, only the operating system. Linux kernel supports up to 256 sections.

Thanks to the addressing LBA, GPT, unlike MBR, can create sections up to 9.4 zb, and this is enough in the near future.

In addition, GPT service information is duplicated, it is placed not only at the beginning of the disk but at the end, so in many cases, when damaged GPT can work automatic recovery And you will not even notice problems. It is already immediately becoming clear what is better than MBR or GPT.

GPT supports Unicode Therefore, you can set the names and attributes to the partitions. Names can be specified on any supported language and you can access the disks on these names. For disks, global unique Identifier (Globally Unique Identifier) \u200b\u200bare used, this is one of the UUID variations with a greater probability. unique valuesmay also be used to identify disks instead of names.

Minus or another plus GPT is that when loading is checked control sums Tables, which means that if you want to change something manually, the system will not boot. As you can see the difference between MBR and GPT are just colossal.

Support for operating systems

MacOS and new windows version Starting from Windows 8 use GPT by default. You will not be able to install MacOS in the MBR system, it will work on this disk, but you will not be able to install it there. Windows supports both MBR and GPT starting from version 8, earlier versions to install on GPT will not be able to work with GPT from XP.

Linux kernel includes support for both MBR and GPT, only to install on GPT you will have to use the GRUB2 loader. Here, the MBR VS GPT comparison is not so unambiguous. If you need an old operating system, nothing with GPT will be released.

What is the partition table

Now let's look at how to learn GPT or MBR is used on your computer. Of course, if you have Windows 10 on a laptop, there is nothing to think here, there is exactly GPT, but in other cases it will be useful to learn.

In Linux, we can use the FDISK utility for this. Just perform:

Disk / Dev / SDA: 465,8 Gib, 500107862016 Bytes, 976773168 Sectors
Units: sectors of 1 * 512 \u003d 512 bytes
SECEM Size (Logical / Physical): 512 bytes / 512 bytes
I / O Size (Minimum / Optimal): 512 bytes / 512 bytes
DiskLabel Type: DOS
Disk Identifier: 0x1C50DF99

Disklabel Type: DOS means that you use the MBR, it will be both written in GPT - GPT. You can also learn GPT or MBR using the GParted program.

conclusions

Now you know what the MBR differs from GPT, and you will not have difficulties when choosing a partition table. If you use a disk size less than two terabytes and you do not need more than four partitions, it is possible not to choose GPT. Some old BIOS do not support the normal system load from the GPT tables, moreover, without UEFI, you will not be able to install Windows to this partition table. But if you want to install only Linux on GPT, then there is nothing wrong with that. Determine what is better than MBR or GPT, depending on your situation.

Let's summarize everything above the written and once again we give the advantages of GPT in front of MBR:

  • MBR supports to 2 TB discs, GPT - up to 9 zb
  • GPT supports more than four sections
  • GPT uses GUID to identify disks, which means less chance of name conflicts
  • GPT uses new system LBA addressing, instead of obsolete chs
  • GPT service information is duplicated at the beginning and end of the disk
  • GPT checks the control homes, which allows you to detect the modification of the partition table
  • GPT supports Unicode, and therefore Cyrillic names.

The latest versions of Windows and other operating systems can use one of the two standards to store information about the hard disk sections. This is the old standard - the main boot record of the MBR and the new standard - the GUID partition table or simply GPT. Today we will tell you how to learn GPT or MBR drive is used in the computer to store information about the disk sections.

As we have noted, only a few standards are used to store data on the disk sections. GPT sections table is the most progressive and new standard. It is necessary for windows downloads systems in UEFI mode. Earlier operating systems are capable of working only with the main boot record of the MBR standard. For example, Windows 7, without any restrictions, can boot from the disk with sections marked according to the MBR standard. Windows 7 can boot from the GPT partition, but under certain conditions: OS should be 64-bit, and motherboard Instead of obsolete BIOS, it must be equipped with a modern UEFI software interface that connects the operating system and the hardware firmware of the platform.

In order to determine which partition table is used by your disk - GPT or MBR, there are two simple and affordable tools. First of them, regular windows utility With a graphical interface called Disk Management Tool. The second, more complex and incomprehensible for beginner - commands entered on the command line.

Method First: Analysis in the Disk Management Tool utility

Find out information about the standard hard sections You can use the DISK Management Tool utility using the Disk Management Tool utility.

  1. In order to start the utility in Windows 7, right-click on the "Computer" shortcut on the desktop and select "Management" in the context menu:
  • Next, in the list of system utilities, select "Disk Management" or "Disk Management".
  • In some cases, it is possible to start the utility easier - just click the Windows Key + x key combination and select "Disc Control".
  • Another launch option. Click simultaneously windows keys Key and R to run the "Run" dialog box. Insert or dial "diskmgmt.msc" in the input string, and then press "ENTER".
  • In the graphics window, the "Disk Management" utility will find that hard disk, the table of sections of which interests you. Click on it right-click and select "Properties" or "Properties" in the context menu.
  • In a new disk properties window, select the "Volumes" tab. In Tom properties, find the PARTITION STYLE parameter. It is here that you can find out, GPT or MBR drive you use. In our example, it can be seen that the disk partition table corresponds to the MBR standard - "MBR basic boot record". In English, it is written as "Master Boot Record (MBR), otherwise -" GUID PARTITION TABLE (GPT) ".

  • The second method: Using the DiskPart command on the command prompt

      1. To evaluate which partition table is used on a disk - GPT or MBR, you can use the standard "diskpart" command via the Windows OS command prompt. To do this, you first need to open the command prompt window with administrator rights. This can be done in one way:
    • Click the "Start" button and in the list of the program list, enter the name of the "CMD" command line utility in the search string. In the list of objects found, select the program with the name "CMD", click on it right key and select in the list context menu "Run on behalf of the administrator." This method is suitable for both Windows 7 and Windows 8.
    • Click the "Windows" and "X" keys simultaneously and select "Command Prompt (Admin)" or "Command Line (Administrator)". This method is available only for Windows 8.
  • Now that the command line window opened, type two commands sequentially. Each Enter Command Complete by pressing the "ENTER" button. So consistently type:
    1. As a result, a list of all disks connected to the computer will open in the command line window. If the disk has a partition table in the GPT standard, then in the "GPT" column it will be marked with an asterisk "*". If there is no sprocket in this column, then it is a disk with MBR markup.

    In our case, in the screenshot, it is clear below that two disks Disk 0 and Disk 1 have marked partitions according to GPT, and Disk 2 disk is a MBR disk.

    So, now, when you know how to determine the GPT or MBR disc, you can proceed to the question of how, from one standard to another. What and the following article will be devoted.

    MBR - outdated hard disk format (or flash drive),
    in demand so far (because of his unpretentiousness)

    Master Boot Record (MBR) is the main boot record of the information media containing information about its sections. Damage or loss of MBR makes inaccessible information on a disk or flash drive. To restore the MBR exist special utilities, Testdisk type.

    Testdisk "will review" the entire medium of information and create a partition table. The program requests from the BIOS or operating system information about hard drives in the system, makes a quick check of disk structures and partition tables to "correctness". In case of error detection, TestDisk will help fix them. In addition, TestDisk, when scanning a carrier, can detect long-distance sections on it.

    TestDisk - free free-distributed program for restoring the main boot record disk or flash drives. The program is swinging without problems from the Internet. English interface, but is the rare case when it is better not to chase.

    Testdisk has no graphic shell. Communication with the program occurs in the Black DOS-owl window. It is probably. If the system "fell", what's the graphic shell here. We load from dos and run TestDisk.

    Testdisk supports work, virtually all known operational and file Systems. The list of basic features of the program looks like this:

    1. Restoring remote sections
    2. Perestroika partition table
    3. Overwriting MBR

    Hello.

    Pretty many users have already encountered errors associated with the markup on the disk. For example, quite often, an error appears when installing Windows: " Installing Windows on the this disc Impossible. Selected disk has GPT sections style«.

    Well, or questions on MBR or GPT appear when some users buy a disk, the size of which is more than 2 TB (i.e. more than 2000 GB).

    In this article, I want to affect issues related to this topic. So, proceed ...

    MBR, GPT - why it is needed and what is better

    Perhaps this is the first question that users are asked for the first time encountered with this abbreviation. I will try to explain more simple words (Some terms will be specifically simplified).

    Before the disk can be used to work, it must be divided into a specific partition. Store information about the partitions of the disk (data on the start and end of the partitions, which section belongs to a specific disk sector, which section is main and is bootable, etc.) can be in different ways:

    • -MBR: home boot record;
    • -GPT: GUID partition table.

    MBR appeared for a long time, in the 80s of the last century. The main limitation that large disk holders may notice are that the MBR works with disks whose size does not exceed 2 TB (although, under certain conditions, you can use discs and more).

    Under the same detail: MBR supports only 4 major sections (although for most users it is enough with interest!).

    GPT is a relatively new markup and it has no restrictions, like MBR: wheels can be much more than 2 TB (and in the near future with this problem, someone is hardly encountered). In addition, GPT allows you to create an unlimited number of partitions (the restriction in this case will impose your used OS).

    In my opinion, GPT has one undeniable advantage: if the MBR is damaged, then an error will arise and failure when loading OS (because mBR data Stores only in one place). GPT also stores several copies of data, so that if one of them is damaged - it will restore the data from another place.

    It is also worth noting that GPT works in parallel with the UEFI (which came to the BIOS shift), and due to this has a higher download speed, supports secure load, encrypted discs, etc.

    Easy way to recognize the markup on the disk (MBR or GPT) - through the disk management menu

    You must first open the Windows OS control panel and go to the next way: Control Panel / System and Security / Administration (Screenshot is presented below) .

    After that, on the left menu, open the section " Disc management", And in the opening list of discs on the right, select the desired disk and go to its properties (see on the red arrows on the screenshot below).

    Example Tab Tab - MBR.

    But below is a screenshot, what the GPT markup looks like.

    An example of the TOMA tab - GPT.

    Determining disk marking via the command line

    Quite quickly determine the markup of the disk by using command line. I will consider the steps how this is done.

    1. First press the button combination Win + R. To open the "Run" tab (or through the Start menu, if you use Windows 7). In the Run - Write diskpart. And press ENTER.