<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disaster-Recovery on The Infinite Unknown</title>
    <link>https://www.jaredwatkins.com/tags/disaster-recovery/</link>
    <description>Recent content in Disaster-Recovery on The Infinite Unknown</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Feb 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://www.jaredwatkins.com/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>System Rescue CD to the.. rescue!</title>
      <link>https://www.jaredwatkins.com/posts/2011/02/system-rescue-cd-to-the-rescue/</link>
      <pubDate>Fri, 18 Feb 2011 00:00:00 +0000</pubDate>
      <author>Jared Watkins</author>
      <guid>https://www.jaredwatkins.com/posts/2011/02/system-rescue-cd-to-the-rescue/</guid>
      <description>&lt;p&gt;
  &lt;img src=&#34;http://farm6.static.flickr.com/5211/5421694137_c92bd1b195.jpg&#34; alt=&#34;&#34; width=&#34;160&#34; /&gt;

&lt;/p&gt;
&lt;p&gt;Here’s the scenario..  It’s 1 am and I have to shut down a critical linux server to relocate it in a rack to make room for new equipment. It should have been a 5 minute job.. but on powering up the server it refused to boot past printing the word ‘&lt;a href=&#34;http://en.wikipedia.org/wiki/GNU_GRUB&#34;&gt;Grub&lt;/a&gt;‘ on the screen.  This isn’t good..  this server is needed by a couple hundred thousand customers and rebuilding it wasn’t planned or scheduled.  On closer examination 3 of the 16 hard drive power lights are not on. It’s extremely unlikely that 3 drives would die like that on a server that isn’t even two years old.  Unfortunately I didn’t have a copy of the the &lt;a href=&#34;http://www.sysresccd.org&#34;&gt;System Rescue CD&lt;/a&gt; so the fix attempt would have to wait until morning.&lt;/p&gt;
&lt;p&gt;I had the &lt;a href=&#34;http://www.equinix.com/&#34;&gt;CoLo&lt;/a&gt; staff burn me a copy which I used to boot the damaged server the next morning.  It booted into a live linux environment and correctly detected all the server hardware.. including the raid controller.  I was able to check the status of the 3 raid arrays and found them to be all in working order.. the 3 dark drive lights were unrelated.  I was then able to &lt;a href=&#34;http://en.wikipedia.org/wiki/Chroot&#34;&gt;chroot&lt;/a&gt; into the broken system and &lt;a href=&#34;http://www.sysresccd.org/Sysresccd-Partitioning-EN-Repairing-a-damaged-Grub&#34;&gt;reinstall grub&lt;/a&gt; onto the primary disk. The server then booted normally and all was well. I still don’t know how or when the &lt;a href=&#34;http://en.wikipedia.org/wiki/Master_boot_record&#34;&gt;MBR&lt;/a&gt; got corrupted.. but thanks to the utility of the &lt;a href=&#34;http://www.sysresccd.org&#34;&gt;RescueCD&lt;/a&gt; this was an easy fix.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
