Bug 991692
| Summary: | Fedora become unbootable after swap partition reformat | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||
| Component: | dracut | Assignee: | dracut-maint | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 27 | CC: | d3matt, dracut-maint, harald, jonathan, martin.steigerwald, mszpak, p.erdelyi, tadej.j | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-11-30 17:39:57 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
Mikhail
2013-08-03 17:21:22 UTC
Created attachment 782345 [details]
screen with error message
Boot with the rescue grub entry. # dracut -f --regenerate-all https://fedoraproject.org/wiki/Features/DracutHostOnly#Release_Notes I will make this more failure proof. Dracut currently expects the swap partition to show up, so it can resume from suspend-to-disk. anything I can do to help get this fixed? I ran into this tonight, and it took me longer than I'd like to admit figure out... (In reply to Matthew Stoltenberg from comment #3) > anything I can do to help get this fixed? I ran into this tonight, and it > took me longer than I'd like to admit figure out... should be fixed in F20 and F21 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. (In reply to Harald Hoyer from comment #4) > (In reply to Matthew Stoltenberg from comment #3) > > anything I can do to help get this fixed? I ran into this tonight, and it > > took me longer than I'd like to admit figure out... > > should be fixed in F20 and F21 Don't understand what means by "fixed" ? I repeated experiment and broke system again. Why systemd can't find automatically "swap" partition and ignore all non critical errors. Of course system can continue working without swap and /home partitions but currently we have problems with boot if they is unavailable :( I have my system woken up from suspend to ram, but it does not found the swap partition and stopped at dracut#. All I see is /run/initramfs/rdsosreport.txt file was generated, I shuld copy it to usb device or /boot. I have no access to /boot or any other partition. The problem exists on my system since two days, I had access via liveuser (usb) and executed dracut as described above. It worked one time, the system started, worked in kde some minutes and then ~/.config/kscreenlocker/greetrc can not be saved and the same for drkokirc. The desktop is frozen, I had to reboot but no chance. The rescue image doesn't start anyway, has trouble with the missing swap Partition. I'm on FC 21 daily updates. Today I installed Fedora 22 beta using another partition and by the way I reformatted SWAP. My fully updated Fedora 21 refused to boot with the error message similar to mentioned by the reported. So it doesn't seem to be "fixed". This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. 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 21 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. This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase Related: Bug 1346231 - unbootable after removing swap partition In there for LVM I describe a way on how to use a system without swap. I do get the resume from hibernation case, but I think an initramfs shall *never* *ever* boot an outdated hibernation image, as it may lead to severe data loss (been there, recovered from that using xfs_repair a long time ago). I understand that there is some challenge to make sure of that. One way would be to store hibernation image id into /boot/something and then on a further reboot *without* resuming, remove that hibernation marker again. Then only resume from hibernation if the hibernation image id is *same* as the one in /boot/something. And also don´t resume if /boot/something has no hibernation image id. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. 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 24 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. Mikhail, if you still want to have this fixed, you´d need to update that. I am not allowed to do it. Thanks, Martin I re-tested, now format the swap partition does not make the system unbootable. The only thing I did not like was that the system was waiting for 1.5m nothing doing. Therefore, I ask here a question: It possible to mounting the swap partition in parallel, without stopping the system load? Let these 1.5 minutes pass after I log in GNOME and begin working with system. Created attachment 1304917 [details]
1.5m waiting for nothing
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. |