ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17

[ashori]

Hi all,

My security output is filled with these errors (several hundred every day).

<freenas> local kernel log messages:
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses1: Element 1 has Additional Status type 1, invalid for SES element type 0x17
> ses0: Element 1 has Additional Status type 1, invalid for SES element type 0x17

I've tried searching for clues as to what these are and how to make them go away, to no avail (Google + this forum).

Might anyone have an idea what these mean and/or point me in the right direction, please?

Freenas 11.1-U4, LSI SAS backplane, smartmicro ext nas chassis.

 

[Ericloewe]

What's the output of sesutil? Are there any firmware updates for your backplanes?

 

[ashori]

% sudo sesutil status
ses0: OK
ses1: OK

% sudo sesutil map |more
ses0:
Enclosure Name: LSI SAS3x40 0601
Enclosure ID: xxxxxxxxxxxxxxxxxxxxx (xx'ed on purpose)
Element 0, Type: Array Device Slot
Status: Unsupported (0x00 0x00 0x00 0x00)
Description: ArrayDevicesInSubEnclsr0
Element 1, Type: Array Device Slot
Status: OK (0x01 0x00 0x00 0x00)
Description: Slot00
Device Names: da0,pass0

This is whats in da1

(SR#'s blanked so ppl don't mess with my warranties ;D. I know they'd need the physical drives too but I'm trained to be paranioid)

SMART reports no errors on that drive.

I'm using an LSI AS 9300-4I HOST BUS ADAPTER

Latest firmware is P14 but I'm running P13 (haven't requested a maintenance window to upgrade it, I will if that's the fix).

I'm also running this tunable. It's a leftover from freenas 9.2 days. Not sure if its still relevant in Freenas 11x days but I figure if it aint broke, why fix it? :p

 

[Ericloewe]

I'm also running this tunable.

Get rid of it I doubt it's doing anything, but it's needless clutter.

As for the firmware, definitely update it. What is more urgent, however, is to ensure that the backplane (not the HBA) is running the latest firmware.

 

[ashori]

I'm running a external jbod:

Try as I might, I've never been able to find a firmware updates for the two backplanes in the chassis:

Searches on the supermicro site including their FTP had no luck.

I'll upgrade the LSI firmware during my next maintenance window and see if that fixes the error message.

Thanks for the prompt replies!