Description of problem: I've tried to install Mageia 3 RC LiveDVD-KDE x86_64 on my new internal HDD and it failed to discover existing Windows 7 partitions on that disk. Initially partitions were created on an empty HDD using Windows 7 x64 installer (in manual mode to prevent it occupy the hole HDD). Then I've run Mga3 LiveDVD and it failed to see any partitions on that drive. After that I've boot Mga2 from external HDD and both gparted and diskdrake successfully found all Windows partitions on internal HDD and allowed me to create three more partitions for linux installation (swap, root and home) on the disk but Mga3 installer failed to see them too. Next I've tested diskdrake from mga2 and mga3. diskdrake from mga2 successfully discovers and correctly shows all partitions while mga3 version always fails and shows an empty disk. Also I've tried to run diskdrake in mga3 from console and seen the following warning: "Warning: /dev/sda contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?" At the same time diskdrake in mga2 runs without any warnings. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create a single Windows 7 partition with Windows 7 (x64 version) installer on an empty HDD in manual mode leaving some unallocated free space for further linux installation. Allow Windows installer to create additional 100 Mb partition when prompted. Do not change types of these partitions. 2. After finishing Windows installations try to install Mga3 LiveDVD on the same drive. 3. Reproducible: Steps to Reproduce:
Created attachment 3885 [details] diskdrake in Mageia 2 correctly showing all disk partiotions diskdrake in Mageia 2 correctly showing all disk partiotions
Created attachment 3886 [details] diskdrake in Mageia 3 can not determine disk partiotions and shows an empty disk instead diskdrake in Mageia 3 can not determine disk partiotions and shows an empty disk instead
CC: (none) => olegbosis
(In reply to Oleg Bosis from comment #0) > > Also I've tried to run diskdrake in mga3 from console and seen the following > warning: > > "Warning: /dev/sda contains GPT signatures, indicating that it has a GPT > table. However, it does not have a valid fake msdos partition table, as it > should. Perhaps it was corrupted -- possibly by a program that doesn't > understand GPT partition tables. Or perhaps you deleted the GPT table, and > are now using an msdos partition table. Is this a GPT partition table?" > > At the same time diskdrake in mga2 runs without any warnings. > assigning to maintainer
CC: (none) => ennael1, marja11, qa-bugs, thierry.vignaud, tmbAssignee: bugsquad => pterjanSource RPM: (none) => drakxtoolsWhiteboard: (none) => 3RC
what does said fdisk -l ?
Version: 3 => Cauldron
# LC_ALL=C fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x7b534c14 Device Boot Start End Blocks Id System /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT /dev/sda2 206848 308029439 153911296 7 HPFS/NTFS/exFAT /dev/sda3 308029440 324806655 8388608 82 Linux swap / Solaris /dev/sda4 324806656 1465147391 570170368 5 Extended /dev/sda5 324808704 419180543 47185920 83 Linux /dev/sda6 419182592 1465147391 522982400 83 Linux
Note: this was output from fdisk in Mageia 2 installed on external USB HDD (/dev/sdb).
Some additional info from gdisk: ************************************************************************** # gdisk /dev/sda GPT fdisk (gdisk) version 0.8.1 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 1 Command (? for help): p Disk /dev/sda: 1465149168 sectors, 698.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): 72F89366-850E-4813-A137-B938BCE87E06 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1465149134 Partitions will be aligned on 2048-sector boundaries Total free space is 7853 sectors (3.8 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Microsoft basic data 2 206848 308029439 146.8 GiB 0700 Microsoft basic data 3 308029440 324806655 8.0 GiB 8200 Linux swap 5 324808704 419180543 45.0 GiB 8300 Linux filesystem 6 419182592 1465147391 498.8 GiB 8300 Linux filesystem Command (? for help): ************************************************************************* # gdisk /dev/sda GPT fdisk (gdisk) version 0.8.1 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 2 Using GPT and creating fresh protective MBR. Command (? for help): p Disk /dev/sda: 1465149168 sectors, 698.6 GiB Logical sector size: 512 bytes Disk identifier (GUID): 3D5948A7-1EBB-419F-ADE6-19D776E7182C Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1465149134 Partitions will be aligned on 2048-sector boundaries Total free space is 1465149101 sectors (698.6 GiB) Number Start (sector) End (sector) Size Code Name Command (? for help): ************************************************************************** BTW can I remove empty GPT keeping MBR untouched and working or I would loose both?
I have fixed my disk with gdisk -> r -> x -> z (remove GPT with keeping MBR), but harddrake still needs to be fixed to prevent data loss. This situation (both GPT & MBR on the same HDD) is not rare at all according to google... The solution could be the following: 1. GUI warning about the presence of both MBR & GPT with blocking access to the device in normal mode (do not allow the user to destroy the correct partition table by accident). 2. In expert (advanced) mode: ability to see the difference between MBR & GPT, ability to choose which one should be used for further disk operations.
Ups, "harddrake" means "diskdrake" :)
Version: Cauldron => 3
Ping ! This bug seems fixed ? There is no draxtools package on media Core_Updates_Testing to validate !
CC: (none) => geiger.david68210
(In reply to David GEIGER from comment #10) > Ping ! > > This bug seems fixed ? > Why have you decided it's fixed? > There is no draxtools package on media Core_Updates_Testing to validate ! Yes, there's no any new version of drakxtools to test. So my question is the same again: Why you have decided it's fixed? All I've done is got rid of an empty GPT on my HDD. This removed the erroneous conditions so everything else went normally and I had managed to install Mageia 3 on that HDD in parallel with Win 7. But AFAICS the problem in diskdrake not working properly with GPT+MBR disk configs still remains.
Oleg Bosis, I have not decided that the bug is fixed !! I just asked if it was fixed or not?
No, I think it was not fixed. But as far as I don't have such HDD anymore I will not be able to test if the diskdrake developers fix it.
(In reply to David GEIGER from comment #10) > Ping ! > > This bug seems fixed ? > > There is no draxtools package on media Core_Updates_Testing to validate ! The bug report has not been assigned to qa-bugs, so it isn't ready for testing. Only bugs shown by http://mageia.madb.org/tools/updates/application/0 that are don't have a gray background, are ready for qa testing.
CC: (none) => davidwhodgins
I'm seeing this in current cauldron, but only during install. If you choose "Custom" disk configuration, when diskdrake opens the /dev/sda disk appears empty, exactly as in the attachment here. In my case, I have an /dev/sdb as well. If you tab to that, it is populated normally, and if you tab back to /dev/sda then it is also populated normally. Running diskdrake in a running system shows /dev/sda normally upon entry.
CC: (none) => ftg
This may be a dup of bug#11988 . I just tried this on an install on a laptop with a single drive, and /dev/sda was populated/drawn normally. Bug#11988 claims that this behavior is hit-or-miss, so that may account for it. Or, it may have to do with having two or more drives.
(In reply to Frank Griffin from comment #16) > This may be a dup of bug#11988 . I just tried this on an install on a > laptop with a single drive, and /dev/sda was populated/drawn normally. > > Bug#11988 claims that this behavior is hit-or-miss, so that may account for > it. Or, it may have to do with having two or more drives. This bug has nothing common with Bug 11988. This one *is* about using GPT instead of MBR if both are present on the same disk and GPT is empty and *not* about visual glitches in GUI.
This bug is still valid in Mageia 4.
CC: (none) => ugal12v
CC: (none) => loginov_alex
Whiteboard: 3RC => 3RC MGA4TOO
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
Reopened with according Comment 18.
Status: RESOLVED => REOPENEDHardware: x86_64 => AllVersion: 3 => CauldronResolution: OLD => (none)Whiteboard: 3RC MGA4TOO => MGA4TOO
Could you try a net install of Cauldron in order to see if it behaves better? A lot of fixes went it regarding that. Just boot with "boot-nonfree.iso" from eg http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia//distrib/cauldron/x86_64/install/images/ The install using boot.iso is explained there: https://wiki.mageia.org/en/Boot.iso_install#Choose_the_installation_method
Keywords: (none) => NEEDINFO
Created attachment 6173 [details] report.bug for drakx 16.75
CC: (none) => vzawalin1
Can you try Mga 5 RC? We're now at drakx 16.95 and there's been several improvements that could apply there
Vlad has ISO access as part of QA team so should have first build of final
(In reply to Thierry Vignaud from comment #23) > Can you try Mga 5 RC? > We're now at drakx 16.95 and there's been several improvements that could > apply there I do recall seing sda blank, tabbing to sdd (say), then tabbing back to sda and finding it populated, but I havent seen this recently. Next time I am at the partitioning step, I will make a point of checking this again.
(In reply to Thierry Vignaud from comment #23) > Can you try Mga 5 RC? > We're now at drakx 16.95 and there's been several improvements that could > apply there Just tried with 'final' classical. Installer(In reply to Thierry Vignaud from comment #23) > Can you try Mga 5 RC? > We're now at drakx 16.95 and there's been several improvements that could > apply there Just tried with Final-v1 classical. Partitioning step shows all relevant disks correctly populated, regardless of tabbing sequence.
Closing then
Status: REOPENED => RESOLVEDResolution: (none) => FIXED