Description of problem:
I added 2 drives after system install and created a raid1 on them for /home in my setup anaconda crashes the same if run directly or from a livecd. it seems myraid array is being detected but not initialised correctly. im really not doing anything at all. if i start the install disk and wait it will crash.
Version-Release number of selected component:
The following was filed automatically by anaconda:
anaconda 19.30.8-1 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/blivet/devicelibs/mdraid.py", line 269, in name_from_md_node
for link in os.listdir(md_dir):
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2196, in resolveDevice
md_name = devicelibs.mdraid.name_from_md_node(devspec[5:])
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 2985, in parseFSTab
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 2908, in findExistingInstallations
(mounts, swaps) = parseFSTab(devicetree, chroot=ROOT_PATH)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 424, in reset
self.roots = findExistingInstallations(self.devicetree)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 144, in storageInitialize
File "/usr/lib64/python2.7/threading.py", line 764, in run
File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run
threading.Thread.run(self, *args, **kwargs)
OSError: [Errno 2] No such file or directory: '/dev/md'
cmdline: /usr/bin/python /sbin/anaconda
cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora\x2019-TC5\x20x86_64 quiet
release: Cannot get release name.
Created attachment 762889 [details]
Created attachment 762890 [details]
Created attachment 762891 [details]
Created attachment 762892 [details]
Created attachment 762893 [details]
Created attachment 762894 [details]
Created attachment 762895 [details]
Created attachment 762896 [details]
Created attachment 762897 [details]
Created attachment 762898 [details]
Created attachment 762899 [details]
Let me guess: you have /dev/md0 in your /etc/fstab file? It is impossible for the installer to predict which minor an md array will get since your mdadm.conf is not present in the installer's runtime environment. Therefore, you must use persistent device identification in /etc/fstab, eg: UUID=, LABEL=, or name your array when you create it and specify the path using the name, eg: /dev/md/home .
This shouldn't be causing a crash, but there is little we can do about identifying an array specified as "/dev/md0" during installation.
Let's combine the two reports that both appear to cover the same situation (installer explodes if an mdraid array is identified by device node in fstab).
*** This bug has been marked as a duplicate of bug 980267 ***