Bug 19267 - Mageia Installer panics when it sees a primary partition used by OpenBSD
Summary: Mageia Installer panics when it sees a primary partition used by OpenBSD
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-30 20:43 CEST by Elmar Stellnberger
Modified: 2020-03-20 17:06 CET (History)
4 users (show)

See Also:
Source RPM: drakx-installer-stage2, drakxtools
CVE:
Status comment:


Attachments
screenshot (461.00 KB, image/jpeg)
2016-08-30 21:42 CEST, Elmar Stellnberger
Details
report.bug (293.40 KB, text/plain)
2016-08-31 10:27 CEST, Elmar Stellnberger
Details

Description Elmar Stellnberger 2016-08-30 20:43:24 CEST
OpenBSD, FreeBSD and NetBSD use another primary to allocate sub-partitions in it which are then recognized by Linux and assigned partition numbers which start after the number of the first extended partition. On the system where I have tested the Mageia 6 installer the last logical partition was /dev/sda7 within the extended partition sda3 while the BSD partitions out of primary sda2 started with sda8 (afaik). 
  Now the Mageia installer gets irritated when it sees that Linux allocates more than 7 partitions. It claims that the partition table would be corrupt and wants to delete all data (yes) or at least 'fix' the issue (no) which would likely destroy my OpenBSD installation equally. It does not even offer a secure reboot option to exit the installer.
  My request would be to make th Mageia installer BSD-safe (I`d guess it would just need to ignore the partition count or any partitions beyond the last logical partition.). Some time ago I have been working successfully to let the Mageia installer recognize and boot OpenBSD; however this was when I installed OpenBSD after installing Mageia.
Comment 1 Elmar Stellnberger 2016-08-30 21:42:46 CEST
Created attachment 8382 [details]
screenshot
Rémi Verschelde 2016-08-31 09:31:00 CEST

Assignee: bugsquad => mageiatools

Rémi Verschelde 2016-08-31 09:31:26 CEST

Source RPM: (none) => drakx

Comment 2 Thierry Vignaud 2016-08-31 09:48:50 CEST
Please try again the installer up to that error, and then:
- plug a USB key
- go to tty2 (alt+ctrl+F2)
- run the "bug" command
- attach (not paste) the report.bug file you'll find on the USB key here

Source RPM: drakx => drakx-installer-stage2
Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 3 Elmar Stellnberger 2016-08-31 10:27:54 CEST
Created attachment 8384 [details]
report.bug

  Unfortunately the undertaking of plugging an USB stick did not lead to success, neither on a current Mageia 5 nor on Mageia 6 sta1 though I remember this to have worked before. Possibly newer Linux kernels have a problem with the USB 1.1 support of that computer (PIV 3Ghz, 2GB RAM). Luckily the existing OpenBSD installation did in this case come to the rescue ...
Comment 4 Thierry Vignaud 2016-08-31 11:28:17 CEST
You tested with a somewhat older cauldron but that doesn't matter here (drakx v17.46 vs 17.55).

Humm, we only support full disk disklabels (this was added for supporting sparc workstations in the old days).
We don't support yet disklabels nested in a MBR partition.

It should work on GPT partitions as we rely on libparted there.
I guess MBR embedded disklabels will be supported when we switched MBR to using libparted too
Comment 5 Elmar Stellnberger 2016-08-31 12:04:54 CEST
  I doubt that OpenBSD would install into a GPT drive; up to now that was not possible. What else do you use for MBR/msdos-disklabels?
Comment 6 Marja Van Waes 2016-08-31 13:51:45 CEST
(In reply to Thierry Vignaud from comment #4)
> You tested with a somewhat older cauldron but that doesn't matter here
> (drakx v17.46 vs 17.55).
> 
> Humm, we only support full disk disklabels (this was added for supporting
> sparc workstations in the old days).
> We don't support yet disklabels nested in a MBR partition.
> 
> It should work on GPT partitions as we rely on libparted there.
> I guess MBR embedded disklabels will be supported when we switched MBR to
> using libparted too

CC'ing pterjan, because he isn't a member of the mageiatools ml (yet).

Source RPM: drakx-installer-stage2 => drakx-installer-stage2, drakxtools
Keywords: NEEDINFO => (none)
CC: (none) => marja11, pterjan

Thierry Vignaud 2020-03-20 17:06:02 CET

CC: (none) => mageia


Note You need to log in before you can comment on or make changes to this bug.