nefarius/SmartArrayControllerTool
1
0
Fork 0
Code
HP Array Configuration Utility - Reverse Engineering
10 Commits 1 Branch 0 Tags 12 MiB
C++ 51%
C 49%
2770d44955
Go to file
Benjamin Höglinger-Stelzer 2770d44955 Added copy of HpSAMD.sys (from Windows 8.1 x64)
2023-06-25 17:05:26 +02:00
drivers/hpsamd.inf_amd64_ecc432cd9ea41679 Added copy of HpSAMD.sys (from Windows 8.1 x64) 2023-06-25 17:05:26 +02:00
SmartArrayControllerTool Updated README 2023-06-25 16:56:47 +02:00
.gitattributes Add .gitattributes and .gitignore. 2023-06-23 02:21:33 +02:00
.gitignore Add .gitattributes and .gitignore. 2023-06-23 02:21:33 +02:00
README.md Updated README 2023-06-25 16:56:47 +02:00
SmartArrayControllerTool.sln Add project files. 2023-06-23 02:21:34 +02:00

README.md

HP Array Configuration Utility - Reverse Engineering

About

Trying to figure out which requests the HP ProLiant Array Configuration Utility for Windows 64-bit sends to my HP Smart Array P410 RAID Controller, so that I can script it to e.g. fetch disk alerts etc.

Heavily work in progress 🔥

Details

The ACU sends a couple of IOCTL_SCSI_MINIPORT IOCTLs with custom payloads on controller selection; this is received and handled by the HpSAMD.sys driver. So far cross-checking the payload format with the well-known Linux sources hasn't yielded any success; I assume when IOCTL_SCSI_MINIPORT is used, the payload isn't what 1:1 gets sent to the controller, unlike IOCTL_SCSI_PASS_THROUGH which isn't what the ACU uses. Next step might be trying to port over the Linux CCISS example requests to the Windows SCSI API by using IOCTL_SCSI_PASS_THROUGH to try if the controller then responds with the same packet structure as it would under Linux.

3rd party sources