|
Bugzilla – Full Text Bug Listing |
| Summary: | Unknown device | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Dr. Werner Fink <werner> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aschnell |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Popup from YaST2
xz-zipped /var/log/YaST2/y2log |
||
Created attachment 711116 [details]
xz-zipped /var/log/YaST2/y2log
2017-01-21 11:38:23 <1> tux(9948) [Ruby] routines/lib_iface.rb:250 Reading device mapping
2017-01-21 11:38:23 <1> tux(9948) [Ruby] routines/lib_iface.rb:262 Read device mapping: $["/dev/disk/by-id/ata-ST2000LM003_HN-M201RAD_S377J9BG900367":"hd1", "/dev/disk/by-id/nvme-2002538c7610008c9":"hd0"]
2017-01-21 11:38:23 <1> tux(9948) [Ruby] bootloader/udev_mapping.rb:63 /dev/disk/by-id/ata-ST2000LM003_HN-M201RAD_S377J9BG900367 looked as kernel device name: /dev/sda
2017-01-21 11:38:23 <1> tux(9948) [Ruby] bootloader/udev_mapping.rb:83 mount by: uuid
2017-01-21 11:38:23 <2> tux(9948) [Ruby] bootloader/udev_mapping.rb:92 Cannot find udev link to satisfy mount by for /dev/sda
2017-01-21 11:38:23 <1> tux(9948) [Ruby] bootloader/udev_mapping.rb:63 /dev/disk/by-id/nvme-2002538c7610008c9 looked as kernel device name: /dev/nvme0n1
2017-01-21 11:38:23 <1> tux(9948) [Ruby] bootloader/udev_mapping.rb:83 mount by: uuid
2017-01-21 11:38:23 <2> tux(9948) [Ruby] bootloader/udev_mapping.rb:92 Cannot find udev link to satisfy mount by for /dev/nvme0n1
The disk layout as reported by fdisk ... as one can see, indeed there is no /dev/sda2 ... why it should be as I'm using an extended parition tux:~ # fdisk -l Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x0009d768 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 3907028991 3907026944 1.8T f W95 Ext'd (LBA) /dev/sda5 4096 2147489791 2147485696 1T 83 Linux /dev/sda6 2147491840 2357200895 209709056 100G 83 Linux /dev/sda7 2357202944 2776627199 419424256 200G 83 Linux /dev/sda8 2776629248 3907028991 1130399744 539G 83 Linux Disk /dev/nvme0n1: 119.2 GiB, 128035676160 bytes, 250069680 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 7F4096E9-6314-4371-A320-9E2D425079E3 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 16779263 16777216 8G Linux swap /dev/nvme0n1p2 16779264 37750783 20971520 10G Linux extended boot /dev/nvme0n1p3 37750784 250069646 212318863 101.2G Linux root (x86-64) There is indeed no sda2 in the system but also no device with scsi-SATA_SAMSUNG_MZHPV12S1X3NYAG800155. This is the by-id link of the drive you removed. I assume it is still used in some bootloader configuration file. So YaST is right in giving and error but the message could be better (it is not an internal error). Additionally the nvme device has no by-id links (maybe duplicate of bug #928391. As I've now upgraded to Leap 42.2 I can only check if this might happen again on Leap 42.2 ;) Leap 42.2 have better error message and also more suggest to repropose bootloader configuration, so it behave nicely. *** This bug has been marked as a duplicate of bug 931291 *** (In reply to Josef Reidinger from comment #5) > Leap 42.2 have better error message and also more suggest to repropose > bootloader configuration, so it behave nicely. > > *** This bug has been marked as a duplicate of bug 931291 *** ah, it is for SP3, so Leap 42.3 contain this fix. I do not catch deadline for SP2. |
Created attachment 711115 [details] Popup from YaST2 I had some time ago changed my SSD which was former an SATA Samsung MZHP SM951 due to flaky hardware on higher temperature to a NVME Samsung MZVK SM961. ANd now Yast2 crashes: Run command: /sbin/yast2 system_settings & YaST got signal 11 at file /usr/share/YaST2/modules/Popup.rb:961 sender PID: 481046984 /sbin/yast2: line 440: 9948 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Is there any way to clear the old data base of YaST2 that is to rescan all disks?