From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Testing a used hard drive to make SURE it is good.
Date: Mon, 15 Jun 2020 13:04:53 -0700 [thread overview]
Message-ID: <CAK2H+ee1QPQCm+3YOhSEoJfbJeAHrV0ZB-ezbuH448YqW8V6tg@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_=CVgk20k17CNRJGgXMY0+40FpYQESQEhP9Bc2qc3sgHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Mon, Jun 15, 2020 at 1:01 PM Rich Freeman <rich0@gentoo.org> wrote:
>
> On Mon, Jun 15, 2020 at 3:54 PM Mark Knecht <markknecht@gmail.com> wrote:
> >
> > The SMART test, long version, will do a very reasonable job catching
problems. Run it 2 or 3 times if it makes you feel better.
> >
> > Chris's suggestion about Spinrite is another option but it is slow,
slow, slow. Might take you weeks? On a drive that large if it worked at all.
>
> Is spinrite really still of any use in this era? I'm skeptical of
> that. Maybe in the pre-IDE days it made more sense.
>
I used it a few years ago on some 2TB or 3TB drives, more out of curiosity
when I found my old license. Other than that I agree with you Rich
[-- Attachment #2: Type: text/html, Size: 941 bytes --]
next prev parent reply other threads:[~2020-06-15 20:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 16:07 [gentoo-user] Testing a used hard drive to make SURE it is good Dale
2020-06-15 19:20 ` Spackman, Chris
2020-06-15 19:54 ` Mark Knecht
2020-06-15 20:00 ` Rich Freeman
2020-06-15 20:04 ` Mark Knecht [this message]
2020-06-16 7:34 ` Dale
2020-06-16 8:22 ` Wols Lists
2020-06-16 9:04 ` Dale
2020-06-16 11:02 ` Wols Lists
2020-06-16 11:26 ` Dale
2020-06-16 11:36 ` Michael
2020-06-16 12:25 ` Rich Freeman
2020-06-16 23:38 ` antlists
2020-06-17 9:47 ` Rich Freeman
2020-06-23 16:14 ` Sid Spry
2020-06-23 17:20 ` Rich Freeman
2020-06-23 18:44 ` Sid Spry
2020-06-16 13:14 ` Dale
2020-06-16 23:24 ` antlists
2020-06-17 4:47 ` Dale
2020-06-17 12:32 ` Wols Lists
2020-06-17 12:04 ` Rich Freeman
2020-06-16 8:29 ` Neil Bothwick
2020-06-16 8:52 ` Dale
2020-06-15 19:54 ` [gentoo-user] " Grant Edwards
2020-06-15 20:04 ` Grant Edwards
2020-06-15 23:03 ` [gentoo-user] " madscientistatlarge
2020-06-15 23:18 ` David Haller
2020-06-16 7:17 ` Dale
2020-06-16 7:32 ` William Kenworthy
2020-06-16 7:37 ` Dale
2020-06-17 15:27 ` David Haller
2020-06-18 8:07 ` Dr Rainer Woitok
2020-06-23 16:08 ` Sid Spry
2020-06-23 16:38 ` [gentoo-user] " Grant Edwards
2020-06-23 16:41 ` Sid Spry
2020-06-23 17:26 ` Dale
2020-06-23 18:32 ` Sid Spry
2020-06-23 19:37 ` Dale
2020-06-23 20:03 ` Rich Freeman
2020-06-24 4:26 ` Wols Lists
2020-06-18 9:14 ` [gentoo-user] " Dale
2020-06-22 1:52 ` Pengcheng Xu
2020-06-22 2:15 ` Dale
2020-06-22 19:10 ` David Haller
2020-06-22 20:29 ` Dale
2020-06-22 22:59 ` David Haller
2020-06-23 4:18 ` Dale
2020-06-17 6:02 ` Dale
2020-06-20 9:50 ` 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=CAK2H+ee1QPQCm+3YOhSEoJfbJeAHrV0ZB-ezbuH448YqW8V6tg@mail.gmail.com \
--to=markknecht@gmail.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