public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Want to seriously test a NEW hard drive
Date: Mon, 6 Aug 2012 11:49:42 +0200	[thread overview]
Message-ID: <CAGK8UzA9HouLFTE81ONqW26qckVwSgm8HcZsaTBp4gLm5SgmUQ@mail.gmail.com> (raw)
In-Reply-To: <501F9179.8000504@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]

What do you gain if you abuse your drive so hard that its lifetime is
severly impacted?
Am 06.08.2012 11:47 schrieb "Dale" <rdalek1967@gmail.com>:

> Dale wrote:
> > Howdy,
> >
> > I finally got me a 3Tb drive on the way.  Should be here Wednesday.  I
> > have seen some reviews where it would not work right.  I think some of
> > it may be BIOS related since some BIOS's don't like drives that large.
> > Anyway, I want to test this thing real good to really make sure it is up
> > to the task before putting my data on it.  It's going to be so much
> > data, there is really no way to do back-ups at this point.  Come on, 2
> > to 3Tbs on 4Gb DVDs.  Really?  lol  Maybe a external drive later on but
> > for now, well.
> >
> > I have heard of bonnie and friends.  I also think dd could do some
> > testing too.  Is there any other way to give this a good work and see if
> > it holds up?  Oh, helpful hints with Bonnie would be great too.  I have
> > never used it before.  Maybe someone has some test that is really brutal.
> >
> > Thanks
> >
> > Dale
> >
> > :-)  :-)
> >
>
> I seem to have got a few really good responses to my question.  Since I
> really want to test this drive really hard, I'll try them all.  lol  If
> it survives a few runs of all this, maybe it is going to live.  Like the
> one with the script too.  May have to edit for my needs but certainly a
> GREAT start.
>
> While at it, I found a lot of references to the flood in Japan or I
> assume it was Japan.  Anyone think this could still be a problem?
> Should they all be flushed out of the system by now?  Pardon the flush
> term there.  ;-)
>
> Linky:
>
>
> http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1310560&CatId=4357
>
> Please, no hard drive brand flame wars.  Seagates fail, WD fails, they
> all fail at some point.  We all know that already.  This is what I got
> so it is what it is.  :-D  That is why I want to test this thing like a
> wild man BEFORE putting anything on it.  If it has a issue, hopefully
> the test will bring that to the front now instead of later.
>
> Waiting on Wednesday to get here now.
>
> Dale
>
> :-)  :-)
>
> P. S.  What is a good way to back up something this large BESIDES
> another drive the same size or larger?  I thought about getting a blue
> ray burner but even that will take a lot of media.  Another drive is all
> I can think of myself.
>
> --
> I am only responsible for what I said ... Not for what you understood or
> how you interpreted my words!
>
>
>

[-- Attachment #2: Type: text/html, Size: 3155 bytes --]

  reply	other threads:[~2012-08-06  9:51 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 12:45 [gentoo-user] Want to seriously test a NEW hard drive Dale
2012-08-05 12:53 ` Mark Knecht
2012-08-05 16:05 ` Alex Schuster
2012-08-05 20:02 ` victor romanchuk
2012-08-06  9:42 ` Dale
2012-08-06  9:49   ` Volker Armin Hemmann [this message]
2012-08-06 10:14     ` Dale
2012-08-06 10:48       ` Hinnerk van Bruinehsen
2012-08-06 12:17         ` Mick
2012-08-06  9:57   ` Mick
2012-08-06 10:25     ` Dale
2012-08-06 11:01   ` Neil Bothwick
2012-08-06 11:25     ` Dale
2012-08-06 11:51       ` Neil Bothwick
2012-08-06 11:58       ` Michael Hampicke
2012-08-06 12:01       ` Mick
2012-08-06 15:17 ` Paul Hartman
2012-08-07 22:26   ` Dale
2012-08-07 22:39     ` Mark Knecht
2012-08-07 23:05       ` Dale
2012-08-08  0:31         ` Mark Knecht
2012-08-07 23:06       ` Peter Humphrey
2012-08-08  0:32         ` Mark Knecht
2012-08-08  7:06           ` Peter Humphrey
2012-08-07 23:07     ` Paul Hartman
2012-08-08  2:19       ` Dale
2012-08-08  3:55         ` William Kenworthy
2012-08-08  4:18           ` Dale
2012-08-08  5:42             ` William Kenworthy
2012-08-08  6:24               ` Dale
2012-08-08  4:02         ` Adam Carter
2012-08-08  4:16           ` William Kenworthy
2012-08-08  4:21             ` Adam Carter
2012-08-08 12:10               ` Mick
2012-08-08 12:53                 ` Dale
2012-08-10 13:40                   ` Mick
2012-08-08 15:10         ` Paul Hartman
2012-08-08 15:39           ` Dale
2012-08-09 13:30         ` Alex Schuster
2012-08-09 13:53           ` Dale
2012-08-09 15:29             ` Alan McKinnon
2012-08-08 14:48   ` Ricardo Jesus
2012-08-08 18:02 ` Dale
2012-08-08 18:25   ` Mark Knecht
2012-08-08 22:09     ` Dale
2012-08-09  3:22       ` Dale
2012-08-09  6:13         ` Yohan Pereira
2012-08-09  6:31           ` Dale
2012-08-09  8:46         ` Neil Bothwick
2012-08-09  9:35           ` Dale
2012-08-09 10:58             ` Neil Bothwick
2012-08-09 12:02               ` Dale
2012-08-10  8:53                 ` 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=CAGK8UzA9HouLFTE81ONqW26qckVwSgm8HcZsaTBp4gLm5SgmUQ@mail.gmail.com \
    --to=volkerarmin@googlemail.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