Bug 1015629
Summary: | fedora becomes unbootable after installing debian | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | mordred | ||||
Component: | dracut | Assignee: | dracut-maint | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 19 | CC: | dracut-maint, dwilkins, harald, jonathan | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-02-17 17:30:53 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
mordred
2013-10-04 16:14:14 UTC
I noticed this bug report, and have experienced the same problem myself. I did not save sosreport.txt however. In recent weeks, I have been setting up multiple boots on desktop computers: this one boots into Fedora 19, Windows 7, Debian 7.1 and FreeBSD 9.1. I found that Debian installs made Fedora unbootable (under the normal boot), and took note that I should install Fedora last. I think I have found part of the reason for the problem. Partitions are identified in /etc/fstab by their UUIDs. The Debian installation does not touch the ext3 partitions, but the Debian installer reformats the Linux swap partition and gives it a new UUID. Of course this makes the Fedora fstab file incorrect. As in the above report, I found that the normal Fedora boot crashed in the Dracut phase, whereas the rescue boot succeeded. Once I realized that the UUID of the swap partition had been changed by the Debian installation, I booted into Debian, mounted the Fedora root partition, and hand-edited /etc/fstab. I assumed that this would solve the problem. However correcting /etc/fstab did not solve the problem. The Fedora boot crashed on trying to access the swap partition under its old UUID in /dev/disk/by-uuid I used find to grep for the previous UUID on all files in /etc/, and concluded that the replaced UUID of the swap partition was not to be found in plain text in any file in /etc, apart from my backup copies of the installed /etc/fstab I concluded from this that the Fedora boot process must archive the UUIDs of the partitions to be mounted outside /etc, and probably uses the archived ids to do things like file system checks before mounting the root partition. But I am no expert on Linux, or on the Fedora boot process. === On doing a web search, I found that someone else had apparently recovered the boot by re-synchronizing files with a yum repository, and that gave me an idea. I used yum to erase the most recent kernel, then updated with yum to force the machine to reinstall that kernel, and I found that the machine then rebooted normally. === Apologies for not keeping error reports and log files and forwarding them on, but I am adding these comments in the hope that they might be helpful. boot with the rescue entry, then do: # dracut --regenerate-all --force i tried dracut --force --regenerate-all before i filed this bug, as i stated. this command still does not work. but i have found part of the problem: dracut leaves /etc/fstab in unworkable state. when i edited /etc/fstab to use the current uuids, the system booted. but there is still a problem: the user password has been trashed and i can not log in. (In reply to mordred from comment #3) > but i have found part of the problem: dracut leaves /etc/fstab in unworkable > state. > > when i edited /etc/fstab to use the current uuids, the system booted. Well, dracut does not modify /etc/fstab. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |