<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Rebuilding error on LC2000 server in Netservers</title>
    <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296372#M9575</link>
    <description>Kris, &lt;BR /&gt;I thought that a little portion of log could be enough.&lt;BR /&gt;I attached the entire log now.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks and regards&lt;BR /&gt;Paolo</description>
    <pubDate>Thu, 30 Oct 2008 08:30:29 GMT</pubDate>
    <dc:creator>WW156629</dc:creator>
    <dc:date>2008-10-30T08:30:29Z</dc:date>
    <item>
      <title>Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296368#M9571</link>
      <description>Hi,&lt;BR /&gt;I have exactly the same issue posted in threadId 1188491 with an LC 2000 NetServer.&lt;BR /&gt;Please, can you take a look at attached JPG.&lt;BR /&gt;I have a RAID 5 situation composed by six 18GB HDs: 5 disks are composing the unique logical drive, the 6th was as hotspare. Yesterday I realized a red led on front panel.&lt;BR /&gt;Now the situation is:&lt;BR /&gt;-if I try to rebuild the fail disk (ID 9) I get a "rebuild error" message;&lt;BR /&gt;-if I try to change the READY disk (ID 3) in hotspare, it tries automatically to rebuild itself but after few seconds I receve an error and it changes in FAIL status. Contemporarily the prevoius FAIL disk (ID 9) changes in READY status;&lt;BR /&gt;-if I try again the "ping-pong" continues!&lt;BR /&gt;&lt;BR /&gt;One of the other ON-LINE disks (ID 1) has some "Media Errors" and this should be the reason of rebuild error.&lt;BR /&gt;Looking at other HP articles I found that one of the suggestion is to try to upgrade FW of disks (see article:  &lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=50440&amp;amp;prodTypeId=15351&amp;amp;prodSeriesId=50440&amp;amp;objectID=tis13104)," target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=50440&amp;amp;prodTypeId=15351&amp;amp;prodSeriesId=50440&amp;amp;objectID=tis13104),&lt;/A&gt; but on other posts/articles it is strongly recommended do not upgrade FW wher an array is in CRITICAL status.&lt;BR /&gt;&lt;BR /&gt;Has someone any suggestion? Is the only solution to backup the server, recreate the entire RAID configuration and reinstall NOS and data from backup?&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;BR /&gt;Paolo</description>
      <pubDate>Wed, 29 Oct 2008 13:49:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296368#M9571</guid>
      <dc:creator>WW156629</dc:creator>
      <dc:date>2008-10-29T13:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296369#M9572</link>
      <description>Paolo,&lt;BR /&gt;&lt;BR /&gt;the disk f/w upgrade is not going to cure the media errors on ID=1, so it will not help to fix the rebuild issue you have now.&lt;BR /&gt;&lt;BR /&gt;The only solution is to backup/repalced bad disks/re-create array/restore data unfortunately.&lt;BR /&gt;&lt;BR /&gt;Did you had the Netraid monitor service running on this server ? This periodically(once a week i.e.) checks the complete parity in the  array and corrects any soft errors, this to avoid running into the issue this array is in now.&lt;BR /&gt;&lt;BR /&gt;The Netraid Assistant log file will explain why the rebuild stops, so you can post the log file and we can look it up.&lt;BR /&gt;The log file can be retrieved with the 3th icon (counting from the right) of the icons at the top of the Netraid Assistnt GUI.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2008 07:06:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296369#M9572</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2008-10-30T07:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296370#M9573</link>
      <description>Hi Kris,&lt;BR /&gt;&lt;BR /&gt;unfortunately it is just what I imaginated!&lt;BR /&gt;I haven't the Netraid monitor service, but now I understand its utility...too late!&lt;BR /&gt;&lt;BR /&gt;Here below the log:&lt;BR /&gt;********************************************&lt;BR /&gt;Log Started.&lt;BR /&gt; - Wed Oct 29 12:58:20 2008&lt;BR /&gt;DRIVE STATE changed in CHNL 0 TARG 9 to HOTSPARE - Wed Oct 29 12:58:51 2008&lt;BR /&gt;Rebuild Started on  CHNL 0 TARG 9. - Wed Oct 29 12:58:56 2008&lt;BR /&gt;Notify message : DRIVE STATE changed in Ch 0 ID 3 to READY - Wed Oct 29 12:58:56 2008&lt;BR /&gt;Notify message : DRIVE STATE changed in Ch 0 ID 9 to REBUILD - Wed Oct 29 12:58:57 2008&lt;BR /&gt;Error on Rebuilding CHNL 0 TARG 9  - Wed Oct 29 12:59:04 2008&lt;BR /&gt;Notify message : DRIVE STATE changed in Ch 0 ID 9 to FAILED - Wed Oct 29 12:59:09 2008&lt;BR /&gt;NOTIFY:Check Condition on Ch 0 ID 1 with the following sense key - Wed Oct 29 12:59:13 2008&lt;BR /&gt;&lt;BR /&gt;Time Stamp Date =  On Oct,28 2008 At 12:58:8 &lt;BR /&gt;&lt;BR /&gt;The CDB = 28 00 00 02 89 00 00 00 80 00 &lt;BR /&gt;&lt;BR /&gt;Sense Data = f0 00 03 00 02 89 39 28 00 00 00 00 11 01 00 80 00 3f&lt;BR /&gt;********************************************&lt;BR /&gt;&lt;BR /&gt;Thank you for your support&lt;BR /&gt;&lt;BR /&gt;Best Regards&lt;BR /&gt;Paolo</description>
      <pubDate>Thu, 30 Oct 2008 07:55:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296370#M9573</guid>
      <dc:creator>WW156629</dc:creator>
      <dc:date>2008-10-30T07:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296371#M9574</link>
      <description>Paolo,&lt;BR /&gt;&lt;BR /&gt;this decodes into this :&lt;BR /&gt;&lt;BR /&gt;Byte  2: Sense key = 03 = Medium Error&lt;BR /&gt;MEDIUM ERROR.  Indicates that the command terminated with a non-recovered error condition that was probably caused by a flaw in the medium or an error in the recorded data.&lt;BR /&gt;&lt;BR /&gt;Byte 12: ASC = 11 = \ unrecovered read error&lt;BR /&gt;Byte 13: ASCQ= 00 = /&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;So if you rebuild the array, get disk id=1 out of it also besides the disk that failed first, i guess this must have b een ID=3 (if ID=9 was your original hotspare).&lt;BR /&gt;&lt;BR /&gt;The Windows log file should indicate which disk failed first, go back in history of the system.evt log file and if the monitor s/w was installed, it will show how it all started.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2008 08:23:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296371#M9574</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2008-10-30T08:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296372#M9575</link>
      <description>Kris, &lt;BR /&gt;I thought that a little portion of log could be enough.&lt;BR /&gt;I attached the entire log now.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks and regards&lt;BR /&gt;Paolo</description>
      <pubDate>Thu, 30 Oct 2008 08:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296372#M9575</guid>
      <dc:creator>WW156629</dc:creator>
      <dc:date>2008-10-30T08:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296373#M9576</link>
      <description>Paolo,&lt;BR /&gt;&lt;BR /&gt;the first time the issue got detected was way back in July on ID=1:&lt;BR /&gt;&lt;BR /&gt;"NOTIFY:Check Condition on Ch 0 ID 1 with the following sense key - Tue Oct 28 19:36:11 2008&lt;BR /&gt;&lt;BR /&gt;Time Stamp Date =  On Jul,2 2008 At 22:11:32 "&lt;BR /&gt;&lt;BR /&gt;Then on 28 Oct ID=3 kicked in to rebuild, so i assume ID=3 was defined as a hotspare in the original config.&lt;BR /&gt;Then ID=9 was defined as a hotspare.&lt;BR /&gt;&lt;BR /&gt;Anyhow, config and history is not 100% clear but there is no way to fix it unfortunately.&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2008 08:40:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296373#M9576</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2008-10-30T08:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: Rebuilding error on LC2000 server</title>
      <link>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296374#M9577</link>
      <description>Hi Kris,&lt;BR /&gt;&lt;BR /&gt;thank you for your support.&lt;BR /&gt;I'll take care of your suggestion for the future (NETraid monitor).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I'll proceed with server reinstallation.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Paolo&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2008 09:14:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/rebuilding-error-on-lc2000-server/m-p/4296374#M9577</guid>
      <dc:creator>WW156629</dc:creator>
      <dc:date>2008-10-30T09:14:09Z</dc:date>
    </item>
  </channel>
</rss>

