| Summary: | Suggested safety and usability improvements for partitioner in Mga5 B3 (Classical installer) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Vladimir Zawalinski <vzawalin1> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | doktor5000, eeeemail, ennael1, rverschelde, thierry.vignaud, wilcal.int |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Vladimir Zawalinski
2015-02-09 10:02:03 CET
The behaviour of auto-allocate described in (2) above, after further testing, was seen to depend on the skill mode chosen (normal/expert). When 'expert' mode is chosen, together with auto-allocate, a menu is tripped asking the user to state the use of the machine (simple,server or +/usr). After email discussion with Remi Verschelde, it was felt that this menu served no real purpose, since auto-allocate would not generally be used in building a server and was dangerous in this context while /usr could be added by any user as a separate partition. The key request in this bug report is to remove the supplementary (simple/server/usr) menu, and to allow auto-allocate to be available in 'normal' (ie not expert) mode only. The logic of auto-allocate should be checked to ensure that 'auto-allocate' will never operate on any disc other than the one chosen by the user.. The other points are smaller annoyances whose removal would lead to a polished user experience. After further testing, I think that the user level is not relevant. I selected custom partioning -> sde and pressed 'use entire disk'. Nothing much seemed to happen. I then looked at sdc, and found that it had been re-partitioned as per the auto-allocate formula, and the new partition table had been written to disk, causing major damage to other existing systems. I suspect this bug is not directly related to EFI changes, but has been lurking for a while. Hence, the following text summarises this bug report: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv In a multi disk hardware installation, the partitioner included with the MGA5B3.4 behaves unpredicatbly. Specifically, if the user selects a particular disk for partitioning, and invokes either the 'use entire disk' or 'auto-allocate', the partitioner can decide to use a disk other than the one selected by the user, without warning. The 'use entire disk' is particularly dangerous as it does the damage immediately and with no prior warning of any kind. The only safe way in multi-disk systems is to do everything manually, with the othe options locked out. I would be very uncomfortable releasing a new Mageia that lacks a resolution of this bug for general use. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Priority:
Normal =>
release_blocker Your comments are very useful and may help to improve a lot interface. But we are very near from final release. The tool is not perfect and may be improved. This will be a perfect report for Mageia 6 specifications :) Priority:
release_blocker =>
High As you say, the release date is too close to start changing a critical component where the problem affects only a small proportion of users. To prevent accidents, though, 'errata' for the release should make it very clear which partitioner options to avoid for those wanting to install Mageia 5 on machines that include multiple disks and pre-existing operating systems.
Thierry Vignaud
2015-02-18 16:58:16 CET
Summary:
Suggested safety and useability improvements for installer (partitioner) in Mageia 5 Beta 3 Release 2(Classical iso) =>
Suggested safety and usability improvements for installer (partitioner) in Mga5 Beta 3 Release 2(Classical iso) An advisory message for this issue has been placed in Wiki - Mageia5 - Errata. Please review and edit as necessary.
claire robinson
2015-03-02 22:01:55 CET
CC:
(none) =>
eeeemail
William Kenney
2015-03-02 22:02:37 CET
CC:
(none) =>
wilcal.int Vladimir, could you create separate bugs for the issues you encountered, or at least for the _huge_ issue with the partitioner trying to use the wrong disk when you choose "auto-allocate" or "use entire disk"? As Anne said, the current bug report will be a nice basis for the mga6 specifications (and you did name it "Suggested ... improvements", but there are a couple real bugs in there that would deserve specific attention. CC:
(none) =>
remi Item 3 in original description is not a bug. I will create separate bugs for items 4, 5, 6, 7 and advise bug numbers here and by email once done.
Florian Hubold
2015-03-08 20:22:32 CET
CC:
(none) =>
doktor5000 Have you create those bugs? Keywords:
(none) =>
NEEDINFO I had, they were discussed and mostly closed. Now, clicking on 'My Bugs' only returns this one? Are closed bugs archived off line, or am I missing something? I haven't kept a separate list. IIUC the "My bugs" link only searches for bugs with Status = one of UNCONFIRMED, NEW, ASSIGNED, REOPENED (In reply to James Kerr from comment #10) > IIUC the "My bugs" link only searches for bugs with Status = one of > UNCONFIRMED, NEW, ASSIGNED, REOPENED Thank you for letting me know. Closing this one then. Status:
NEW =>
RESOLVED |