[Bug 889733] New: partitioning in installation fails
https://bugzilla.novell.com/show_bug.cgi?id=889733 https://bugzilla.novell.com/show_bug.cgi?id=889733#c0 Summary: partitioning in installation fails Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers@suse.de ReportedBy: jslaby@suse.com QAContact: jsrain@suse.com CC: coolo@suse.com Found By: --- Blocker: --- See: https://openqa.opensuse.org/tests/15550/modules/partitioning/steps/2 There is a win8 disk, which is to be resized and opensuse installed. There are two issues: 1) the note about the failure is wrong (cannot resize because it is not clean). It cannot resize because the label has to be changed. See y2logs from the URL above. 2) Why is the change to GPT needed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c1
--- Comment #1 from Jiri Slaby
2) Why is the change to GPT needed?
I mean, this is an EFI booted machine with non-EFI win installation. But EFI does not require GPT, so? I think the best we can do is just resize the partition (and leave the table msdos). win8 was unbootable, and will be, but the user obviously wants it that way (switched from legacy bios boot to EFI in BIOS/EFI). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c2
--- Comment #2 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c3
--- Comment #3 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c4
Arvin Schnell
2) Why is the change to GPT needed?
AFAIK EFI needs GPT, see e.g. bug #709334 and bug #710402. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c5
--- Comment #5 from Jiri Slaby
(In reply to comment #0)
2) Why is the change to GPT needed?
AFAIK EFI needs GPT
This is not true at least for UEFI. The standard says that UEFI has to support both msdos (legacy MBR) and GPT. Explicitly, 12.2.2 of UEFI 2.1 std states: This specification requires the firmware to be able to parse the legacy master boot record(MBR), GUID Partition Table (GPT), and El Torito logical device volumes. And msdos is indeed preferred on devices like USB flash disks for example, as one would not be able use the flash disk on older machines otherwise. In other words, if our installation requires and insists on GPT for disks when booted in EFI, it is a bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c6
--- Comment #6 from Arvin Schnell
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c7
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c8
--- Comment #8 from Raymund Will
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c9
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c10
--- Comment #10 from Lukas Ocilka
IMHO, we should *not* try to support that! Ways might be provided for an "expert" to work around "our" recommendation, stating unmistakably that the trouble ahead is self-inflicted and to be solved solely by the originator.
I agree that we should limit the number of supported scenarios and the proposal should make sure the system will be working. Guessing from "it probably works now, so let's keep it" is worse than proposing something we are sure that works. Power user can change the proposal anyway. And yes, we will obviously get reports like: Why installer changes something that works for me? The answer is simple: We can hardly tell, that it really works. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c11
Arvin Schnell
https://bugzilla.novell.com/show_bug.cgi?id=889733
https://bugzilla.novell.com/show_bug.cgi?id=889733#c12
Arvin Schnell
participants (1)
-
bugzilla_noreply@novell.com