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] Re: Hard drive RPMs and data speed.
Date: Fri, 28 Oct 2011 16:55:12 +0200	[thread overview]
Message-ID: <4865742.Fs5ycOxmZR@localhost> (raw)
In-Reply-To: <CA+czFiD+UppMYSR8r8a70LF9TidC2wjvqTzf8vP0yYT8YuDuyQ@mail.gmail.com>

Am Donnerstag 27 Oktober 2011, 16:00:09 schrieb Michael Mol:
> On Thu, Oct 27, 2011 at 3:41 PM, Volker Armin Hemmann
> 
> <volkerarmin@googlemail.com> wrote:
> > Am Donnerstag 27 Oktober 2011, 15:17:45 schrieb Michael Mol:
> >> On Thu, Oct 27, 2011 at 2:52 PM, Volker Armin Hemmann
> >> 
> >> <volkerarmin@googlemail.com> wrote:
> >> > Am Donnerstag 27 Oktober 2011, 13:51:47 schrieb Michael Mol:
> >> >> Just don't buy a SAMSUNG drive. I know, I know, everyone has
> >> >> their pet "Don't Buy Hard Drives Made By $x" experience.
> >> >> 
> >> >> Here's mine.
> >> >> 
> >> >> I bought a 1TB SAMSUNG drive for cheap from Newegg at a Black
> >> >> Friday
> >> >> sale a couple years ago. It failed on me. Around the same time,
> >> >> I
> >> >> identified some flaws in the firmware which I considered
> >> >> severe[2].
> >> > 
> >> >  Model=SAMSUNG MMCRE64G5MXP-0VB, FwRev=VBM1901Q,
> >> > SerialNo=S0FDNEAZ600013 Model=SAMSUNG HD502IJ, FwRev=1AA01109,
> >> > SerialNo=S13TJDWQ346413 Model=SAMSUNG HD753LJ, FwRev=1AA01113,
> >> > SerialNo=S13UJ1CQB07158 Model=SAMSUNG HD502HJ, FwRev=1AJ100E5,
> >> > SerialNo=S20BJDWS913888 Model=SAMSUNG HD103SJ, FwRev=1AJ10001,
> >> > SerialNo=S246JD1Z910209 Model=SAMSUNG HD103SJ, FwRev=1AJ100E5,
> >> > SerialNo=S246JDWSA20722
> >> > 
> >> > Oh, yeah it was THAT 2tb drive with the smart bug.
> >> > 
> >> > Which was solved with an easy to do firmware update.
> >> 
> >> I checked at the time. There was no firmware update, and, to my
> >> knowledge, there never was for the drive model that failed on me.
> >> Shortly after my second drive failed, Newegg discontinued selling
> >> model. (The most I remember about the model number can be expressed as
> >> a regex: HD10.*UI. I don't remember the firmware revision.
> >> 
> >> It was the combination of historical problems, personal incidental
> >> experience and terrible customer service that led me to swear off
> >> SAMSUNG drives. Take away any one of those issues from my experiences
> >> at the time, and I'd consider buying another drive from them.
> >> 
> >> You've got six working drives of various sizes, models and firmware
> >> revisions. Good for you. I've got a still-functional 40GB IBM
> >> DeathStar. (It's not powered up right now, but it never failed on me
> >> after five years of use.)
> > 
> > and I had 5 death stars failing on me.
> 
> My point is that the numbers aren't what mattered here. My point is
> that SAMSUNG sold me a shoddy product, replaced it with another
> instance of the the same shoddy product, wouldn't replace it again,
> and never addressed a detailed technical report of a systemic problem
> in the same. Bad tech, bad customer service, and it looked like this
> was a more common scenario than among other manufacturers. All of it
> boiled down to a nasty case of being a bad candidate for spending time
> and money.

Samsung replaced my two drives (one 500gb drive from a known shady series and 
the SSD when the firmware overwrote itself) without any fuss.

Of course, I included the results of their check tool. No problem.

> 
> Did IBM refuse to replace your failing drives? 

no, but 5 out of 5 died and took tons of valuable data with them.

That is the worst case scenario. All other harddrives had no problems at all. 
Different mobos, PSUs - nothing changed the fact that all death stars I ever 
owned died violently - except the last one, because I sold the computer it was 
built in in time.

> Did you include
> detailed technical information that should have allowed them to
> resolve issues leading to those drives' failures? For me, SAMSUNG's
> behavior in the customer service department indicated that I wasn't
> likely to get good service in the future, and the rapidly-failing
> drives (combined with my analysis of the SMART output and the history
> of SMART problems with SAMSUNG drives) indicated to me that I'd need
> to use that customer service department in the future if I bought more
> of their drives.

there was one smart related problem with Samsung in the last year. With their 
2tb drives. Samsung released a firmware patch after they were informed of the 
problem.

Apart from that Samsung drives just work for me - and the people around me.

I also had no problems with drives getting replaced - but the replacing was 
always the problem of my trusted hardware dealer. That is why you buy hdds 
from a trusted, local guy. The rest was the problem of Samsung. They can't 
wiggle out of Germany's warranty laws ;)

> 
> So you've got six working drives, and a drive that works now that you
> patched the firmware. Congrats on choosing a model for which a
> firmware patch was made available (unless that was just luck...).
> Also, good luck if you have a failing drive that was sent to you by
> RMA. It's been a few years; if you're lucky, they may have cleaned up
> their act.

In fact there were two: a 500gb from a known series, and the SSD. Both got 
replaced because both failed in the warranty period. They had no chance but 
had to replace them. It went quickly and without any fuss. I did run their 
check tool and reported the results. No more questions asked. Here is the old 
one, thanks for the new one.

Western Digital - two drives. They worked. They were lousy, noisy, lame, hot, 
but worked.

Seagate: now 3 drives, 1 had to be replaced. It was pretty much dead on 
arrival, with a severe spindle defect. All three worked just fine until I 
replaced them

Toshiba&co have to check my Dell Poweredge what drives are in there...

IBM all death stars I ever owned failed except the last one - which was given 
away (and failed with its new owner). Which is the worst possible outcome. No 
customer support can outweight such a disaster.


-- 
#163933



  reply	other threads:[~2011-10-28 14:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  8:15 [gentoo-user] Hard drive RPMs and data speed Dale
2011-10-27 10:09 ` [gentoo-user] " Nikos Chantziaras
2011-10-27 11:18   ` Michael Mol
2011-10-27 16:24   ` Volker Armin Hemmann
2011-10-27 17:30     ` Dale
2011-10-27 17:51       ` Michael Mol
2011-10-27 18:41         ` Dale
2011-10-27 18:52         ` Volker Armin Hemmann
2011-10-27 19:17           ` Michael Mol
2011-10-27 19:41             ` Volker Armin Hemmann
2011-10-27 20:00               ` Michael Mol
2011-10-28 14:55                 ` Volker Armin Hemmann [this message]
2011-10-28 15:19                   ` Michael Mol
2011-10-28 19:08                     ` Volker Armin Hemmann
2011-10-31 16:21                 ` Alex Schuster
2011-10-31 16:53                   ` Michael Mol
2011-10-31 18:47                   ` Volker Armin Hemmann
2011-10-27 20:36               ` Bill Longman
2011-10-27 20:11         ` Paul Hartman
2011-10-27 18:49       ` Florian Philipp
2011-10-28  4:10         ` Dale
2011-10-28 11:15           ` Mark Knecht
2011-10-28 11:36             ` Dale
2011-10-28 13:40               ` Michael Mol
2011-10-28 14:18             ` Paul Hartman
2011-10-28 15:53               ` Mark Knecht
2011-10-28 19:11                 ` Volker Armin Hemmann
2011-10-28 20:49                   ` Mark Knecht
2011-10-30  5:04                     ` daid kahl
2011-10-31  9:49 ` [gentoo-user] " James Broadhead
2011-10-31 10:58   ` Dale
2011-10-31 14:42     ` James Broadhead

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=4865742.Fs5ycOxmZR@localhost \
    --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