topic Re: P420i - Smart Path - Code 347 in Disk Enclosures

P420i - Smart Path - Code 347

Patrick Neuner — Thu, 24 Jul 2014 13:51:22 GMT

Hello,

using P420i Controller with 2 SSD RAIDs (RAID 1 & RAID 5) - Smart Path enabled for both logical Drives.

Since Smart Path is activated the Controller gives me Code 347. (The cache for smart array p420i in embedded slot is not configured)

The "Configure Cache" Option is also gone ... as soon as I deactivate Smart Path the Error is gone and Cache is configureable again ...

Is this behaviour intended? Why does this Configuration raise an Error?

Thank you

Andreas Schnederle-Wagner

Re: P420i - Smart Path - Code 347

PGTRI — Tue, 29 Jul 2014 09:26:06 GMT

hi,

Please try with the latest version of the Smart Storage Administrator. That should fix it.

regards,

Re: P420i - Smart Path - Code 347

J-C_M — Wed, 30 Jul 2014 17:08:35 GMT

I had the same issue and it was fixed by following the solution proposed in the link below:

Basically you need to disable SSD SmartPaths:

Answer/Solution
FIX: In order to resolve the issue follow the steps below:

1. Open the HP SSA.

2. Click on arrays.

3. Now click on Disable HP SSD Smart path & save it.

4. Once when it is saved user will see the cache manager enabled.

http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/mostViewedDisplay/?sp4ts.oid=5177953&spf_p.tpst=psiContentDisplay&spf_p.prp_psiContentDisplay=wsrp-navigationalState%3DdocId%253Dmmr_kc-0116980-4%257CdocLocale%253Den_US&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

Re: P420i - Smart Path - Code 347

Patrick Neuner — Wed, 30 Jul 2014 17:12:21 GMT

Thanks for your information. I know that would fix the error, but basically it shouldn't give out an error if you use smarth path. With Raid 1 or 1-0 it doesn't show the error.

So yes, a newer version most probably will fix it anyway, we have the version installed that was shipped with the last PSP of June and haven't checked a newer version yet.

Anyway, as we saw performance penalties on write when using Smarth Path we disabled it now and as you mentioned, the error is gone too.

Thanks

Patrick