| Summary: | "DM multipath kernel driver not loaded" message when running update-grub2 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bequimao.de, cjw, davidwhodgins, geiger.david68210, joequant, kernel, lovaren, mageia, marja11, ngompa13, thierry.vignaud, tmb, zen25000 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| See Also: | https://bugs.mageia.org/show_bug.cgi?id=15752 | ||
| Whiteboard: | |||
| Source RPM: | multipath-tools | CVE: | |
| Status comment: | |||
| Attachments: |
Information about my hardware
CLI output of grub2-mkconfig |
||
|
Description
Kristoffer Grundström
2019-04-17 15:57:49 CEST
Kernel version is 5.0.7-desktop-5.mga7. The same message occurs here on a multiboot-system. LVM and btrfs involved. Do you have os-prober installed and active? It looks like a warning. The file /boot/grub2/grub.cfg is valid and works. The process slowed down considerably. cc'ing Barry Jackson. Ulrich CC:
(none) =>
bequimao.de, zen25000 Created attachment 10954 [details]
CLI output of grub2-mkconfig
Took approx. 15 minutes.
The message appeared with the kernel 5.0 series.
Ulrich Beckmann
2019-04-19 19:40:43 CEST
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=15752 (In reply to Ulrich Beckmann from comment #3) > Do you have os-prober installed and active? It's installed, but I have no idea if it's active or not. CC'ing our multipath-tools maintainer and our kernel maintainers, because I lack the needed knowledge to triage this report. Source RPM:
grub2-common =>
grub2? os-prober? multipath-tools? kernel? [root@localhost ~]# service multipathd status Redirecting to /bin/systemctl status multipathd.service ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; vendor preset: disabled) Active: inactive (dead) It's not supposed to be like that, right? (In reply to Marja Van Waes from comment #6) > CC'ing our multipath-tools maintainer and our kernel maintainers, because I > lack the needed knowledge to triage this report. (In reply to Kristoffer Grundström from comment #7) > [root@localhost ~]# service multipathd status > Redirecting to /bin/systemctl status multipathd.service > ● multipathd.service - Device-Mapper Multipath Device Controller > Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; > vendor preset: disabled) > Active: inactive (dead) > > It's not supposed to be like that, right? Assuming multipath is the culprit and assigning to all packagers collectively, because we no longer have a multipath-tools maintainer, and CC'ing a bunch of its committers CC:
(none) =>
cjw, joequant, mageia, ngompa13, thierry.vignaud, tmb Ping! Any progress on this? Closing as invalid. It's simply an information message that the multipath kernel has not been loaded. It's not being loaded because the multipath feature allowing multiple paths through storage arrays to access a given pool of storage devices has not been configured. See https://www.thegeekdiary.com/understanding-linux-multipath-using-dm-multipath/ It's not something a home user is going to be using, and is not related to multi-boot. Status:
NEW =>
RESOLVED |