[Bug 949796] New: YaST2-Bootloader complains "Unknown udev device" then crashes.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 Bug ID: 949796 Summary: YaST2-Bootloader complains "Unknown udev device" then crashes. Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: bpesavento@infinito.it QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 651027 --> http://bugzilla.opensuse.org/attachment.cgi?id=651027&action=edit yast2-log and udev information Trying to modify the bootloader setup, YaST2-Bootloader complains: Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-id/wwn-0x50025388a064af10-part3 Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42:in `to_kernel_device' Then crashes on user acknowledge. The offending partition is mounted as / (root) and is where the bootloader code is stored. The disk is a plain MBR formatted SSD that worked for years, no RAID or LVM or the like. Looking at the attached details it's no wonder that udev_mapping.rb at line 42 complains. Reproducible: always Tested with Tumbleweed 20151002 X86_64 (but the problem is likely there from the last few snapshots) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 Bruno Pesavento <bpesavento@infinito.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |YaST2 Assignee|jsrain@suse.com |yast2-maintainers@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c2 Bruno Pesavento <bpesavento@infinito.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpesavento@infini | |to.it) | --- Comment #2 from Bruno Pesavento <bpesavento@infinito.it> --- Created attachment 651137 --> http://bugzilla.opensuse.org/attachment.cgi?id=651137&action=edit Yast2-log look for "2015-10-09 17:28:54" Sorry, didn't look through the whole log. Please search for "2015-10-09 17:28:54" to find the offfending lines. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c6 Bruno Pesavento <bpesavento@infinito.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpesavento@infini | |to.it) | --- Comment #6 from Bruno Pesavento <bpesavento@infinito.it> --- Created attachment 651255 --> http://bugzilla.opensuse.org/attachment.cgi?id=651255&action=edit Bootloader update log: look at lines 4863 - 4914 - 5018 Maybe I've spotted the origin of the problem. See the attached perl-BL-standalone-log. At line 4863: lrwxrwxrwx 1 root root 10 Jul 25 20:16 wwn-0x50025388a064af10-part3 -> ../../sda3 the offending partition is still identified by its wwn. At line 5018: lrwxrwxrwx 1 root root 10 Jul 31 00:16 scsi-SATA_Samsung_SSD_840_S1DBNSBF844694B-part3 -> ../../sda3 or the following, there are no more wwn- identifiers. In-between is line 4914: bootloader_entry was called as: add desktop 4.1.3-1-desktop vmlinuz-4.1.3-1-desktop initrd-4.1.3-1-desktop a bootloader update, likely the result of a routine "zypper dup" involving a new kernel. The next wwn- is at line 6433: a new DVD drive, nothing to do with the problem at hand. If this is only my own corner case, close the bug report and I'll live with it till the next clean install. If this is of more general interest, I'm ready to help chasing it down. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c7 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |systemd-maintainers@suse.de --- Comment #7 from Josef Reidinger <jreidinger@suse.com> --- OK, so udev persistent link dispappeared. Systemd maintainers I think that wwn devices sounds familiar for me, so known issue or dup? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c13 Bruno Pesavento <bpesavento@infinito.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpesavento@infini | |to.it) | --- Comment #13 from Bruno Pesavento <bpesavento@infinito.it> --- Created attachment 651345 --> http://bugzilla.opensuse.org/attachment.cgi?id=651345&action=edit udevadm info -e for the ATA subsystem SCSI_IDENT_LUN_NAA_REG=50025388a064af10 seems correct (line 461) but the DEVLINKS=/dev/disk/by-id/wwn-* is missing from line 420. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c14 --- Comment #14 from Bruno Pesavento <bpesavento@infinito.it> --- According to logs, the problem first appeared on July 31st, seemingly after a "zypper dup" that should have involved Tumbleweed snapshots # 20150725, 20150727 and 20150728. The only relevant entry I see in the changelogs of those snapshots is in Changes.20150725.txt: ==== yast2-storage ==== Version update (3.1.63 -> 3.1.64) - Added NoCoW subvolume for /var/lib/libvirt/images (Fate#319299) - 3.1.64 Hope this helps. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c15 --- Comment #15 from Bruno Pesavento <bpesavento@infinito.it> --- (In reply to Thomas Blume from comment #12)
(In reply to Dr. Werner Fink from comment #11)
(In reply to Josef Reidinger from comment #9)
Sorry, but my crystal ball is currently beamless :) Please be more specific
AFAICS from a search the bug #909561 and do passing mentioned wwn only bug #913515 seems to have the simliar problem and no feedback
I'd blame these rules from /usr/lib/udev/rules.d/55-scsi-sg3_id.rules:
# ID_WWN compat mapping ENV{SCSI_IDENT_LUN_NAA_REGEXT}=="?*", ENV{ID_WWN}!="?*", ENV{ID_WWN}="0x$env{SCSI_IDENT_LUN_NAA_REGEXT}" ENV{SCSI_IDENT_LUN_NAA_REG}=="?*", ENV{ID_WWN}!="?*", ENV{ID_WWN}="0x$env{SCSI_IDENT_LUN_NAA_REG}" ENV{SCSI_IDENT_LUN_NAA_EXT}=="?*", ENV{ID_WWN}!="?*", ENV{ID_WWN}="0x$env{SCSI_IDENT_LUN_NAA_EXT}" ENV{SCSI_IDENT_LUN_NAA_LOCAL}=="?*", ENV{ID_WWN}!="?*", ENV{ID_WWN}="0x$env{SCSI_IDENT_LUN_NAA_LOCAL}" ENV{SCSI_IDENT_LUN_NAA_REGEXT}=="?*", ENV{ID_WWN_WITH_EXTENSION}!="?*", ENV{ID_WWN_WITH_EXTENSION}="0x$env{SCSI_IDENT_LUN_NAA_REGEXT}" ENV{SCSI_IDENT_LUN_NAA_EXT}=="?*", ENV{ID_WWN_WITH_EXTENSION}!="?*", ENV{ID_WWN_WITH_EXTENSION}="0x$env{SCSI_IDENT_LUN_NAA_EXT}"
A test shows that the above SCSI_IDENT_LUN_NAA* information are filled via:
/usr/bin/sg_inq --export --page=di /dev/sdX
(X is the letter of the disc).
Later ID_WWN is used in 60-persistent-storage.rules to create the symlinks.
Can you provide the output of:
/usr/bin/sg_inq --export --page=di /dev/sda
and:
udevadm info -e
?
I double checked and sg3_utils 1.41-1.1 was installed on 20150725 at 20:56:24. The last correct wwn-* entries in the Bootloader update log are marked "Jul 25 20:16". Maybe those entries were the last ones made using the old version? And when the new version was first called the problem appeared? If so, the bug might hide in the updated 55-scsi-sg3_id.rules or 58-scsi-sg3_symlink.rules -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c31 --- Comment #31 from Bruno Pesavento <bpesavento@infinito.it> --- Just FYI, I've checked Leap Beta1 on my test box (presumably with sg3_utils coming from SLED): NO wwn-* whatsoever and Yast2-bootloader works as expected. So this is limited to Tumbleweed currently? That's the reason why nobody reported since July? -- You are receiving this mail because: You are on the CC list for the bug.
(In reply to Hannes Reinecke from comment #30)
But still, you might want to fixup yast2-bootloader, too.
yast2 crashing is always horrible, for whatever reason. Blaming that on the underlying programs is not a good design principle.
Josef, have you fixed up yast2?
What can be changed is to modify storage to not use wwn as udev device. But how do you expect I can fix yast2-bootloader? grub2 have specified that it is booting from /dev/disk/by-id/wwn* so yast2-bootloader report problem, as it do not know what it is. ... This is not entirely true, at least in my setup. My current GRUB2 setup references UUIDs throughout, local disks only, no attempt at even looking for WWNs. I didn't even "know" about WWNs until this bug surfaced. From what I see here, Yast warns and exits just looking at /dev/disk/by-id and doesn't even get to GRUB files. If I manually change the GRUB config and rebuild GRUB, everything works. The system has been "zypper dup"-ed several times since the bug appeared, GRUB
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c38 --- Comment #38 from Bruno Pesavento <bpesavento@infinito.it> --- (In reply to Josef Reidinger from comment #33) menu updated, newly installed kernels booted without problems. Maybe just deferring the WWN check until an actual attempt at using network disks, where hopefully needed WWNs are in place, could be a safer choice. Just an user's standpoint... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c45 --- Comment #45 from Bruno Pesavento <bpesavento@infinito.it> --- (In reply to Simon Lees from comment #43)
I can confirm that its happening on my older laptop running leap recently upgraded from 13.2. A screenshot of my disk setup is at the following link (mostly because i took it for other reasons earlier) https://www.enlightenment.org/ss/display.php?image=e-564323711815c7.40034673. jpg
FYI this problem is NOT showing anymore after a clean Leap 42.1 install after a complete disk reformatting (GPT) on the same HW where I originally reported this bug. At the time of first reporting this laptop had been first installed with 13.2 Beta (Legacy, MBR), updated to 13.2 release, upgraded to Tumbleweed and "zypper dup"-ed several times since. Maybe the bug is rooted in incompatibilities or leftovers from previous installs. I also wonder if GPT or MBR might matter. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c46 --- Comment #46 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Bruno Pesavento from comment #45)
(In reply to Simon Lees from comment #43)
I can confirm that its happening on my older laptop running leap recently upgraded from 13.2. A screenshot of my disk setup is at the following link (mostly because i took it for other reasons earlier) https://www.enlightenment.org/ss/display.php?image=e-564323711815c7.40034673. jpg
FYI this problem is NOT showing anymore after a clean Leap 42.1 install after a complete disk reformatting (GPT) on the same HW where I originally reported this bug. At the time of first reporting this laptop had been first installed with 13.2 Beta (Legacy, MBR), updated to 13.2 release, upgraded to Tumbleweed and "zypper dup"-ed several times since. Maybe the bug is rooted in incompatibilities or leftovers from previous installs. I also wonder if GPT or MBR might matter.
It is expected as problem is that udev link in format wwn disappeared, so new installation is not affected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c47 --- Comment #47 from Simon Lees <simon@simotek.net> --- It probably doesn't make much difference that the last time this laptop had a clean install was 12.3, i've zypper dup'd through everything since then -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c48 CHAUFOURNIER Jérôme <chocho63.pub@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chocho63.pub@free.fr --- Comment #48 from CHAUFOURNIER Jérôme <chocho63.pub@free.fr> --- I've got the same bug since OpenSUSE 13.1. On each upgrade, the installer complains about udev mounted by kernel device. On OpenSUSE Leap too. The difference is that Yast cannot load the bootloader configuration under OpenSUSE LEAP 42.1 : 2015-12-05 13:54:14 <1> Spirit(17430) [Ruby] routines/lib_iface.rb:250 Reading device mapping 2015-12-05 13:54:15 <1> Spirit(17430) [Ruby] routines/lib_iface.rb:262 Read device mapping: $["/dev/disk/by-id/ata-Hitachi_HDS721050CLA362_JPB540HA0K0H8B":"hd0", "/dev/disk/by-id/ata-ST3160811AS_6PT14L2J":"hd1"] 2015-12-05 13:54:15 <1> Spirit(17430) [Ruby] bootloader/udev_mapping.rb:63 /dev/disk/by-id/ata-Hitachi_HDS721050CLA362_JPB540HA0K0H8B looked as kernel device name: /dev/sda 2015-12-05 13:54:15 <1> Spirit(17430) [Ruby] bootloader/udev_mapping.rb:83 mount by: id 2015-12-05 13:54:15 <1> Spirit(17430) [Ruby] bootloader/udev_mapping.rb:63 /dev/disk/by-id/ata-ST3160811AS_6PT14L2J looked as kernel device name: /dev/sdb 2015-12-05 13:54:15 <1> Spirit(17430) [Ruby] bootloader/udev_mapping.rb:83 mount by: id 2015-12-05 13:54:15 <3> Spirit(17430) [Ruby] yast/wfm.rb:202 Client call failed with 'Unknown udev device /dev/disk/by-id/wwn-0x5000cca371c7bc28-part4' and backtrace ["/usr/share/YaST2/lib/bootloader/udev_mapping.rb:42:in `to_kernel_device'", "/usr/share/YaST2/modules/BootCommon.rb:201:in `block in Read'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:518:in `call'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:518:in `block in mapmap'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:517:in `each'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:517:in `mapmap'", "/usr/share/YaST2/modules/BootCommon.rb:199:in `Read'", "/usr/share/YaST2/modules/BootGRUB2.rb:58:in `Read'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/share/YaST2/include/bootloader/routines/switcher.rb:70:in `blRead'", "/usr/share/YaST2/modules/Bootloader.rb:195:in `Read'", "/usr/share/YaST2/include/bootloader/routines/dialogs.rb:52:in `ReadDialog'", "/usr/share/YaST2/include/bootloader/routines/wizards.rb:94:in `block in BootloaderSequence'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:542:in `call'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/builtins.rb:542:in `eval'", "/usr/share/YaST2/modules/Sequencer.rb:263:in `WS_run'", "/usr/share/YaST2/modules/Sequencer.rb:335:in `block in Run'", "/usr/share/YaST2/modules/Sequencer.rb:327:in `loop'", "/usr/share/YaST2/modules/Sequencer.rb:327:in `Run'", "/usr/share/YaST2/include/bootloader/routines/wizards.rb:115:in `BootloaderSequence'", "/usr/share/YaST2/clients/bootloader.rb:117:in `GuiHandler'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/fun_ref.rb:33:in `call'", "/usr/share/YaST2/modules/CommandLine.rb:1541:in `Run'", "/usr/share/YaST2/clients/bootloader.rb:105:in `main'", "/usr/share/YaST2/clients/bootloader.rb:190:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:189:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:189:in `run_client'"] 2015-12-05 13:54:15 <3> Spirit(17430) [Ruby] yast/wfm.rb:207 Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-id/wwn-0x5000cca371c7bc28-part4 Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42:in `to_kernel_device' 2015-12-05 13:54:15 <1> Spirit(17430) [ui] YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for YPushButton "OK" at 0x7fc3503a0540 from function key F10 No WWN références in my grub configuration : Spirit:/var/log/YaST2 # cd /boot/grub2 Spirit:/boot/grub2 # grep wwn * Spirit:/boot/grub2 # grep wwn */* Spirit:/boot/grub2 # grep wwn */*/* Spirit:/boot/grub2 # grep by-id * grep: backgrounds: Is a directory device.map:(hd1) /dev/disk/by-id/scsi-SATA_ST3160811AS_6PT14L2J device.map:(hd0) /dev/disk/by-id/ata-Hitachi_HDS721050CLA362_JPB540HA0K0H8B Spirit:/boot/grub2 # grep "/dev/sd" * device.map.old:(hd0) /dev/sda device.map.old:(hd1) /dev/sdb grub.cfg:menuentry 'Microsoft Windows XP Professionnel (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-3C441846441804F4' { grub.cfg.20151111:menuentry 'Microsoft Windows XP Professionnel (sur /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-3C441846441804F4' { -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c51 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hdf3@comcast.net --- Comment #51 from Josef Reidinger <jreidinger@suse.com> --- *** Bug 963247 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c56 Norbert X <norko.solko@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |norko.solko@gmail.com --- Comment #56 from Norbert X <norko.solko@gmail.com> --- Got to this issue after changing rootfs device connection. System was installed on QEMU-KVM, then booted on physical hardware. So if I start "Boot Loader" YaST2 module I get error window with text: "Error Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part1 Caller: /usr/share/YaST2/lib/bootloader/device_mapping.rb:42 in `to_kernel_device' " I need to update bootloader manually with "grub2-mkconfig -o /boot/grub2/grub.cfg". This problem is openSUSE-specific. Ubuntu, for example, does not have this problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c57 patrick adams <padamsn@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |padamsn@gmail.com --- Comment #57 from patrick adams <padamsn@gmail.com> --- I can confirm this exist in 42.1 whenever I clone a hard drive with clonezilla. Related BUG # 993643 Cloned drives not booting, I had this bug happen when trying to fix that issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c58 Philippe Condé <conde.philippe@skynet.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |conde.philippe@skynet.be --- Comment #58 from Philippe Condé <conde.philippe@skynet.be> --- Hello I have also a similar problem but it refers to a non existing disk "Internal error: Please report a bug report with logs. Details:Unknown udev device /dev/disk/by-label/msdos Caller: /usr/share/YaSTé/lib/bootloader/udev_mapping.rb:33.in 'to_kernel_device'" I never had a msdos partition : maybe it can refers to a USB stick? the fstab content is /dev/disk/by-id/scsi-3600508b1001c99233458581ffb65cc88-part2 / ext4 acl,user_xattr 1 1 LABEL=usr /usr ext4 acl,user_xattr 1 2 LABEL=home /home ext4 acl,user_xattr 1 2 LABEL=srv /srv ext4 acl,user_xattr 1 2 LABEL=var /var ext4 acl,user_xattr 1 2 LABEL=local /local ext4 acl,user_xattr 1 2 LABEL=opt /opt ext4 acl,user_xattr 1 2 /dev/disk/by-id/scsi-3600508b1001c99233458581ffb65cc88-part1 swap swap defaults 0 0 I'll attach the full YaST.log Regard Philippe -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c59 --- Comment #59 from Philippe Condé <conde.philippe@skynet.be> --- Created attachment 691733 --> http://bugzilla.opensuse.org/attachment.cgi?id=691733&action=edit YaST log -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 Devin Henderson <devin@six19.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |devin@six19.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=949796 http://bugzilla.opensuse.org/show_bug.cgi?id=949796#c61 David Kane <dave.kane@geokinetics.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dave.kane@geokinetics.com Flags|needinfo?(ke@suse.com) |needinfo? --- Comment #61 from David Kane <dave.kane@geokinetics.com> --- I built a system from openSUSE 13.2 and performed online updates (3.16.7-53-desktop) over the past couple years. I used ACRONIS to image that system and installed it on 8 other systems which all have the smae problem. I suspect my problem is related to the uuid from the original system that I imaged. When I start Yast2 as root and select either Kernel Settings or Bootloader I get the below error. If someone knows a simple file I can edit to resolve the problem it is much appreciated. Error Internal error. Please report a bug report with logs. Details: Unknown udev device /dev/disk/by-id/scsi-1ATA_MTFDDAK256MAY-1AH1ZASHA_14500E0C147D-part2 Caller: /usr/share/Yast2/lib/bootloader/device_mapping.rb:42:in `to_kernel_device’ /dev/disk/by-id: lrwxrwxrwx 1 root root 9 Jan 20 13:10 ata-MTFDDAK256MAY-1AH1ZABHA_14280CF191FF -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 ata-MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 ata-MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 ata-MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:03 ata-hp_DVD_A_DH16AESH_248427914038 -> ../../sr0 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-0ATA_MTFDDAK256MAY-1A_14280CF191FF -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-0ATA_MTFDDAK256MAY-1A_14280CF191FF-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-0ATA_MTFDDAK256MAY-1A_14280CF191FF-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-0ATA_MTFDDAK256MAY-1A_14280CF191FF-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-1ATA_MTFDDAK256MAY-1AH1ZABHA_14280CF191FF -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-1ATA_MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-1ATA_MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-1ATA_MTFDDAK256MAY-1AH1ZABHA_14280CF191FF-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-3500a07510cf191ff -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-3500a07510cf191ff-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-3500a07510cf191ff-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-3500a07510cf191ff-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-3600508e000000000c1f3e9201d0f5609 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-3600508e000000000c1f3e9201d0f5609-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-3600d02310002c4d779a774fc49535b55 -> ../../sdc lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-3600d02310002c4d779a774fc49535b55-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1A_14280CF191FF -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1A_14280CF191FF-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1A_14280CF191FF-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1A_14280CF191FF-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1_14280CF191FF -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1_14280CF191FF-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1_14280CF191FF-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SATA_MTFDDAK256MAY-1_14280CF191FF-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-SIFT_DS_S12S-G2240-4_02C4D779A774FC49535B55 -> ../../sdc lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SIFT_DS_S12S-G2240-4_02C4D779A774FC49535B55-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jan 20 13:10 scsi-SLSI_Logical_Volume_552203201156634909 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 20 13:10 scsi-SLSI_Logical_Volume_552203201156634909-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 20 13:10 wwn-0x500a07510cf191ff -> ../../sda lrwxrwxrwx 1 root root 10 Jan 20 13:10 wwn-0x500a07510cf191ff-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jan 20 13:10 wwn-0x500a07510cf191ff-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Jan 20 13:10 wwn-0x500a07510cf191ff-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Jan 20 13:10 wwn-0x600508e000000000c1f3e9201d0f5609 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 20 13:10 wwn-0x600508e000000000c1f3e9201d0f5609-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 20 13:10 wwn-0x600d02310002c4d779a774fc49535b55 -> ../../sdc lrwxrwxrwx 1 root root 10 Jan 20 13:10 wwn-0x600d02310002c4d779a774fc49535b55-part1 -> ../../sdc1 /etc/fstab: LABEL=swap swap swap defaults 0 0 LABEL=system / btrfs defaults 0 0 LABEL=home /home xfs defaults 1 2 LABEL=system /boot/grub2/i386-pc btrfs subvol=boot/grub2/i386-pc 0 0 LABEL=system /boot/grub2/x86_64-efi btrfs subvol=boot/grub2/x86_64-efi 0 0 LABEL=system /opt btrfs subvol=opt 0 0 LABEL=system /srv btrfs subvol=srv 0 0 LABEL=system /tmp btrfs subvol=tmp 0 0 LABEL=system /usr/local btrfs subvol=usr/local 0 0 LABEL=system /var/crash btrfs subvol=var/crash 0 0 LABEL=system /var/lib/mailman btrfs subvol=var/lib/mailman 0 0 LABEL=system /var/lib/named btrfs subvol=var/lib/named 0 0 LABEL=system /var/lib/pgsql btrfs subvol=var/lib/pgsql 0 0 LABEL=system /var/log btrfs subvol=var/log 0 0 LABEL=system /var/opt btrfs subvol=var/opt 0 0 LABEL=system /var/spool btrfs subvol=var/spool 0 0 LABEL=system /var/tmp btrfs subvol=var/tmp 0 0 LABEL=system /.snapshots btrfs subvol=.snapshots 0 0 LABEL=eraid /eraid xfs defaults,nofail 0 0 LABEL=iraid /iraid xfs defaults,nofail 0 0 #hp2:/RAID/shared/ /eve2 nfs auto,nofail 0 0 #hp1:/eraid /eve1 nfs auto,nofail 0 0 If additional information is needed I will be happy to accommodate the request. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com