|
Bugzilla – Full Text Bug Listing |
| Summary: | expert partitioner tool - won't let me put the disks the right way round without a (false) "GPT disk label" error message | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Jedi Beeftrix <jedibeeftrix> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, jedibeeftrix, jlopez |
| Version: | Leap 42.3 | Flags: | jlopez:
needinfo?
(jedibeeftrix) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jedi Beeftrix
2017-09-11 15:16:21 UTC
Could you please attach the YaST logs? In the following link you can find out how to do it: https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22_.28for_package_installation_also_.22libzypp_logging.22.29._What_does_that_mean.2C_and_how_do_I_do_that.3F This seems to be the message: https://github.com/yast/yast-storage/blob/master/src/include/partitioning/custom_part_helptexts.rb#L172 It is displayed here: https://github.com/yast/yast-storage/blob/master/src/include/partitioning/custom_part_check_generated.rb#L500 In the beginning of supporting EFI it was assumed that EFI requires GPT. This is in general not the case. Otherwise in the expert partitioner in the overview dialog for a specific disk behind the "Expert..." button there is an entry "Create New Partition Table". According to Arvin's explanation, you could avoid the message by creating a new GPT partition table for the disk. To do that, you have use the button "Expert ..." in the disk view and then "Create New Partition Table". Indeed the message could be improved, but Leap 42.3 will only receive critical updates. Moreover, next releases are coming with a totally new storage layer, so this kind of improvements probably will be fixed there. |