Analysis of storage related issues post-mortem is rather difficult as the state of the storage before anaconda changes it is unknown and has to be reverse engineered from incomplete logs (dmesg is missing systemd related messages for example.)
We can always make sure to run lsblk by default into program.log -- that should dump a pretty good amount of useful information.
It might also be useful to run lvdisplay/vgdisplay/pvdisplay or cat /proc/mdstat.
Some inspiration can be found in dracut's rdsosreport.sh:
Tested on RHEL-7.3-20160729.1 with anaconda-184.108.40.206-1. Service anaconda-pre.service is not available.
[anaconda root@localhost /] readlink /usr/lib/systemd/system/anaconda.target.wants/anaconda-pre.service
[anaconda root@localhost /] ls /lib/systemd/system/anaconda-pre.service
ls: cannot access /lib/systemd/system/anaconda-pre.service: No such file or directory
Verified on RHEL-7.3-20160825.1 with anaconda-220.127.116.11-1.el7.
Sounds reasonable to me.
note this means a package needs to depend on socat. Funny enough, currently not a single package in rhel6 or rhel7 "Requires" socat
PR in Lorax to add new dependencies: https://github.com/rhinstaller/lorax/pull/181
PR to Anaconda: https://github.com/rhinstaller/anaconda/pull/947
I've add dependency on nmap-ncat instead of socat. So socat is still not required.
anaconda-26.21.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f620d8c7c2
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.