Bugzilla – Full Text Bug Listing
|Summary:||After swap removed via partitioner cannot boot|
|Product:||[openSUSE] openSUSE Distribution||Reporter:||Daniel Noga <noga.dany>|
|Component:||Basesystem||Assignee:||YaST Team <yast-internal>|
|Status:||NEW ---||QA Contact:||E-mail List <qa-bugs>|
|Priority:||P5 - None||CC:||ancor, antonio.feijoo|
|Found By:||---||Services Priority:|
|Marketing QA Status:||---||IT Deployment:||---|
Description Daniel Noga 2022-02-18 20:31:42 UTC
How to reproduce: 1. Install openSUSE Leap 15.3 KDE with swap and encryption 2. Open YaST Partitioner 3. Remove swap partition 4. Restart computer Expected: Computer boots without swap Current: Computer does not boot because it wait infinitely long on resuming from hibernation from missing partition Workaround: 1. Boot via failsafe mode 2. Run YaST Bootloader 3. Remove missing partition from "Other kernel parameters" Looks like bug https://bugzilla.opensuse.org/show_bug.cgi?id=906716 , but that was fixed years ago, so I am not sure if it just reapears or it is different culprit with same symptoms I am not sure, if it is YaST bug or Basesystem bug...
Comment 1 Antonio Feijoo 2022-03-15 14:38:02 UTC
(In reply to Daniel Noga from comment #0) > Looks like bug https://bugzilla.opensuse.org/show_bug.cgi?id=906716 , but > that was fixed years ago, so I am not sure if it just reapears or it is > different culprit with same symptoms No, it has nothing to do with that bug. I followed your steps to reproduce this issue, and what's happening here is the initrd is not regenerated after removing the swap partition, so it still contains the resume module... and if there is a resume cmdline argument referencing the non-existing swap partition, the system boot fails. > I am not sure, if it is YaST bug or Basesystem bug... The solution is run "dracut -f --regenerate-all" after removing the swap partition with the YaST Partitioner.
Comment 2 Ancor Gonzalez Sosa 2022-03-17 12:32:52 UTC
So this is not exactly a bug in YaST, but it's true that we should add a warning to the Partitioner to alert when the changes would leave the "resume=" parameter outdated. We even have a Trello card in our for that in our list of planned enhancement (with a loose meaning for "planned", since it's considered low priority).