You are not logged in.

Pages: 1

#1 2014-05-28 08:27:08

sinopeus
Member
Registered: 2014-05-28
Posts: 6

[SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

Hello everyone,

I recently acquired a new Western Digital Blue 1TB HDD for my laptop (2.5" evidently). I installed it in a 2011 MB Pro using a third-party HDD dock to put the HDD where the DVD drive used to be. When I installed it, the kernel started emitting error messages of the following sort:

[   45.865200] ata2.00: exception Emask 0x10 SAct 0x1000 SErr 0x400100 action 0x6 frozen
[   45.865285] ata2.00: irq_stat 0x08000000, interface fatal error
[   45.865340] ata2: SError: { UnrecovData Handshk }
[   45.865387] ata2.00: failed command: WRITE FPDMA QUEUED
[   45.865444] ata2.00: cmd 61/00:60:d0:3f:77/02:00:00:00:00/40 tag 12 ncq 262144 out
         res 40/00:64:d0:3f:77/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   45.865569] ata2.00: status: { DRDY }
[   45.865609] ata2: hard resetting link
[   46.184973] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   46.185849] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.186847] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.187002] ata2.00: configured for UDMA/133
[   46.187043] ata2: EH complete

I would get dozens of these sets of error messages in a row, clogging up the kernel log. Now this, of course, smelt like a bad SATA connector or something of the sort, not something I could fix. So I sent the HDD back to Western Digital. A few weeks ago, I received a brand new hard drive, exactly the same model. To my dismay, when I installed it once more, the same messages started popping up. Since I considered it unlikely they would send me another defective hard drive, I decided to do some research on the matter to see what could be causing the errors. It turned out that most of the issues with this model of hard drive had to do with one of the following:

1. This model is an Advanced Format hard drive with 4K sectors instead of 512B sectors. This apparently causes I/O errors with older versions of fdisk if you assign a number of blocks to a partition on the hard drive which is not divisible by 4 (or so I've read). This problem, however, should not occur with the version of fdisk I used to partition the hard drive, I'm just putting this here for the sake of completeness.

2. The WD Green is marketed as having very low power consumption (I think something like 50% of a classic HDD). I discovered some other cases of people having the same issues as me; the apparent cause was the mechanism the drive uses to save power, namely, spinning down the drive after 8 seconds of inactivity (*facepalm*). Someone out there wrote a small program (idle3-tools, found at http://idle3-tools.sourceforge.net/) which disables the hard drive's built-in spindown timer, which I then replaced by my own hdparm settings (spinning down after 25 minutes). I thought that this would be the end of my issues.

Now, this last solution did apparently work for a few days (that or I didn't read my kernel logs attentively), but then, the same type of error started resurfacing. Initially, this caused no actual problems in use, so I decided (perhaps against my better judgment) to soldier on. I still can't find out what's happening though, and I worry that it may be an issue that causes my HDD to fail prematurely. So now I'm trying to find out what may be causing the errors. I've come up with four possibilities:

1. Another issue with the power management is causing this problem, or I did not correctly unset the HDD's built-in spindown timer. If so, I really don't know how to do this. Idle3-tools says the spindown timer is off.

2. I am using btrfs on the HDD; don't know if that might cause this type of problem in some cases.

3. I received another faulty disk: I consider this unlikely, given the fact that I get exactly the same errors.

4. The third-party SATA dock I use does not provide enough power somehow. This also seems unlikely given the fact that I used it for a year and a half without any problems with another hard drive which consumes more power.

All of which entail either black magic I have no knowledge of or returning the HDD to WD and asking for a refund. Still, I don't think I've exhausted all the possibilities at this point and I hoped that some of you guys would know what to do with this issue. It would save me a load of trouble. Thanks for any responses! For good measure, here's the partition's line in the fstab:

/dev/sdb1           	/home/sinopeus/         	btrfs      	rw,relatime,compress-force=zlib,autodefrag	0 0

EDIT 1: X session errors were a little mistake in my xinitrc. The ATA errors still persist, though.

Last edited by sinopeus (2014-06-05 12:48:36)

Offline

#2 2014-05-30 21:14:51

sinopeus
Member
Registered: 2014-05-28
Posts: 6

Re: [SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

Does no one who read the original post have any idea what this might be caused by? Maybe I didn't phrase my question clearly enough or I'm overlooking something glaringly obvious which everyone but me sees immediately. I've Googled the problem extensively and I'm really stumped at this point. I did notice that the OS scales down the SATA link speed from 6.0Gbps to 3.0Gbps when a series of such errors occurs. Here's a more extensive excerpt from dmesg:

[   45.865200] ata2.00: exception Emask 0x10 SAct 0x1000 SErr 0x400100 action 0x6 frozen
[   45.865285] ata2.00: irq_stat 0x08000000, interface fatal error
[   45.865340] ata2: SError: { UnrecovData Handshk }
[   45.865387] ata2.00: failed command: WRITE FPDMA QUEUED
[   45.865444] ata2.00: cmd 61/00:60:d0:3f:77/02:00:00:00:00/40 tag 12 ncq 262144 out
         res 40/00:64:d0:3f:77/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   45.865569] ata2.00: status: { DRDY }
[   45.865609] ata2: hard resetting link
[   46.184973] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   46.185849] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.186847] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.187002] ata2.00: configured for UDMA/133
[   46.187043] ata2: EH complete
[   46.198292] ata2.00: exception Emask 0x10 SAct 0x3fff0000 SErr 0x400100 action 0x6 frozen
[   46.198379] ata2.00: irq_stat 0x08000000, interface fatal error
[   46.198434] ata2: SError: { UnrecovData Handshk }
[   46.198481] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.198536] ata2.00: cmd 61/60:80:80:f7:07/00:00:00:00:00/40 tag 16 ncq 49152 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.198660] ata2.00: status: { DRDY }
[   46.198696] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.198749] ata2.00: cmd 61/40:88:20:fe:07/00:00:00:00:00/40 tag 17 ncq 32768 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.198872] ata2.00: status: { DRDY }
[   46.198907] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.198959] ata2.00: cmd 61/20:90:80:fe:07/00:00:00:00:00/40 tag 18 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.199082] ata2.00: status: { DRDY }
[   46.199119] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.199171] ata2.00: cmd 61/20:98:80:02:08/00:00:00:00:00/40 tag 19 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.199292] ata2.00: status: { DRDY }
[   46.199328] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.199381] ata2.00: cmd 61/20:a0:a0:03:08/00:00:00:00:00/40 tag 20 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.199505] ata2.00: status: { DRDY }
[   46.199539] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.199592] ata2.00: cmd 61/80:a8:00:04:08/00:00:00:00:00/40 tag 21 ncq 65536 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.199715] ata2.00: status: { DRDY }
[   46.199751] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.199804] ata2.00: cmd 61/40:b0:a0:f5:27/00:00:00:00:00/40 tag 22 ncq 32768 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.199927] ata2.00: status: { DRDY }
[   46.199963] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.200015] ata2.00: cmd 61/20:b8:00:f6:27/00:00:00:00:00/40 tag 23 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.200139] ata2.00: status: { DRDY }
[   46.200174] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.200226] ata2.00: cmd 61/60:c0:80:f7:27/00:00:00:00:00/40 tag 24 ncq 49152 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.200349] ata2.00: status: { DRDY }
[   46.200385] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.200437] ata2.00: cmd 61/40:c8:20:fe:27/00:00:00:00:00/40 tag 25 ncq 32768 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.200559] ata2.00: status: { DRDY }
[   46.200593] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.200647] ata2.00: cmd 61/20:d0:80:fe:27/00:00:00:00:00/40 tag 26 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.200770] ata2.00: status: { DRDY }
[   46.200805] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.200858] ata2.00: cmd 61/20:d8:80:02:28/00:00:00:00:00/40 tag 27 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.200980] ata2.00: status: { DRDY }
[   46.201017] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.201069] ata2.00: cmd 61/20:e0:a0:03:28/00:00:00:00:00/40 tag 28 ncq 16384 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.201191] ata2.00: status: { DRDY }
[   46.201226] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.201279] ata2.00: cmd 61/80:e8:00:04:28/00:00:00:00:00/40 tag 29 ncq 65536 out
         res 40/00:ec:00:04:28/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.201401] ata2.00: status: { DRDY }
[   46.204672] ata2: hard resetting link
[   46.521476] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   46.522368] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.523249] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.523386] ata2.00: configured for UDMA/133
[   46.523493] ata2: EH complete
[   46.531532] ata2.00: exception Emask 0x10 SAct 0x3fc0 SErr 0x400100 action 0x6 frozen
[   46.534865] ata2.00: irq_stat 0x08000000, interface fatal error
[   46.538151] ata2: SError: { UnrecovData Handshk }
[   46.541427] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.544676] ata2.00: cmd 61/40:30:a0:f5:27/00:00:00:00:00/40 tag 6 ncq 32768 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.551214] ata2.00: status: { DRDY }
[   46.553852] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.556451] ata2.00: cmd 61/80:38:00:04:08/00:00:00:00:00/40 tag 7 ncq 65536 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.561711] ata2.00: status: { DRDY }
[   46.564113] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.566508] ata2.00: cmd 61/20:40:a0:03:08/00:00:00:00:00/40 tag 8 ncq 16384 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.571308] ata2.00: status: { DRDY }
[   46.573702] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.575921] ata2.00: cmd 61/20:48:80:02:08/00:00:00:00:00/40 tag 9 ncq 16384 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.580343] ata2.00: status: { DRDY }
[   46.582560] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.584612] ata2.00: cmd 61/20:50:80:fe:07/00:00:00:00:00/40 tag 10 ncq 16384 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.588714] ata2.00: status: { DRDY }
[   46.590757] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.592809] ata2.00: cmd 61/40:58:20:fe:07/00:00:00:00:00/40 tag 11 ncq 32768 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.596635] ata2.00: status: { DRDY }
[   46.598540] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.600443] ata2.00: cmd 61/60:60:80:f7:07/00:00:00:00:00/40 tag 12 ncq 49152 out
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.604265] ata2.00: status: { DRDY }
[   46.606061] ata2.00: failed command: READ FPDMA QUEUED
[   46.607841] ata2.00: cmd 60/20:68:40:01:08/00:00:00:00:00/40 tag 13 ncq 16384 in
         res 40/00:6c:40:01:08/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.611414] ata2.00: status: { DRDY }
[   46.613101] ata2: hard resetting link
[   46.931275] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   46.932141] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.933115] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   46.933254] ata2.00: configured for UDMA/133
[   46.933332] ata2: EH complete
[   46.941325] ata2: limiting SATA link speed to 3.0 Gbps
[   46.941340] ata2.00: exception Emask 0x10 SAct 0x304000 SErr 0x400100 action 0x6 frozen
[   46.944716] ata2.00: irq_stat 0x08000000, interface fatal error
[   46.948030] ata2: SError: { UnrecovData Handshk }
[   46.951336] ata2.00: failed command: READ FPDMA QUEUED
[   46.954635] ata2.00: cmd 60/20:70:40:01:08/00:00:00:00:00/40 tag 14 ncq 16384 in
         res 40/00:ac:a0:f5:27/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.959983] ata2.00: status: { DRDY }
[   46.962648] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.965315] ata2.00: cmd 61/80:a0:00:04:08/00:00:00:00:00/40 tag 20 ncq 65536 out
         res 40/00:ac:a0:f5:27/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.970194] ata2.00: status: { DRDY }
[   46.972626] ata2.00: failed command: WRITE FPDMA QUEUED
[   46.975060] ata2.00: cmd 61/40:a8:a0:f5:27/00:00:00:00:00/40 tag 21 ncq 32768 out
         res 40/00:ac:a0:f5:27/00:00:00:00:00/40 Emask 0x10 (ATA bus error)
[   46.979539] ata2.00: status: { DRDY }
[   46.981771] ata2: hard resetting link
[   47.301095] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   47.301951] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   47.302922] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   47.303062] ata2.00: configured for UDMA/133
[   47.303112] ata2: EH complete

Last edited by sinopeus (2014-05-31 10:46:24)

Offline

#3 2014-06-04 16:58:05

sinopeus
Member
Registered: 2014-05-28
Posts: 6

Re: [SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

Still haven't found out what is causing this problem. I have tested it with a different kernel and the same result pops up (not that I expected anything else). I investigated the possibility of the problem being caused by the SATA link only being ready for SATAII but smartctl tells me that:

 SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)

I also noticed that the link speed is only throttled after the partition is mounted. Full output for smartctl, just to be complete:

smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.12.20-gentoo] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD10JPVX-00JC3T0
Serial Number:    WD-WX71EA3MVL73
LU WWN Device Id: 5 0014ee 6597f02b0
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Jun  4 18:57:37 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(17760) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 199) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x7035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   184   181   021    Pre-fail  Always       -       1758
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       482
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       336
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       66
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       16
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       2032
194 Temperature_Celsius     0x0022   115   105   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Last edited by sinopeus (2014-06-04 16:59:35)

Offline

#4 2014-06-04 17:19:41

ukhippo
Member
From: Non-paged pool
Registered: 2014-02-21
Posts: 366

Re: [SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

Does your SATA dock and/or cable support SATA 3.0 speeds? Was the previous HDD SATA 3.0 or 2.0?

Offline

#5 2014-06-04 19:21:01

sinopeus
Member
Registered: 2014-05-28
Posts: 6

Re: [SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

The previous HDD in the dock was SATA 2.0 (a Hitachi Travelstar 5K500.B 320GB), but I just discovered this:

Testing has demonstrated that Apple factory hardware does not reliably support a 6G (6Gb/s) Solid State Drive or Hard Disk Drive in the optical bay of 2011 MacBook Pros (ModeI ID8,1; 8,2; 8,3). If your OWC Data Doubler bundle comes with a 6G drive, you should ONLY install that drive in the main drive bay and utilize the Data Doubler to re-task your existing drive or install a new 3G SSD or HDD in the optical bay. PRE-2011 models can utilize a 6G drive in the optical bay, but will do so at a reduced 3G (3Gb/s) speed.

Found that tidbit here. So apparently installing a SATA 3.0 drive in the optical bay is akin to a game of Russian roulette. I guess that kind of seals it.

Last question before I mark this solved: how do I manually throttle the SATA link speed for this particular drive? I'm kind of tired of these messages. I've read stuff about setting jumpers, but if possible, I'd like to set this via kernel parameters or hdparm or something, but I can't seem to find anything (guess I'm Googling it wrong). Any ideas?

Offline

#6 2014-06-04 21:28:04

sinopeus
Member
Registered: 2014-05-28
Posts: 6

Re: [SOLVED] ATA bus / DMA errors with new WD Blue 2.5" hard drive

Okay, I've found a way to throttle the link speed myself. I set an extra kernel parameter in the GRUB_CMDLINE_LINUX line in /etc/default/grub following the example at http://askubuntu.com/questions/145965/h … er-modding, regenerated grub.cfg and rebooted. No more errors! Thanks for the reply though :-)

(Full description of possible libata parameters is found at https://www.kernel.org/doc/Documentatio … meters.txt.)

Last edited by sinopeus (2014-06-04 21:29:21)

Offline

Pages: 1

Board footer

Powered by FluxBB