Difference between revisions of "SCSI Hard Drive Testing"
Jump to navigation
Jump to search
m |
m |
||
| Line 10: | Line 10: | ||
* If successful, boot up & run "badblocks", | * If successful, boot up & run "badblocks", | ||
* syntax = "time badblocks -svw /dev/sd"a or b or c up to p. | * syntax = "time badblocks -svw /dev/sd"a or b or c up to p. | ||
| + | |||
| + | SCSI HD TESTING VS IDE/SATA HD TESTING | ||
| + | = Jumpers = | ||
| + | == Drive ID == | ||
| + | == Other == | ||
| + | |||
| + | = Test Station Repair & Maintenance = | ||
| + | == Controller Cards == | ||
| + | == Cables == | ||
| + | |||
[[Category:Advanced Testing]] | [[Category:Advanced Testing]] | ||
Revision as of 13:05, 16 April 2010
First triage the drives here SCSI Hard Drive Triage
- DISCUSS - test stations config (which controller which cable, external enclosures, logons)
- We are now experimenting with using the HD test script from the network on SCSI Test "Green". SCSI Test "Blue" is still using the SCSI controller utility & Ubuntu (see below).
- DISCUSS - jumpering
- DISCUSS/RESEARCH - SMART FOR SCSI
- Using SCSI controller utility, do low-level format.
- If successful, boot up & run "badblocks",
- syntax = "time badblocks -svw /dev/sd"a or b or c up to p.
SCSI HD TESTING VS IDE/SATA HD TESTING