|
Bugzilla – Full Text Bug Listing |
| Summary: | upgrade to 42.3 from 42.2 with / in extended partition fails to boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | R Silverman <suselist2> |
| Component: | Installation | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | jreidinger, suselist2 |
| Version: | Leap 42.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | openSUSE 42.3 | ||
| URL: | https://trello.com/c/VD5EMCp6 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs | ||
Could you please provide y2logs? Please, take a look at https://en.opensuse.org/openSUSE:Report_a_YaST_bug Created attachment 744477 [details]
y2logs
Logs are from an extra laptop that hasn't been used much, if at all, since the upgrade except by me to fix the reported problem by manually changing the boot flag from wrong sda3 to correct sda6. I think what you need is in the y2log-1.gz subfile.
This laptop has luks partitions and passwords were provided to the installer. If the passwords are recorded anywhere in the installer logs then please advise so I may change them. On a quick look I see password length *is* recorded in there (that's not good) but I don't see anything else but please confirm that. Thanks.
No, we do not record passwords anywhere, neither in the y2logs nor in the macro we record during installation. We respect our users' privacy. OK, let me explain what happened here: Boot flag is set to sda3 and not sda6 because generic boot code cannot boot from logical partition, as it can point only to primary partitions ( so first 4 partitions ). But when this happen, chainloading to sda6 cannot work, so boot from extended have to chosen. In general configuration is not valid. It should be boot from extended or boot from MBR. boot from root when root is on logical partition can work only if bios support it, but we cannot guarantee it. Due to Josef comment, I will close this bug as invalid. Thank you for the explanation of what happened, Josef. But Gilson, you 'close as invalid' way too fast (27 minutes!). You can certainly declare the configuration as 'not valid'. You folks can even declare that you will no longer support BIOS drives at all. That is your prerogative. Technology advances. But you still have a bug here. The installer ALLOWS me to upgrade what you call an invalid configuration without complaining. It totally accepts the configuration. It then SILENTLY changes the boot location during the upgrade, resulting in an unbootable installation. Likewise, after upgrade completion yast2-bootloader gui lies and shows boot location as boot from "/" when in fact it will rewrite the bootloader to try to boot from the front of the extended partition, which will again result in an unbootable installation. You seriously don't consider either of those a bug? BTW, 'Boot from Extended Partition' was not an option presented when upgrading on this configuration, the only options were 'Boot from Root Partition', 'Boot from Master Boot Record', or 'Custom Boot Partition'. Yes, I remember there used to be a 'Boot from Extended Partition' option in previous releases but it isn't shown anymore (at least, in these upgrade cases). Ralph I This is automated batch bugzilla cleanup. The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please feel free to reopen this bug against that version (!you must update the "Version" component in the bug fields, do not just reopen please), or alternatively create a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |
On upgrade by DVD from Leap 42.2 to 42.3 on system with existing grub2 in / in an extended partition on a BIOS disk, on first reboot the system tries to boot from the front of the extended partiton itself rather than from the / partition and obviously fails. I used parted-magic to reset the boot flag to / and repaired this but subsequently days later when using yast-bootloader module to modify an option in the bootloader caused it to rewrite the bootloader to again point to the front of the extended partition, even though yast-bootloader itself shows it is still correctly set to boot from /. This has happened on multiple machines. steps for the install/upgrade situation: 1 - proceed with normal DVD upgrade until presented with the screen showing list of all actions that will occur if you proceed 2 - in my cases, under BOOTING choice, STATUS LOCATION was shown as /dev/sda (MBR) 3 - click on BOOTING to edit 4 - change BOOT FROM MASTER BOOT RECORD to BOOT FROM ROOT PARTITION 5 - check box for SET ACTIVE FLAG IN PARTITION TABLE FOR BOOT PARTITION 6 - check box for WRITE GENERIC CODE TO MBR 7 - return to the previous screen 8 - BOOTING now is correctly shown (in my cases) as STATUS LOCATION /dev/sda6 ("/") and DO NOT INSTALL BOOTCODE INTO MBR and INSTALL BOOTCODE INTO "/" PARTITION 9 - do the upgrade. system will try to boot from the front of the extended partition and will fail. steps for the yast2-bootloader situation: 1 - start yast2-bootloader 2 - change any option (in my cases, I added a bootloader password) 3 - exit and yast2 will save and rewrite the bootloader 4 - on next boot, system will again try to boot from the front of the extended partition and will again fail. Ralph