Description of problem: something to do with /dev/md127, but I changed that in fstab to LABEL=250GB_RAID1, so I don't know... Version-Release number of selected component: anaconda-20.25.15-1 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/block/__init__.py", line 196, in getNameFromDmNode stat = _os.stat(dm_node) File "/usr/lib/python2.7/site-packages/blivet/devicelibs/dm.py", line 53, in name_from_dm_node name = block.getNameFromDmNode(dm_node) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2287, in resolveDevice dm_name = devicelibs.dm.name_from_dm_node(devspec[5:]) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 3129, in parseFSTab options=options) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 3052, in findExistingInstallations (mounts, swaps) = parseFSTab(devicetree, chroot=ROOT_PATH) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 427, in reset self.roots = findExistingInstallations(self.devicetree) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 142, in storageInitialize storage.reset() File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) OSError: [Errno 2] No such file or directory: '/dev/dm-4' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20
Created attachment 869389 [details] File: anaconda-tb
Created attachment 869390 [details] File: anaconda.log
Created attachment 869391 [details] File: environ
Created attachment 869392 [details] File: install.log
Created attachment 869393 [details] File: lsblk_output
Created attachment 869394 [details] File: nmcli_dev_list
Created attachment 869395 [details] File: os_info
Created attachment 869396 [details] File: program.log
Created attachment 869397 [details] File: storage.log
Created attachment 869398 [details] File: syslog
Created attachment 869399 [details] File: ifcfg.log
Oh, I see - I've fixed the /dev/md problem; now, I've got the /dev/dm problem... I guess I might fix if the same way? Linking in bugs 980267 and 975811 because these are obviously related. Any suggestions welcome.
bug 980267 bug 975811
naming drives and referring to those names by LABEL= in fstab seems to fix both /dev/md and /dev/dm bugs - I guess people know this?
device nodes named /dev/dm-<digit> and /dev/md<digit> are not suitable for use in /etc/fstab. You should either use the names of the devices (eg: /dev/mapper/vgname-lvname or /dev/md/root) or refer to them by some constant identifier (eg: label, UUID). FWIW this is no longer a fatal error in F21, so even if you have these unusable device names in /etc/fstab the installation can still continue.