Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #177505
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: How to fix I/O errors? |
| Date | 2017-02-06 23:20 +0100 |
| Message-ID | <t7ZND-2v6-1@gated-at.bofh.it> (permalink) |
| References | <t6wNI-No-25@gated-at.bofh.it> <t7e2l-4XW-11@gated-at.bofh.it> <t7TRT-6RC-7@gated-at.bofh.it> <t7VgZ-80j-1@gated-at.bofh.it> |
| Organization | less than infinite |
Gene Heskett composed on 2017-02-06 12:28 (UTC-0500): > That cold spare will eventually develop stiction, seizing the parked haed > to the surface of the disk solidly enough that the disk motor cannot > break it loose to spin the disk up. Such is best treated by hooking up > the cables, but holding the drive in your hand so that you can turn on > the power, and within a couple seconds, give the drive a good sideways > blow on a corner with the ball of the wrist so the drive housing/casting > is caused to rotate a few degrees around the axis of the disk, breaking > the stiction so the spindle motor can spin it up. The theory is that the > drive frame rotates when you drive it by hitting the corner, but the > disk doesn't, breaking the stiction seal. The other theory is the motor got too weak to start the platters in motion. It wouldn't surprise me that these things have separate electronics for startup and for maintain, and that something in startup simply expires to cause spinup failure. The first HD I ever bought, a 3.5" "full-height" SCSI-I 80MB Seagate in 1990, acquired the won't spin up problem a month after its 12 month warranty expired. I avoided the problem a long time via a UPS, but eventually an extended power outage claimed it permanently. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:10 +0100
Re: How to fix I/O errors? <tomas@tuxteam.de> - 2017-02-02 22:30 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:50 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 23:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-03 07:30 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 08:40 +0100
Re: How to fix I/O errors? Mark Fletcher <mark27q1@gmail.com> - 2017-02-03 16:00 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:40 +0100
Re: How to fix I/O errors? Jonathan Dowland <jmtd@debian.org> - 2017-02-07 12:00 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:50 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 08:20 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-06 22:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 23:40 +0100
Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-04 16:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 20:20 +0100
Re: How to fix I/O errors? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-02-06 17:00 +0100
Re: How to fix I/O errors? Gene Heskett <gheskett@shentel.net> - 2017-02-06 18:30 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100
Re: How to fix I/O errors? Felix Miata <mrmazda@earthlink.net> - 2017-02-06 23:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100
csiph-web