After upgrade startup errors

I just upgraded my unraid server from 4.7 to 5.0-rc6-r8168-test2.

Everything went smooth, and is working fine, but in my syslog I see some errors which I've not seen on 4.7 on the startup phase.

sas: ata7: end_device-0:0: dev error handler

sas: ata8: end_device-0:1: dev error handler

sas: ata9: end_device-0:2: dev error handler

While detecting ata7 it gives one message, which is repeated on the next ata, so for the last I get errors for all end_device-0:0 to 0:7.

My hardware is a Supermicro X7SPA-HF/X7SPA-HF, BIOS 1.2a with one AOC-SASLP-MV8 and the errors occur for disk attached to the MV8

I have unmenu running with ssmtp, minidlna, apc-ups,screen packages.

While working with the server I did not see these errors again, but did just get a

unraidserver kernel: smartctl[5695]: segfault at 80aa048 ip 080aa048 sp bfd84ad4 error 15

which I'll investigate later on

Forum search/google search did not find any results, anyone have an idea what is wrong ?

syslog-2012-08-11.txt

The smartctl segfault disappeared once I disabled unmenu and all plugins.

The dev error handler remains (as was to be expected as they occurred before unmenu was even started)

Talking to myself...

Is this just an informational message telling me it's using the 'dev error handler' for the sas ata7 end_device-0:0 ?

The unmenu syslog is flagging it as an error (red line) because of the 'error' text within it.

Found some info on http://comments.gmane.org/gmane.linux.ide/51327 which implies my previoud statement that it's just saying which error handler will be used in case of errors..