Update on Feb/20/2024:
The Dell Perc H755 (installed on a R750) is now also tested with Debian Bullseye (Proxmox VE 7.x) and the perccli64 still works very well on both showing/setting parameters of the card and VDs.
Update on Oct/5/2022:
a newer version dell perccli64 has been found in following link:
https://www.dell.com/support/home/zh-cn/drivers/driversdetails?driverid=36g6n
from which you can easily find the .deb directly from the tar.gz file, and this means you don't need to alien that from a rpm package, and the deb can be installed directly into debian 11 and Proxmox (which has been tested).
I went search Dell PERC H750 and found out that Dell provided PercCli instead, as RPM package for Linux, which means we can use the alien command to switch the package format from RPM to DEB.
After installing the PercCli, this works quite well on Debian 11 using same syntax as Broadcom StorCli (which has different syntax against the traditional MegaCli).
https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=nf8g9
This has been tested on my new Dell R640 instance and proved working well.
oh, btw, check files using dpkg -c xxx.deb to get to know what's inside the deb package before (or after) the dpkg -i xxx.deb installation, otherwise it maybe not easy for you to find out where the binary is.
Actually it should be there as /opt/MegaRAID/perccli/perccli64 for your information.
Update on Feb/20/2024:
The Dell Perc H755 (installed on a R750) is now also tested with Debian Bullseye (Proxmox VE 7.x) and the perccli64 still works very well on both showing/setting parameters of the card and VDs.
Update on Oct/5/2022:
a newer version dell perccli64 has been found in following link:
https://www.dell.com/support/home/zh-cn/drivers/driversdetails?driverid=36g6n
from which you can easily find the .deb directly from the tar.gz file, and this means you don't need to alien that from a rpm package, and the deb can be installed directly into debian 11 and Proxmox (which has been tested).
I went search Dell PERC H750 and found out that Dell provided PercCli instead, as RPM package for Linux, which means we can use the alien command to switch the package format from RPM to DEB.
After installing the PercCli, this works quite well on Debian 11 using same syntax as Broadcom StorCli (which has different syntax against the traditional MegaCli).
https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=nf8g9
This has been tested on my new Dell R640 instance and proved working well.
oh, btw, check files using dpkg -c xxx.deb to get to know what's inside the deb package before (or after) the dpkg -i xxx.deb installation, otherwise it maybe not easy for you to find out where the binary is.
Actually it should be there as /opt/MegaRAID/perccli/perccli64 for your information.
Turns out that offending command which gets blocked is megacli -AdpAllInfo -a0 -NoLog where perccli64 will be blocked for this command as well as megacli.
One can hopefully patch megaclisas-status to avoid such command
diff --git a/megaclisas-status b/megaclisas-status
index 870e3a5..a9bc55b 100755
--- a/megaclisas-status
+++ b/megaclisas-status
@@ -27,7 +27,7 @@ nagiosbaddisk = 0
# Sane defaults
printarray = True
-printcontroller = True
+printcontroller = False
debugmode = False
notempmode = False
totaldrivenumber = 0
We lost information about controller and BBU but megaclisas-status daemon can be used to monitor the status of the array without need for heavy refactoring for perccli64 (not talking about perccli64 /c0 show all segfaults for us anyway -- R540 + H750)
Dell R 730 PERC H730P [ Solved ] | Proxmox Support Forum
VMWare ESX 7.0 - DELL (PERC H730P)
New PERC DELL
PERC H730P Firmware Update
Hi,
I want to use perccli commands on DELL Hosts. I am assuming not installed on ESX Hosts. How can I install this ?
There is no any return below command.
esxcli software vib list | grep perccli
thanks,
Morning (I think)
I'm entirely stumped.
Flashed Dell Perc 310 successfully (lol, I mean after 3 days of trying).
Running Open Media Vault, so debian. Lspci shows the controller, all good.
No drives show up. I've tried different drives, different cables. Card has latest LSI firmware flashed to it.
Is there something system wise I need to do? I can't work out if there is a driver issue or what it is. I didn't have this issue on the last machine, but it was so long ago that I set that one up I can't remember. First time using a 310, previously I had a standard LSI which was simple and easy to sort out.
I know there is no bios on the card now as I don't have the option of entering controller bios when I boot up. Does that make a difference? It's only JBOD/IT so I'm pretty sure I don't need that for a passthrough.
Would love some trouble shooting tips before I rip the damn card out and yeet it out the window. Can tell I am stressed when I adopt my ten year old's gamer language.