pcahyna

The `lsblk` command was executed on the original server? If so, why doesn't it show `sdb` as part of a multipath device? By the way, please quote the output of...

I don't get it. Is your original `lsblk` output on the original system or not? If yes, why does not it show the same multipath devices as your `multipath -ll`...

@jsmeix > so it seems the disklayout.conf does not match the original system? indeed: > I restored on a different system, with different new disks. and I suspect this may...

Also WWIDs are not that much related to multipath, it's just that without multipath you can mostly ignore them, with multipath you need them (or some other persistent identifier), because...

In RHEL, multipath seem to be configured by default to name devices like `mpatha`, `mpathb`, ..., without embedding the WWID in the device name, so part of the problem is...

> When you do not have fully compatible replacement hardware > then recreating the system becomes what we call a MIGRATION. The problem is, if your disk(s) die, and you...

Note that you don't need a SAN to obtain a multipath setup. It is enough to have e.g. SAS disks and connect them using both ports (SAS disks are dual-port,...

I will need to look, because it is possible that it actually works for this case already, e.g. by regenerating /etc/multipath/wwids dynamically, or by transforming them with `sed`, or something...

As the first step I believe the current Git master code, or at least 2.6, should be tested, because it may behave differently or even fix the issue.

@markbertolin I don't see the log files... and how it "fell down"? UserInput seems to indicate that it merely needs confirmation from you (on console). By the way, it is...