Bug 22582

Summary:	The check of allowed filesystems for /boot and / need be updated
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	Low	CC:	marja11, pterjan
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	27117

Description Morgan Leijström 2018-02-13 16:27:10 CET

Description of problem:
Checks for what filesystem type is allowed for /boot (and /?) are not correct, and the message it pops up what are allowed are also wrong.


Examples:

( Trying to see if filesystem type of /boot would help UEFI problem, i tried some normally stupid choices: )

1) When closing the dialog defining partition it checks for allowed partitions types, i.e /boot can not be FAT32.   But it is possible to select ext4 there, then click on the partition, button [Type], and select anything else - it not checked then.  - I suggest the check be run when changing type too.


2) While creating /boot i selected type XFS. That pass the check, A but After partitioning step it then failed to mount it. same if i try Reiserfs.  Note that they are listed as allowed in the message that pops up during creating /boot if i select another illegal type.  I suggest that message be updated with what really works.


3) For /boot i selected type btrfs. After installing a lot of packages, then defining users, installer fail to write /boot/EFI

Comment 1 Marja Van Waes 2018-02-14 17:08:32 CET

This was with a traditional iso, right?

If so: 
Please attach /root/drakx/report.bug.xz from the install during which you did this?

Does diskdrake on an installed system such a wrong choice, too?

Assignee: bugsquad => mageiatools
CC: (none) => marja11, pterjan
Keywords: (none) => NEEDINFO
Source RPM: diskdrake? => drakx-installer-stage2

Comment 2 Morgan Leijström 2018-02-14 20:15:36 CET

That was with mga7 cauldron netinstall

I dont think a log would be of much help;

§ First it need be investigated and decided on what filesystems it *should* work to select for /boot and for /.

§ Then the detection what user choose in the dialogue when creating the partition should be updated to accept/warn - and the message it displays should be in coherence with what it accept  ;)  (that is not the case currently)

§ And that check+message should be done also when changing type or mount point of an already existing partition, if type is or is changed to / or /boot

This is just some mess i stumbled into... Maybe there are/should be checks for other type/mount point combos, maybe need updating, or ...

This may be something an apprentice could work on

This is low priority as defaults are OK few people wish to try setting the stupid things i tried.  But it would be elegant if it works.

Priority: Normal => Low
Keywords: NEEDINFO => (none)

Aurelien Oudelet 2020-08-14 19:15:27 CEST

Blocks: (none) => 27117