Hard Drive Testing - Revision history

Kevin.Williams at 21:07, 25 July 2014

2014-07-25T21:07:35Z

KevinWright at 16:39, 29 March 2014

2014-03-29T16:39:32Z

Ryan52: as a link formatted

2013-10-25T17:49:12Z

as a link formatted

Ryan52: add link to disktest page

2013-10-25T17:48:51Z

add link to disktest page

KevinWright: /* Storing Passed Hard Drives */

2013-10-24T23:09:18Z

Storing Passed Hard Drives

KevinWright: /* Sorting Incoming Hard Drives */

2013-10-24T23:03:21Z

Sorting Incoming Hard Drives

KevinWright: /* Finishing a Batch */

2013-10-24T23:00:11Z

Finishing a Batch

KevinWright: /* Setting Up */

2013-10-24T22:41:32Z

Setting Up

Psullivan: /* Finishing a Batch */

2012-09-07T21:12:50Z

Finishing a Batch

Psullivan: /* During Testing */

2012-09-07T21:12:01Z

During Testing

← Older revision		Revision as of 21:07, 25 July 2014
Line 1:		Line 1:
−	{{~~migrate~~}}	+	{{migrated}}
		+	[https://docs.google.com/document/d/1ntvt7pE8qK-cpGenhGFfqXZ3vhCEFn4W-eeJATiRYaE/edit?usp=sharing Link]
		+
	''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''		''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''

← Older revision		Revision as of 16:39, 29 March 2014
Line 1:		Line 1:
		+	{{migrate}}
	''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''		''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''

@@ Line 1: / Line 1: @@
 ''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest|Starting Disktest]], [[Hard Drive Testing#During Testing|During Testing]], and [[Hard Drive Testing#Finishing a Batch|Finishing a Batch]] should be relevant to use in other areas.''
-The technical details of the software used can be found on the [Hard Drive Testing/Disktest] page.
+The technical details of the software used can be found on the [[Hard Drive Testing/Disktest]] page.
 The process of hard drive testing incorporates verification of a drive's SMART status, verification of the drive's ability to write and read all available surface area of the drive, and repeated overwriting of any previous data on the drive to ensure donors' data security.

← Older revision		Revision as of 17:48, 25 October 2013
Line 1:		Line 1:
	''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''		''This document is written from the perspective of use in Hardware Testing, but the sections on [[Hard Drive Testing#Starting Disktest\|Starting Disktest]], [[Hard Drive Testing#During Testing\|During Testing]], and [[Hard Drive Testing#Finishing a Batch\|Finishing a Batch]] should be relevant to use in other areas.''
		+
		+	The technical details of the software used can be found on the [Hard Drive Testing/Disktest] page.

	The process of hard drive testing incorporates verification of a drive's SMART status, verification of the drive's ability to write and read all available surface area of the drive, and repeated overwriting of any previous data on the drive to ensure donors' data security.		The process of hard drive testing incorporates verification of a drive's SMART status, verification of the drive's ability to write and read all available surface area of the drive, and repeated overwriting of any previous data on the drive to ensure donors' data security.

@@ Line 125: / Line 125: @@
 ===Storing Passed Hard Drives===
-* Passed 3.5" (desktop) drives should be stored on the labeled shelves on the west wall inside TARDIS. The top shelf is for SCSI drives, the second shelf is for IDE drives, and the third shelf is for SATA drives. The stacks are grouped by size and the shelves themselves are labeled with what sizes go where. There are also special purpose bins for size/interface combinations needed for special systems and projects.
+* Passed 3.5" (desktop) drives should be stored in the build room. There are crates in the build room labled with the capacity and either SATA, or IDE.  There are also special purpose bins for size/interface combinations needed for special systems and projects.
-* Passed 2.5" (laptop) drives are stored in the blue bins on the top shelf at the southwest corner of TARDIS; the bins are organized by size and interface.
+* Passed 2.5" (laptop) drives are stored in the laptop area; the bins are organized by size and interface.
 === Future: Certificate of Destruction Tracking ===

@@ Line 122: / Line 122: @@
 ===Sorting Incoming Hard Drives===
-Incoming hard drives will be placed in the tan lockbox just inside the door to TARDIS; this should be checked regularly and sorted into the labeled stacks in the big brown lockbox. Currently they are grouped by size (&le;100GB, >100GB to <300GB, >300GB/all SCSI) and interface (IDE/SATA).
+Incoming hard drives will be removed from systems in the SDA by SDA staff only; hard drives will be sorted by size & capacity until wiped; Currently they are grouped by size (&le;100GB, >100GB to <300GB, >300GB/all SCSI) and interface (IDE/SATA).
 ===Storing Passed Hard Drives===

@@ Line 112: / Line 112: @@
 ## Be certain you have positively identified all drives before powering down the system as there is no easy way to recall these results once the board is off.
 ## Do not place labels over model numbers, serial numbers, or other identifying information that may be necessary for future tests.
-# Place the passed and labeled drives in the green tray to await [[Hard Drive Testing#Storing Passed Hard Drives|storage in TARDIS]].
+# Place the passed and labeled drives in the green tray to await Hard Drive storage in build room. 80GB-160GB stored in labled crates, 200GB & larger get locked in box 107 in build room.
 # [[Hard Drive Testing#Destroying Failed Hard Drives|Destroy failed drives promptly]].
 # [[Hard Drive Testing#Setting Up|Start a new batch!]]

@@ Line 11: / Line 11: @@
 If there are finished hard drives already on the racks then proceed to [[Hard Drive Testing#Finishing a Batch|Finishing a Batch]].
 # The drives in the box should be fairly well organized by size and interface. If this is the first batch of the day you'll want to grab smaller drives. If it's the second batch you can go for the larger ones. Load up the tray with an equal number of IDE- and SATA-connected hard drives. Don't forget about the 2.5" (laptop-sized) drives on the smaller top shelf! If they are present and you have the time you should grab a few SCSI drives as well. Be sure to lock up the big brown box again when you're done.
 # Take the tray of drives over to one of the wiping racks and start connecting them to the boards. Most boards have 4 connections with various mixtures of IDE and SATA cables.

@@ Line 99: / Line 99: @@
 Once disktest has finished you will be presented with a results screen like this:
-  sda: IDE 80.0GB <<Seagate SD380830A (5GQ1DB70)>>
+  sda: 3.5" IDE 80.0GB <<Seagate SD380830A (5GQ1DB70)>>
   sda passed! Label and store it.
-  sdb: IDE 80.0GB <<Samsung SV400AH (173G27Q37282S)>>
+  sdb: 2.5" IDE 80.0GB <<Samsung SV400AH (173G27Q37282S)>>
   sdb failed! Recycle it!
-  sdc: SATA 80.0GB <<Seagate SD380830A (5GQ1HG92)>>
+  sdc: 3.5" SATA 80.0GB <<Seagate SD380830A (5GQ1HG92)>>
   sdc passed! Label and store it.
-  sdd: SATA 80.0GB <<Western Digital WD800JBB (WMAMF92810)>>
+  sdd: 3.5" SATA 80.0GB <<Western Digital WD800JBB (WMAMF92810)>>
   sdd passed! Label and store it.
   Hit enter to shut down.

@@ Line 74: / Line 74: @@
 While disktest is running it will output status updates on the drives every few seconds.
-  sda: IDE 80.0GB <<Seagate SD380830A (5GQ1DB70)>>: 13% of wipe complete - 2:58:02
+  sda: 3.5" IDE 80.0GB <<Seagate SD380830A (5GQ1DB70)>>: 13% of wipe complete - 2:58:02
-  sdb: IDE 80.0GB <<Samsung SV400AH (173G27Q37282S)>>: 80% of badblocks read (part 1) complete - 2:58:02
+  sdb: 2.5" IDE 80.0GB <<Samsung SV400AH (173G27Q37282S)>>: 80% of badblocks read (part 1) complete - 2:58:02
-  sdc: SATA 80.0GB <<Seagate SD380830A (5GQ1HG92)>>: all tests passed:
+  sdc: 3.5" SATA 80.0GB <<Seagate SD380830A (5GQ1HG92)>>: all tests passed:
   ---
   -smart test passed
@@ Line 88: / Line 88: @@
   -smart test passed
   -2:08:32
-  sdd: SATA 80.0GB <<Western Digital WD800JBB (WMAMF92810)>> 22% of badblocks write (part 2) complete - 2:58:02
+  sdd: 3.5" SATA 80.0GB <<Western Digital WD800JBB (WMAMF92810)>> 22% of badblocks write (part 2) complete - 2:58:02
 Any variation on the outputs above is normal. Drive sdc in the example above has successfully finished testing and wiping and is giving it's final status summary. If you notice drives' progress percentages or running time failing to advance this may indicate the system has frozen and needs to be restarted. If you suspect a freeze then make a note of which board it is and what the percentages/times indicated are; check it again in 10 minutes and abort testing if there has been no progress.