[Bug 533782] New: after changing filesystem label system doesn't boot
http://bugzilla.novell.com/show_bug.cgi?id=533782 Summary: after changing filesystem label system doesn't boot Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: aschnell@novell.com QAContact: jsrain@novell.com Found By: Development When using mount-by-label for the root filesystem (also in grub config) the system doesn't boot clean after changing the label in the expert partitioner since the grub config is not updated. Right now there is simply no code to handle this situation. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533782 zhu rensheng <rszhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |juhliarik@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533782 http://bugzilla.novell.com/show_bug.cgi?id=533782#c1 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #1 from Jozef Uhliarik <juhliarik@novell.com> 2010-02-04 16:03:32 UTC --- During installation yast2-bootloader uses kernel device names and device names are finally convert (during writting) to persistent device names. You have no change to see your changes. yast2-bootloader during installation checks Storage::GetTargetChangeTime() and if the time is changed it tries to change proposal of bootloader. Usually it leads to complete new proposal of bootloader settings. If there are some troubles with changes of bootloader settings there is some pop-message which inform user about manual checking of bootloader settings but it is not about using persistent device names. next changes of mount-by on installed system has not effect to bootloader settings. It is necessary to run yast2-bootloader after changes in disk configuration manually. IMHO it is OK. After running of yast2-bootloader all device names are converted to actual persistent device names instead of option resume. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=533782 http://bugzilla.novell.com/show_bug.cgi?id=533782#c2 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED --- Comment #2 from Jozef Uhliarik <juhliarik@novell.com> 2010-02-11 12:57:04 UTC --- I added fix for converting "resume" option to persistent device name. Now if user start yast2-bootloader all devices from menu.lst is converted to actual persistent device names during reading. But if user decide to change device name in y2-bootloader it is possible. Devices are not converted again to persistent device names during writing. It allows users to edit device names in y2-bootloadr.
From my point of view the bug is fixed.
The code is in trunk and it will in y2-bootloader 2.19.5 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com