So I tried reverting 3 of the scripts modified by the update. This is the snapper diff of the changes I made:
— /.snapshots/33/snapshot/usr/lib/dracut/modules.d/95udev-rules/module-setup.sh 2017-08-09 19:06:30.307530679 -0600
+++ /.snapshots/34/snapshot/usr/lib/dracut/modules.d/95udev-rules/module-setup.sh 2017-08-09 19:08:43.868745682 -0600
@@ -56,10 +56,6 @@
# eudev rules
inst_rules 80-drivers-modprobe.rules
-
bsc#1040153
- inst_rules 61-persistent-storage-compat.rules
- inst_multiple -o ${udevdir}/compat-symlink-generation
- if dracut_module_included “systemd”; then
inst_multiple -o ${systemdutildir}/network/.link
$hostonly ]] && inst_multiple -H -o /etc/systemd/network/.link
— /.snapshots/33/snapshot/usr/lib/udev/rules.d/60-persistent-storage.rules 2017-07-19 10:33:31.000000000 -0600
+++ /.snapshots/34/snapshot/usr/lib/udev/rules.d/60-persistent-storage.rules 2017-08-09 19:20:56.855112253 -0600
@@ -44,8 +44,17 @@
SCSI devices
KERNEL==“sd*!0-9]|sr*”, ENV{ID_SERIAL}!=“?", IMPORT{program}=“scsi_id --export --whitelisted -d $devnode”, ENV{ID_BUS}=“scsi”
KERNEL=="cciss”, ENV{DEVTYPE}==“disk”, ENV{ID_SERIAL}!=“?", IMPORT{program}=“scsi_id --export --whitelisted -d $devnode”, ENV{ID_BUS}=“cciss”
-KERNEL=="sd|sr*|cciss*”, ENV{DEVTYPE}==“disk”, ENV{ID_SERIAL}==“?", SYMLINK+=“disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}”
-KERNEL=="sd|cciss*”, ENV{DEVTYPE}==“partition”, ENV{ID_SERIAL}==“?", SYMLINK+=“disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n”
+KERNEL=="nvme”, ENV{DEVTYPE}==“disk”, ENV{ID_SERIAL}!=“?", IMPORT{program}=“scsi_id --export --whitelisted -d $tempnode”, ENV{ID_BUS}=“nvme”
+KERNEL=="sd|sr*|cciss*|nvme*”, ENV{DEVTYPE}==“disk”, ENV{ID_SERIAL}==“?", SYMLINK+=“disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}”
+KERNEL=="sd|cciss*|nvme*”, ENV{DEVTYPE}==“partition”, ENV{ID_SERIAL}==“?", SYMLINK+=“disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n”
+
+# scsi compat links for ATA devices
+KERNEL=="sd!0-9]”, ENV{ID_BUS}==“ata”, PROGRAM=“scsi_id --whitelisted --replace-whitespace -p0x80 -d $devnode”, RESULT==“?“, ENV{ID_SCSI_COMPAT}=”$result", SYMLINK+=“disk/by-id/scsi-$env{ID_SCSI_COMPAT}”
+KERNEL=="sd[0-9]”, ENV{ID_SCSI_COMPAT}==“?", SYMLINK+=“disk/by-id/scsi-$env{ID_SCSI_COMPAT}-part%n”
+
+# scsi compat links for ATA devices (for compatibility with udev < 184)
+KERNEL=="sd!0-9]”, ENV{ID_BUS}==“ata”, PROGRAM=“scsi_id --truncated-serial --whitelisted --replace-whitespace -p0x80 -d$tempnode”, RESULT==“?“, ENV{ID_SCSI_COMPAT_TRUNCATED}=”$result", SYMLINK+=“disk/by-id/scsi-$env{ID_SCSI_COMPAT_TRUNCATED}”
+KERNEL=="sd[0-9]”, ENV{ID_SCSI_COMPAT_TRUNCATED}==“?*”, SYMLINK+=“disk/by-id/scsi-$env{ID_SCSI_COMPAT_TRUNCATED}-part%n”
FireWire
KERNEL==“sd*!0-9]|sr*”, ATTRS{ieee1394_id}==“?“, SYMLINK+=“disk/by-id/ieee1394-$attr{ieee1394_id}”
@@ -66,6 +75,11 @@
ENV{DEVTYPE}==“disk”, ENV{ID_PATH}==”?”, SYMLINK+=“disk/by-path/$env{ID_PATH}”
ENV{DEVTYPE}==“partition”, ENV{ID_PATH}==“?*”, SYMLINK+=“disk/by-path/$env{ID_PATH}-part%n”
+# by-path (parent device path, compat version, only for ATA/NVMe/SAS bus)
+ENV{DEVTYPE}==“disk”, ENV{ID_BUS}==“ata|nvme|scsi”, DEVPATH!=“/virtual/”, IMPORT{program}=“path_id_compat %p”
+ENV{DEVTYPE}==“disk”, ENV{ID_PATH_COMPAT}==“?“, SYMLINK+=“disk/by-path/$env{ID_PATH_COMPAT}”
+ENV{DEVTYPE}==“partition”, ENV{ID_PATH_COMPAT}==”?”, SYMLINK+=“disk/by-path/$env{ID_PATH_COMPAT}-part%n”
+
probe filesystem metadata of optical drives which have a media inserted
KERNEL==“sr*”, ENV{DISK_EJECT_REQUEST}!=“?“, ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}==”?”, ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}==“?*”,
IMPORT{builtin}=“blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}”
— /.snapshots/33/snapshot/usr/lib/udev/rules.d/61-persistent-storage-compat.rules 2017-07-19 10:33:31.000000000 -0600
+++ /.snapshots/34/snapshot/usr/lib/udev/rules.d/61-persistent-storage-compat.rules 1969-12-31 17:00:00.000000000 -0700
@@ -1,71 +0,0 @@
-# Do not edit this file, it will be overwritten on update.
-# This file contains depecrated rules kept only for backward
…
I removed the last file so I don’t include all the changes
After rebooting, at least the RAID was activated. The /proc/mdstat file, which hadn’t been showing up, showed the RAID status. The following is a grep for raid in the output of the dmesg command:
2.967352] raid6: sse2x1 gen() 4801 MB/s
3.035334] raid6: sse2x1 xor() 4806 MB/s
3.103349] raid6: sse2x2 gen() 8126 MB/s
3.171334] raid6: sse2x2 xor() 8154 MB/s
3.239348] raid6: sse2x4 gen() 8822 MB/s
3.307343] raid6: sse2x4 xor() 3932 MB/s
3.307345] raid6: using algorithm sse2x4 gen() 8822 MB/s
3.307345] raid6: .... xor() 3932 MB/s, rmw enabled
3.307346] raid6: using intx1 recovery algorithm
8.673240] md/raid:md0: device sdc1 operational as raid disk 2
8.673247] md/raid:md0: device sdb1 operational as raid disk 1
8.673250] md/raid:md0: device sda6 operational as raid disk 0
8.673251] md/raid:md0: device sdd1 operational as raid disk 3
8.674295] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2
I was not seeing the last 5 lines prior to making the script changes. I’m not sure what to try next, but I’m won’t be able to play with this for a couple of days.
Everything boots fine until I apply the opensuse-2017-847 update and then it’s lights out (see the prior post).
but i just wanted to confirm that this is happening to my machine as well.