http://bugzilla.novell.com/show_bug.cgi?id=513004
http://bugzilla.novell.com/show_bug.cgi?id=513004#c7
Jozef Uhliarik changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |WONTFIX
--- Comment #7 from Jozef Uhliarik 2010-02-09 13:37:26 UTC ---
sorry for delay but I also working on other projects.
The bad news is that YaST logs are not useful because there is long time
running system and YaST logs are overwritten by other yast actions. (log
rotation)
I read again your description of bug. IMHO we try to solve a lot of problems
and we still open new problems. It is not good idea because there is not any
result.
I try to return back to your description of problem and I see there 3 basic
problems:
1. change /boot partition
2. using device names mount by label
3. wrong reading of bootloader settings after your changes
1. change /boot partition
=========================
Usually it is good idea if there is not enough space but problem is with
installation of new kernel. It is still uses old configuration from
/etc/sysconfig/bootloader.
There are options like: XEN_KERNEL_APPEND, FAILSAFE_APPEND, DEFAULT_APPEND
which still includes old settings. These options are used for installation or
update kernel.
Next problem is /etc/grub.conf which includes settings for installation of GRUB
if you change /boot partition you have to also update this file because it
still point on your old /boot partition.
2. using device names mount by label
====================================
openSUSE 11.2 includes some fixes for working with persistent device names but
there is still some bugs see bug#533782 but the idea is use persistent device
names (mount-by) for each partition. User can define type of persistent device
name for each partition or disk in yast2-storage during installation.
yast2-bootloader check settings for each partition and use defined persistent
name from option "mount-by" if it is not defined there is also global mount-by
option. I read disk settings from yast2-storage. It means if you want to skip
using persistent device names or use preferred persistent device names you have
to change it in yast2-storage. I am not sure if it is good idea to change these
settings on installed system.
3. wrong reading of bootloader settings after your changes
==========================================================
I skip details. Simple yast2-bootloader read your NEW settings because it is
located on your new /boot partition old is not mounted. But GRUB stage1 located
in MBR still points to your old /boot partition and it is cause why you saw old
boot menu after reboot. As I wrote before you have to upadte also
/etc/grub.conf after your change with /boot partition.
Finally:
--------
We also had discussion about XFS and lilo. IMHO we had troubles with XFS and
GRUB configuration because XFS can use the first 512B of partition and it leads
to broken GRUB stage1 in some cases. There is recommended install GRUB stage1
to MBR.
LILO is not supported or better configuration of LILO is not supported any
more.
I decide to accept only problem with using persistent device names for
partition - problem number 2. I will try to solve it in bug#533782. Your other
problems are result of your changes with /boot partition. I know it is really
hard to know what everything should be updated if you change your /boot
partition.
I close bug like WONTFIX but your problem with persistent device names is not
lost. It will be fixed with bug#533782. It is similar bug.
--
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.
