Bug 533782

Summary:	after changing filesystem label system doesn't boot
Product:	[openSUSE] openSUSE 11.2	Reporter:	Arvin Schnell <aschnell>
Component:	YaST2	Assignee:	Jozef Uhliarik <juhliarik>
Status:	VERIFIED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P3 - Medium
Version:	Milestone 5
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Arvin Schnell 2009-08-24 15:26:31 UTC

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.

Comment 1 Jozef Uhliarik 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.

Comment 2 Jozef Uhliarik 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