-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: Add ability to control LEDs of drives behind RAID adapters #522
Comments
Faced similar. at the same time command: works great:
|
@napaster Have you tried exposing the enclosure to the OS? In my case I was using # perccli /c0 set backplane expose=on You can check if it's already exposed with # perccli /c0 show backplane | grep ^Expose
Expose Backplane ON Now you should see the enclosure in the output of # lsscsi | grep enclosu
[0:0:64:0] enclosu DP BP_EXP 1.61 - And |
@BenoitKnecht thanks, yes it should, but [root@host]# lspci -v | grep SAS -A 2
19:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)
DeviceName: Integrated RAID
Subsystem: Dell PERC H330 Adapter
[root@host]# storcli /c0 show backplane J nolog | jq {
"Controllers": [
{
"Command Status": {
"CLI Version": "007.3103.0000.0000 Aug 22, 2024",
"Operating system": "Linux 4.18.0-448.el8.x86_64",
"Controller": 0,
"Status": "Success",
"Description": "None"
},
"Response Data": {
"Controller Properties": [
{
"Ctrl_Prop": "BackPlaneState",
"Value": "auto detect logic of backplanes like SGPIO & i2c SEP"
},
{
"Ctrl_Prop": "Expose Backplane",
"Value": "ON"
}
]
}
}
]
} Backplane exposed [root@host]# lsscsi | grep enclosu
[0:0:32:0] enclosu DP BP14G+EXP 2.52 - Still get 153 [root@host]# lsmcli local-disk-ident-led-on --path=/dev/sde
NO_SUPPORT(153): controller type unknown and unsupported
[root@host]# lsmcli --version
/bin/lsmcli 1.10.1 |
Some raid adapters, like those that use the
storcli
(megaraid) management utility have the ability to control identification LEDs.eg.
The library API could be extended to add support for this by adding something like:
Adding this would resolve:
#479
The text was updated successfully, but these errors were encountered: