From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] mkfs somewhere else?
Date: Sun, 8 Feb 2015 15:10:58 -0500 (EST) [thread overview]
Message-ID: <20150208201058.488D51DE414@lignose.oclsc.org> (raw)
Would anyone know if it's still possible to just replace the platters and
clean the heads?
If the heads are really crashed, the only safe course is
to replace both the damaged heads and the damaged disk pack.
Anything else admits a substantial risk of carrying the
crash forward.
Cleaning the heads probably isn't an option; when they
crash, they don't just pick up material from the disk
platter, they may themselves be damaged enough that sharp
bits of the heads themselves are sticking out.
Norman Wilson
Toronto ON
next reply other threads:[~2015-02-08 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 20:10 Norman Wilson [this message]
2015-02-12 15:29 ` Dave Horsfall
2015-02-12 15:50 ` cowan
2015-02-12 19:18 ` random832
-- strict thread matches above, loose matches on Subject: below --
2015-02-08 20:20 Norman Wilson
2015-02-08 20:12 Norman Wilson
2015-02-08 6:22 Jacob Ritorto
2015-02-08 6:36 ` Dave Horsfall
2015-02-08 7:03 ` Jacob Ritorto
2015-02-08 7:15 ` Jacob Ritorto
2015-02-08 17:34 ` Dave Horsfall
2015-02-08 18:52 ` Jacob Ritorto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150208201058.488D51DE414@lignose.oclsc.org \
--to=norman@oclsc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).