-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-11 19:53, John Andersen wrote:
On 2/11/2014 3:24 AM, Carlos E. R. wrote:
However, you probably used a disk partitioning tool too old to recognize the situation and bail out. It did wrote partition data on that MBR, having now GPT partition data and MBR data, and even worst, they do not match.
Wow, what a trap.
So the "Protective" measures built into the MBR fails to offer any real protection?
It appears so. But my hunch has yet to be proved... In a GPT partitioned disk, there is an MBR table. Nothing impedes you from entering partition data on that MBR, if you wish or insist. The wikipedia article says: "Operating systems and tools which cannot read GPT disks will generally recognize the disk as containing one partition of unknown type and no empty space, and will typically refuse to modify the disk unless the user explicitly requests and confirms the deletion of this partition." If the partitioning tool is reasonably recent, it will recognize the presence of a GPT table and stop or give a warning. If it is too old or daft, it will just see an MBR with a huge partition. My guess is that he used some such software. If this is true, the entire disk should be erased and repartitioned, with GPT aware software. Another possibility, mind, is that GPT disks store a backup copy of the table at the end of the disk. The disk might be properly partitioned now as MBR, but that second copy of the GPT table, which is placed at the end of the disk, was probably not erased. And some software is still reading it, and thus saying this is a GPT disk with such and such partitions... If you tell such software to repair the missing main GPT table, then the real and actual MBR will be destroyed! If this is the case, the solution instead is to erase (fill with zeros) the area of the second table. This actually happened to a chap on the forums. There is a CLI command sequence to find out if this is happening, and to erase that second table. But I don't have a link to that thread in this laptop. And it doesn't occur to me a good string to do a search with. I think Andrey Borzenkov was involved in that one. If it was him, he will remember. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL6eSgACgkQja8UbcUWM1zPmAD/RSKg6qRGSU2bcKRnaTLtTmK7 Hc/1Vmy0Sq+esWnq4fwA/RIrT/Wwh8OgCOjQyWs9UcZEjZKgy4RJKHVU819pa9i7 =SIWc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org