http://bugzilla.suse.com/show_bug.cgi?id=907457 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Flags| |needinfo?(snwint@suse.com), | |needinfo?(jreidinger@suse.c | |om) --- Comment #22 from Arvin Schnell <aschnell@suse.com> --- The default mount method is by-uuid, not by-id. AFAIS the code in YaST works as designed: It tries to find a udev link for /dev/sda satifying the by-uuid mount method. Since UUID refer to filesystems and not hard disks or partitions this fails: 2014-11-25 15:49:28 <1> 10.100.12.94(3432) [Ruby] bootloader/udev_mapping.rb:52 /dev/sda looked as kernel device name: /dev/sda 2014-11-25 15:49:28 <1> 10.100.12.94(3432) [Ruby] bootloader/udev_mapping.rb:70 mount by: uuid 2014-11-25 15:49:28 <2> 10.100.12.94(3432) [Ruby] bootloader/udev_mapping.rb:79 Cannot find udev link to satisfy mount by for /dev/sda Possible solutions might include: 1. Don't write device.map at all. Michael Chang proposes that in comment #17 if I read it correctly. Michael, can we drop writing device.map? 2. The corresponding to a UUID for a disk would be the MBR signature or GPT disk GUID. But there are no udev links generated for these so this solution requires bigger implementation efforts. We also don't have much experience with using MBR signature, e.g. who unique they are. 3. Change YaST to use some other fallback in the by-uuid mount case, e.g. by-id. But by-id is broken so this solution doesn't look so promising. So can the bootloader experts please comment. -- You are receiving this mail because: You are on the CC list for the bug.