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: Harddisk trouble ... or not yet?
Date: Wed, 26 May 2010 19:59:32 +0200	[thread overview]
Message-ID: <201005261959.32671.volkerarmin@googlemail.com> (raw)
In-Reply-To: <20100526170934.GA5120@solfire>

On Mittwoch 26 Mai 2010, meino.cramer@gmx.de wrote:
> Grant Edwards <grant.b.edwards@gmail.com> [10-05-26 17:19]:
> > On 2010-05-26, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
> > >  [...] I have two WDC WD10EARS-00Y5B1 (pasted from
> > >  hdparm -i) harddisk (1TB, advanced format 4096 kb sectors).
> > >
> > >[...]
> > >
> > >     dd if=/dev/sda of=/dev/sdb bs=8192
> > >  
> > >  which gave me a LOT of I/O errors after a short time.
> > >
> > >[...]
> > >
> > >  From what kernel version the new advanced format
> > >  of the hd is fully supported ?
> > 
> > My understanding is that the new format doesn't cause I/O errors, just
> > slower transfer rates if you format with disk clusters that aren't
> > aligned on 4K boundaries.  I'm not aware of any "support" in the
> > kernel.
> > 
> > >  Are there other reasons -- beside defective hardware -- for
> > >  the failing dd and how can I fix them ?
> > 
> > In my experience, I/O errors have always been hardware problems
> > (usually a failing drive, but it could also be a faulty cable or
> > connector).
> 
> Hi
> 
> If it happens again, I will try to save the error list and post it
> here...
> 
> May be: The WD-harddiscs are SATA2 my controllers are "only" SATA1...
> is it  this, which cause the problems?
> 
> Best regards,
> mcc

usually it shouldn't.



  reply	other threads:[~2010-05-26 17:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  3:15 [gentoo-user] Harddisk trouble ... or not yet? meino.cramer
2010-05-26  6:38 ` [gentoo-user] howto increase INODE kitti jaisong
2010-05-26  7:09   ` Bert Swart
2010-05-26 11:16   ` Volker Armin Hemmann
2010-05-26 12:55   ` Alex Schuster
2010-05-26 11:17 ` [gentoo-user] Harddisk trouble ... or not yet? Volker Armin Hemmann
2010-05-26 14:22 ` [gentoo-user] " Grant Edwards
2010-05-26 17:09   ` meino.cramer
2010-05-26 17:59     ` Volker Armin Hemmann [this message]
2010-05-26 19:05       ` Neil Bothwick
2010-05-26 19:13         ` Volker Armin Hemmann
2010-05-26 20:40           ` Neil Bothwick
2010-05-27  0:19             ` meino.cramer
2010-05-27  1:48               ` walt
2010-05-27  2:43                 ` meino.cramer
2010-05-27  3:52                   ` W.Kenworthy
2010-05-27  4:29                     ` Iain Buchanan
2010-05-27  9:39                   ` Andrea Conti
2010-05-28  1:54                     ` meino.cramer
2010-05-28 23:24                       ` walt
2010-05-29  3:47                         ` meino.cramer
2010-05-29  7:25                       ` Andrea Conti
2010-05-29  8:16                         ` Volker Armin Hemmann
2010-05-29 19:05                           ` Alan McKinnon
2010-05-29 20:08                             ` Volker Armin Hemmann
2010-05-29  8:56                         ` meino.cramer
2010-05-29 19:13                           ` Andrea Conti
2010-05-27  8:17               ` Stroller

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=201005261959.32671.volkerarmin@googlemail.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