Description of problem: In dual boot, the partitioning option "Use free space" is unable to carry out a correct partitioning. Version-Release number of selected component (if applicable): Mageia 5 RC x86_64 DVD classical on real EFI hardware How reproducible: A 160 GB disk with an OS already installed as follow: /sda1: ESP /sda2: ext4 / /sda3: swap /sda4: ext4 /home Boot on the USB stick, "Install mageia 5 from USB" Upgrade or install -> Install Partitioning: "Use free space" Message: "You need to reboot for the partition table modifications to take effect". Ctrl Alt F2 -> see file report1.bug Reboot After the licence, there is sometime this message: "I cannot read the partition table of device Sda, it is too corrupted ........ Do you agree to lose all the partitions? Yes or No" I did not have it this time Upgrade or install -> Install Sometime, only one choice "Use existing partitions" this time, there was also "Erase and use entire disk" and Custom disk partitioning" -> 1: Use existing partitions New screen: "Choose the mount points", Sda2 is by default mounted on /, Sda4 on /home and nothing for Sda5. Sda6, Sda7 and Sda8 aren't displayed. Impossible to go on, no way to assign the mounting points Ctrl Alt F2 -> see file report2.bug If I try to go on with the default values (overwriting the existing installation), an error message pops up: "An error occurred. You must have a ESP FAT 32 partition mounted in /boot/EFI" -> 2: Custom disk partitioning Here, I can see all the partitions Sda2 is by default mounted on /, Sda4 on /home and /mnt/windows on sda1 Sda5 299MB ext4 is wasted place, unusable. Sda7 3,9 GB unformatted is also wasted place, there is already a swap. I must enter the expert mode to format Sda6 and Sda7. The installation is then possible, but difficult, long and dirty (two useless partitions). Reproducible: Steps to Reproduce:
Created attachment 6034 [details] first report.bug
Created attachment 6035 [details] second report.bug
This bug looks like bug 15449
CC: (none) => ennael1, pterjan, thierry.vignaud, tmb
CC: (none) => eeeemail
Can you check a network install with latest stage2? eg: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/ has yesterday's stage2. Does my fix prevent this useless reboot when partitionning?
Keywords: (none) => NEEDINFO
I have been experiencing exactly the same issues and custom partitioning is the only approach that has worked for me in this situation.
CC: (none) => vzawalin1
(In reply to Thierry Vignaud from comment #4) > Can you check a network install with latest stage2? > eg: > http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/ > x86_64/install/stage2/ has yesterday's stage2. > > Does my fix prevent this useless reboot when partitionning? Yes but not today. Sorry. What fix are you talking about? is it included in the "yesterday's stage2"?
(In reply to Vladimir Zawalinski from comment #5) > I have been experiencing exactly the same issues and custom partitioning is > the only approach that has worked for me in this situation. I did the installation several times and as you said in the ML, the behaviour isn't always the same, available formatting options vary from a try to another one. Custom partitioning is indeed the only option that works, it works but it is not clean, complicated and there is useless partitions.
(In reply to André DESMOTTES from comment #6) > (In reply to Thierry Vignaud from comment #4) > > Can you check a network install with latest stage2? > > eg: > > http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/ > > x86_64/install/stage2/ has yesterday's stage2. > > > > Does my fix prevent this useless reboot when partitionning? > > Yes but not today. Sorry. > What fix are you talking about? is it included in the "yesterday's stage2"? Hi André, Thierry is talking about drakx-installer-stage2-16.67-3.mga5 :-) : tv <tv> 16.67-3.mga5: + Revision: 818290 - try to fix "need to reboot" after partition changes (mga#14758, mga#15449) If that version is on your mirror, then mdkinst.sqfs (that is stage2, which boot.iso will pull in from the mirror) should be from 16.67-3.mga5, too. To be sure, you can check its time stamp on your mirror. It should be in /path/to/your/mirror/mageia/distrib/cauldron/x86_64/install/stage2/ On my local mirror it looks like: -rwxrwxrwx 1 marja marja 56623104 Mar 10 18:29 mdkinst.sqfs* Cheers, marja
CC: (none) => marja11
(In reply to Thierry Vignaud from comment #4) > Can you check a network install with latest stage2? > eg: > http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/ > x86_64/install/stage2/ has yesterday's stage2. > > Does my fix prevent this useless reboot when partitionning? Boot.iso doesn't boot "error: invalid magic number. alloc magic is broken at Oxb062ee00: b0579b80 Aborted. Press any key to exit"
Your download is corrupted.
I redid the download, md5sum is right and still the same message I downloaded the file from here: http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/cauldron/x86_64/install/images/
I did a new try with rsync://isoqa@bcd.mageia.org/isos/docteam-5/Mageia-5-RC-x86_64-DVD/Mageia-5-RC-x86_64-DVD.iso.(a new build for docteam) I selected the option "Use existing partitions", no reboot for partitioning, but the system created four partitions. a new ESP partition, /, /home and swap. The former ESP partition is mounted on /mnt/windows and the new one on /EFI/boot. All the Operating systems start on the new ESP. So it is better but still not perfect.
(In reply to André DESMOTTES from comment #12) > I did a new try with > rsync://isoqa@bcd.mageia.org/isos/docteam-5/Mageia-5-RC-x86_64-DVD/Mageia-5- > RC-x86_64-DVD.iso.(a new build for docteam) Anne said she used the drakx-installer-stage2 srpm that I sent her to create it. That one was based on version 16.67, only this was changed: "Version 16.67_DocTeam - 6 March 2015 - remove Mga version from perl-install/install/pixmaps/left-background.png" So AFAIK it doesn't include Thierry's fix :-/ > I selected the option "Use existing partitions", no reboot for partitioning, > but the system created four partitions. a new ESP partition, /, /home and > swap. "Use existing partitions" shouldn't create new partitions, but only create mountpoints for existing partitions. Or did you mean you chose "Use Free Space"? > The former ESP partition is mounted on /mnt/windows and the new one on > /EFI/boot. > All the Operating systems start on the new ESP. > So it is better but still not perfect.
Created attachment 6060 [details] report.bug.xz of no reboot needed after partitioning Just tried an EFI-install with boot.iso, selected an external HD in doPartitionDisks and chose "Use free space" Partitions were created fine, no reboot was needed and install went on as expected Attaching report.bug.xz of the success :-)
(In reply to Marja van Waes from comment #13) > > "Use existing partitions" shouldn't create new partitions, but only create > mountpoints for existing partitions. > > Or did you mean you chose "Use Free Space"? > > Yes of course, you are right, it was "Use Free Space". Sorry. If the iso given to write doc isn't the last one, it is useless. I'll wait for the next build to have Thierry's fix.
(In reply to André DESMOTTES from comment #15) > (In reply to Marja van Waes from comment #13) > > > > Or did you mean you chose "Use Free Space"? > > > > > Yes of course, you are right, it was "Use Free Space". Sorry. No problem > If the iso given to write doc isn't the last one, it is useless. > I'll wait for the next build to have Thierry's fix. Well, maybe ennael didn't use my srpm, after all. The ddebug.log from an install with it should show the following on the second line: * second stage install running (DrakX v16.67_DocTeam) Anyway, I'll try again with a custom boot.iso install, deleting, resizing and creating partitions.
Created attachment 6062 [details] report.bug.xz from almost good custom partitioning Custom partitioning went pretty well, I've happily deleted, created and resized. The only issue was with the resized partition, that was intended to be /home, but: error: INTERNAL ERROR: unknown device sdb11 I finally decided to create a new partition for /home, and then install went on fine (without reboot being needed)
commit 281d55f77a148cb8fafd4e73912c31e06d81acf4 Author: Thierry Vignaud <thierry.vignaud@...> Date: Fri Mar 27 08:45:06 2015 -0400 fix failing to read partition table (mga#13592, mga#15272) this is making it more readable regarding: "I cannot read the partition table of device XXX, it is too corrupted" (mga#13592, mga#15272, mga#15472) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=281d55f77a148cb8fafd4e73912c31e06d81acf4 Bug links: Mageia https://bugs.mageia.org/15472 https://bugs.mageia.org/15272 https://bugs.mageia.org/13592
Closing. Though a secondary bug (see comment #17) hints we should probably call 'udevadm settle' after writing partition table in partition_table::write()
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED