Description of problem: Fedora 28 - Fedora 33 grub2-mkconfig throws device-mapper errors in a multiboot GPT based environment Version-Release number of selected component (if applicable): Fedora 28 through Fedora 33 INCLUSIVE How reproducible: 100% Steps to Reproduce: 1. Start with a multiboot GPT based system. 2. Attempt to create a new grub.cfg file using the string "grub2-mkconfig -o ./grub.cfg". 3. Actual results: Most of the time a new grub.cfg file will not be created. All of the time device-mapper errors will be thrown. Expected results: A useable grub.cfg file. No device-mapper errors. Additional info: This bug was introduced when file os-prober30 had a major rewrite for inclusion in Fedora 28.
Please attach the complete os-prober/grub2-mkconfig logs (appear in your journal logs). Also, if it is really related to 30_os-prober file, it belongs to grub2 package not os-prober. But its better to see the logs before deciding about it. Surprisingly, os-prober doesn't depend on device-mapper anymore (at least directly). So, I've no idea about what your errors could be.
I reproduced the problem in Fedora 33 beta and will attempt to reproduce it again after Fedora 33 has been officially released. Not being familiar with the acquisition of log data I am uncertain concerning which steps should I go through to obtain the information that you are seeking. Would you mind providing guidance?
Run the following command in a separate shell prompt: journalctl -lf > mkconfig.log Then run grub2-mkconfig in another prompt. When finished, press Ctrl+C in the first shell, so that the journalctl command is terminated. Then send the log file. Thanks
I am trying to remove egg from my face. This bug manifests with grub2-mkconfig version 2.03 but grub2-mkconfig version 2.04 works as expected both from a Fedora 33 LiveCD and also from an updated installation. Failure associated with a stupid user error led me to believe that this problem existed in Fedora 32 and Fedora 33 Beta. When I tested correctly, grub2-mkconfig version 2.04 in Fedora 32 and Fedora 33 worked as expected.
:) So, can we close this report? Seems that everything is OK now, right?
Yes, Please close this report.
Thanks.