On Monday 05 of October 2015 10:29:50 Andrei Borzenkov wrote:
This is multipath device.
ST3120811AS_6PT0TQ9P dm-0 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running
This changed since yesterday, ST3120811AS_6PT0TQ9P dm-2 ATA,ST3120811AS size=112G features='0' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 2:0:0:0 sdc 8:32 active ready running I don't know much about this, but, according to the documentation, dmsetup table indicates the number of paths, which should be >1 for a multipath device. Also, during boot, before the root is mounted, multipathd[734]: ok multipathd[288]: path checkers start up multipathd[288]: sda: failed to get uid: Invalid argument multipathd[288]: sda: failed to get uid: Invalid argument multipathd[288]: sdb: failed to get uid: Invalid argument multipathd[288]: sdb: failed to get uid: Invalid argument multipathd[288]: sdc: failed to get uid: Invalid argument multipathd[288]: sdc: failed to get uid: Invalid argument multipathd[288]: sda: add path (uevent) multipathd[288]: sda: spurious uevent, path already in pathvec multipathd[288]: ST31000528AS_9VP2VWC2: load table [0 1953525168 multipath 0 0 1 1 service-time 0 1 1 8:0 1] multipathd[288]: ST31000528AS_9VP2VWC2: event checker started multipathd[288]: sda [8:0]: path added to devmap ST31000528AS_9VP2VWC2 multipathd[288]: sdb: add path (uevent) multipathd[288]: sdb: spurious uevent, path already in pathvec multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: load table [0 234441648 multipath 0 0 1 1 service-time 0 1 1 8:16 1] multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: event checker started multipathd[288]: sdb [8:16]: path added to devmap WDC_WD1200JD-00GBB0_WD-WMAES3432850 multipathd[288]: sdc: add path (uevent) multipathd[288]: sdc: spurious uevent, path already in pathvec multipathd[288]: ST3120811AS_6PT0TQ9P: load table [0 234441648 multipath 0 0 1 1 service-time 0 1 1 8:32 1] multipathd[288]: ST3120811AS_6PT0TQ9P: event checker started multipathd[288]: sdc [8:32]: path added to devmap ST3120811AS_6PT0TQ9P multipathd[288]: sdd: add path (uevent) multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: load table [0 156301488 multipath 0 0 1 1 service-time 0 1 1 8:48 1] multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: event checker started multipathd[288]: sdd [8:48]: path added to devmap WDC_WD800JB-00ETA0_WD- WMAHL1387773 multipathd[288]: ST31000528AS_9VP2VWC2: stop event checker thread (140410342287104) multipathd[288]: WDC_WD1200JD-00GBB0_WD-WMAES3432850: stop event checker thread (140410342250240) multipathd[288]: ST3120811AS_6PT0TQ9P: stop event checker thread (140410342213376) multipathd[288]: WDC_WD800JB-00ETA0_WD-WMAHL1387773: stop event checker thread (140410342176512) multipathd[288]: --------shut down------- There is no reason for multipath on this system, unless systemd or dracut do something weird. Perhaps this is related to the fact that I've been using these disks for several years with different motherboards, originally with a RAID controller that wrote some metadata on them (they were appearing as RAID disks in lsblk -f, even though I've never used any RAID feature). The booting problem started after the transition to dracut, and shortly thereafter I removed the metadata. Perhaps some of it is still left? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org