From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive screws
Date: Sat, 06 Jun 2020 09:23:28 +0100 [thread overview]
Message-ID: <20672991.EfDdHjke4D@lenovo.localdomain> (raw)
In-Reply-To: <e214f56d-1363-860a-0b06-6f1859bd7fe5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
On Saturday, 6 June 2020 04:06:54 BST Dale wrote:
> We have reds, purples, greens and all sort of color codes for hard
> drives, maybe they need to color code their screws as well. :/
>
> Now to go find a grab bag or something. This sucks.
Yes, getting the thread wrong and damaging the female thread in the enclosure,
while thinking this /almost/ fits, is not good for your nerves. There are
thread gauges which you can match the pitch of a screw/bolt and help determine
the thread specification, but they are typically used for larger screws/holes:
https://en.wikipedia.org/wiki/Thread_pitch_gauge
A way to determine a *potential* match between screw and hole, is to count the
turns per unit of length and of course the diameter of the hole. Use a
magnifying glass and measure how many turns you can see inside the whole,
while holding a piece of thin wire in it. You need only dip the wire up to
the first 3 threads, but if you can see further in, even better. Then offer
*exactly* the same length of wire against your screws and see which of these
matches.
Then use a reference table to find out from your thread pitch and diameter a
likely specification for your screws; e.g.
http://theoreticalmachinist.com/Threads_UnifiedImperial.aspx
P.S. if you have no magnifying glass you can use binoculars or a scope,
looking from the far end, or the camera of a smart phone, or an SLR.
> P. S. It seems those older not working enclosures may have caused issues
> with my drive. I'm having to dd the first one, redo the partitions and
> still having issues getting it to work. May be a doorstop when this is
> over.
You're not saying what problems these are, but smartctl should report anything
amiss with the drive internals. Otherwise, check power supply and loose
connectors.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-06 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 2:06 [gentoo-user] Hard drive screws Dale
2020-06-06 2:24 ` William Kenworthy
2020-06-06 2:39 ` Jack
2020-06-06 3:06 ` Dale
2020-06-06 8:23 ` Michael [this message]
2020-06-06 14:22 ` antlists
2020-06-06 19:14 ` J. Roeleveld
2020-06-07 7:41 ` antlists
2020-06-07 9:50 ` J. Roeleveld
2020-06-07 12:25 ` antlists
2020-06-07 21:24 ` Dale
2020-06-08 1:59 ` james
2020-06-08 2:50 ` Dale
2020-06-06 12:42 ` karl
2020-07-18 4:07 ` Dale
2020-07-18 7:16 ` karl
2020-07-18 11:35 ` Dale
2020-07-18 12:03 ` karl
2020-07-18 12:29 ` Dale
2020-07-18 13:08 ` [gentoo-user] " Grant Edwards
2020-07-18 13:27 ` Dale
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=20672991.EfDdHjke4D@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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