<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Therese</id>
	<title>DISI - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Therese"/>
	<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Special:Contributions/Therese"/>
	<updated>2026-05-24T00:35:45Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8153</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8153"/>
		<updated>2014-10-29T22:08:17Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: You can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: Choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (the vm must be powered off) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you see the following errors when you start your virtual machine:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:vmerr1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:vmerr2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Don&#039;t worry, it&#039;s a simple two minute fix.  Please just ask one of the sysadmins to fix it.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=File:Vmerr2.png&amp;diff=8152</id>
		<title>File:Vmerr2.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=File:Vmerr2.png&amp;diff=8152"/>
		<updated>2014-10-29T22:07:34Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8151</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8151"/>
		<updated>2014-10-29T22:07:20Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: You can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: Choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (the vm must be powered off) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you see the following errors when you start your virtual machine:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:vmerr1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:vmerr2.png]]&lt;br /&gt;
&lt;br /&gt;
Don&#039;t worry, it&#039;s a simple two minute fix.  Please just ask one of the sysadmins to fix it.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=File:Vmerr1.png&amp;diff=8150</id>
		<title>File:Vmerr1.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=File:Vmerr1.png&amp;diff=8150"/>
		<updated>2014-10-29T21:36:31Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8149</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8149"/>
		<updated>2014-10-29T21:36:14Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: You can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: Choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (the vm must be powered off) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you see the following errors when you start your virtual machine:&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:vmerr1.png]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8120</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8120"/>
		<updated>2014-10-10T22:20:54Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: You can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: Choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (the vm must be powered off) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8119</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8119"/>
		<updated>2014-10-10T22:20:09Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: You can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: Choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8118</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8118"/>
		<updated>2014-10-10T22:17:37Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
&lt;br /&gt;
Marvin&lt;br /&gt;
&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
&lt;br /&gt;
Chimera&lt;br /&gt;
&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
&lt;br /&gt;
ChemDraw &lt;br /&gt;
&lt;br /&gt;
End Note&lt;br /&gt;
&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
&lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: you can call it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Type: choose Microsoft Windows.&lt;br /&gt;
&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
&lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi&lt;br /&gt;
&lt;br /&gt;
Then click Create.&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
&lt;br /&gt;
To change your password:&lt;br /&gt;
&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8117</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8117"/>
		<updated>2014-10-10T22:14:19Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
Marvin&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
Chimera&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
ChemDraw &lt;br /&gt;
End Note&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. &lt;br /&gt;
You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: you can call it whatever you want.&lt;br /&gt;
Type: choose Microsoft Windows.&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next.&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine-1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi&lt;br /&gt;
Then click Create.&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
To change your password select:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8116</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8116"/>
		<updated>2014-10-10T22:13:00Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
Marvin&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
Chimera&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
ChemDraw &lt;br /&gt;
End Note&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. You will then see this box:&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot-Create Virtual Machine.png]]&lt;br /&gt;
&lt;br /&gt;
Name: you can call it whatever you want.&lt;br /&gt;
Type: choose Microsoft Windows.&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi&lt;br /&gt;
Then click Create.&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
To change your password select:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=File:Screenshot-Create_Virtual_Machine-1.png&amp;diff=8115</id>
		<title>File:Screenshot-Create Virtual Machine-1.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=File:Screenshot-Create_Virtual_Machine-1.png&amp;diff=8115"/>
		<updated>2014-10-10T22:12:06Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=File:Screenshot-Create_Virtual_Machine.png&amp;diff=8114</id>
		<title>File:Screenshot-Create Virtual Machine.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=File:Screenshot-Create_Virtual_Machine.png&amp;diff=8114"/>
		<updated>2014-10-10T22:11:39Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8113</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8113"/>
		<updated>2014-10-10T22:11:14Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
Marvin&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
Chimera&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
ChemDraw &lt;br /&gt;
End Note&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: you can call it whatever you want.&lt;br /&gt;
Type: choose Microsoft Windows.&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi&lt;br /&gt;
Then click Create.&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
To change your password select:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8112</id>
		<title>The Lab Windows VM and VirtualBox</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=The_Lab_Windows_VM_and_VirtualBox&amp;diff=8112"/>
		<updated>2014-10-10T22:08:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: Created page with &amp;quot;&amp;#039;&amp;#039;&amp;#039;All About the Lab Windows VM and VirtualBox&amp;#039;&amp;#039;&amp;#039;  The current Lab VM runs on Windows 7 and has an 80GB hard drive. It comes with the following software:  Pymol Marvin Pip...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[&#039;&#039;&#039;All About the Lab Windows VM and VirtualBox&#039;&#039;&#039;]]&lt;br /&gt;
&lt;br /&gt;
The current Lab VM runs on Windows 7 and has an 80GB hard drive.&lt;br /&gt;
It comes with the following software:&lt;br /&gt;
&lt;br /&gt;
Pymol&lt;br /&gt;
Marvin&lt;br /&gt;
Pipeline Pilot&lt;br /&gt;
Chimera&lt;br /&gt;
GraphPad Prism&lt;br /&gt;
Adobe Acrobat&lt;br /&gt;
Adobe Creative Suite&lt;br /&gt;
ChemDraw &lt;br /&gt;
End Note&lt;br /&gt;
Microsoft Office&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Setup Your Windows VM:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Your VM is located in your home folder in a Directory called Vms, ie, ~/Vms/LabWindows.vdi.&lt;br /&gt;
To setup the VM open up VirtualBox and click on New. You will then see this box:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Name: you can call it whatever you want.&lt;br /&gt;
Type: choose Microsoft Windows.&lt;br /&gt;
Version: Windows 7 (64 bit)&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
For the Memory size, you can make it whatever you want.  &lt;br /&gt;
I usually select about 5000 MB.&lt;br /&gt;
&lt;br /&gt;
Then click Next&lt;br /&gt;
&lt;br /&gt;
You will see a box that looks like this:&lt;br /&gt;
&lt;br /&gt;
Select &amp;quot;Use an existing virtual hard drive file&amp;quot;&lt;br /&gt;
Then click the little folder icon to the right and navigate to and select: ~/Vms/LabWindows.vdi&lt;br /&gt;
Then click Create.&lt;br /&gt;
Click the Start button in the bottom left hand corner.&lt;br /&gt;
Then click Control Panel =&amp;gt; User Accounts and Family Safety =&amp;gt; User Accounts =&amp;gt; Your account =&amp;gt; Change your password&lt;br /&gt;
&lt;br /&gt;
Now to use your newly created machine, click on the Start arrow up at the top.&lt;br /&gt;
Your default login will be your user name on the cluster and your initial password will be emailed to you.&lt;br /&gt;
Once you&#039;ve logged in please change your password.  &lt;br /&gt;
To change your password select:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want to attach your directories on nfs or your local directories to the VM (highly recommended):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Open VirtualBox (do not start the vm) and click on Machine =&amp;gt; Settings =&amp;gt; Shared Folders&lt;br /&gt;
You will see a little folder icon with a green plus sign on the right, click on that.&lt;br /&gt;
Then click on Folder Path and navigate to the directory you want to mount.&lt;br /&gt;
Once you&#039;ve selected the folder, click on the Auto-mount button and then click ok.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8111</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8111"/>
		<updated>2014-10-08T23:05:18Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    To this:&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;nowiki&amp;gt;#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
    IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
    BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
    &lt;br /&gt;
    # Check to see if image format is qcow2 and if so create a snapshot:	&lt;br /&gt;
    for HOST in `ls $IMAGEDIR`;do &lt;br /&gt;
       FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
       if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;]; then&lt;br /&gt;
         virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
       fi&lt;br /&gt;
    done&lt;br /&gt;
&lt;br /&gt;
    tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
    tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8110</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8110"/>
		<updated>2014-10-08T23:04:53Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    To this:&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;nowiki&amp;gt;#!/bin/bash&lt;br /&gt;
    IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
    BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
    &lt;br /&gt;
    # Check to see if image format is qcow2 and if so create a snapshot:	&lt;br /&gt;
    for HOST in `ls $IMAGEDIR`;do &lt;br /&gt;
       FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
       if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;]; then&lt;br /&gt;
         virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
       fi&lt;br /&gt;
    done&lt;br /&gt;
&lt;br /&gt;
    tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
    tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8109</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8109"/>
		<updated>2014-10-08T21:55:10Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    To this:&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;nowiki&amp;gt;#!/bin/bash&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
    IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
    BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
    &amp;lt;nowiki&amp;gt;# Check to see if image format is qcow2 and if so create a snapshot:	&lt;br /&gt;
        for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8108</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8108"/>
		<updated>2014-10-08T21:53:26Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    To this:&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;nowiki&amp;gt;#!/bin/bash&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
	&lt;br /&gt;
	IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
	BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
&lt;br /&gt;
	# Check to see if image format is qcow2 and if so create a snapshot:&lt;br /&gt;
	&lt;br /&gt;
	for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8107</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8107"/>
		<updated>2014-10-08T21:51:49Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    To this:&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
	#!/bin/bash&lt;br /&gt;
	&lt;br /&gt;
	IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
	BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
&lt;br /&gt;
	# Check to see if image format is qcow2 and if so create a snapshot:&lt;br /&gt;
	&lt;br /&gt;
	for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	http://fedoraproject.org/wiki/Features/Virt_Live_Snapshots&lt;br /&gt;
&lt;br /&gt;
		http://kashyapc.com/2012/09/14/externaland-live-snapshots-with-libvirt/&lt;br /&gt;
&lt;br /&gt;
		http://serverfault.com/questions/567234/how-to-replace-qemu-binary-with-newer-version-for-libvirt-live-snapshots&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8106</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8106"/>
		<updated>2014-10-08T21:49:45Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
Then determine the volume format type using qemu-img info: &lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
    /var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
    virsh snapshot-list my_image&lt;br /&gt;
&lt;br /&gt;
     Name                 Creation Time             State&lt;br /&gt;
    ------------------------------------------------------------&lt;br /&gt;
     my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
    qemu-img info my_image&lt;br /&gt;
&lt;br /&gt;
    image: my_image&lt;br /&gt;
    file format: raw&lt;br /&gt;
    virtual size: 10G (10737418240 bytes)&lt;br /&gt;
    disk size: 8.9G&lt;br /&gt;
    cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
    virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
    cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
    qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
Then edit the xml file:&lt;br /&gt;
&lt;br /&gt;
    virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
    Change this:    &lt;br /&gt;
&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
    To this:&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
         &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    Save and quit.&lt;br /&gt;
&lt;br /&gt;
    virsh start my_image&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I have a cron job that runs this script I wrote to back up the hypervisor monthly:&lt;br /&gt;
&lt;br /&gt;
	#!/bin/bash&lt;br /&gt;
	&lt;br /&gt;
	IMAGEDIR=/var/lib/libvirt/images/&lt;br /&gt;
	BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
&lt;br /&gt;
	# Check to see if image format is qcow2 and if so create a snapshot:&lt;br /&gt;
	&lt;br /&gt;
	for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	http://fedoraproject.org/wiki/Features/Virt_Live_Snapshots&lt;br /&gt;
&lt;br /&gt;
		http://kashyapc.com/2012/09/14/externaland-live-snapshots-with-libvirt/&lt;br /&gt;
&lt;br /&gt;
		http://serverfault.com/questions/567234/how-to-replace-qemu-binary-with-newer-version-for-libvirt-live-snapshots&lt;br /&gt;
&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8105</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8105"/>
		<updated>2014-10-08T21:44:08Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
cd /var/lib/libvirt/images/&lt;br /&gt;
Then type &amp;quot;qemu-img info image_name&amp;quot; &lt;br /&gt;
qemu-img info my_image&lt;br /&gt;
image: my_image&lt;br /&gt;
file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
virtual size: 10G (10737418240 bytes)&lt;br /&gt;
disk size: 8.9G&lt;br /&gt;
cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
/var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
virsh snapshot-list my_image&lt;br /&gt;
&lt;br /&gt;
 Name                 Creation Time             State&lt;br /&gt;
------------------------------------------------------------&lt;br /&gt;
 my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
qemu-img info my_image&lt;br /&gt;
image: my_image&lt;br /&gt;
file format: raw&lt;br /&gt;
virtual size: 10G (10737418240 bytes)&lt;br /&gt;
disk size: 8.9G&lt;br /&gt;
cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
Change this:    &lt;br /&gt;
&lt;br /&gt;
&amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
      &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
To this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
      &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
virsh start my_image&lt;br /&gt;
&lt;br /&gt;
That&#039;s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have this script run monthly:&lt;br /&gt;
&lt;br /&gt;
	#!/bin/bash&lt;br /&gt;
	&lt;br /&gt;
	IMAGEDIR=/var/lib/libvirt/images/bulk&lt;br /&gt;
	BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
&lt;br /&gt;
	# Cleanup of backup directory&lt;br /&gt;
    	X=`ls -l $BACKUPDIR | wc -l`&lt;br /&gt;
    	if (($X &amp;gt; 1)); then&lt;br /&gt;
          rm -rf $BACKUPDIR/*&lt;br /&gt;
    	fi&lt;br /&gt;
&lt;br /&gt;
	# Check to see if image format is qcow2 and if so create a snapshot:&lt;br /&gt;
	&lt;br /&gt;
	for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	http://fedoraproject.org/wiki/Features/Virt_Live_Snapshots&lt;br /&gt;
		http://kashyapc.com/2012/09/14/externaland-live-snapshots-with-libvirt/&lt;br /&gt;
		http://serverfault.com/questions/567234/how-to-replace-qemu-binary-with-newer-version-for-libvirt-live-snapshots&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8104</id>
		<title>How to Backup a Hypervisor</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Backup_a_Hypervisor&amp;diff=8104"/>
		<updated>2014-10-08T21:37:54Z</updated>

		<summary type="html">&lt;p&gt;Therese: Created page with &amp;quot;There are essentially three steps to fully backing up a hypervisor:  1) Create snapshots of all images 2) Create a tarball of the /var/lib/libvirt directory 3) Create a tarbal...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are essentially three steps to fully backing up a hypervisor:&lt;br /&gt;
&lt;br /&gt;
1) Create snapshots of all images&lt;br /&gt;
2) Create a tarball of the /var/lib/libvirt directory&lt;br /&gt;
3) Create a tarball of the /etc/libvirt directory&lt;br /&gt;
&lt;br /&gt;
The second and third steps are self explainatory, so I am only going over step 1. :)&lt;br /&gt;
&lt;br /&gt;
In order to create a snapshot of an image it needs to have a qcow2 image format.&lt;br /&gt;
&lt;br /&gt;
To determine the volume format type, go into the directory where the images are:&lt;br /&gt;
cd /var/lib/libvirt/images/&lt;br /&gt;
Then type &amp;quot;qemu-img info image_name&amp;quot; &lt;br /&gt;
qemu-img info my_image&lt;br /&gt;
image: my_image&lt;br /&gt;
file format: qcow2			&amp;lt;==== This is the disk/image format&lt;br /&gt;
virtual size: 10G (10737418240 bytes)&lt;br /&gt;
disk size: 8.9G&lt;br /&gt;
cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You take a snapshot like this:&lt;br /&gt;
&lt;br /&gt;
virsh snapshot-create-as my_image my_image_snapshot1&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;my_image&amp;quot; is the domain name and &amp;quot;my_image_snapshot1&amp;quot; is the name that I am giving the snapshot.&lt;br /&gt;
&lt;br /&gt;
All the snapshots are stored as an xml file here:&lt;br /&gt;
&lt;br /&gt;
/var/lib/libvirt/qemu/snapshot/&lt;br /&gt;
&lt;br /&gt;
You can also see a list of snapshots for a particular domain by typing:&lt;br /&gt;
&lt;br /&gt;
virsh snapshot-list my_image&lt;br /&gt;
&lt;br /&gt;
 Name                 Creation Time             State&lt;br /&gt;
------------------------------------------------------------&lt;br /&gt;
 my_image_snapshot1    2014-09-30 16:36:51 -0700 running&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To convert the image from another format type to qcow2 (using my_image as an example):&lt;br /&gt;
&lt;br /&gt;
qemu-img info my_image&lt;br /&gt;
image: my_image&lt;br /&gt;
file format: raw&lt;br /&gt;
virtual size: 10G (10737418240 bytes)&lt;br /&gt;
disk size: 8.9G&lt;br /&gt;
cluster_size: 65536&lt;br /&gt;
&lt;br /&gt;
You have to power off the domain first: &lt;br /&gt;
&lt;br /&gt;
virsh shutdown my_image&lt;br /&gt;
&lt;br /&gt;
Next, convert my_image from raw to qcow2:&lt;br /&gt;
&lt;br /&gt;
cd /var/lib/libvirt/images/&lt;br /&gt;
&lt;br /&gt;
qemu-img convert -f raw my_image -O qcow2 my_image.qcow2&lt;br /&gt;
&lt;br /&gt;
virsh edit my_image&lt;br /&gt;
&lt;br /&gt;
Change this:    &lt;br /&gt;
&lt;br /&gt;
&amp;lt;driver name=&#039;qemu&#039; type=&#039;raw&#039;/&amp;gt;&lt;br /&gt;
      &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image&#039;/&amp;gt;&lt;br /&gt;
To this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;driver name=&#039;qemu&#039; type=&#039;qcow2&#039;/&amp;gt;&lt;br /&gt;
      &amp;lt;source file=&#039;/var/lib/libvirt/images/my_image.qcow2&#039;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
virsh start my_image&lt;br /&gt;
&lt;br /&gt;
That&#039;s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have this script run monthly:&lt;br /&gt;
&lt;br /&gt;
	#!/bin/bash&lt;br /&gt;
	&lt;br /&gt;
	IMAGEDIR=/var/lib/libvirt/images/bulk&lt;br /&gt;
	BACKUPDIR=/var/backup/home/data/&lt;br /&gt;
&lt;br /&gt;
	# Cleanup of backup directory&lt;br /&gt;
    	X=`ls -l $BACKUPDIR | wc -l`&lt;br /&gt;
    	if (($X &amp;gt; 1)); then&lt;br /&gt;
          rm -rf $BACKUPDIR/*&lt;br /&gt;
    	fi&lt;br /&gt;
&lt;br /&gt;
	# Check to see if image format is qcow2 and if so create a snapshot:&lt;br /&gt;
	&lt;br /&gt;
	for HOST in `ls -l $IMAGEDIR`;do &lt;br /&gt;
	   FORMAT=`qemu-img info $HOST | grep format | cut -d&#039; &#039; -f3`&lt;br /&gt;
	   if [&amp;quot;$FORMAT&amp;quot; == &amp;quot;qcow2&amp;quot;];then&lt;br /&gt;
	      virsh snapshot-create-as $HOST $HOST_1&lt;br /&gt;
	   fi&lt;br /&gt;
	done&lt;br /&gt;
&lt;br /&gt;
	tar -czvf $BACKUPDIR/var_libvirt.tar.gz /var/lib/libvirt&lt;br /&gt;
  	tar -czvf $BACKUPDIR/etc_libvirt.tar.gz /etc/libvirt&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
References: 	http://fedoraproject.org/wiki/Features/Virt_Live_Snapshots&lt;br /&gt;
		http://kashyapc.com/2012/09/14/externaland-live-snapshots-with-libvirt/&lt;br /&gt;
		http://serverfault.com/questions/567234/how-to-replace-qemu-binary-with-newer-version-for-libvirt-live-snapshots&lt;br /&gt;
		http://linux.die.net/man/1/virsh&lt;br /&gt;
		http://www.bashrc.in/2014/01/snapshot-of-kvm-vm-rhel-6.html&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User_talk:Zebarjadi&amp;diff=8058</id>
		<title>User talk:Zebarjadi</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User_talk:Zebarjadi&amp;diff=8058"/>
		<updated>2014-09-22T22:20:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: Welcome!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Welcome to &#039;&#039;DISI&#039;&#039;!&#039;&#039;&#039;&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:Therese|Therese]] ([[User talk:Therese|talk]]) 15:20, 22 September 2014 (PDT)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User:Zebarjadi&amp;diff=8057</id>
		<title>User:Zebarjadi</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User:Zebarjadi&amp;diff=8057"/>
		<updated>2014-09-22T22:20:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: Creating user page for new user.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Staff Research Associate I&lt;br /&gt;
&lt;br /&gt;
Laboratory of Brian K. Shoichet&lt;br /&gt;
&lt;br /&gt;
BS, University of California, Davis Biology: Neurobiology, Physiology, and Behavior&lt;br /&gt;
MS, San Francisco State University Biology: Cell and Molecular Biology&lt;br /&gt;
&lt;br /&gt;
BS, University of California, Davis Biology: Neurobiology, Physiology, and Behavior&lt;br /&gt;
MS, San Francisco State University Biology: Cell and Molecular Biology&lt;br /&gt;
&lt;br /&gt;
BS, University of California, Davis Biology: Neurobiology, Physiology, and Behavior&lt;br /&gt;
MS, San Francisco State University Biology: Cell and Molecular Biology&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8031</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8031"/>
		<updated>2014-09-09T19:55:12Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
  Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
  md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
  A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
  Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
  User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
  SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
  Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
  mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Check if this is correct or not. &amp;lt;br/&amp;gt;&lt;br /&gt;
  If any of the lines is incorrect, fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
    [...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
    title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
    initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
    title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
    initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy the partitions from one disk to the other:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the new disk to the raid array:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sanity check:&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;      &lt;br /&gt;
  md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  resync=DELAYED   &amp;lt;br/&amp;gt;     &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8030</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8030"/>
		<updated>2014-09-09T19:54:35Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
  Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
  md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
  A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
  Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
  User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
  SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
  Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
  mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Check if this is correct or not. &amp;lt;br/&amp;gt;&lt;br /&gt;
  If any of the lines is incorrect, fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
    [...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
    title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
    initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
    title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
    kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
    initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy the partitions from one disk to the other:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add the new disk to the raid array:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sanity check:&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;      &lt;br /&gt;
  md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  resync=DELAYED   &amp;lt;br/&amp;gt;     &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8029</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8029"/>
		<updated>2014-09-09T19:51:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
  Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
  md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
  A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
  Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
  User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
  === START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
  SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
  Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
  mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Check if this is correct or not. &amp;lt;br/&amp;gt;&lt;br /&gt;
  If any of the lines is incorrect, fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  This device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
  (hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
  Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
    [...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
    title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
[&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
resync=DELAYED   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8028</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8028"/>
		<updated>2014-09-09T19:47:34Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
  Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
  md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
  md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
  139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
  unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
  A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
  smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  === START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
  Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
  Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
  User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
  ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
  Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
  SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  === START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
  SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
  Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
  mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  [root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
  mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Check if this is correct or not. &amp;lt;br/&amp;gt;&lt;br /&gt;
If any of the lines is incorrect, fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
[&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
resync=DELAYED   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8027</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8027"/>
		<updated>2014-09-09T19:42:49Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Check if this is correct or not. &amp;lt;br/&amp;gt;&lt;br /&gt;
If any of the lines is incorrect, fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
[&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
resync=DELAYED   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8026</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8026"/>
		<updated>2014-09-09T19:41:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,   &amp;lt;br/&amp;gt;&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.   &amp;lt;br/&amp;gt;&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda2  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: added /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check   &amp;lt;br/&amp;gt;&lt;br /&gt;
Personalities : [raid1] [linear]    &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/2] [UU]   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
[&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]   &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_]   &amp;lt;br/&amp;gt;&lt;br /&gt;
resync=DELAYED   &amp;lt;br/&amp;gt;&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)   &amp;lt;br/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8025</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8025"/>
		<updated>2014-09-09T19:25:29Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
Installation finished. No error reported.   &amp;lt;br/&amp;gt;&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,   &amp;lt;br/&amp;gt;&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd0)     /dev/sda   &amp;lt;br/&amp;gt;&lt;br /&gt;
(hd1)     /dev/sdb   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0  &amp;lt;br/&amp;gt;&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas.   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
Should look like this:  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[...]   &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd1,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
title CentOS (2.6.18-128.el5)  &amp;lt;br/&amp;gt;&lt;br /&gt;
root (hd0,0)  &amp;lt;br/&amp;gt;&lt;br /&gt;
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/  &amp;lt;br/&amp;gt;&lt;br /&gt;
initrd /initrd-2.6.18-128.el5.img  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8024</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8024"/>
		<updated>2014-09-09T19:22:03Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda   &amp;lt;br/&amp;gt;              &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id   &amp;lt;br/&amp;gt;&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb  &amp;lt;br/&amp;gt;&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)   &amp;lt;br/&amp;gt;&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===    &amp;lt;br/&amp;gt;&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10    &amp;lt;br/&amp;gt;&lt;br /&gt;
Device Model:     ST3160815AS    &amp;lt;br/&amp;gt;&lt;br /&gt;
Serial Number:    9RA6DZP8     &amp;lt;br/&amp;gt;&lt;br /&gt;
Firmware Version: 4.AAB    &amp;lt;br/&amp;gt;&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]   &amp;lt;br/&amp;gt;&lt;br /&gt;
Sector Size:      512 bytes logical/physical   &amp;lt;br/&amp;gt;&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Version is:   7   &amp;lt;br/&amp;gt;&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated   &amp;lt;br/&amp;gt;&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT  &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Available - device has SMART capability.   &amp;lt;br/&amp;gt;&lt;br /&gt;
SMART support is: Enabled   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===   &amp;lt;br/&amp;gt; &lt;br /&gt;
SMART overall-health self-assessment test result: PASSED   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is a lot more that gets printed, but I cut it out.  &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has clearly failed.   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here are the steps:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it:   &amp;lt;br/&amp;gt; &lt;br /&gt;
Serial Number:    9RA6DZP8   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:   &amp;lt;br/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2   &amp;lt;br/&amp;gt; &lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda1   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda2   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
mdadm: hot removed /dev/sda3   &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8023</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8023"/>
		<updated>2014-09-09T19:17:09Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8022</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8022"/>
		<updated>2014-09-09T19:16:03Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
      128384 blocks [2/1] [U_]  &amp;lt;br/&amp;gt;&lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
      16779776 blocks [2/1] [U_] &amp;lt;br/&amp;gt;&lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F) &amp;lt;br/&amp;gt;&lt;br /&gt;
      139379840 blocks [2/1] [U_] &amp;lt;br/&amp;gt;    &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8021</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8021"/>
		<updated>2014-09-09T19:15:02Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F)&lt;br /&gt;
&lt;br /&gt;
      128384 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F)&lt;br /&gt;
&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F)&lt;br /&gt;
&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8020</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8020"/>
		<updated>2014-09-09T19:14:48Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &amp;lt;br /&amp;gt;&lt;br /&gt;
Personalities : [raid1] &amp;lt;br/&amp;gt;&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F)&lt;br /&gt;
&lt;br /&gt;
      128384 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F)&lt;br /&gt;
&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F)&lt;br /&gt;
&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8019</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8019"/>
		<updated>2014-09-09T19:13:41Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &lt;br /&gt;
&lt;br /&gt;
Personalities : [raid1] &lt;br /&gt;
&lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F)&lt;br /&gt;
&lt;br /&gt;
      128384 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F)&lt;br /&gt;
&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F)&lt;br /&gt;
&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8018</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8018"/>
		<updated>2014-09-09T19:13:09Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &lt;br /&gt;
Personalities : [raid1] &lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F)&lt;br /&gt;
      128384 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F)&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F)&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8017</id>
		<title>How to Replace a Failed Disk</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_Replace_a_Failed_Disk&amp;diff=8017"/>
		<updated>2014-09-09T19:00:06Z</updated>

		<summary type="html">&lt;p&gt;Therese: Created page with &amp;quot;Steps to fix a hard drive failure that is in a raid 1 configuration:  [root@myServer ~]# cat /proc/mdstat  Personalities : [raid1]  md0 : active raid1 sdb1[0] sda1[2](F)      ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Steps to fix a hard drive failure that is in a raid 1 configuration:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat &lt;br /&gt;
Personalities : [raid1] &lt;br /&gt;
md0 : active raid1 sdb1[0] sda1[2](F)&lt;br /&gt;
      128384 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sdb2[0] sda2[2](F)&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sdb3[0] sda3[2](F)&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To see which disk is failed:&lt;br /&gt;
&lt;br /&gt;
The following demonstrates what a failed disk looks like:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sda                  &lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
Short INQUIRY response, skip product id&lt;br /&gt;
A mandatory SMART command failed: exiting. To continue, add one or more &#039;-T permissive&#039; options.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# smartctl -a /dev/sdb&lt;br /&gt;
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-371.1.2.el5] (local build)&lt;br /&gt;
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
=== START OF INFORMATION SECTION ===&lt;br /&gt;
Model Family:     Seagate Barracuda 7200.10&lt;br /&gt;
Device Model:     ST3160815AS&lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
Firmware Version: 4.AAB&lt;br /&gt;
User Capacity:    160,041,885,696 bytes [160 GB]&lt;br /&gt;
Sector Size:      512 bytes logical/physical&lt;br /&gt;
Device is:        In smartctl database [for details use: -P show]&lt;br /&gt;
ATA Version is:   7&lt;br /&gt;
ATA Standard is:  Exact ATA specification draft version not indicated&lt;br /&gt;
Local Time is:    Mon Sep  8 15:50:48 2014 PDT&lt;br /&gt;
SMART support is: Available - device has SMART capability.&lt;br /&gt;
SMART support is: Enabled&lt;br /&gt;
&lt;br /&gt;
=== START OF READ SMART DATA SECTION ===&lt;br /&gt;
SMART overall-health self-assessment test result: PASSED&lt;br /&gt;
&lt;br /&gt;
General SMART Values:&lt;br /&gt;
Offline data collection status:  (0x82)	Offline data collection activity&lt;br /&gt;
					was completed without error.&lt;br /&gt;
					Auto Offline Data Collection: Enabled.&lt;br /&gt;
Self-test execution status:      (   0)	The previous self-test routine completed&lt;br /&gt;
					without error or no self-test has ever &lt;br /&gt;
					been run.&lt;br /&gt;
Total time to complete Offline &lt;br /&gt;
data collection: 		(  430) seconds.&lt;br /&gt;
Offline data collection&lt;br /&gt;
capabilities: 			 (0x5b) SMART execute Offline immediate.&lt;br /&gt;
					Auto Offline data collection on/off support.&lt;br /&gt;
					Suspend Offline collection upon new&lt;br /&gt;
					command.&lt;br /&gt;
					Offline surface scan supported.&lt;br /&gt;
					Self-test supported.&lt;br /&gt;
					No Conveyance Self-test supported.&lt;br /&gt;
					Selective Self-test supported.&lt;br /&gt;
SMART capabilities:            (0x0003)	Saves SMART data before entering&lt;br /&gt;
					power-saving mode.&lt;br /&gt;
					Supports SMART auto save timer.&lt;br /&gt;
Error logging capability:        (0x01)	Error logging supported.&lt;br /&gt;
					General Purpose Logging supported.&lt;br /&gt;
Short self-test routine &lt;br /&gt;
recommended polling time: 	 (   1) minutes.&lt;br /&gt;
Extended self-test routine&lt;br /&gt;
recommended polling time: 	 (  54) minutes.&lt;br /&gt;
&lt;br /&gt;
SMART Attributes Data Structure revision number: 10&lt;br /&gt;
Vendor Specific SMART Attributes with Thresholds:&lt;br /&gt;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE&lt;br /&gt;
  1 Raw_Read_Error_Rate     0x000f   100   253   006    Pre-fail  Always       -       0&lt;br /&gt;
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0&lt;br /&gt;
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       8&lt;br /&gt;
  7 Seek_Error_Rate         0x000f   084   060   030    Pre-fail  Always       -       239527837&lt;br /&gt;
  9 Power_On_Hours          0x0032   043   043   000    Old_age   Always       -       50308&lt;br /&gt;
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0&lt;br /&gt;
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       44&lt;br /&gt;
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0&lt;br /&gt;
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0&lt;br /&gt;
190 Airflow_Temperature_Cel 0x0022   075   061   045    Old_age   Always       -       25 (Min/Max 22/31)&lt;br /&gt;
194 Temperature_Celsius     0x0022   025   039   000    Old_age   Always       -       25 (0 22 0 0 0)&lt;br /&gt;
195 Hardware_ECC_Recovered  0x001a   064   057   000    Old_age   Always       -       155109699&lt;br /&gt;
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0&lt;br /&gt;
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0&lt;br /&gt;
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0&lt;br /&gt;
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0&lt;br /&gt;
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0&lt;br /&gt;
&lt;br /&gt;
SMART Error Log Version: 1&lt;br /&gt;
No Errors Logged&lt;br /&gt;
&lt;br /&gt;
SMART Self-test log structure revision number 1&lt;br /&gt;
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error&lt;br /&gt;
# 1  Extended offline    Completed without error       00%     13097         -&lt;br /&gt;
# 2  Extended offline    Completed without error       00%      4345         -&lt;br /&gt;
# 3  Short offline       Completed without error       00%         0         -&lt;br /&gt;
&lt;br /&gt;
SMART Selective self-test log data structure revision number 1&lt;br /&gt;
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS&lt;br /&gt;
    1        0        0  Not_testing&lt;br /&gt;
    2        0        0  Not_testing&lt;br /&gt;
    3        0        0  Not_testing&lt;br /&gt;
    4        0        0  Not_testing&lt;br /&gt;
    5        0        0  Not_testing&lt;br /&gt;
Selective self-test flags (0x0):&lt;br /&gt;
  After scanning selected spans, do NOT read-scan remainder of disk.&lt;br /&gt;
If Selective self-test is pending on power-up, resume after 0 minute delay.&lt;br /&gt;
&lt;br /&gt;
So /dev/sda has failed.&lt;br /&gt;
&lt;br /&gt;
Here are the steps:&lt;br /&gt;
&lt;br /&gt;
Take note of the GOOD disk serial number so I leave that one in when I replace it: &lt;br /&gt;
Serial Number:    9RA6DZP8&lt;br /&gt;
&lt;br /&gt;
Mark and remove failed disk from raid:&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --fail /dev/sda1&lt;br /&gt;
mdadm: set /dev/sda1 faulty in /dev/md0&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --fail /dev/sda2&lt;br /&gt;
mdadm: set /dev/sda2 faulty in /dev/md1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --fail /dev/sda3&lt;br /&gt;
mdadm: set /dev/sda3 faulty in /dev/md2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --remove /dev/sda1&lt;br /&gt;
mdadm: hot removed /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --remove /dev/sda2&lt;br /&gt;
mdadm: hot removed /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --remove /dev/sda3&lt;br /&gt;
mdadm: hot removed /dev/sda3&lt;br /&gt;
&lt;br /&gt;
Make sure grub is installed on the good disk and that grub.conf is updated:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# grub-install /dev/sdb&lt;br /&gt;
Installation finished. No error reported.&lt;br /&gt;
This is the contents of the device map /boot/grub/device.map.&lt;br /&gt;
Check if this is correct or not. If any of the lines is incorrect,&lt;br /&gt;
fix it and re-run the script `grub-install&#039;.&lt;br /&gt;
&lt;br /&gt;
# this device map was generated by anaconda&lt;br /&gt;
(hd0)     /dev/sda&lt;br /&gt;
(hd1)     /dev/sdb&lt;br /&gt;
&lt;br /&gt;
Take note of the which hd partition corresponds with the good disk, ie hd1 in this case.&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# vim /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Add fallback=1 right after default=0&lt;br /&gt;
Go to the bottom section where you should find some kernel stanzas. &lt;br /&gt;
Copy the first of them and paste the stanza before the first existing stanza; replace root (hd0,0) with root (hd1,0)&lt;br /&gt;
Should look like this:&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd1,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
title CentOS (2.6.18-128.el5)&lt;br /&gt;
        root (hd0,0)&lt;br /&gt;
        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/&lt;br /&gt;
        initrd /initrd-2.6.18-128.el5.img&lt;br /&gt;
&lt;br /&gt;
Save and quit&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mkinitrd /boot/initramfs-$(uname -r).img $(uname -r)&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# init 0&lt;br /&gt;
&lt;br /&gt;
Swap the bad drive with the new drive and boot the machine.&lt;br /&gt;
&lt;br /&gt;
Once it&#039;s booted:&lt;br /&gt;
&lt;br /&gt;
Check the device names with cat /proc/mdstat and/or fisk -l.&lt;br /&gt;
The newly installed drive on myServer was named /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe raid1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# modeprobe linear&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -d /dev/sdb | sfdisk --force /dev/sda&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# sfdisk -l =&amp;gt; sanity check&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md0 --add /dev/sda1&lt;br /&gt;
mdadm: added /dev/sda1&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md1 --add /dev/sda2&lt;br /&gt;
mdadm: added /dev/sda2&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# mdadm --manage /dev/md2 --add /dev/sda3&lt;br /&gt;
mdadm: added /dev/sda3&lt;br /&gt;
&lt;br /&gt;
[root@myServer ~]# cat /proc/mdstat   =&amp;gt; Sanity check&lt;br /&gt;
Personalities : [raid1] [linear] &lt;br /&gt;
md0 : active raid1 sda1[1] sdb1[0]&lt;br /&gt;
      128384 blocks [2/2] [UU]&lt;br /&gt;
      &lt;br /&gt;
md1 : active raid1 sda2[2] sdb2[0]&lt;br /&gt;
      16779776 blocks [2/1] [U_]&lt;br /&gt;
      [&amp;gt;....................]  recovery =  3.2% (548864/16779776) finish=8.8min speed=30492K/sec&lt;br /&gt;
      &lt;br /&gt;
md2 : active raid1 sda3[2] sdb3[0]&lt;br /&gt;
      139379840 blocks [2/1] [U_]&lt;br /&gt;
      	resync=DELAYED&lt;br /&gt;
      &lt;br /&gt;
unused devices: &amp;lt;none&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! :)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User_talk:Sbarelier&amp;diff=7980</id>
		<title>User talk:Sbarelier</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User_talk:Sbarelier&amp;diff=7980"/>
		<updated>2014-08-19T21:53:27Z</updated>

		<summary type="html">&lt;p&gt;Therese: Welcome!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Welcome to &#039;&#039;DISI&#039;&#039;!&#039;&#039;&#039;&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:Therese|Therese]] ([[User talk:Therese|talk]]) 14:53, 19 August 2014 (PDT)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User:Sbarelier&amp;diff=7979</id>
		<title>User:Sbarelier</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User:Sbarelier&amp;diff=7979"/>
		<updated>2014-08-19T21:53:27Z</updated>

		<summary type="html">&lt;p&gt;Therese: Creating user page for new user.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I received my PhD in 2010 from Université de Lyon in France, under the direction of Isabelle Krimm. I worked on fragment-based drug design, using NMR to investigate the specificity of fragment-protein interactions.&lt;br /&gt;
I am now a postdoctoral fellow Brian Shoichet laboratory at UCSF, where I work on fragment screening, docking and chemoinformatics.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7968</id>
		<title>How to create a vpn/ssh tunnel</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7968"/>
		<updated>2014-08-04T22:19:54Z</updated>

		<summary type="html">&lt;p&gt;Therese: /* FOR LINUX (COMMAND LINE) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= FOR MAC OS =&lt;br /&gt;
For command line options see the Linux section below, otherwise:&lt;br /&gt;
&lt;br /&gt;
Go to the app store and search for “ssh tunnel manager”&lt;br /&gt;
&lt;br /&gt;
Download this free app.&lt;br /&gt;
&lt;br /&gt;
Click the “Show in menu bar” button on the upper lefthand corner.&lt;br /&gt;
&lt;br /&gt;
Open it and then click the little ‘+’ sign on the bottom part of the white box.&lt;br /&gt;
&lt;br /&gt;
Enter the following information:&lt;br /&gt;
&lt;br /&gt;
For the Name field, name it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Login: your_user_name&lt;br /&gt;
&lt;br /&gt;
Host: portal.uoft.bkslab.org&lt;br /&gt;
&lt;br /&gt;
Port: 62&lt;br /&gt;
&lt;br /&gt;
Then click on the Options button in the bottom righthand corner.&lt;br /&gt;
&lt;br /&gt;
Make sure “Handle authentication” is checked and check the “Enable SOCKS4 proxy”.&lt;br /&gt;
&lt;br /&gt;
Make sure the port is 1080 (or something above port 1024).&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this (except with port 62 rather than 22):&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:tunnelMac.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then close the SSH Tunnel Manager.&lt;br /&gt;
&lt;br /&gt;
Go to System Preferences -&amp;gt; Network&lt;br /&gt;
&lt;br /&gt;
Click on the connection you are connected to (ie Airport, Ethernet, etc).&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced in the bottom right corner.&lt;br /&gt;
&lt;br /&gt;
Then click on Proxies up in the top right of the box.&lt;br /&gt;
&lt;br /&gt;
Then check SOCKS Proxy&lt;br /&gt;
&lt;br /&gt;
Then under “SOCKS PROXY SERVER” enter localhost and to the right 1080 (or whatever port you decided to use previously).  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1080.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
Then go to the ssh Tunnel Manger and click the “play”button on the right hand side:&lt;br /&gt;
&lt;br /&gt;
It should say connected and possibly prompt you for your password (the one associated with your ssh key).&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)  &lt;br /&gt;
&lt;br /&gt;
Your computer will now act as if you were connected to the internet in the lab.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you’re done with the vpn session click on the ssh Tunnel Manager and click the “stop” button.&lt;br /&gt;
&lt;br /&gt;
Then go to System Preferences -&amp;gt; Network -&amp;gt; Advanced -&amp;gt; Proxies&lt;br /&gt;
&lt;br /&gt;
and uncheck the SOCKS Proxy, click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
That’s it!&lt;br /&gt;
&lt;br /&gt;
= FOR LINUX (COMMAND LINE) =&lt;br /&gt;
&lt;br /&gt;
I am going to illustrate how to create a ssh tunnel using a couple examples.&lt;br /&gt;
&lt;br /&gt;
Pretend &#039;&#039;you want to create a ssh tunnel from your laptop to sgehead through the portal.&#039;&#039;&lt;br /&gt;
  &lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 1080 localhost&lt;br /&gt;
&lt;br /&gt;
Then when you log in type hostname and you will see that you are logged into sgehead!&lt;br /&gt;
&lt;br /&gt;
Here&#039;s another example, say &#039;&#039;you want to scp files directly from your laptop to your home directory on sgehead.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 scp -P 1080 file_you_want_to_copy localhost:~&lt;br /&gt;
&lt;br /&gt;
= FOR WINDOWS OS =&lt;br /&gt;
&lt;br /&gt;
Open putty.exe and select the session that you want to use as a ssh tunnel (ie portal.uoft.bkslab.org).&lt;br /&gt;
&lt;br /&gt;
Then click on Connection -&amp;gt; SSH -&amp;gt; tunnels&lt;br /&gt;
&lt;br /&gt;
In Source Port enter 1080 (or any port above 1024).&lt;br /&gt;
&lt;br /&gt;
Then click the Dynamic button and then click Add.  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then go back to Session and click Save.&lt;br /&gt;
&lt;br /&gt;
Then download the &amp;quot;standard&amp;quot; version of FoxyProxy here:  http://getfoxyproxy.org/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you’ve downloaded it there should be a little fox picture next to the url bar (upper right hand corner of web browser).  Click on that little picture and select Options from the dropdown list.&lt;br /&gt;
&lt;br /&gt;
You should see this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click on Add New Proxy&lt;br /&gt;
&lt;br /&gt;
Then click on the General tab.&lt;br /&gt;
&lt;br /&gt;
Enter a proxy name and then select the Proxy Details tab.&lt;br /&gt;
&lt;br /&gt;
Enter “localhost” in “Host or IP Address” and 1080 for “Port” (or whatever port number you entered in putty).&lt;br /&gt;
&lt;br /&gt;
Click the “SOCKS proxy?” Button and make sure the “SOCKS v5” button is also clicked.&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click Save.&lt;br /&gt;
&lt;br /&gt;
Then click on the fox again on the upper right hand corner and click on “Us proxy whatever_you_named_it Proxy for all URLs”&lt;br /&gt;
&lt;br /&gt;
Then click on putty and open your session.  A terminal will pop up and ask for your passphrase.  Enter your passphrase (for your ssh key).  That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)   &lt;br /&gt;
&lt;br /&gt;
This session will remain open as long as your ssh putty session is open.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To scp files in Windows&#039;&#039;&#039; through this ssh tunnel, download WinSCP here: http://winscp.net/download/winscp551setup.exe&lt;br /&gt;
&lt;br /&gt;
Once it finishes downloading, run it and go through all the prompts.  You can (if you want) to import all your existing sessions from putty, but it’s really not necessary.  &lt;br /&gt;
&lt;br /&gt;
Once it’s done, open it.  &lt;br /&gt;
&lt;br /&gt;
Click on “New Site”.&lt;br /&gt;
&lt;br /&gt;
Then, in the File protocol drop down menu, select SCP.&lt;br /&gt;
&lt;br /&gt;
In Host name, put the host name or IP address of the machine you want to transfer files to.&lt;br /&gt;
&lt;br /&gt;
Keep the port number as 22.  It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced -&amp;gt; Connection -&amp;gt; Proxy&lt;br /&gt;
&lt;br /&gt;
Click on the “Proxy type” drop down menu and select SOCKS5.&lt;br /&gt;
&lt;br /&gt;
For “Proxy host name” write localhost.  Make the port number 1080 (or whatever port you chose to use in putty).&lt;br /&gt;
&lt;br /&gt;
it should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then Save.&lt;br /&gt;
&lt;br /&gt;
It will prompt you to enter a name, call it whatever makes sense to you.&lt;br /&gt;
&lt;br /&gt;
Assuming that your putty session is still open, click Login.&lt;br /&gt;
&lt;br /&gt;
It should prompt you to enter your username and password in the bottom.  &lt;br /&gt;
&lt;br /&gt;
You should then see a screen that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp3.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To transfer files from one to the other, select the file that you want to transfer and then click “Upload” to transfer files to the server and then specify which folder you want to save it to.  If you are downloading files from the server to your computer, click the file you want to download and then click “Download” and specify where you want to download it to.&lt;br /&gt;
&lt;br /&gt;
To exit, click on session -&amp;gt; disconnect&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When you are done&#039;&#039;&#039; with your vpn session, exit from the ssh putty session (type exit on the terminal screen).&lt;br /&gt;
&lt;br /&gt;
Then, on your browser, click on the little fox in the upper right hand corner and select “Disable FoxyProxy”.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User_talk:Pharma24&amp;diff=7966</id>
		<title>User talk:Pharma24</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User_talk:Pharma24&amp;diff=7966"/>
		<updated>2014-07-29T00:09:12Z</updated>

		<summary type="html">&lt;p&gt;Therese: Welcome!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Welcome to &#039;&#039;DISI&#039;&#039;!&#039;&#039;&#039;&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:Therese|Therese]] ([[User talk:Therese|talk]]) 17:09, 28 July 2014 (PDT)&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=User:Pharma24&amp;diff=7965</id>
		<title>User:Pharma24</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=User:Pharma24&amp;diff=7965"/>
		<updated>2014-07-29T00:09:12Z</updated>

		<summary type="html">&lt;p&gt;Therese: Creating user page for new user.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;My name is Mina, 24 year old.I am from Iran.I study pharmacy, Now i am working on my thesis. I am interested in molecular simulation and molecular docking. neurosciences, special Neuroeconomics is so interesting for me. my hobbies are listening to music and reading books. &lt;br /&gt;
my favorite sentence is:&amp;quot; You can win, if you want&amp;quot;.&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7950</id>
		<title>How to create a vpn/ssh tunnel</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7950"/>
		<updated>2014-07-18T00:57:26Z</updated>

		<summary type="html">&lt;p&gt;Therese: /* FOR MAC OS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= FOR MAC OS =&lt;br /&gt;
For command line options see the Linux section below, otherwise:&lt;br /&gt;
&lt;br /&gt;
Go to the app store and search for “ssh tunnel manager”&lt;br /&gt;
&lt;br /&gt;
Download this free app.&lt;br /&gt;
&lt;br /&gt;
Click the “Show in menu bar” button on the upper lefthand corner.&lt;br /&gt;
&lt;br /&gt;
Open it and then click the little ‘+’ sign on the bottom part of the white box.&lt;br /&gt;
&lt;br /&gt;
Enter the following information:&lt;br /&gt;
&lt;br /&gt;
For the Name field, name it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Login: your_user_name&lt;br /&gt;
&lt;br /&gt;
Host: portal.uoft.bkslab.org&lt;br /&gt;
&lt;br /&gt;
Port: 62&lt;br /&gt;
&lt;br /&gt;
Then click on the Options button in the bottom righthand corner.&lt;br /&gt;
&lt;br /&gt;
Make sure “Handle authentication” is checked and check the “Enable SOCKS4 proxy”.&lt;br /&gt;
&lt;br /&gt;
Make sure the port is 1080 (or something above port 1024).&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this (except with port 62 rather than 22):&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:tunnelMac.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then close the SSH Tunnel Manager.&lt;br /&gt;
&lt;br /&gt;
Go to System Preferences -&amp;gt; Network&lt;br /&gt;
&lt;br /&gt;
Click on the connection you are connected to (ie Airport, Ethernet, etc).&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced in the bottom right corner.&lt;br /&gt;
&lt;br /&gt;
Then click on Proxies up in the top right of the box.&lt;br /&gt;
&lt;br /&gt;
Then check SOCKS Proxy&lt;br /&gt;
&lt;br /&gt;
Then under “SOCKS PROXY SERVER” enter localhost and to the right 1080 (or whatever port you decided to use previously).  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1080.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
Then go to the ssh Tunnel Manger and click the “play”button on the right hand side:&lt;br /&gt;
&lt;br /&gt;
It should say connected and possibly prompt you for your password (the one associated with your ssh key).&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)  &lt;br /&gt;
&lt;br /&gt;
Your computer will now act as if you were connected to the internet in the lab.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you’re done with the vpn session click on the ssh Tunnel Manager and click the “stop” button.&lt;br /&gt;
&lt;br /&gt;
Then go to System Preferences -&amp;gt; Network -&amp;gt; Advanced -&amp;gt; Proxies&lt;br /&gt;
&lt;br /&gt;
and uncheck the SOCKS Proxy, click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
That’s it!&lt;br /&gt;
&lt;br /&gt;
= FOR LINUX (COMMAND LINE) =&lt;br /&gt;
&lt;br /&gt;
I am going to illustrate how to create a ssh tunnel using a couple examples.&lt;br /&gt;
&lt;br /&gt;
Pretend &#039;&#039;you want to create a ssh tunnel from your laptop to sgehead through the portal.&#039;&#039;&lt;br /&gt;
  &lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 62 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 1080 localhost&lt;br /&gt;
&lt;br /&gt;
Then when you log in type hostname and you will see that you are logged into sgehead!&lt;br /&gt;
&lt;br /&gt;
Here&#039;s another example, say &#039;&#039;you want to scp files directly from your laptop to your home directory on sgehead.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 scp -P 1080 file_you_want_to_copy localhost:~&lt;br /&gt;
&lt;br /&gt;
= FOR WINDOWS OS =&lt;br /&gt;
&lt;br /&gt;
Open putty.exe and select the session that you want to use as a ssh tunnel (ie portal.uoft.bkslab.org).&lt;br /&gt;
&lt;br /&gt;
Then click on Connection -&amp;gt; SSH -&amp;gt; tunnels&lt;br /&gt;
&lt;br /&gt;
In Source Port enter 1080 (or any port above 1024).&lt;br /&gt;
&lt;br /&gt;
Then click the Dynamic button and then click Add.  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then go back to Session and click Save.&lt;br /&gt;
&lt;br /&gt;
Then download the &amp;quot;standard&amp;quot; version of FoxyProxy here:  http://getfoxyproxy.org/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you’ve downloaded it there should be a little fox picture next to the url bar (upper right hand corner of web browser).  Click on that little picture and select Options from the dropdown list.&lt;br /&gt;
&lt;br /&gt;
You should see this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click on Add New Proxy&lt;br /&gt;
&lt;br /&gt;
Then click on the General tab.&lt;br /&gt;
&lt;br /&gt;
Enter a proxy name and then select the Proxy Details tab.&lt;br /&gt;
&lt;br /&gt;
Enter “localhost” in “Host or IP Address” and 1080 for “Port” (or whatever port number you entered in putty).&lt;br /&gt;
&lt;br /&gt;
Click the “SOCKS proxy?” Button and make sure the “SOCKS v5” button is also clicked.&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click Save.&lt;br /&gt;
&lt;br /&gt;
Then click on the fox again on the upper right hand corner and click on “Us proxy whatever_you_named_it Proxy for all URLs”&lt;br /&gt;
&lt;br /&gt;
Then click on putty and open your session.  A terminal will pop up and ask for your passphrase.  Enter your passphrase (for your ssh key).  That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)   &lt;br /&gt;
&lt;br /&gt;
This session will remain open as long as your ssh putty session is open.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To scp files in Windows&#039;&#039;&#039; through this ssh tunnel, download WinSCP here: http://winscp.net/download/winscp551setup.exe&lt;br /&gt;
&lt;br /&gt;
Once it finishes downloading, run it and go through all the prompts.  You can (if you want) to import all your existing sessions from putty, but it’s really not necessary.  &lt;br /&gt;
&lt;br /&gt;
Once it’s done, open it.  &lt;br /&gt;
&lt;br /&gt;
Click on “New Site”.&lt;br /&gt;
&lt;br /&gt;
Then, in the File protocol drop down menu, select SCP.&lt;br /&gt;
&lt;br /&gt;
In Host name, put the host name or IP address of the machine you want to transfer files to.&lt;br /&gt;
&lt;br /&gt;
Keep the port number as 22.  It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced -&amp;gt; Connection -&amp;gt; Proxy&lt;br /&gt;
&lt;br /&gt;
Click on the “Proxy type” drop down menu and select SOCKS5.&lt;br /&gt;
&lt;br /&gt;
For “Proxy host name” write localhost.  Make the port number 1080 (or whatever port you chose to use in putty).&lt;br /&gt;
&lt;br /&gt;
it should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then Save.&lt;br /&gt;
&lt;br /&gt;
It will prompt you to enter a name, call it whatever makes sense to you.&lt;br /&gt;
&lt;br /&gt;
Assuming that your putty session is still open, click Login.&lt;br /&gt;
&lt;br /&gt;
It should prompt you to enter your username and password in the bottom.  &lt;br /&gt;
&lt;br /&gt;
You should then see a screen that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp3.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To transfer files from one to the other, select the file that you want to transfer and then click “Upload” to transfer files to the server and then specify which folder you want to save it to.  If you are downloading files from the server to your computer, click the file you want to download and then click “Download” and specify where you want to download it to.&lt;br /&gt;
&lt;br /&gt;
To exit, click on session -&amp;gt; disconnect&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When you are done&#039;&#039;&#039; with your vpn session, exit from the ssh putty session (type exit on the terminal screen).&lt;br /&gt;
&lt;br /&gt;
Then, on your browser, click on the little fox in the upper right hand corner and select “Disable FoxyProxy”.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7949</id>
		<title>How to create a vpn/ssh tunnel</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7949"/>
		<updated>2014-07-18T00:56:40Z</updated>

		<summary type="html">&lt;p&gt;Therese: /* FOR LINUX (COMMAND LINE) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= FOR MAC OS =&lt;br /&gt;
Go to the app store and search for “ssh tunnel manager”&lt;br /&gt;
&lt;br /&gt;
Download this free app.&lt;br /&gt;
&lt;br /&gt;
Click the “Show in menu bar” button on the upper lefthand corner.&lt;br /&gt;
&lt;br /&gt;
Open it and then click the little ‘+’ sign on the bottom part of the white box.&lt;br /&gt;
&lt;br /&gt;
Enter the following information:&lt;br /&gt;
&lt;br /&gt;
For the Name field, name it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Login: your_user_name&lt;br /&gt;
&lt;br /&gt;
Host: portal.uoft.bkslab.org&lt;br /&gt;
&lt;br /&gt;
Port: 62&lt;br /&gt;
&lt;br /&gt;
Then click on the Options button in the bottom righthand corner.&lt;br /&gt;
&lt;br /&gt;
Make sure “Handle authentication” is checked and check the “Enable SOCKS4 proxy”.&lt;br /&gt;
&lt;br /&gt;
Make sure the port is 1080 (or something above port 1024).&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this (except with port 62 rather than 22):&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:tunnelMac.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then close the SSH Tunnel Manager.&lt;br /&gt;
&lt;br /&gt;
Go to System Preferences -&amp;gt; Network&lt;br /&gt;
&lt;br /&gt;
Click on the connection you are connected to (ie Airport, Ethernet, etc).&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced in the bottom right corner.&lt;br /&gt;
&lt;br /&gt;
Then click on Proxies up in the top right of the box.&lt;br /&gt;
&lt;br /&gt;
Then check SOCKS Proxy&lt;br /&gt;
&lt;br /&gt;
Then under “SOCKS PROXY SERVER” enter localhost and to the right 1080 (or whatever port you decided to use previously).  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1080.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
Then go to the ssh Tunnel Manger and click the “play”button on the right hand side:&lt;br /&gt;
&lt;br /&gt;
It should say connected and possibly prompt you for your password (the one associated with your ssh key).&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)  &lt;br /&gt;
&lt;br /&gt;
Your computer will now act as if you were connected to the internet in the lab.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you’re done with the vpn session click on the ssh Tunnel Manager and click the “stop” button.&lt;br /&gt;
&lt;br /&gt;
Then go to System Preferences -&amp;gt; Network -&amp;gt; Advanced -&amp;gt; Proxies&lt;br /&gt;
&lt;br /&gt;
and uncheck the SOCKS Proxy, click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= FOR LINUX (COMMAND LINE) =&lt;br /&gt;
&lt;br /&gt;
I am going to illustrate how to create a ssh tunnel using a couple examples.&lt;br /&gt;
&lt;br /&gt;
Pretend &#039;&#039;you want to create a ssh tunnel from your laptop to sgehead through the portal.&#039;&#039;&lt;br /&gt;
  &lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 62 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 1080 localhost&lt;br /&gt;
&lt;br /&gt;
Then when you log in type hostname and you will see that you are logged into sgehead!&lt;br /&gt;
&lt;br /&gt;
Here&#039;s another example, say &#039;&#039;you want to scp files directly from your laptop to your home directory on sgehead.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 scp -P 1080 file_you_want_to_copy localhost:~&lt;br /&gt;
&lt;br /&gt;
= FOR WINDOWS OS =&lt;br /&gt;
&lt;br /&gt;
Open putty.exe and select the session that you want to use as a ssh tunnel (ie portal.uoft.bkslab.org).&lt;br /&gt;
&lt;br /&gt;
Then click on Connection -&amp;gt; SSH -&amp;gt; tunnels&lt;br /&gt;
&lt;br /&gt;
In Source Port enter 1080 (or any port above 1024).&lt;br /&gt;
&lt;br /&gt;
Then click the Dynamic button and then click Add.  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then go back to Session and click Save.&lt;br /&gt;
&lt;br /&gt;
Then download the &amp;quot;standard&amp;quot; version of FoxyProxy here:  http://getfoxyproxy.org/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you’ve downloaded it there should be a little fox picture next to the url bar (upper right hand corner of web browser).  Click on that little picture and select Options from the dropdown list.&lt;br /&gt;
&lt;br /&gt;
You should see this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click on Add New Proxy&lt;br /&gt;
&lt;br /&gt;
Then click on the General tab.&lt;br /&gt;
&lt;br /&gt;
Enter a proxy name and then select the Proxy Details tab.&lt;br /&gt;
&lt;br /&gt;
Enter “localhost” in “Host or IP Address” and 1080 for “Port” (or whatever port number you entered in putty).&lt;br /&gt;
&lt;br /&gt;
Click the “SOCKS proxy?” Button and make sure the “SOCKS v5” button is also clicked.&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click Save.&lt;br /&gt;
&lt;br /&gt;
Then click on the fox again on the upper right hand corner and click on “Us proxy whatever_you_named_it Proxy for all URLs”&lt;br /&gt;
&lt;br /&gt;
Then click on putty and open your session.  A terminal will pop up and ask for your passphrase.  Enter your passphrase (for your ssh key).  That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)   &lt;br /&gt;
&lt;br /&gt;
This session will remain open as long as your ssh putty session is open.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To scp files in Windows&#039;&#039;&#039; through this ssh tunnel, download WinSCP here: http://winscp.net/download/winscp551setup.exe&lt;br /&gt;
&lt;br /&gt;
Once it finishes downloading, run it and go through all the prompts.  You can (if you want) to import all your existing sessions from putty, but it’s really not necessary.  &lt;br /&gt;
&lt;br /&gt;
Once it’s done, open it.  &lt;br /&gt;
&lt;br /&gt;
Click on “New Site”.&lt;br /&gt;
&lt;br /&gt;
Then, in the File protocol drop down menu, select SCP.&lt;br /&gt;
&lt;br /&gt;
In Host name, put the host name or IP address of the machine you want to transfer files to.&lt;br /&gt;
&lt;br /&gt;
Keep the port number as 22.  It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced -&amp;gt; Connection -&amp;gt; Proxy&lt;br /&gt;
&lt;br /&gt;
Click on the “Proxy type” drop down menu and select SOCKS5.&lt;br /&gt;
&lt;br /&gt;
For “Proxy host name” write localhost.  Make the port number 1080 (or whatever port you chose to use in putty).&lt;br /&gt;
&lt;br /&gt;
it should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then Save.&lt;br /&gt;
&lt;br /&gt;
It will prompt you to enter a name, call it whatever makes sense to you.&lt;br /&gt;
&lt;br /&gt;
Assuming that your putty session is still open, click Login.&lt;br /&gt;
&lt;br /&gt;
It should prompt you to enter your username and password in the bottom.  &lt;br /&gt;
&lt;br /&gt;
You should then see a screen that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp3.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To transfer files from one to the other, select the file that you want to transfer and then click “Upload” to transfer files to the server and then specify which folder you want to save it to.  If you are downloading files from the server to your computer, click the file you want to download and then click “Download” and specify where you want to download it to.&lt;br /&gt;
&lt;br /&gt;
To exit, click on session -&amp;gt; disconnect&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When you are done&#039;&#039;&#039; with your vpn session, exit from the ssh putty session (type exit on the terminal screen).&lt;br /&gt;
&lt;br /&gt;
Then, on your browser, click on the little fox in the upper right hand corner and select “Disable FoxyProxy”.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7948</id>
		<title>How to create a vpn/ssh tunnel</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7948"/>
		<updated>2014-07-18T00:55:44Z</updated>

		<summary type="html">&lt;p&gt;Therese: /* FOR LINUX (COMMAND LINE) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= FOR MAC OS =&lt;br /&gt;
Go to the app store and search for “ssh tunnel manager”&lt;br /&gt;
&lt;br /&gt;
Download this free app.&lt;br /&gt;
&lt;br /&gt;
Click the “Show in menu bar” button on the upper lefthand corner.&lt;br /&gt;
&lt;br /&gt;
Open it and then click the little ‘+’ sign on the bottom part of the white box.&lt;br /&gt;
&lt;br /&gt;
Enter the following information:&lt;br /&gt;
&lt;br /&gt;
For the Name field, name it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Login: your_user_name&lt;br /&gt;
&lt;br /&gt;
Host: portal.uoft.bkslab.org&lt;br /&gt;
&lt;br /&gt;
Port: 62&lt;br /&gt;
&lt;br /&gt;
Then click on the Options button in the bottom righthand corner.&lt;br /&gt;
&lt;br /&gt;
Make sure “Handle authentication” is checked and check the “Enable SOCKS4 proxy”.&lt;br /&gt;
&lt;br /&gt;
Make sure the port is 1080 (or something above port 1024).&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this (except with port 62 rather than 22):&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:tunnelMac.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then close the SSH Tunnel Manager.&lt;br /&gt;
&lt;br /&gt;
Go to System Preferences -&amp;gt; Network&lt;br /&gt;
&lt;br /&gt;
Click on the connection you are connected to (ie Airport, Ethernet, etc).&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced in the bottom right corner.&lt;br /&gt;
&lt;br /&gt;
Then click on Proxies up in the top right of the box.&lt;br /&gt;
&lt;br /&gt;
Then check SOCKS Proxy&lt;br /&gt;
&lt;br /&gt;
Then under “SOCKS PROXY SERVER” enter localhost and to the right 1080 (or whatever port you decided to use previously).  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1080.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
Then go to the ssh Tunnel Manger and click the “play”button on the right hand side:&lt;br /&gt;
&lt;br /&gt;
It should say connected and possibly prompt you for your password (the one associated with your ssh key).&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)  &lt;br /&gt;
&lt;br /&gt;
Your computer will now act as if you were connected to the internet in the lab.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you’re done with the vpn session click on the ssh Tunnel Manager and click the “stop” button.&lt;br /&gt;
&lt;br /&gt;
Then go to System Preferences -&amp;gt; Network -&amp;gt; Advanced -&amp;gt; Proxies&lt;br /&gt;
&lt;br /&gt;
and uncheck the SOCKS Proxy, click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= FOR LINUX (COMMAND LINE) =&lt;br /&gt;
&lt;br /&gt;
I am going to illustrate how to create a ssh tunnel using a couple examples.&lt;br /&gt;
&lt;br /&gt;
Pretend [you want to create a ssh tunnel from your laptop to sgehead through the portal.]&lt;br /&gt;
  &lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 62 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 1080 localhost&lt;br /&gt;
&lt;br /&gt;
Then when you log in type hostname and you will see that you are logged into sgehead!&lt;br /&gt;
&lt;br /&gt;
Here&#039;s another example, say [[you want to scp files directly from your laptop to your home directory on sgehead.uoft.bkslab.org.]]&lt;br /&gt;
&lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 scp -P 1080 file_you_want_to_copy localhost:~&lt;br /&gt;
&lt;br /&gt;
= FOR WINDOWS OS =&lt;br /&gt;
&lt;br /&gt;
Open putty.exe and select the session that you want to use as a ssh tunnel (ie portal.uoft.bkslab.org).&lt;br /&gt;
&lt;br /&gt;
Then click on Connection -&amp;gt; SSH -&amp;gt; tunnels&lt;br /&gt;
&lt;br /&gt;
In Source Port enter 1080 (or any port above 1024).&lt;br /&gt;
&lt;br /&gt;
Then click the Dynamic button and then click Add.  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then go back to Session and click Save.&lt;br /&gt;
&lt;br /&gt;
Then download the &amp;quot;standard&amp;quot; version of FoxyProxy here:  http://getfoxyproxy.org/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you’ve downloaded it there should be a little fox picture next to the url bar (upper right hand corner of web browser).  Click on that little picture and select Options from the dropdown list.&lt;br /&gt;
&lt;br /&gt;
You should see this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click on Add New Proxy&lt;br /&gt;
&lt;br /&gt;
Then click on the General tab.&lt;br /&gt;
&lt;br /&gt;
Enter a proxy name and then select the Proxy Details tab.&lt;br /&gt;
&lt;br /&gt;
Enter “localhost” in “Host or IP Address” and 1080 for “Port” (or whatever port number you entered in putty).&lt;br /&gt;
&lt;br /&gt;
Click the “SOCKS proxy?” Button and make sure the “SOCKS v5” button is also clicked.&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click Save.&lt;br /&gt;
&lt;br /&gt;
Then click on the fox again on the upper right hand corner and click on “Us proxy whatever_you_named_it Proxy for all URLs”&lt;br /&gt;
&lt;br /&gt;
Then click on putty and open your session.  A terminal will pop up and ask for your passphrase.  Enter your passphrase (for your ssh key).  That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)   &lt;br /&gt;
&lt;br /&gt;
This session will remain open as long as your ssh putty session is open.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To scp files in Windows&#039;&#039;&#039; through this ssh tunnel, download WinSCP here: http://winscp.net/download/winscp551setup.exe&lt;br /&gt;
&lt;br /&gt;
Once it finishes downloading, run it and go through all the prompts.  You can (if you want) to import all your existing sessions from putty, but it’s really not necessary.  &lt;br /&gt;
&lt;br /&gt;
Once it’s done, open it.  &lt;br /&gt;
&lt;br /&gt;
Click on “New Site”.&lt;br /&gt;
&lt;br /&gt;
Then, in the File protocol drop down menu, select SCP.&lt;br /&gt;
&lt;br /&gt;
In Host name, put the host name or IP address of the machine you want to transfer files to.&lt;br /&gt;
&lt;br /&gt;
Keep the port number as 22.  It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced -&amp;gt; Connection -&amp;gt; Proxy&lt;br /&gt;
&lt;br /&gt;
Click on the “Proxy type” drop down menu and select SOCKS5.&lt;br /&gt;
&lt;br /&gt;
For “Proxy host name” write localhost.  Make the port number 1080 (or whatever port you chose to use in putty).&lt;br /&gt;
&lt;br /&gt;
it should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then Save.&lt;br /&gt;
&lt;br /&gt;
It will prompt you to enter a name, call it whatever makes sense to you.&lt;br /&gt;
&lt;br /&gt;
Assuming that your putty session is still open, click Login.&lt;br /&gt;
&lt;br /&gt;
It should prompt you to enter your username and password in the bottom.  &lt;br /&gt;
&lt;br /&gt;
You should then see a screen that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp3.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To transfer files from one to the other, select the file that you want to transfer and then click “Upload” to transfer files to the server and then specify which folder you want to save it to.  If you are downloading files from the server to your computer, click the file you want to download and then click “Download” and specify where you want to download it to.&lt;br /&gt;
&lt;br /&gt;
To exit, click on session -&amp;gt; disconnect&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When you are done&#039;&#039;&#039; with your vpn session, exit from the ssh putty session (type exit on the terminal screen).&lt;br /&gt;
&lt;br /&gt;
Then, on your browser, click on the little fox in the upper right hand corner and select “Disable FoxyProxy”.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7947</id>
		<title>How to create a vpn/ssh tunnel</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_create_a_vpn/ssh_tunnel&amp;diff=7947"/>
		<updated>2014-07-18T00:54:19Z</updated>

		<summary type="html">&lt;p&gt;Therese: /* FOR LINUX (COMMAND LINE) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= FOR MAC OS =&lt;br /&gt;
Go to the app store and search for “ssh tunnel manager”&lt;br /&gt;
&lt;br /&gt;
Download this free app.&lt;br /&gt;
&lt;br /&gt;
Click the “Show in menu bar” button on the upper lefthand corner.&lt;br /&gt;
&lt;br /&gt;
Open it and then click the little ‘+’ sign on the bottom part of the white box.&lt;br /&gt;
&lt;br /&gt;
Enter the following information:&lt;br /&gt;
&lt;br /&gt;
For the Name field, name it whatever you want.&lt;br /&gt;
&lt;br /&gt;
Login: your_user_name&lt;br /&gt;
&lt;br /&gt;
Host: portal.uoft.bkslab.org&lt;br /&gt;
&lt;br /&gt;
Port: 62&lt;br /&gt;
&lt;br /&gt;
Then click on the Options button in the bottom righthand corner.&lt;br /&gt;
&lt;br /&gt;
Make sure “Handle authentication” is checked and check the “Enable SOCKS4 proxy”.&lt;br /&gt;
&lt;br /&gt;
Make sure the port is 1080 (or something above port 1024).&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this (except with port 62 rather than 22):&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:tunnelMac.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then close the SSH Tunnel Manager.&lt;br /&gt;
&lt;br /&gt;
Go to System Preferences -&amp;gt; Network&lt;br /&gt;
&lt;br /&gt;
Click on the connection you are connected to (ie Airport, Ethernet, etc).&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced in the bottom right corner.&lt;br /&gt;
&lt;br /&gt;
Then click on Proxies up in the top right of the box.&lt;br /&gt;
&lt;br /&gt;
Then check SOCKS Proxy&lt;br /&gt;
&lt;br /&gt;
Then under “SOCKS PROXY SERVER” enter localhost and to the right 1080 (or whatever port you decided to use previously).  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1080.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
Then go to the ssh Tunnel Manger and click the “play”button on the right hand side:&lt;br /&gt;
&lt;br /&gt;
It should say connected and possibly prompt you for your password (the one associated with your ssh key).&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)  &lt;br /&gt;
&lt;br /&gt;
Your computer will now act as if you were connected to the internet in the lab.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you’re done with the vpn session click on the ssh Tunnel Manager and click the “stop” button.&lt;br /&gt;
&lt;br /&gt;
Then go to System Preferences -&amp;gt; Network -&amp;gt; Advanced -&amp;gt; Proxies&lt;br /&gt;
&lt;br /&gt;
and uncheck the SOCKS Proxy, click OK, then apply.&lt;br /&gt;
&lt;br /&gt;
That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= FOR LINUX (COMMAND LINE) =&lt;br /&gt;
&lt;br /&gt;
I am going to illustrate how to create a ssh tunnel through an example.&lt;br /&gt;
Pretend [[you want to create a ssh tunnel from your laptop to sgehead through the portal.]]&lt;br /&gt;
  &lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 62 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 1080 localhost&lt;br /&gt;
&lt;br /&gt;
Then when you log in type hostname and you will see that you are logged into sgehead!&lt;br /&gt;
&lt;br /&gt;
Here&#039;s another example, say [[you want to scp files directly from your laptop to your home directory on sgehead.uoft.bkslab.org.]]&lt;br /&gt;
&lt;br /&gt;
First open two terminals.  In one terminal type the following:&lt;br /&gt;
&lt;br /&gt;
 ssh -p 22 -L 1080:sgehead.uoft.bkslab.org:22 portal.uoft.bkslab.org -N&lt;br /&gt;
&lt;br /&gt;
In the other terminal type:&lt;br /&gt;
&lt;br /&gt;
 scp -P 1080 file_you_want_to_copy localhost:~&lt;br /&gt;
&lt;br /&gt;
= FOR WINDOWS OS =&lt;br /&gt;
&lt;br /&gt;
Open putty.exe and select the session that you want to use as a ssh tunnel (ie portal.uoft.bkslab.org).&lt;br /&gt;
&lt;br /&gt;
Then click on Connection -&amp;gt; SSH -&amp;gt; tunnels&lt;br /&gt;
&lt;br /&gt;
In Source Port enter 1080 (or any port above 1024).&lt;br /&gt;
&lt;br /&gt;
Then click the Dynamic button and then click Add.  &lt;br /&gt;
&lt;br /&gt;
It should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:proxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then go back to Session and click Save.&lt;br /&gt;
&lt;br /&gt;
Then download the &amp;quot;standard&amp;quot; version of FoxyProxy here:  http://getfoxyproxy.org/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you’ve downloaded it there should be a little fox picture next to the url bar (upper right hand corner of web browser).  Click on that little picture and select Options from the dropdown list.&lt;br /&gt;
&lt;br /&gt;
You should see this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click on Add New Proxy&lt;br /&gt;
&lt;br /&gt;
Then click on the General tab.&lt;br /&gt;
&lt;br /&gt;
Enter a proxy name and then select the Proxy Details tab.&lt;br /&gt;
&lt;br /&gt;
Enter “localhost” in “Host or IP Address” and 1080 for “Port” (or whatever port number you entered in putty).&lt;br /&gt;
&lt;br /&gt;
Click the “SOCKS proxy?” Button and make sure the “SOCKS v5” button is also clicked.&lt;br /&gt;
&lt;br /&gt;
Your screen should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:foxy2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click Save.&lt;br /&gt;
&lt;br /&gt;
Then click on the fox again on the upper right hand corner and click on “Us proxy whatever_you_named_it Proxy for all URLs”&lt;br /&gt;
&lt;br /&gt;
Then click on putty and open your session.  A terminal will pop up and ask for your passphrase.  Enter your passphrase (for your ssh key).  That’s it!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To test if your tunnel is good, go to: http://whatismyipaddress.com/&lt;br /&gt;
&lt;br /&gt;
This will tell you what ip address you have.  If it says the IP address of the remote host you&#039;re connecting to in putty, you are good to go! :)   &lt;br /&gt;
&lt;br /&gt;
This session will remain open as long as your ssh putty session is open.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;To scp files in Windows&#039;&#039;&#039; through this ssh tunnel, download WinSCP here: http://winscp.net/download/winscp551setup.exe&lt;br /&gt;
&lt;br /&gt;
Once it finishes downloading, run it and go through all the prompts.  You can (if you want) to import all your existing sessions from putty, but it’s really not necessary.  &lt;br /&gt;
&lt;br /&gt;
Once it’s done, open it.  &lt;br /&gt;
&lt;br /&gt;
Click on “New Site”.&lt;br /&gt;
&lt;br /&gt;
Then, in the File protocol drop down menu, select SCP.&lt;br /&gt;
&lt;br /&gt;
In Host name, put the host name or IP address of the machine you want to transfer files to.&lt;br /&gt;
&lt;br /&gt;
Keep the port number as 22.  It should look something like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp1.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Then click on Advanced -&amp;gt; Connection -&amp;gt; Proxy&lt;br /&gt;
&lt;br /&gt;
Click on the “Proxy type” drop down menu and select SOCKS5.&lt;br /&gt;
&lt;br /&gt;
For “Proxy host name” write localhost.  Make the port number 1080 (or whatever port you chose to use in putty).&lt;br /&gt;
&lt;br /&gt;
it should look like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Click OK, then Save.&lt;br /&gt;
&lt;br /&gt;
It will prompt you to enter a name, call it whatever makes sense to you.&lt;br /&gt;
&lt;br /&gt;
Assuming that your putty session is still open, click Login.&lt;br /&gt;
&lt;br /&gt;
It should prompt you to enter your username and password in the bottom.  &lt;br /&gt;
&lt;br /&gt;
You should then see a screen that looks like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:scp3.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To transfer files from one to the other, select the file that you want to transfer and then click “Upload” to transfer files to the server and then specify which folder you want to save it to.  If you are downloading files from the server to your computer, click the file you want to download and then click “Download” and specify where you want to download it to.&lt;br /&gt;
&lt;br /&gt;
To exit, click on session -&amp;gt; disconnect&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When you are done&#039;&#039;&#039; with your vpn session, exit from the ssh putty session (type exit on the terminal screen).&lt;br /&gt;
&lt;br /&gt;
Then, on your browser, click on the little fox in the upper right hand corner and select “Disable FoxyProxy”.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Copying_files&amp;diff=7902</id>
		<title>Copying files</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Copying_files&amp;diff=7902"/>
		<updated>2014-06-06T21:19:39Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;One way to copy files to and from a machine is as follows:&lt;br /&gt;
&lt;br /&gt;
To copy from the machine you are on&lt;br /&gt;
&lt;br /&gt;
 tar czf - dir1 dir2 dir3 | ssh tbalius@sgehead.bkslab.org &amp;quot;tar xzf - -C path/for/new/files &amp;quot;&lt;br /&gt;
&lt;br /&gt;
To copy from a remote machine to the machine you are on&lt;br /&gt;
&lt;br /&gt;
 ssh tbalius@sgehead.uoft.bkslab.org &amp;quot;cd path/to/dir/you/want ; tar czf - diryouwant1 diryouwant2 &amp;quot; | tar xzf - -C where/it/goes/locally&lt;br /&gt;
&lt;br /&gt;
This has advantages that it does not copy symbolic links.  &lt;br /&gt;
It also compresses the data while copying&lt;br /&gt;
&lt;br /&gt;
Clear?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Another (better) way to copy files is by using rsync and screen.  I am going to use a scenario, say I am going to copy my home to another server.&lt;br /&gt;
&lt;br /&gt;
On my desktop:&lt;br /&gt;
&lt;br /&gt;
  screen -dR my_home&lt;br /&gt;
&lt;br /&gt;
Note that my_home could be anything, it&#039;s just the name of the screen.&lt;br /&gt;
Then to copy my files:&lt;br /&gt;
&lt;br /&gt;
  rsync -arv /home/jill/* someServer:/home/jill/&lt;br /&gt;
&lt;br /&gt;
Then to detach from the screen:&lt;br /&gt;
&lt;br /&gt;
  Hold ctrl+A, let go and then type d&lt;br /&gt;
&lt;br /&gt;
You should now be detached from the screen.  &lt;br /&gt;
&lt;br /&gt;
To see a list of your screens type:&lt;br /&gt;
&lt;br /&gt;
  screen -ls&lt;br /&gt;
&lt;br /&gt;
To reattach to my screen:&lt;br /&gt;
&lt;br /&gt;
  screen -r my_home&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Copying_files&amp;diff=7901</id>
		<title>Copying files</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Copying_files&amp;diff=7901"/>
		<updated>2014-06-06T21:18:55Z</updated>

		<summary type="html">&lt;p&gt;Therese: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;One way to copy files to and from a machine is as follows:&lt;br /&gt;
&lt;br /&gt;
To copy from the machine you are on&lt;br /&gt;
&lt;br /&gt;
 tar czf - dir1 dir2 dir3 | ssh tbalius@sgehead.bkslab.org &amp;quot;tar xzf - -C path/for/new/files &amp;quot;&lt;br /&gt;
&lt;br /&gt;
To copy from a remote machine to the machine you are on&lt;br /&gt;
&lt;br /&gt;
 ssh tbalius@sgehead.uoft.bkslab.org &amp;quot;cd path/to/dir/you/want ; tar czf - diryouwant1 diryouwant2 &amp;quot; | tar xzf - -C where/it/goes/locally&lt;br /&gt;
&lt;br /&gt;
This has advantages that it does not copy symbolic links.  &lt;br /&gt;
It also compresses the data while copying&lt;br /&gt;
&lt;br /&gt;
Clear?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Another (better) way to copy files is by using rsync and screen.  I am going to use a scenario, say I am going to copy my home to another server.&lt;br /&gt;
&lt;br /&gt;
On my desktop:&lt;br /&gt;
&lt;br /&gt;
  screen -dR my_home&lt;br /&gt;
&lt;br /&gt;
Note that my_home could be anything, it&#039;s just the name of the screen.&lt;br /&gt;
Then to copy my files:&lt;br /&gt;
&lt;br /&gt;
  rsync -arv /home/jill/* someServer:/home/jill/&lt;br /&gt;
&lt;br /&gt;
Then to detach from the screen:&lt;br /&gt;
&lt;br /&gt;
  Hold ctrl+A let go and then type d&lt;br /&gt;
&lt;br /&gt;
You should now be detached from the screen.  &lt;br /&gt;
&lt;br /&gt;
To see a list of your screens type:&lt;br /&gt;
&lt;br /&gt;
  screen -ls&lt;br /&gt;
&lt;br /&gt;
To reattach to my screen:&lt;br /&gt;
&lt;br /&gt;
  screen -r my_home&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Internal]]&lt;/div&gt;</summary>
		<author><name>Therese</name></author>
	</entry>
</feed>