Bug 1936824

Summary:	cannot monitor megaraid-sas
Product:	[Fedora] Fedora	Reporter:	David Woodhouse <dwmw2>
Component:	smartmontools	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	mhlavink, pizza, tsmetana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	smartmontools-7.2-11.fc35 smartmontools-7.2-11.fc33 smartmontools-7.2-11.fc34	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-06 01:26:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Woodhouse 2021-03-09 09:45:39 UTC

Mar  9 00:42:25 bombadil smartd[878]: Device: /dev/sda [megaraid_disk_00], open() failed: cannot open /dev/megaraid_sas_ioctl_node or /dev/megadev0

The node exists but has no permissions. If I make it u+rw it works. But it's not created by udev; we seem to make it *ourself*? Why not just fix the kernel to advertise it properly so that it gets managed by udev properly?

I also can't actually work out *what* creates it. I hacked smartd, smartctl to change the name of the node they would create and use, and the original /dev/megaraid_sas_ioctl_node is *still* there after a reboot. I grepped the entire file system for 'megaraid_sas_ioctl_node' and don't know what's still making that node after a reboot.

Comment 1 Solomon Peachy 2021-10-22 02:05:56 UTC

I just ran into this too, on Fedora 34.

Edit /etc/sysconfig/smartmontools and get rid of '--capabilities' from the smartd_opts variable, then restart.

Basically, smartd is dropping capabilities before it tries to open /dev/megaraid_sas_ioctl_node, causing it to fail.  I've reported this bug upstream [1]


[1] https://github.com/smartmontools/smartmontools/issues/113

Comment 2 Fedora Update System 2021-11-03 08:07:01 UTC

FEDORA-2021-56742379c6 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-56742379c6

Comment 3 Fedora Update System 2021-11-03 08:07:02 UTC

FEDORA-2021-1b4fe7ef4a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1b4fe7ef4a

Comment 4 Fedora Update System 2021-11-03 08:07:03 UTC

FEDORA-2021-c2823218af has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c2823218af

Comment 5 Ben Cotton 2021-11-04 13:37:34 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora Update System 2021-11-04 13:56:43 UTC

FEDORA-2021-c2823218af has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c2823218af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c2823218af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Ben Cotton 2021-11-04 14:07:10 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora Update System 2021-11-04 14:08:18 UTC

FEDORA-2021-1b4fe7ef4a has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1b4fe7ef4a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1b4fe7ef4a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2021-11-04 14:13:42 UTC

FEDORA-2021-56742379c6 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-56742379c6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-56742379c6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Ben Cotton 2021-11-04 15:04:09 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora Update System 2021-11-06 01:26:46 UTC

FEDORA-2021-1b4fe7ef4a has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2021-11-12 00:58:43 UTC

FEDORA-2021-c2823218af has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2021-11-12 02:06:46 UTC

FEDORA-2021-56742379c6 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.