<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/megactl/patches/" rel="alternate"/><link href="https://sourceforge.net/p/megactl/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/megactl/patches/</id><updated>2012-11-13T21:47:40Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>Add in device id for megactl</title><link href="https://sourceforge.net/p/megactl/patches/2/" rel="alternate"/><published>2012-11-13T21:47:40Z</published><updated>2012-11-13T21:47:40Z</updated><author><name>David Ibarra</name><uri>https://sourceforge.net/u/gatordibarra/</uri></author><id>https://sourceforge.net291c6b8a13da87ad8d78e3795a26d4cb5ea63ef4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hey there,&lt;/p&gt;
&lt;p&gt;There are cases on our farm where we would like the device id for the disks in the array (for smartctl), but the MegaCli client generates 5/24/00 errors on some disks, which causes "other" errors to increase far to often for our liking. The attached patch alters the "name" of each disk, by prepending "dX" to the name, where X is the device id. I hope it helps somebody, or maybe even gets included into megactl.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>64 bit, BBU battery status on SAS, megactl.spec</title><link href="https://sourceforge.net/p/megactl/patches/1/" rel="alternate"/><published>2009-01-01T14:23:43Z</published><updated>2009-01-01T14:23:43Z</updated><author><name>ilmis</name><uri>https://sourceforge.net/u/ilmis/</uri></author><id>https://sourceforge.net8533cf61cde21d5bdaee6fcd6e198aa0c569aee7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;- Patched to compile as 64 bit binary except for megatrace.&lt;br /&gt;
- Wrote a megactl.spec for rpm -system.&lt;br /&gt;
- Wrote megachk -daemon which reports by mail only when problems are found.&lt;br /&gt;
- On a Fujitsu-Siemens RX300 S4 megasasctl reported battery always failed. Added a mask to battery status check. This probably needs further investigation still.&lt;br /&gt;
* "batt:FAULT, unknown charge state 0/5839mV/27C", FSC ServerView RAID manager still says status "Normal"&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>