Start a Conversation

Unsolved

This post is more than 5 years old

J

3565

March 25th, 2018 12:00

Cannot disable DirectPdMapping on PERC H310

Hey all,

I am having a bit of a glitch for which I hope you may have some ideas. I'm currently running in this setup a PowerEdge R710 running Windows Server 2016.

Inside of the system is the standard PERC6/i which is working fine. I have added to the system in addition to the integrated controller a PERC H310 Adapter. The system recognizes the adapter. It can also see all of the HD plugged into the enclosure through the rackable. Although, they are in LINUX so unconfigurable right now. 

But that is not my problem. The problem is I cannot boot the system up with the enclosure turned on as I continue to get an error indicating that the enclosure does not support Direct PD Mapping.

(Controller 0) I have successfully disabled DirectPDMapping on the PERC6/i
(Controller 1) I cannot get it to disable on the H310 despite numerous attempts using different methods.

- When attempting to disable this function via perccli or perccli64:
1, Failed Directpdmapping, -, Directpdmapping failed for set cmd, 3

- When attempting to disable this function via StorCLI:
Cannot locate either of the controllers on the PC

- When attempting to disable this function via MegaCli:
It like the perccli lets me adjust the value on C0, but fails when attempting to adjust value on C1

Upgraded the BIOS on the computer. I have attempted to upgrade the firmware on the H310 controller but every attempt has failed due to a system configuration mismatch, thus far. 

All attempts above were done in the administrative CMD.

Thoughts?

3 Posts

March 26th, 2018 16:00

Anyone out there able to help on this?

3 Posts

March 27th, 2018 11:00

Hey all,

I am having a bit of a glitch for which I hope you may have some ideas. I'm currently running in this setup a PowerEdge R710 running Windows Server 2016.

Inside of the system is the standard PERC6/i which is working fine. I have added to the system in addition to the integrated controller a PERC H310 Adapter. The system recognizes the adapter. It can also see all of the HD plugged into the enclosure through the rackable. Although, they are in LINUX so unconfigurable right now. 

But that is not my problem. The problem is I cannot boot the system up with the enclosure turned on as I continue to get an error indicating that the enclosure does not support Direct PD Mapping.

(Controller 0) I have successfully disabled DirectPDMapping on the PERC6/i
(Controller 1) I cannot get it to disable on the H310 despite numerous attempts using different methods.

- When attempting to disable this function via perccli or perccli64:
1, Failed Directpdmapping, -, Directpdmapping failed for set cmd, 3

- When attempting to disable this function via StorCLI:
Cannot locate either of the controllers on the PC

- When attempting to disable this function via MegaCli:
It like the perccli lets me adjust the value on C0, but fails when attempting to adjust value on C1

Upgraded the BIOS on the computer. I have attempted to upgrade the firmware on the H310 controller but every attempt has failed due to a system configuration mismatch, thus far. 

All attempts above were done in the administrative CMD.

Thoughts?

5 Posts

July 9th, 2018 18:00

I had a similar issue to this with my PERC H730P:

Using Megacli did not work. It always returned "Failed to Set data on Adapter 0", despite other configuration commands working quite happily, and the same command working perfectly on older controllers like the H700.

In the end I downloaded the RPM Perccli package, converted it to a DEB package using the Alien tool, but found that Perccli couldn't see my controller:

 

$ /opt/MegaRAID/perccli/perccli64 show all
Status Code = 0
Status = Success
Description = None

Number of Controllers = 0
Host Name = lamaar
Operating System  = Linux4.15.0-23-generic

$

Turns out I had to run Perccli(64) as root:

 

$ sudo /opt/MegaRAID/perccli/perccli64 show all
Status Code = 0
Status = Success
Description = None

Number of Controllers = 1
Host Name = lamaar
Operating System  = Linux4.15.0-23-generic

System Overview :
===============

----------------------------------------------------------------------------
Ctl Model            Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth 
----------------------------------------------------------------------------
  0 PERCH730PAdapter     8   0   0     0   0     0 Opt On  3  N      0 Opt  
----------------------------------------------------------------------------

Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled P*trol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot


ASO :
===

----
Ctl 
----
  0 
----

Cl=Cluster|MD=Max Disks|WC=Wide Cache|SS=Safe Store|FP=Fast Path|Re=Recovery
CR=CacheCade(Read)|RF=Reduced Feature Set|CO=Cache Offload
CW=CacheCade(Read/Write)|X=Not Available/Not Installed|U=Unlimited|T=Trial
|HA=High Availability |SSHA=Single server High Availability 
$

So, with that in mind, this time I was successfully able to turn Direct PD Mapping off:

 

 

$ sudo /opt/MegaRAID/perccli/perccli /c0 set directpdmapping =off
Controller = 0
Status = Success
Description = None


Controller Properties :
=====================

-------------------------------------------------
Ctrl_Prop Value 
-------------------------------------------------
Directpdmapping OFF (Requires reboot for effect) 
-------------------------------------------------

$

 

 

And to confirm it worked:

 

 

$ sudo /opt/MegaRAID/perccli/perccli /c0 show directpdmapping
Controller = 0
Status = Success
Description = None


Controller Properties :
=====================

----------------------
Ctrl_Prop Value 
----------------------
Directpdmapping OFF 
----------------------

$

 

 

I'm using Ubuntu 18.04 LTS 64-bit. Interestingly I was able to use either Perccli or Perccli64 to do this.

Beyond that, the only other quirk I had was that I was unable to upgrade the firmware on this controller without it being installed in a Dell server. Had to stick it into an old R710 before I could get that to run.

 

No Events found!

Top