During installation - of Mageia-5 RC - after first reboot, - the PARTITION-TABLE (MBR) was LOST. (CSM-Mode/Legacy-Mode of EFI-Bios ASRock J1900 ITX; internal SSD Samsung EVO 840) After reconstruction of the PARTITION-TABLE (testdisk was used) - REINSTALLATION the OLD Mageia-4 WITHOUT any problems. A SECOND TRY later - the installation of Mageia-5 RC has left to the same PROBLEM AGAIN. - The Partition-Table of the internal disk was LOST. Used Installation MEDIA: Mageia-5-RC-x86_64-DVD.iso on USB (dd used to copy) - produced the problem (..instead with the Mageia 5 RC gnome-live-version (1,6GB) - had NOT THIS problem before..)
What do you mean exactly by "the partition table was lost" ?
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
did you install mageia4 as efi system or legacy bios install ? if mga4 is legacy install and you try to install mga5 as efi it will wipe the partition table when we switch from dos to gpt partitioning
CC: (none) => tmb
(In reply to Thomas Backlund from comment #2) > did you install mageia4 as efi system or legacy bios install ? > > if mga4 is legacy install and you try to install mga5 as efi it will wipe > the partition table when we switch from dos to gpt partitioning when we switch from mbr to gpt that is
(In reply to Thierry Vignaud from comment #1) > What do you mean exactly by "the partition table was lost" ? ALL INSTALLATIONS DONE WITH BIOS-CSM / LEGACY-MODE ! mga4 is running for a year now. partition table is mbr type (part. separated for "/boot" - "/" - and "/home"). one partition is extended type. THE OTHER INSTALLER (GNOME-LIVE): mga5-gnome-live - is not booting every time to graphic-mode. but i COULD install mga5 RC this way. (then only MSEC security-profile was not changeable..) THE PROBLEM (FULL DVD-MEDIA - first time): installation of mga5-64bit-DVD RC did not work - for reboot. installer-disk-tool then said SOMETHING LIKE: "Could not read Part.-Table" - "Analyzing (?)" - "This is what was found:" then the inst.-part.-tool has shown an uncomplete partition table (i think the extended part. was not there - AND in the area of un-used space, there was shown an older partition-name (?)) REPAIRING: As "testdisk" is part of "gparted live cd" it was used to analize the disk. it found all missed partition-table-info - so i could write it again. ;-) THE PROBLEM - second time: so i started to install mga5 to another disk (external usb-drive). (i have to say the part-tool is a nice power-tool - but can lead to some confusing - as it is working now.) the tool said it could not read the table (now for every sda, sdb, sdc) - but seconds later every table was there. the tool is AUTOSELECTING partitions from different drives - as they match the usage. - it is a feature ! but in a strange situation like this - you want to know EXACTLY what IS on the disk, - what did YOU select - and WHEN will the disk be changed (a button like "refresh / read the disks" (like "gparted") would be nice)) ..but this way.. - i had to shut-off the machine.. - and to check if the main disk is not touched (BEFORE writing more to disk). (a well decided shut-off should not disrupt the part. table - if the tool works optimal/normal) reboot told then: "kernel-panic" - so "testdisk" was used again to repair partition table. a complete reinstall of the old mga4 followed. OLD mga4 is running perfectly again.
(In reply to Thomas Backlund from comment #2) > did you install mageia4 as efi system or legacy bios install ? > > if mga4 is legacy install and you try to install mga5 as efi it will wipe > the partition table when we switch from dos to gpt partitioning ALL INSTALLATIONS DONE WITH BIOS-CSM / LEGACY-MODE. ..ONLY MBR / DOS PARTITION TABLE WAS USED (no GPT, EFI). (typical ?: ..EVERY booting of installation-media gave same warnings about problems with "LEGACY configuration")
(In reply to Peter Grabner from comment #5) > > ALL INSTALLATIONS DONE WITH BIOS-CSM / LEGACY-MODE. > ..ONLY MBR / DOS PARTITION TABLE WAS USED (no GPT, EFI). Please try to avoid CAPS LOCK when writing in a bug report, even though you probably mean no harm, it's often associated with anger or shouting... not really suited for debugging issues.
(In reply to Rémi Verschelde from comment #6) > (In reply to Peter Grabner from comment #5) > > > > ALL INSTALLATIONS DONE WITH BIOS-CSM / LEGACY-MODE. > > ..ONLY MBR / DOS PARTITION TABLE WAS USED (no GPT, EFI). > > Please try to avoid CAPS LOCK when writing in a bug report, even though you > probably mean no harm, it's often associated with anger or shouting... not > really suited for debugging issues. thank you ! but it should be practical only. as you can see - i have written a lot. - i think without "BOLD" or replacement it would be a sad communication.
Keywords: NEEDINFO => (none)
If you can reproduce the bug, after you see the bug, please connect an USB key to your computer, switch to tty2 (alt + F2) and type bug. This should add a file named report.bug to the key, that you can then attach to this bug report.
Keywords: (none) => NEEDINFO
Peter, please respond to comment 8
CC: (none) => nic
No answer
Status: NEW => RESOLVEDResolution: (none) => OLD