On 11/02/14 22:24, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-11 10:55, Basil Chupin wrote:
On 11/02/14 18:50, jdd wrote:
Le 11/02/2014 05:31, Basil Chupin a �crit :
Ce`?
If fdisk cannot read GPT then why is it coming up with the wrong partitioning info? The GPT partition table contains an MBR table at the start, at the place that fdisk expects it. It is made such that programs that do not understand GPT think there is an MBR. This is called "protective MBR".
Se the wikipedia article http://en.wikipedia.org/wiki/GUID_Partition_Table
+++··········· Traditionally, in IBM PC compatible systems the first sector of the disk holds the Master Boot Record (MBR), containing the drive's partitioning information and the code of the first stage boot loader for BIOS-based systems. For limited backward compatibility, this sector is still reserved for a MBR in the GPT specification, but it is now used in a way that prevents MBR-based disk utilities from mis-recognizing, and possibly over-writing, GPT disks. This is referred to as a "protective MBR".
A single partition type of EEh, encompassing the entire GPT drive (where "entire" actually means as much of the drive as can be represented in an MBR), is indicated and identifies it as GPT. 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. This minimizes accidental erasures. Furthermore, GPT-aware OSes will check the protective MBR and if the enclosed partition type is not of type EEh or if there are multiple partitions defined on the target device, the device should not be manipulated. ···········++-
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.
Please post the output of "fdisk -l" from an openSUSE system, even a rescue system. I do not trust that SystemRescueCD of yours. And the ouput of "parted -l".
Thanks for the above - I will study it more closely later. In answer to your last para, the fdisk -l info I provided comes from openSUSE 13.1 :-) , as did the YaST info. I would need to get at the laptop to be able to post here the exact output of fdisk but believe me it gives exactly what I mentioned - the partitions as they were before I formatted the HDD. BTW, when I installed 13.1 after formatting the HDD I had YaST replace the MBR during the installation process. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org