<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>controller on alexbrueckel.de</title>
		<link>https://www.alexbrueckel.de/tag/controller/</link>
		<description>Recent content in controller on alexbrueckel.de</description>
		<generator>Hugo</generator>
		<language>de-DE</language>
		
		
		
		
			<lastBuildDate>Thu, 11 Jun 2015 20:42:02 +0200</lastBuildDate>
		
			<atom:link href="https://www.alexbrueckel.de/tag/controller/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>weird log_info messages from mpt2sas</title>
				<link>https://www.alexbrueckel.de/weird-log_info-messages-from-mpt2sas/</link>
				<pubDate>Thu, 11 Jun 2015 20:42:02 +0200</pubDate>
				<guid>https://www.alexbrueckel.de/weird-log_info-messages-from-mpt2sas/</guid>
				<description>&lt;p&gt;&lt;img alt=&#34;LSI SAS 9200 package&#34; class=&#34;alignright wp-image-646 size-thumbnail&#34; decoding=&#34;async&#34; height=&#34;150&#34; src=&#34;https://www.alexbrueckel.de/wp-content/uploads/2015/06/lsi9200-150x150.jpg&#34; width=&#34;150&#34;/&gt;For no obvious reason mpt2sas started to spam my system logs on a Wheezy box with an LSI SAS 9200 controller, no raid function, many disks attached) and I worried about something being broken or breaking right away. Just for the record: I would recommend this particular controller as being rock-solid and fast under heavy load.&lt;/p&gt;&#xA;&lt;blockquote&gt;&lt;p&gt;mpt2sas0: log_info(0x30030101): originator(IOP), code(0x03), sub_code(0x0101)&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Sadly, there was no useful documentation from LSI and no good hints anywhere else. Also the &lt;a href=&#34;https://github.com/baruch/lsi_decode_loginfo&#34; target=&#34;_blank&#34;&gt;lsi_log_decode&lt;/a&gt; i stumbled upon had no clue at all. What led me to the cause of these messages was an &lt;a href=&#34;https://bugs.centos.org/view.php?id=2364&#34; target=&#34;_blank&#34;&gt;old bug report from CentOS&lt;/a&gt; which finally mentioned the &lt;em&gt;exact log message&lt;/em&gt; i got and pointed me to an issue with &lt;em&gt;calls to non-existent pages&lt;/em&gt; from a controller related management software.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
