Managing Drive Failures with AN!CDB - Revision history

Digimer: /* Recovering from Accidental Ejection of Good Drive */

2014-02-17T03:59:43Z

Recovering from Accidental Ejection of Good Drive

← Older revision		Revision as of 03:59, 17 February 2014
Line 193:		Line 193:
	{{warning\|1=Ejecting a physical disk that is currently operating risks damaging the physical disk, it's controller, interface, the node's storage back-plane and/or the RAID controller. '''''Never eject a running drive'''''! We do it here using a test node and we accepted the risk of damaging the hardware.}}		{{warning\|1=Ejecting a physical disk that is currently operating risks damaging the physical disk, it's controller, interface, the node's storage back-plane and/or the RAID controller. '''''Never eject a running drive'''''! We do it here using a test node and we accepted the risk of damaging the hardware.}}

	There are numerous reasons why a perfectly good drive might get ejected from a node. In spite of the risks in the above warning, people often seem to eject a running disk. Perhaps ~~out of ignorance~~, or out of a desire to simulate a failure. In any case, it happens and it is important to know how to recover from it.		There are numerous reasons why a perfectly good drive might get ejected from a node. In spite of the risks in the above warning, people often seem to eject a running disk. Perhaps not realizing the system is running, or out of a desire to simulate a failure. In any case, it happens and it is important to know how to recover from it.

	As we [[#Drive Vanishes Entirely\|discussed above]], ejecting a disk will cause it to vanish from the list of physical disks and the logical disk it was in will become degraded.		As we [[#Drive Vanishes Entirely\|discussed above]], ejecting a disk will cause it to vanish from the list of physical disks and the logical disk it was in will become degraded.

Digimer: /* Drive Vanishes Entirely */

2014-02-17T03:57:48Z

Drive Vanishes Entirely

← Older revision		Revision as of 03:57, 17 February 2014
Line 112:		Line 112:
	In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on the bay with the failed or missing disk. If it is not lit, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.		In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on the bay with the failed or missing disk. If it is not lit, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.

	Once you know which disk is dead, remove it and install a replacement disk. ~~So long as~~ '<span class="code">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', the drive should immediately be added to the logical disk and the rebuild process should start.		Once you know which disk is dead, remove it and install a replacement disk. If '<span class="code">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', then the drive should immediately be added to the logical disk and the rebuild process should start.

	=== Inserting a Replacement Physical Disk ===		=== Inserting a Replacement Physical Disk ===
Line 122:		Line 122:
	[[Image:an-cdb_storage-control_12.png\|thumb\|800px\|center\|Disk is 'Unconfigured(good), Spun Up' with option to add the physical disk to logical disk #0.]]		[[Image:an-cdb_storage-control_12.png\|thumb\|800px\|center\|Disk is 'Unconfigured(good), Spun Up' with option to add the physical disk to logical disk #0.]]

	Click on ~~that~~ and the drive will be added to the logical disk. The rebuild process will start immediately.		Click on '<span class="code">Add to Logical Disk #X</span>' and the drive will be added to the logical disk. The rebuild process will start immediately.

	[[Image:an-cdb_storage-control_13.png\|thumb\|800px\|center\|Replacement physical disk manually added to logical disk #0, rebuild process started.]]		[[Image:an-cdb_storage-control_13.png\|thumb\|800px\|center\|Replacement physical disk manually added to logical disk #0, rebuild process started.]]

Digimer: /* Attempting to Recover a Failed Disk */

2014-02-17T02:32:48Z

Attempting to Recover a Failed Disk

← Older revision		Revision as of 02:32, 17 February 2014
Line 159:		Line 159:
	=== Attempting to Recover a Failed Disk ===		=== Attempting to Recover a Failed Disk ===

	{{warning\|1=If you do know why the drive failed, replace it. Even if it appears to recover, it will likely fail again soon.}}		{{warning\|1=If you do not know why the drive failed, replace it. Even if it appears to recover, it will likely fail again soon.}}

	Depending on why the physical disk failed, it may be possible to mark is as "good" again. This should only be done in two cases;		Depending on why the physical disk failed, it may be possible to mark is as "good" again. This should only be done in two cases;

Digimer: /* Managing Hot-Spares */

2014-02-17T02:31:44Z

Managing Hot-Spares

Digimer: /* Failure and Recovery */

2014-02-17T02:20:32Z

Failure and Recovery

Digimer at 01:36, 17 February 2014

2014-02-17T01:36:54Z

Digimer: /* Storage Display Window */

2014-02-17T00:10:53Z

Storage Display Window

← Older revision		Revision as of 00:10, 17 February 2014
Line 21:		Line 21:
	The auxiliary power and logical disks will be slightly indented under their parent controller.		The auxiliary power and logical disks will be slightly indented under their parent controller.

	The physical disks ~~associates~~ with a given logical disk are further indented, to show their association.		The physical disks associated with a given logical disk are further indented to show their association.

	[[Image:an-cdb_storage-control_02.png\|thumb\|800px\|center\|AN!CDB storage management page.]]		[[Image:an-cdb_storage-control_02.png\|thumb\|800px\|center\|AN!CDB storage management page.]]

Digimer at 23:45, 16 February 2014

2014-02-16T23:45:11Z

← Older revision		Revision as of 23:45, 16 February 2014
Line 3:		Line 3:
	{{note\|1=At this time, only LSI-based controllers are supported. Please see [[AN!Cluster_Tutorial_2#Monitoring_LSI-Based_RAID_Controllers_with_MegaCli\|this section]] of the [[AN!Cluster Tutorial 2]] for required node configuration.}}		{{note\|1=At this time, only LSI-based controllers are supported. Please see [[AN!Cluster_Tutorial_2#Monitoring_LSI-Based_RAID_Controllers_with_MegaCli\|this section]] of the [[AN!Cluster Tutorial 2]] for required node configuration.}}

	~~The~~ [[AN!CDB]] ~~dashboard~~ supports basic drive management for nodes using LSI-based [[RAID]] controllers. This covers ~~most~~ all Fujitsu servers.		[[AN!CDB]] supports basic drive management for nodes using LSI-based [[RAID]] controllers. This covers all Fujitsu servers with hardware [[RAID]].

	This guide will show you how to handle a few common storage management tasks easily and quickly.		This guide will show you how to handle a few common storage management tasks easily and quickly.

	= Starting ~~The~~ Storage Manager =		= Starting the Storage Manager =

	From the main [[AN!CDB]] page, under the "''Cluster Nodes - Control'' window, click on the name of the node you wish to manage.		From the main [[AN!CDB]] page, under the "''Cluster Nodes - Control''" window, click on the name of the node you wish to manage.

	[[Image:an-cdb_storage-control_01.png\|thumb\|800px\|center\|AN!CDB main page with node names as click-able items.]]		[[Image:an-cdb_storage-control_01.png\|thumb\|800px\|center\|AN!CDB main page with node names as click-able items.]]
Line 29:		Line 29:
	The Logical volume is a [[RAID level 5]] array with four physical disks.		The Logical volume is a [[RAID level 5]] array with four physical disks.

	= Controlling the Physical Disk Identification ID Light =		= Controlling the Physical Disk Identification Light =

	The first task we will explore is using identification lights to match a physical disk listing with a physical drive in a node.		The first task we will explore is using identification lights to match a physical disk listing with a physical drive in a node.
Line 39:		Line 39:
	Each physical drive will have a buttons labelled either <span class="code">Turn On</span> or <span class="code">Turn Off</span>, depending on the current state of the identification LED.		Each physical drive will have a buttons labelled either <span class="code">Turn On</span> or <span class="code">Turn Off</span>, depending on the current state of the identification LED.

	=== ~~Illumination~~ a Drive's ID Light ===		=== Illuminating a Drive's ID Light ===

	Let's illuminate!		Let's illuminate!
Line 67:		Line 67:
	[[Image:an-cdb_storage-control_07.png\|thumb\|800px\|center\|Physical disk '<span class="code">252:0</span>' ID light turned off successfully.]]		[[Image:an-cdb_storage-control_07.png\|thumb\|800px\|center\|Physical disk '<span class="code">252:0</span>' ID light turned off successfully.]]

	= Refreshing ~~The~~ Storage Page =		= Refreshing the Storage Page =

	{{warning\|1=AN!CDB doesn't (yet) use a command key to prevent a request being sent again if a page is manually reloaded (<span class="code">ctrl + r</span>, <span class="code"><f5></span>, etc). In most all cases, this is harmless as AN!CDB won't do something dangerous without verifying it is still safe to do so. Just the same, please always use the "reload" icon shown below.}}		{{warning\|1=AN!CDB doesn't (yet) use a command key to prevent a request being sent again if a page is manually reloaded (<span class="code">ctrl + r</span>, <span class="code"><f5></span>, etc). In most all cases, this is harmless as AN!CDB won't do something dangerous without verifying it is still safe to do so. Just the same, please always use the "reload" icon shown below.}}

Digimer at 23:23, 16 February 2014

2014-02-16T23:23:44Z

Digimer: /* Replacing a Failing Hot-Spare */

2014-02-16T23:21:46Z

Replacing a Failing Hot-Spare

← Older revision		Revision as of 23:21, 16 February 2014
Line 295:		Line 295:
	[[Image:an-cdb_storage-control_29.png\|thumb\|800px\|center\|Hot-spare physical disk's '<span class="code">Unmark as Hot-Spare</span>' highlighted.]]		[[Image:an-cdb_storage-control_29.png\|thumb\|800px\|center\|Hot-spare physical disk's '<span class="code">Unmark as Hot-Spare</span>' highlighted.]]

			Once you click it, the physical disk reverts to being '<span class="code">Unconfigured(good)</span>'. From here, we can click on '<span class="code">Spin Down Disk</span>' to prepare it for removal.

			[[Image:an-cdb_storage-control_30.png\|thumb\|800px\|center\|Physical disk's '<span class="code">Spin Down Disk</span>' highlighted.]]

			Once spun down, the disk can safely be ejected and replaced.

			[[Image:an-cdb_storage-control_31.png\|thumb\|800px\|center\|Physical disk '<span class="code">[252:6]</span>' ready to be removed.]]

			Done!

	{{footer}}		{{footer}}

← Older revision		Revision as of 02:31, 17 February 2014
Line 249:		Line 249:
	= Managing Hot-Spares =		= Managing Hot-Spares =

	In this final section, we will add a "~~Hot~~-~~Spare~~" drive to our node.		In this final section, we will add a "hot-spare" drive to our node.

	A "Hot-Spare" is an unused drive that the RAID controller knows can be used to immediately replace a failed drive. This is a popular option for people who want to return to a fully redundant state as soon after a failure as possible.		A "Hot-Spare" is an unused drive that the RAID controller knows can be used to immediately replace a failed drive. This is a popular option for people who want to return to a fully redundant state as soon after a failure as possible.

	We will Configure a ~~Hot~~-~~Spare~~, show how it replaces a failed drive, and show how to unmark a drive as a hot-spare, in case the ~~Hot~~-~~Spare~~ itself goes bad.		We will Configure a hot-spare, show how it replaces a failed drive, and show how to unmark a drive as a hot-spare, in case the hot-spare itself goes bad.

	== Creating a Hot-Spare ==		== Creating a Hot-Spare ==

	Up until this point, we've had four physical disks in our system. Here, we've inserted a fifth healthy disk. The logical disk is <span class="code">Optimal</span>, so no default action was ~~take~~. Likewise, no option to add the physical disk to a logical disk is presented.		Up until this point, we've had four physical disks in our system. Here, we've inserted a fifth healthy disk. The logical disk was '<span class="code">Optimal</span>', so no default action was taken. Likewise, no option to add the physical disk to a logical disk is presented.

	[[Image:an-cdb_storage-control_25.png\|thumb\|800px\|center\|Newly inserted physical disk.]]		[[Image:an-cdb_storage-control_25.png\|thumb\|800px\|center\|Newly inserted physical disk.]]
Line 287:		Line 287:
	== Replacing a Failing Hot-Spare ==		== Replacing a Failing Hot-Spare ==

	As we [[#Pre-Failure Drive Replacement\|discussed earlier]], a drive may show signs of failing before it's actually failed. Of course, it could just as well die and get marked as <span class="code">Unconfigured(bad)</span> or vanish entirely.		As we [[#Pre-Failure Drive Replacement\|discussed earlier]], a drive may show signs of failing before it's actually failed. Of course, it could just as well die and get marked as '<span class="code">Unconfigured(bad)</span>' or vanish entirely.

	In this case, we'll pretend the drive is predicted to fail.		In this case, we'll pretend the drive is predicted to fail.

	~~To do this~~, ~~simply~~ click on '<span class="code">Unmark as Hot-Spare</span>'.		Before we can spin down and remove a hot-spare disk, we must first click on '<span class="code">Unmark as Hot-Spare</span>'.

	[[Image:an-cdb_storage-control_29.png\|thumb\|800px\|center\|Hot-spare physical disk's '<span class="code">Unmark as Hot-Spare</span>' highlighted.]]		[[Image:an-cdb_storage-control_29.png\|thumb\|800px\|center\|Hot-spare physical disk's <span class="code">Unmark as Hot-Spare</span> highlighted.]]

	Once you click it, the physical disk reverts to being '<span class="code">Unconfigured(good)</span>'. From here, we can click on '<span class="code">Spin Down Disk</span>' to prepare it for removal.		Once you click it, the physical disk reverts to being '<span class="code">Unconfigured(good)</span>'. From here, we can click on '<span class="code">Spin Down Disk</span>' to prepare it for removal.

← Older revision		Revision as of 02:20, 17 February 2014
Line 92:		Line 92:
	The first three are going to be sort of mashed together. We'll simply eject the drive while it's running, causing it to disappear and for the array to degrade. If this happened in real life, you would simply eject it and insert a new drive.		The first three are going to be sort of mashed together. We'll simply eject the drive while it's running, causing it to disappear and for the array to degrade. If this happened in real life, you would simply eject it and insert a new drive.

	For the second case, we'll re-insert the ejected drive. The drive will be listed as failed ("Unconfigured(bad)"). We'll tell the controller to "spin down" the drive, making it safe to remove. If the real world, we would then eject it and install a new drive.		For the second case, we'll re-insert the ejected drive. The drive will be listed as failed ("Unconfigured(bad)"). We'll tell the controller to "spin down" the drive, making it safe to remove. In the real world, we would then eject it and install a new drive.

	In the third case, we will again eject the drive, and then re-insert it. In this case, we won't spin down the drive, but instead mark it as healthy again.		In the third case, we will again eject the drive, and then re-insert it. In this case, we won't spin down the drive, but instead mark it as healthy again.
Line 110:		Line 110:
	If you look under '''Logical Disk #X''', you will see the number of physical disks in the logical disk beside the '<span class="code">Number of Drives</span>'. When you count the actual number of disks under the logical drive though, you will see the number of displayed disks is smaller.		If you look under '''Logical Disk #X''', you will see the number of physical disks in the logical disk beside the '<span class="code">Number of Drives</span>'. When you count the actual number of disks under the logical drive though, you will see the number of displayed disks is smaller.

	In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on bay with the failed or missing disk. If it is not lit~~, however~~, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.		In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on the bay with the failed or missing disk. If it is not lit, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.

	Once you know which disk is dead, remove it and install a replacement disk. So long as '<span class="code">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', the drive should immediately be added to the logical disk and the rebuild process should start.		Once you know which disk is dead, remove it and install a replacement disk. So long as '<span class="code">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', the drive should immediately be added to the logical disk and the rebuild process should start.
Line 128:		Line 128:
	== Drive is Failed but Still Online ==		== Drive is Failed but Still Online ==

	If a drive has failed, but ~~it's~~ controller is still working, the drive should appear as '<span class="code">Unconfigured(bad)</span>.		If a drive has failed, but its controller is still working, the drive should appear as '<span class="code">Unconfigured(bad)</span>.

	This will be one of the most common failures you will have to deal with.		This will be one of the most common failures you will have to deal with.
Line 137:		Line 137:

	* Prepare it for removal		* Prepare it for removal
	* Try ~~and~~ make the drive "good" again		* Try to make the drive "good" again

	=== Preparing a Failed Disk for Removal ===		=== Preparing a Failed Disk for Removal ===

	A failed disk may still be "spun up", meaning that ~~it's~~ platters are rotating. ~~This places centripidal force on the drive, and moving~~ the disk ~~out of it's rotational axis~~ before the drive has spun down completely could cause a head-crash. Further, the electrical connection to the drive will still be active, making it possible to cause a short when the drive is mechanically ejected, which could damager the drive's controller, the backplane or the RAID controller itself.		A failed disk may still be "spun up", meaning that its platters are rotating. Moving the disk before the drive has spun down completely could cause a head-crash. Further, the electrical connection to the drive will still be active, making it possible to cause a short when the drive is mechanically ejected, which could damager the drive's controller, the backplane or the RAID controller itself.

	To avoid this risk, before a drive is removed, we must prepare it for removal. This will spin-down the disk and make it safe to eject with minimal risk of electrical shorts.		To avoid this risk, before a drive is removed, we must prepare it for removal. This will spin-down the disk and make it safe to eject with minimal risk of electrical shorts.
Line 159:		Line 159:
	=== Attempting to Recover a Failed Disk ===		=== Attempting to Recover a Failed Disk ===

	{{warning\|1=If you do ~~now~~ know why the drive failed, replace it. Even if it appears to recover, it will likely fail again soon.}}		{{warning\|1=If you do know why the drive failed, replace it. Even if it appears to recover, it will likely fail again soon.}}

	Depending on why the physical disk failed, it may be possible to mark is as "good" again. This should only be done in two cases;		Depending on why the physical disk failed, it may be possible to mark is as "good" again. This should only be done in two cases;
Line 174:		Line 174:
	[[Image:an-cdb_storage-control_18.png\|thumb\|800px\|center\|Physical disk marked good.]]		[[Image:an-cdb_storage-control_18.png\|thumb\|800px\|center\|Physical disk marked good.]]

	* If (one of) the logical disk(s) are ~~defraded~~, <span class="code">Add to Logical Disk #X</span> will be available.		* If (one of) the logical disk(s) are degraded, '<span class="code">Add to Logical Disk #X</span>' will be available.
	* If (all) the logical disk(s) are '<span class="code">Optimal</span>', you will be able to mark the disk as a '~~Hpt~~ Spare'.		* If (all) the logical disk(s) are '<span class="code">Optimal</span>', you will be able to mark the disk as a 'Hot Spare'.

	In this section, we will add it to a degraded logical disk. Managing hot-spares is covered further below. Do note though; If you mark a disk as a hot-spare when a logical disk is degraded, it will automatically be added to that degraded logical disk and rebuild will begin.		In this section, we will add the recovered physical disk to the degraded logical disk. Managing hot-spares is covered further below. Do note though; If you mark a disk as a hot-spare when a logical disk is degraded, it will automatically be added to that degraded logical disk and rebuild will begin.

	If there are multiple degraded logical disks, you will see multiple '<span class="code">Add to Logical Disk #X</span>' options, one for each degraded logical disk. In our case, there is just one logical disk, so there is just one option.		If there are multiple degraded logical disks, you will see multiple '<span class="code">Add to Logical Disk #X</span>' options, one for each degraded logical disk. In our case, there is just one logical disk, so there is just one option.

	[[Image:an-cdb_storage-control_19.png\|thumb\|800px\|center\|Recovered physical disk's <span class="code">Add to Logical Disk #0</span> button highlighted.]]		[[Image:an-cdb_storage-control_19.png\|thumb\|800px\|center\|Recovered physical disk's '<span class="code">Add to Logical Disk #0</span>' button highlighted.]]

	Once you click on '<span class="code">Add to Logical Disk #X</span>', the physical disk will appear under the logical disk and rebuild will begin automatically.		Once you click on '<span class="code">Add to Logical Disk #X</span>', the physical disk will appear under the logical disk and rebuild will begin automatically.

	[[Image:an-cdb_storage-control_20.png\|thumb\|800px\|center\|Recovered physical disk's back in the logical disk and rebuild has begun.]]		[[Image:an-cdb_storage-control_20.png\|thumb\|800px\|center\|Recovered physical disk is back in the logical disk and rebuild has begun.]]

	Done.		Done.

← Older revision		Revision as of 01:36, 17 February 2014
Line 3:		Line 3:
	{{note\|1=At this time, only LSI-based controllers are supported. Please see [[AN!Cluster_Tutorial_2#Monitoring_LSI-Based_RAID_Controllers_with_MegaCli\|this section]] of the [[AN!Cluster Tutorial 2]] for required node configuration.}}		{{note\|1=At this time, only LSI-based controllers are supported. Please see [[AN!Cluster_Tutorial_2#Monitoring_LSI-Based_RAID_Controllers_with_MegaCli\|this section]] of the [[AN!Cluster Tutorial 2]] for required node configuration.}}

	[[AN!CDB]] supports basic drive management for nodes using LSI-based [[RAID]] controllers. This covers all Fujitsu servers with hardware [[RAID]].		The [[AN!CDB]] dashboard supports basic drive management for nodes using LSI-based [[RAID]] controllers. This covers all Fujitsu servers with hardware [[RAID]].

	This guide will show you how to handle a few common storage management tasks easily and quickly.		This guide will show you how to handle a few common storage management tasks easily and quickly.
Line 33:		Line 33:
	The first task we will explore is using identification lights to match a physical disk listing with a physical drive in a node.		The first task we will explore is using identification lights to match a physical disk listing with a physical drive in a node.

	If a drive fails completely, ~~it's~~ fault light will light up, making the failed drive easy to find. However, the [[AN!CDB]] [[AN!Cluster_Tutorial_2#Setting_Up_Alerts\|alert system]] can notify us of pending failures. In these cases, the drive's fault light will not illuminate. So it becomes critical to identify the failing drive. Removing the wrong drive, when another drive is unhealthy, may well leave your node non-operational.		If a drive fails completely, its fault light will light up, making the failed drive easy to find. However, the [[AN!CDB]] [[AN!Cluster_Tutorial_2#Setting_Up_Alerts\|alert system]] can notify us of pending failures. In these cases, the drive's fault light will not illuminate. Therefore, it becomes critical to identify the failing drive. Removing the wrong drive, when another drive is unhealthy, may well leave your node non-operational.

	That's no fun.		That's no fun.

	Each physical drive will have a ~~buttons~~ labelled either <span class="code">Turn On</span> or <span class="code">Turn Off</span>, depending on the current state of the identification LED.		Each physical drive will have a button labelled either <span class="code">Turn On</span> or <span class="code">Turn Off</span>, depending on the current state of the identification LED.

	=== Illuminating a Drive's ID Light ===		=== Illuminating a Drive's ID Light ===
Line 83:		Line 83:
	There are many ways for hard drives to fail.		There are many ways for hard drives to fail.

	In this section, we're going to sort-of simulate four failures;		In this section, we're going to sort-of simulate four failures:

	# Drive vanishes entirely		# Drive vanishes entirely

← Older revision		Revision as of 23:23, 16 February 2014
Line 104:		Line 104:
	Likewise, if the disk is physically ejected (by accident or otherwise), the same result will be seen.		Likewise, if the disk is physically ejected (by accident or otherwise), the same result will be seen.

	The logical drive will list as '<span ~~style~~="~~color: #9a131a; font-style: italic;~~">Degraded</span>', but none of the disks will show errors.		The logical drive will list as '<span class="code">Degraded</span>', but none of the disks will show errors.

	[[Image:an-cdb_storage-control_10.png\|thumb\|800px\|center\|Degraded logical disk with no failed physical disks.]]		[[Image:an-cdb_storage-control_10.png\|thumb\|800px\|center\|Degraded logical disk with no failed physical disks.]]

	If you look under '''Logical Disk #X''', you will see the number of physical disks in the logical disk beside the '<span ~~style~~="~~color: #13749a;~~">Number of Drives</span>'. When you count the actual number of disks under the logical drive though, you will see the number of displayed disks is smaller.		If you look under '''Logical Disk #X''', you will see the number of physical disks in the logical disk beside the '<span class="code">Number of Drives</span>'. When you count the actual number of disks under the logical drive though, you will see the number of displayed disks is smaller.

	In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on bay with the failed or missing disk. If it is not lit, however, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.		In this situation, the best thing to do is locate the failed disk. The 'Failed' LED should be illuminated on bay with the failed or missing disk. If it is not lit, however, you may need to light up the ID LED on the remaining good disks and use a simple process of illimination to find the dead drive.

	Once you know which disk is dead, remove it and install a replacement disk. So long as '<span ~~style~~="~~color: #13749a;~~">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', the drive should immediately be added to the logical disk and the rebuild process should start.		Once you know which disk is dead, remove it and install a replacement disk. So long as '<span class="code">Restore Hot-Spare on Insert</span>' is set to '<span class="code">Yes</span>', the drive should immediately be added to the logical disk and the rebuild process should start.

	=== Inserting a Replacement Physical Disk ===		=== Inserting a Replacement Physical Disk ===
Line 118:		Line 118:
	[[Image:an-cdb_storage-control_11.png\|thumb\|800px\|center\|Replaced physical disk automatically added to logical disk and rebuild begun.]]		[[Image:an-cdb_storage-control_11.png\|thumb\|800px\|center\|Replaced physical disk automatically added to logical disk and rebuild begun.]]

	If the replacement drive doesn't automatically get added to the logical disk, you can add the new physical disk to the ''Degraded'' logical disk using the storage manager. The new disk will come up as '<span ~~style~~="~~color: #13749a;~~">Unconfigured(good), Spun Up</span>'. Directly beneath that, you will see the option to '<span ~~style~~="~~color: #7f117f;~~">Add to Logical Disk #X</span>', where X is the logical disk number that is degraded.		If the replacement drive doesn't automatically get added to the logical disk, you can add the new physical disk to the ''Degraded'' logical disk using the storage manager. The new disk will come up as '<span class="code">Unconfigured(good), Spun Up</span>'. Directly beneath that, you will see the option to '<span class="code">Add to Logical Disk #X</span>', where X is the logical disk number that is degraded.

	[[Image:an-cdb_storage-control_12.png\|thumb\|800px\|center\|Disk is 'Unconfigured(good), Spun Up' with option to add the physical disk to logical disk #0.]]		[[Image:an-cdb_storage-control_12.png\|thumb\|800px\|center\|Disk is 'Unconfigured(good), Spun Up' with option to add the physical disk to logical disk #0.]]
Line 128:		Line 128:
	== Drive is Failed but Still Online ==		== Drive is Failed but Still Online ==

	If a drive has failed, but it's controller is still working, the drive should appear as '<span ~~style~~="~~color: #9a131a; font-style: italic;~~">Unconfigured(bad)</span>.		If a drive has failed, but it's controller is still working, the drive should appear as '<span class="code">Unconfigured(bad)</span>.

	This will be one of the most common failures you will have to deal with.		This will be one of the most common failures you will have to deal with.
Line 145:		Line 145:
	To avoid this risk, before a drive is removed, we must prepare it for removal. This will spin-down the disk and make it safe to eject with minimal risk of electrical shorts.		To avoid this risk, before a drive is removed, we must prepare it for removal. This will spin-down the disk and make it safe to eject with minimal risk of electrical shorts.

	To prepare it for removal, you will click on '<span ~~style~~="~~color: #7f117f;~~">Spin Down Disk</span>'.		To prepare it for removal, you will click on '<span class="code">Spin Down Disk</span>'.

	[[Image:an-cdb_storage-control_15.png\|thumb\|800px\|center\|Failed physical disk with 'Spin Down Disk' option highlighted.]]		[[Image:an-cdb_storage-control_15.png\|thumb\|800px\|center\|Failed physical disk with 'Spin Down Disk' option highlighted.]]
Line 166:		Line 166:
	* To try and restore redundancy to the logical disk while you wait for the replacement disk to arrive		* To try and restore redundancy to the logical disk while you wait for the replacement disk to arrive

	Underneath the '<span ~~style~~="~~color: #13749a;~~">Unconfigured(good), Spun Up</span>' disk state will be the option '<span ~~style~~="~~color: #7f117f;~~">Make good</span>'.		Underneath the '<span class="code">Unconfigured(good), Spun Up</span>' disk state will be the option '<span class="code">Make good</span>'.

	[[Image:an-cdb_storage-control_17.png\|thumb\|800px\|center\|Failed disk with 'Make Good' option highlighted.]]		[[Image:an-cdb_storage-control_17.png\|thumb\|800px\|center\|Failed disk with 'Make Good' option highlighted.]]

	If this works, the disk state will change to '<span ~~style~~="~~color: #13749a;~~">Unconfigured(good), Spun Up</span>'. Below this, one of two options will be available;		If this works, the disk state will change to '<span class="code">Unconfigured(good), Spun Up</span>'. Below this, one of two options will be available;

	[[Image:an-cdb_storage-control_18.png\|thumb\|800px\|center\|Physical disk marked good.]]		[[Image:an-cdb_storage-control_18.png\|thumb\|800px\|center\|Physical disk marked good.]]

	* If (one of) the logical disk(s) are defraded, <span ~~style~~="~~color: #7f117f;~~">Add to Logical Disk #X</span> will be available.		* If (one of) the logical disk(s) are defraded, <span class="code">Add to Logical Disk #X</span> will be available.
	* If (all) the logical disk(s) are '<span ~~style~~="~~color: #1a9a13;~~">Optimal</span>', you will be able to mark the disk as a 'Hpt Spare'.		* If (all) the logical disk(s) are '<span class="code">Optimal</span>', you will be able to mark the disk as a 'Hpt Spare'.

	In this section, we will add it to a degraded logical disk. Managing hot-spares is covered further below. Do note though; If you mark a disk as a hot-spare when a logical disk is degraded, it will automatically be added to that degraded logical disk and rebuild will begin.		In this section, we will add it to a degraded logical disk. Managing hot-spares is covered further below. Do note though; If you mark a disk as a hot-spare when a logical disk is degraded, it will automatically be added to that degraded logical disk and rebuild will begin.

	If there are multiple degraded logical disks, you will see multiple '<span ~~style~~="~~color: #7f117f;~~">Add to Logical Disk #X</span>' options, one for each degraded logical disk. In our case, there is just one logical disk, so there is just one option.		If there are multiple degraded logical disks, you will see multiple '<span class="code">Add to Logical Disk #X</span>' options, one for each degraded logical disk. In our case, there is just one logical disk, so there is just one option.

	[[Image:an-cdb_storage-control_19.png\|thumb\|800px\|center\|Recovered physical disk's <span class="code">Add to Logical Disk #0</span> button highlighted.]]		[[Image:an-cdb_storage-control_19.png\|thumb\|800px\|center\|Recovered physical disk's <span class="code">Add to Logical Disk #0</span> button highlighted.]]

	Once you click on '<span ~~style~~="~~color: #7f117f;~~">Add to Logical Disk #X</span>', the physical disk will appear under the logical disk and rebuild will begin automatically.		Once you click on '<span class="code">Add to Logical Disk #X</span>', the physical disk will appear under the logical disk and rebuild will begin automatically.

	[[Image:an-cdb_storage-control_20.png\|thumb\|800px\|center\|Recovered physical disk's back in the logical disk and rebuild has begun.]]		[[Image:an-cdb_storage-control_20.png\|thumb\|800px\|center\|Recovered physical disk's back in the logical disk and rebuild has begun.]]
Line 197:		Line 197:
	As we [[#Drive Vanishes Entirely\|discussed above]], ejecting a disk will cause it to vanish from the list of physical disks and the logical disk it was in will become degraded.		As we [[#Drive Vanishes Entirely\|discussed above]], ejecting a disk will cause it to vanish from the list of physical disks and the logical disk it was in will become degraded.

	Once re-inserted, the disk will be flagged as '<span ~~style~~="~~color: #9a131a; font-style: italic;~~">Unconfigured(bad)</span>'. In this case, you know the disk is fine, so marking it as good after reinserting it is fine.		Once re-inserted, the disk will be flagged as '<span class="code">Unconfigured(bad)</span>'. In this case, you know the disk is fine, so marking it as good after reinserting it is fine.

	Please [[#Drive Vanishes Entirely\|jump up]] to that section to finish recovering the physical disk.		Please [[#Drive Vanishes Entirely\|jump up]] to that section to finish recovering the physical disk.