[gentoo-user] Harddisk trouble ... or not yet?

[gentoo-user] Harddisk trouble ... or not yet?

[meino.cramer]

Hi,

 currently I set up a freshly new gentoo system "from scratch"
 on another harddisk.

 For that purpose I have two WDC WD10EARS-00Y5B1 (pasted from 
 hdparm -i) harddisk (1TB, advanced format 4096 kb sectors).
 One harddisk is currently holding the gento system, the other
 one is intended as a bare plain copy of the other one (a backup
 while setting up the system).

 With an old KNOPPIX dvd I tried to copy the first hd onto
 the other one with

    dd if=/dev/sda of=/dev/sdb bs=8192

 which gave me a LOT of I/O errors after a short time.

 Still hopeing, that my hardware (motherboard/chipset/bios) and
 the hd are ok I am trying to figure out, what the reason was
 for that...

 My motherboard is an Asus AV8.
 


 From what kernel version the new advanced format
 of the hd is fully supported ?
 
 Are there other reasons -- beside defective hardware -- for
 the failing dd and how can I fix them ?




 Thank you very much in advance for any help!
 best regards
 mcc

 
 

-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] howto increase INODE

[kitti jaisong]

Hi All,

I just install sparc machine. i found error "failed: No space left on device 
(28)" when i check inode by df -i command
livecd ~ # df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
tmpfs                 129412    4684  124728    4% /
/dev/hda                   0       0       0    -  /mnt/cdrom
/dev/loop0             14486   14486       0  100% /mnt/livecd
udev                  129412    1399  128013    2% /dev
tmpfs                 129412      81  129331    1% /mnt/livecd/lib/firmware
tmpfs                 129412       1  129411    1% /mnt/livecd/usr/portage
/dev/sda1              32768    2407   30361    8% /mnt/gentoo
/dev/sda4             131072  131072       0  100% /mnt/gentoo/usr
/dev/sda5             131072    3007  128065    3% /mnt/gentoo/var
/dev/sda6            1896832      12 1896820    1% /mnt/gentoo/home


livecd ~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                1012M   36M  976M   4% /
/dev/hda               58M   58M     0 100% /mnt/cdrom
/dev/loop0             49M   49M     0 100% /mnt/livecd
udev                   10M  384K  9.7M   4% /dev
tmpfs                1012M  4.0M 1008M   1% /mnt/livecd/lib/firmware
tmpfs                1012M     0 1012M   0% /mnt/livecd/usr/portage
/dev/sda1             504M   55M  424M  12% /mnt/gentoo
/dev/sda4             2.0G  952M  963M  50% /mnt/gentoo/usr
/dev/sda5             2.0G   83M  1.8G   5% /mnt/gentoo/var
/dev/sda6              29G  173M   27G   1% /mnt/gentoo/home

How to increase or solve this problem

Best Regards,

ti

----- Original Message ----- 
From: <meino.cramer@gmx.de>
To: "Gentoo" <gentoo-user@lists.gentoo.org>
Sent: Wednesday, May 26, 2010 10:15 AM
Subject: [gentoo-user] Harddisk trouble ... or not yet?


>
> Hi,
>
> currently I set up a freshly new gentoo system "from scratch"
> on another harddisk.
>
> For that purpose I have two WDC WD10EARS-00Y5B1 (pasted from
> hdparm -i) harddisk (1TB, advanced format 4096 kb sectors).
> One harddisk is currently holding the gento system, the other
> one is intended as a bare plain copy of the other one (a backup
> while setting up the system).
>
> With an old KNOPPIX dvd I tried to copy the first hd onto
> the other one with
>
>    dd if=/dev/sda of=/dev/sdb bs=8192
>
> which gave me a LOT of I/O errors after a short time.
>
> Still hopeing, that my hardware (motherboard/chipset/bios) and
> the hd are ok I am trying to figure out, what the reason was
> for that...
>
> My motherboard is an Asus AV8.
>
>
>
> From what kernel version the new advanced format
> of the hd is fully supported ?
>
> Are there other reasons -- beside defective hardware -- for
> the failing dd and how can I fix them ?
>
>
>
>
> Thank you very much in advance for any help!
> best regards
> mcc
>
>
>
>
> -- 
> Please don't send me any Word- or Powerpoint-Attachments
> unless it's absolutely neccessary. - Send simply Text.
> See http://www.gnu.org/philosophy/no-word-attachments.html
> In a world without fences and walls nobody needs gates and windows.
>
> 

Re: [gentoo-user] howto increase INODE

[Bert Swart]

On Wed, May 26, 2010 at 01:38:46PM +0700, kitti jaisong wrote:
> Hi All,
> 
> I just install sparc machine. i found error "failed: No space left on device 
> (28)" when i check inode by df -i command
> livecd ~ # df -i
> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> tmpfs                 129412    4684  124728    4% /
> /dev/hda                   0       0       0    -  /mnt/cdrom
> /dev/loop0             14486   14486       0  100% /mnt/livecd
> udev                  129412    1399  128013    2% /dev
> tmpfs                 129412      81  129331    1% /mnt/livecd/lib/firmware
> tmpfs                 129412       1  129411    1% /mnt/livecd/usr/portage
> /dev/sda1              32768    2407   30361    8% /mnt/gentoo
> /dev/sda4             131072  131072       0  100% /mnt/gentoo/usr
> /dev/sda5             131072    3007  128065    3% /mnt/gentoo/var
> /dev/sda6            1896832      12 1896820    1% /mnt/gentoo/home
> 
> 
> livecd ~ # df -h
> Filesystem            Size  Used Avail Use% Mounted on
> tmpfs                1012M   36M  976M   4% /
> /dev/hda               58M   58M     0 100% /mnt/cdrom
> /dev/loop0             49M   49M     0 100% /mnt/livecd
> udev                   10M  384K  9.7M   4% /dev
> tmpfs                1012M  4.0M 1008M   1% /mnt/livecd/lib/firmware
> tmpfs                1012M     0 1012M   0% /mnt/livecd/usr/portage
> /dev/sda1             504M   55M  424M  12% /mnt/gentoo
> /dev/sda4             2.0G  952M  963M  50% /mnt/gentoo/usr
> /dev/sda5             2.0G   83M  1.8G   5% /mnt/gentoo/var
> /dev/sda6              29G  173M   27G   1% /mnt/gentoo/home
> 
> How to increase or solve this problem
Only things I can think of:
1. delete some files (probably not possible on usr partition) ;
2. backup your partition, and rerun mkfs.ext2 or mkfs.ext3 and
use the -i option (see man page)

Some advice is given in the handbook on creating partitions to
install gentoo.

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part1_chap4

Regards,
Bert

> 
> Best Regards,
> 
> ti
> 
> ----- Original Message ----- 
> From: <meino.cramer@gmx.de>
> To: "Gentoo" <gentoo-user@lists.gentoo.org>
> Sent: Wednesday, May 26, 2010 10:15 AM
> Subject: [gentoo-user] Harddisk trouble ... or not yet?
> 
> 
> >
> > Hi,
> >
> > currently I set up a freshly new gentoo system "from scratch"
> > on another harddisk.
> >
> > For that purpose I have two WDC WD10EARS-00Y5B1 (pasted from
> > hdparm -i) harddisk (1TB, advanced format 4096 kb sectors).
> > One harddisk is currently holding the gento system, the other
> > one is intended as a bare plain copy of the other one (a backup
> > while setting up the system).
> >
> > With an old KNOPPIX dvd I tried to copy the first hd onto
> > the other one with
> >
> >    dd if=/dev/sda of=/dev/sdb bs=8192
> >
> > which gave me a LOT of I/O errors after a short time.
> >
> > Still hopeing, that my hardware (motherboard/chipset/bios) and
> > the hd are ok I am trying to figure out, what the reason was
> > for that...
> >
> > My motherboard is an Asus AV8.
> >
> >
> >
> > From what kernel version the new advanced format
> > of the hd is fully supported ?
> >
> > Are there other reasons -- beside defective hardware -- for
> > the failing dd and how can I fix them ?
> >
> >
> >
> >
> > Thank you very much in advance for any help!
> > best regards
> > mcc
> >
> >
> >
> >
> > -- 
> > Please don't send me any Word- or Powerpoint-Attachments
> > unless it's absolutely neccessary. - Send simply Text.
> > See http://www.gnu.org/philosophy/no-word-attachments.html
> > In a world without fences and walls nobody needs gates and windows.
> >
> > 
> 
> 

Re: [gentoo-user] howto increase INODE

[Volker Armin Hemmann]

On Mittwoch 26 Mai 2010, kitti jaisong wrote:
> Hi All,
> 
> I just install sparc machine. i found error "failed: No space left on
> device (28)" when i check inode by df -i command

don't hijack other people's threads.

Re: [gentoo-user] Harddisk trouble ... or not yet?

[Volker Armin Hemmann]

don't use df. Use cp -a. 

Also, the exact errors would be helpfull.

Re: [gentoo-user] howto increase INODE

[Alex Schuster]

kitti jaisong writes:

> I just install sparc machine. i found error "failed: No space left on
> device (28)" when i check inode by df -i command
[...]
> /dev/sda4             2.0G  952M  963M  50% /mnt/gentoo/usr
> /dev/sda5             2.0G   83M  1.8G   5% /mnt/gentoo/var
> /dev/sda6              29G  173M   27G   1% /mnt/gentoo/home
> 
> How to increase or solve this problem

2 GB for a /usr partition looks quite small to me, but may by okay for a 
small installation. But to increase the number of inodes, you have backup 
/usr, re-create the partition with more inodes, and copy the stuff back.

If you do not want to do so, you could move things to your home partition. 
I'd move /usr/portage first (and change the location in make.conf), that 
has many small files eating up many inodes. And if space is still getting 
small, just move other things like/usr/src, and set a symlink so /usr/src 
is still a valid path.

Oh, and please:
  - Do not hijack threads.
  - Do not quote stuff that has absolutely no relevance, like the
    original posting you replied to, instead of starting a new one.

 
> ----- Original Message -----
> From: <meino.cramer@gmx.de>
> To: "Gentoo" <gentoo-user@lists.gentoo.org>
> Sent: Wednesday, May 26, 2010 10:15 AM
> Subject: [gentoo-user] Harddisk trouble ... or not yet?

[BIG SNIP!]


	Wonko

[gentoo-user] Re: Harddisk trouble ... or not yet?

[Grant Edwards]

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).

-- 
Grant Edwards               grant.b.edwards        Yow! PIZZA!!
                                  at               
                              gmail.com            

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

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).
> 
> -- 
> Grant Edwards               grant.b.edwards        Yow! PIZZA!!
>                                   at               
>                               gmail.com            
> 

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

-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Volker Armin Hemmann]

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.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Neil Bothwick]

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

On Wed, 26 May 2010 19:59:32 +0200, Volker Armin Hemmann wrote:

> > May be: The WD-harddiscs are SATA2 my controllers are "only" SATA1...
> > is it  this, which cause the problems?

> usually it shouldn't.

It has done for me in the past. SATA2 drives usually have a jumper to
switch them to SATA1.


-- 
Neil Bothwick

Q-Tip: When an omnipotent alien gives you advice.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Volker Armin Hemmann]

On Mittwoch 26 Mai 2010, Neil Bothwick wrote:
> On Wed, 26 May 2010 19:59:32 +0200, Volker Armin Hemmann wrote:
> > > May be: The WD-harddiscs are SATA2 my controllers are "only" SATA1...
> > > is it  this, which cause the problems?
> > 
> > usually it shouldn't.
> 
> It has done for me in the past. SATA2 drives usually have a jumper to
> switch them to SATA1.

that is why I used 'usually' and 'shouldn't'. But that is not a sata1 or sata2 
jumper but a speed jumper.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Neil Bothwick]

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

On Wed, 26 May 2010 21:13:06 +0200, Volker Armin Hemmann wrote:

> that is why I used 'usually' and 'shouldn't'.

Have you considered a career in politics? ;-)


-- 
Neil Bothwick

A clean desk is a sign of a cluttered desk drawer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

Neil Bothwick <neil@digimed.co.uk> [10-05-27 02:04]:
> On Wed, 26 May 2010 21:13:06 +0200, Volker Armin Hemmann wrote:
> 
> > that is why I used 'usually' and 'shouldn't'.
> 
> Have you considered a career in politics? ;-)
> 
> 
> -- 
> Neil Bothwick
> 
> A clean desk is a sign of a cluttered desk drawer.

Oh, uhh...I did not want to start a political discussion here... ;O)

In the meantime I did the copy thingy ("dd if=....") again with
a new KNOPPIX dvd (kernel 2.6.32.something) and it copied the
whole disk in 204min without a single I/O error.

Now I did not know exactly what think about it...
(which again is like politics ;)

Is there any way to check the disk without damaging its
contents?

best regards,
mcc




-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] Re: Harddisk trouble ... or not yet?

[walt]

On 05/26/2010 05:19 PM, meino.cramer@gmx.de wrote:

> Is there any way to check the disk without damaging its
> contents?

Do you know about SMART?  Install sys-apps/smartmontools if you
don't already have it, and read the manpage for smartctl.

I add smartd to my default runlevel so the hard drives will test
themselves once every month and log the test results in syslog.

Hm.  I just noticed that smartd isn't actually running, so I need
to do some debugging now.  But that's the idea, anyway.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

walt <w41ter@gmail.com> [10-05-27 04:08]:
> On 05/26/2010 05:19 PM, meino.cramer@gmx.de wrote:
> 
> >Is there any way to check the disk without damaging its
> >contents?
> 
> Do you know about SMART?  Install sys-apps/smartmontools if you
> don't already have it, and read the manpage for smartctl.
> 
> I add smartd to my default runlevel so the hard drives will test
> themselves once every month and log the test results in syslog.
> 
> Hm.  I just noticed that smartd isn't actually running, so I need
> to do some debugging now.  But that's the idea, anyway.
> 

Hi,

yes, I know smart...

I was more thinking of a tool, which test the whole disc surface
and reports every bad sector.

Smarts is more of statistical kind: It counts events and tries
to calculate dooms day from that ;)


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[W.Kenworthy]

On Thu, 2010-05-27 at 04:43 +0200, meino.cramer@gmx.de wrote:
> walt <w41ter@gmail.com> [10-05-27 04:08]:
> > On 05/26/2010 05:19 PM, meino.cramer@gmx.de wrote:
> > 
> > >Is there any way to check the disk without damaging its
> > >contents?
> > 
> > Do you know about SMART?  Install sys-apps/smartmontools if you
> > don't already have it, and read the manpage for smartctl.
> > 
> > I add smartd to my default runlevel so the hard drives will test
> > themselves once every month and log the test results in syslog.
> > 
> > Hm.  I just noticed that smartd isn't actually running, so I need
> > to do some debugging now.  But that's the idea, anyway.
> > 
> 
> Hi,

> yes, I know smart...
> 
> I was more thinking of a tool, which test the whole disc surface
> and reports every bad sector.
> 
> Smarts is more of statistical kind: It counts events and tries
> to calculate dooms day from that ;)
> 
> 

Not so easy (coming in late on this thread, sorry if its been covered)

Modern hard drives insulate the outside from whats actually happening
internally.  They have a number of spare locations they can swap into
use when a bad patch develops.  This is invisible except to something
like smart reporting.  Rule of thumb - when a modern drive starts
showing bad sectors to the outside world, its already well past its use
by date.

So something like SMART is the only way for the average Joe to get the
health of a drive.

Google has lots on this sort of thing

BillK

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Iain Buchanan]

On Thu, 2010-05-27 at 11:52 +0800, W.Kenworthy wrote:

> So something like SMART is the only way for the average Joe to get the
> health of a drive.
> 
> Google has lots on this sort of thing

That sentence is correct in more than one way!  "Google the generic term
for any web page found via searching on Google" no doubt has lots on
this sort of thing, but so does "Google the company".

I remember reading a SlasDot post about the results of their disk
monitoring over the last x years, and they use and monitor a lot of
disks.

*looking*

Here's the full study: http://labs.google.com/papers/disk_failures.html

>From the abstract: "...we conclude that models based on SMART parameters
alone are unlikely to be useful for predicting individual drive
failures. Surprisingly, we found that temperature and activity levels
were much less correlated with drive failures than previously reported."

I recall there were some summaries of this article, but I can't find
them right now.

An interesting read.  Basically, you might not be able to get reliable
warnings of impending failures.

Keep Good Backups (so say we all)

-- 
Iain Buchanan <iaindb at netspace dot net dot au>

The naked truth of it is, I have no shirt.
		-- William Shakespeare, "Love's Labour's Lost"

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Stroller]

On 27 May 2010, at 01:19, meino.cramer@gmx.de wrote:
> ...
> Is there any way to check the disk without damaging its
> contents?


If you have copied from /dev/sda to /dev/sdb then `md5sum /dev/sda / 
dev/sdb` will compare both drives. You're probably safest to compare a  
partition at a time `md5sum /dev/sda1 /dev/sdb1` to make sure the free  
space at the end of the drive don't throw things off. I'm pretty sure  
I've used this successfully.

Stroller.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Andrea Conti]

> I was more thinking of a tool, which test the whole disc surface
> and reports every bad sector.

badblocks -wvs (which takes forever, but in my experience is quite good
at make failing disks actually fail ;)

During the test you can monitor the smart attributes (smartctl -A, esp.
the reallocated sector count) to see what is actually going on.

Warning: backup your data as badblocks in destructive mode will wipe the
disk clean.

Also, you can run a SMART offline long test (smartctl -t long), which
will scan the whole surface. But on most disks the test stops at the
first error, so you don't get a complete picture.

> Smarts is more of statistical kind: It counts events and tries
> to calculate dooms day from that ;)

That's just a part of it. Attribute values and the error log actually
provide useful information about the status of the disk.

andrea

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

Andrea Conti <alyf@alyf.net> [10-05-27 17:20]:
> > I was more thinking of a tool, which test the whole disc surface
> > and reports every bad sector.
> 
> badblocks -wvs (which takes forever, but in my experience is quite good
> at make failing disks actually fail ;)
> 
> During the test you can monitor the smart attributes (smartctl -A, esp.
> the reallocated sector count) to see what is actually going on.
> 
> Warning: backup your data as badblocks in destructive mode will wipe the
> disk clean.
> 
> Also, you can run a SMART offline long test (smartctl -t long), which
> will scan the whole surface. But on most disks the test stops at the
> first error, so you don't get a complete picture.
> 
> > Smarts is more of statistical kind: It counts events and tries
> > to calculate dooms day from that ;)
> 
> That's just a part of it. Attribute values and the error log actually
> provide useful information about the status of the disk.
> 
> andrea
> 

"Badblocks" is running since yesterday on one of both harrdisks (and is still
running...for more then 10 hours now (1TB to check)) and I 
got thise errors visible via dmesg:


ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
         res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:f5:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
         res 51/84:0f:80:f5:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:40:d4/00:00:00:00:00/e0 tag 0 dma 65536 in
         res 51/84:6f:80:40:d4/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:a1:40/00:00:00:00:00/e1 tag 0 dma 65536 in
         res 51/84:2f:80:a1:40/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

(I dont know, where the report sequence starts, so I put some
repetitions here in) 

They do not grow in count and badblocks did not report anything
onto the console where I start it.

I started it with

    solfire:/root>badblocks -v -n /dev/sda

At midnight, the DSL connection had been cut by the provider
and automagically reestablished by my linux box, but I dont
think, that this has something do to with it.
Additionall smartd is running in the background...

Smartd's smartd.conf contains this (first try...;)

/dev/sda -a -d sat -o on
/dev/sdb -a -d sat -o on

What the heck is going on in my system?

Thanks a lot in advance for any help !

Best regards,
worried,
mcc


-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

[gentoo-user] Re: Harddisk trouble ... or not yet?

[walt]

On 05/27/2010 06:54 PM, meino.cramer@gmx.de wrote:

> ata1.00: configured for UDMA/33

I know nothing about the new large-sector disks, but the line above makes
me worried that the disk driver doesn't know any more than I do :)

Anyone know if that is the expected response from the disk driver?

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

walt <w41ter@gmail.com> [10-05-29 03:21]:
> On 05/27/2010 06:54 PM, meino.cramer@gmx.de wrote:
> 
> >ata1.00: configured for UDMA/33
> 
> I know nothing about the new large-sector disks, but the line above 
> makes
> me worried that the disk driver doesn't know any more than I do :)
> 
> Anyone know if that is the expected response from the disk driver?
> 
> 

I played around a little more with this "effects"...

At the WD-site there is a paper (pdf), which describes how to
jumper the WD-SATAs to behave as SATA1 even if being SATA2, which
I did.

Then I checked the cableing again and booted the system from a sdb,
which is my "old" system disk which I previously (before this hassle) 
to replace with the WD 1TB-disks, since on the old disk there was
not enoughspace anymore.

Then I mounted two partitions (root and an empty one) of the WD-drive
and copied the root to the empty partition by 

    cp -a <src> <dest>

The process starts and after some blinks of the HD-LED I got again
such in the kernel log:

(there is more things I wrote below this log... ;)

ata1.00: cmd c8/00:00:68:a1:61/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:df:68:a1:61/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:79:7f/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:df:68:79:7f/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:19:84/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:3f:68:19:84/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:a8:85/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:8f:68:a8:85/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:3b:86/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:8f:68:3b:86/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:83:87/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:0f:68:83:87/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:61:88/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:6f:68:61:88/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:c7:89/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:df:68:c7:89/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:72:8c/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:4f:68:72:8c/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:1c:90/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:af:68:1c:90/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:fc:98/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:00:68:fc:98/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:0b:a6/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:5f:68:0b:a6/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:c7:ae/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:ef:68:c7:ae/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:83:b1/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:cf:68:83:b1/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:83:b7/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:00:68:83:b7/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:a0:bf/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:2f:68:a0:bf/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:b6:c6/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:0f:68:b6:c6/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:b8:ce/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:0f:68:b8:ce/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:ef:d5/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:2f:68:ef:d5/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:f9:de/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:2f:68:f9:de/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:cb:f2/00:00:00:00:00/e4 tag 0 dma 131072 in
         res 51/84:4f:68:cb:f2/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:de:13/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:00:68:de:13/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:5c:4b/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:4f:68:5c:4b/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:92:7e/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:7f:68:92:7e/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:e9:80/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:2f:68:e9:80/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:3c:90/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:9f:68:3c:90/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:75:b2/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:6f:68:75:b2/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:7d:ba/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:4f:68:7d:ba/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:2a:bd/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:5f:68:2a:bd/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:52:c0/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:2f:68:52:c0/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:ad:c5/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:af:68:ad:c5/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:c0:d5/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:4f:68:c0:d5/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:47:e2/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:cf:68:47:e2/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:e6:f2/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:bf:68:e6:f2/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:d8:fb/00:00:00:00:00/e5 tag 0 dma 131072 in
         res 51/84:3f:68:d8:fb/00:00:00:00:00/e5 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:16:05/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:3f:68:16:05/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:ef:15/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:bf:68:ef:15/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:5d:25/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:4f:68:5d:25/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:c6:2d/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:ef:68:c6:2d/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:42:2f/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:5f:68:42:2f/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:cd:4e/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:df:68:cd:4e/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:53:5b/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:af:68:53:5b/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:9b:71/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:8f:68:9b:71/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:93:7b/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:1f:68:93:7b/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:ca:84/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:9f:68:ca:84/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:80:c0/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:00:68:80:c0/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:9a:c6/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:1f:68:9a:c6/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:3a:c9/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:6f:68:3a:c9/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:17:cf/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:00:68:17:cf/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:cb:d8/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:af:68:cb:d8/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:77:de/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:af:68:77:de/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:51:e4/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:1f:68:51:e4/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:b1:ef/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:4f:68:b1:ef/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:b2:f0/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:bf:68:b2:f0/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:f5:f2/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:8f:68:f5:f2/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:d7:f8/00:00:00:00:00/e6 tag 0 dma 131072 in
         res 51/84:2f:68:d7:f8/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:24:06/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:df:68:24:06/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:06:19/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:df:68:06:19/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:09:73/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:0f:68:09:73/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:27:83/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:6f:68:27:83/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:0e:8d/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:cf:68:0e:8d/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:5a:ad/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:1f:68:5a:ad/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:8d:b6/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:3f:68:8d:b6/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:99:db/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:00:68:99:db/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:4e:dd/00:00:00:00:00/e7 tag 0 dma 131072 in
         res 51/84:0f:68:4e:dd/00:00:00:00:00/e7 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:cf:0b/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:7f:68:cf:0b/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:f8:70:31:1f/00:00:00:00:00/e8 tag 0 dma 126976 in
         res 51/84:a7:70:31:1f/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:98:3c/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:af:68:98:3c/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:03:5a/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:9f:68:03:5a/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:ab:5c/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:bf:68:ab:5c/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:3e:8e/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:ef:68:3e:8e/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:48:a8/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:6f:68:48:a8/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:89:ad/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:7f:68:89:ad/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:f8:ad/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:3f:68:f8:ad/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:84:bd/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:bf:68:84:bd/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:d7:bd/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:2f:68:d7:bd/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:13:e1/00:00:00:00:00/e8 tag 0 dma 131072 in
         res 51/84:ef:68:13:e1/00:00:00:00:00/e8 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete

Before and after the copy-process I did a 

    hdparm -I /dev/sda

BEFORE (excerpt):
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 128, current value: 254
>>>>>>  DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AFTER (excerpt):
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 128, current value: 254
>>>>>>  DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6

Then I did a 

    dd if=/dev/sda of=/dev/null bs=65536

And after lots of error like those above I did

    killall -USR1 dd

and got back (excerpt):

    108477333504 bytes (108 GB) copied, 1013.81 s, 107 MB/s

which looks like relatively fast, which is not necessarily
"reliable"...

The things, which most important for me is:

WHAT is defective and have to be replaced?
Do I need another/newer motherboard (mine is a ASUS AV8/VIa
AK8T800Pro)?
Do I have to return the harddisks?

Thank you very much in advance for any help!
Best regards,
mcc







-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Andrea Conti]

> ata1.00: failed command: READ DMA
> ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
>          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1.00: status: { DRDY ERR }
> ata1.00: error: { ICRC ABRT }
> ata1: soft resetting link
> ata1.00: configured for UDMA/33
> ata1: EH complete
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.

WD drives are known not to get along too well with VIA SATA1 controllers:

http://www.viaarena.com/forums/showthread.php?t=38871
http://forums.gentoo.org/viewtopic-t-794855.html

What kernel version are you using?
What does the kernel say when it first detects the disk?

Do you get the same errors under a recent kernel (try the latest gentoo
install cd) ?

My experience with WD "advanced format" drives has been positive so far,
especially considering how cheap they are... The only gripe I have is
that they report not only having a 512B *logical* sector size in the
response to ATA INFO commands (which is fine, as they have a translation
layer), but also a 512B *physical* sector size, which is wrong and
causes partitioning tools to use the wrong alignment.
All the five 1TB drives I have behave this way, and from what I read
this is not an isolated behavior...

andrea

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Volker Armin Hemmann]

On Samstag 29 Mai 2010, Andrea Conti wrote:
> > ata1.00: failed command: READ DMA
> > ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
> > 
> >          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
> >          error)
> > 
> > ata1.00: status: { DRDY ERR }
> > ata1.00: error: { ICRC ABRT }
> > ata1: soft resetting link
> > ata1.00: configured for UDMA/33
> > ata1: EH complete
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> 
> I think you have driver issues. Might also be the cabling, but I doubt
> it as faulty SATA cables are in my experience quite rare.

in my experience they are everything but rare. I had several defective cables 
- myself and friends of mine.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[meino.cramer]

Andrea Conti <alyf@alyf.net> [10-05-29 10:08]:
> > ata1.00: failed command: READ DMA
> > ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
> >          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> > ata1.00: status: { DRDY ERR }
> > ata1.00: error: { ICRC ABRT }
> > ata1: soft resetting link
> > ata1.00: configured for UDMA/33
> > ata1: EH complete
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> 
> I think you have driver issues. Might also be the cabling, but I doubt
> it as faulty SATA cables are in my experience quite rare.
> 
> WD drives are known not to get along too well with VIA SATA1 controllers:
> 
> http://www.viaarena.com/forums/showthread.php?t=38871
> http://forums.gentoo.org/viewtopic-t-794855.html
> 
> What kernel version are you using?
> What does the kernel say when it first detects the disk?
> 
> Do you get the same errors under a recent kernel (try the latest gentoo
> install cd) ?
> 
> My experience with WD "advanced format" drives has been positive so far,
> especially considering how cheap they are... The only gripe I have is
> that they report not only having a 512B *logical* sector size in the
> response to ATA INFO commands (which is fine, as they have a translation
> layer), but also a 512B *physical* sector size, which is wrong and
> causes partitioning tools to use the wrong alignment.
> All the five 1TB drives I have behave this way, and from what I read
> this is not an isolated behavior...
> 
> andrea
> 

Hi Andrea,

I tried these kernels (all vanilla):
2.6.32.13
2.6.33.5
2.6.34.0

This is, what I cut from the dmegs out (I hope to get all relevant
infos...if you missing something, I save the complete dmesg output to
disk for later refrence...):

sata_via 0000:00:0f.0: version 2.6
sata_via 0000:00:0f.0: PCI INT B -> GSI 20 (level, low) -> IRQ 20
sata_via 0000:00:0f.0: routed to hard irq line 10
scsi0 : sata_via
PM: Adding info for scsi:host0
PM: Adding info for No Bus:host0
scsi1 : sata_via
PM: Adding info for scsi:host1
PM: Adding info for No Bus:host1
ata1: SATA max UDMA/133 cmd 0xd000 ctl 0xc800 bmdma 0xb800 irq 20
ata2: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb808 irq 20
pata_via 0000:00:0f.1: version 0.3.4
pata_via 0000:00:0f.1: PCI INT A -> GSI 20 (level, low) -> IRQ 20
scsi2 : pata_via
PM: Adding info for scsi:host2
PM: Adding info for No Bus:host2
scsi3 : pata_via
PM: Adding info for scsi:host3
PM: Adding info for No Bus:host3
ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
skge 0000:00:0a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
skge 0000:00:0a.0: PCI: Disallowing DAC for device
skge: 1.13 addr 0xf9c00000 irq 17 chip Yukon-Lite rev 9
PM: Adding info for No Bus:eth0
skge 0000:00:0a.0: eth0: addr 00:15:f2:18:b0:20
sky2: driver version 1.27
usbcore: registered new interface driver usblp

Aligment:

I used 

fdisk -cu -S 56 /dev/sda 

to align my partitions, which seems to work. 

Do I have to replace my motherboard/graphics card/RAM/...
only because WD cannot talk to and/or vice versa?

By the way:
Can I use PCI cards on newer motherboards with PCIe-slots???

Best regards,
mcc



-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Alan McKinnon]

On Saturday 29 May 2010 10:16:39 Volker Armin Hemmann wrote:
> On Samstag 29 Mai 2010, Andrea Conti wrote:
> > > ata1.00: failed command: READ DMA
> > > ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
> > > 
> > >          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
> > >          error)
> > > 
> > > ata1.00: status: { DRDY ERR }
> > > ata1.00: error: { ICRC ABRT }
> > > ata1: soft resetting link
> > > ata1.00: configured for UDMA/33
> > > ata1: EH complete
> > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> > 
> > I think you have driver issues. Might also be the cabling, but I doubt
> > it as faulty SATA cables are in my experience quite rare.
> 
> in my experience they are everything but rare. I had several defective
> cables - myself and friends of mine.

I find SATA connectors are what gives trouble. All fixed nicely with a dab of 
hot glue, but I ask, why should that be necessary?


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Andrea Conti]

Hi,

> I tried these kernels (all vanilla):
> 2.6.32.13
> 2.6.33.5
> 2.6.34.0

So it's not a known problem that has been fixed.

Just a wild guess... can you try recompiling the kernel *without*
pata_via? Some people have reported having problems with sata drives on
VIA controllers when pata_via is also loaded. If you need to access
devices on the PATA ports, you can use the the old non-libata via82cxxx
IDE driver.

> This is, what I cut from the dmegs out (I hope to get all relevant
> infos...if you missing something, I save the complete dmesg output to
> disk for later refrence...):

This is just the controller initialization part, it does not include the
actual information about the drives. Look for something like "ata1: SATA
link up..." a bit further in the log.

> fdisk -cu -S 56 /dev/sda

Well, fdisk -cu defaults to creating the first partition beginning at
sector 2048, which is fine as it's divisible by 8 (and thus is aligned
on a 4096-byte boundary). I don't think you need to specify the number
of sectors per track.

But this is not really relevant, as creating unaligned partitions merely
results in lower performance, not DMA errors :)

> Do I have to replace my motherboard/graphics card/RAM/...
> only because WD cannot talk to and/or vice versa?

If the pata_via trick above does not work, and an upgrade is out of
question, my suggestion is to find a cheap PCI sata2 controller and to
use that instead of the on-board sata ports.

> Can I use PCI cards on newer motherboards with PCIe-slots???

You cannot use PCI cards in PCIe slots, but most new motherboards still
have at least one PCI slot.

andrea

Re: [gentoo-user] Re: Harddisk trouble ... or not yet?

[Volker Armin Hemmann]

On Samstag 29 Mai 2010, Alan McKinnon wrote:
> On Saturday 29 May 2010 10:16:39 Volker Armin Hemmann wrote:
> > On Samstag 29 Mai 2010, Andrea Conti wrote:
> > > > ata1.00: failed command: READ DMA
> > > > ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
> > > > 
> > > >          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
> > > >          error)
> > > > 
> > > > ata1.00: status: { DRDY ERR }
> > > > ata1.00: error: { ICRC ABRT }
> > > > ata1: soft resetting link
> > > > ata1.00: configured for UDMA/33
> > > > ata1: EH complete
> > > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> > > 
> > > I think you have driver issues. Might also be the cabling, but I doubt
> > > it as faulty SATA cables are in my experience quite rare.
> > 
> > in my experience they are everything but rare. I had several defective
> > cables - myself and friends of mine.
> 
> I find SATA connectors are what gives trouble. All fixed nicely with a dab
> of hot glue, but I ask, why should that be necessary?

a spec made to guarantee early hardware death - to keep sales up.