No products in the cart.
8-12-16-Hard-Drive-Replacements.pdf (6 downloads)
ABSTRACT:
Changing out a bad hard drive is not as complex as a task as it may appear when you first open up a server. Nonetheless, even if you’ve replaced them in the past the error message that you receive for a failed hard drive doesn’t come with a large neon sign saying “This One” when you open up the server. This tech bulletin will not contain neon, but it will contain instructions and images for identifying the correct hard-drive that needs to be replaced and the steps you should take in replacing them.
TECH SUPPORT SUMMARY:
Sample Email:
This is an automatically generated mail message from mdadm
running on <facility name> A DegradedArray event had been detected on md device /dev/md/1. Faithfully yours, etc. P.S. The /proc/mdstat file currently contains the following: Personalities : [raid1]
md1 : active raid1 sda2[0](F) sdb2[1]
974750881 blocks super 1.2 [2/1] [_U] md0 : active raid1 sda1[0] sdb1[1]
96244 blocks super 1.2 [2/2] [UU]
|
|
Steps to follow regardless of cube type
1) Trace hard drive connection to mother board to identify which port you are on.
2) Ports are numbered as is the image below. Remember, 1 does not always equal 1; lower corresponds to lower, higher corresponds to higher.
|
HD Cubes
|
|
Bread Box (Stand Alone) Cubes
|
|
Rack Mount
|
|
CONCLUSION:
Hard drive crashes are rare, but as our facilities get older and older they are inevitable. With three different types of servers and a complex numbering/naming convention on these motherboards it can get confusing. When all else fails, if you can’t figure it out, you can always go with the trial and error method. Test one, if the server comes up, you’ve selected the correct HD to replace. If it gets stuck in starting up, you’ve selected the wrong one. However, understanding what you are looking at in these degraded array emails or the diagnostics report can go a long way to addressing the issue in a quick and timely manner.
|