Please note, not filing a new report would delay your problem being addressed as quickly as possible. Home Forums Posting Rules Linux Help & Resources Fedora Set-Up Guides Fedora Magazine Ask Fedora Fedora Project Fedora Project Links The Fedora Project Get Fedora F23 Release Notes F24 Release Notes You only know that memtest86+ is giving your errors, not what the cause is. Could it be an issue between the model of my motherboard and the model of the disk?

First, run this: sudo dd if=/dev/sda bs=512 count=1 of=/dev/null skip=326677146 That should fail with an IO error. I just updated to 12.04 (and 3.2.0-26-generic kernel) and its back. yemu (yemu) wrote on 2012-05-10: #123 @Christopher: thanks, I've just created new bug report as you said and subscribed you to it. Exception Emask ...

I'm using AHCI mode. This is not "bad system RAM", this is not "a bad motherboard", this is not "bad NAND flash on the SSD". Usually a memory diagnostic on failing memory will demonstrate a pattern. Maybe the additional connectors in there degrade the SATA link in a way that makes SATA3 unreliable.

Gerry Reno (greno-verizon) wrote on 2011-01-13: #22 I just went and upgraded to kernel 2.6.37-12-server from kernel-ppa and after rebooting into it I'm still see the same READ FPDMA QUEUED errors Reducing queue_length to 1 was not helpful for me, instead you probably should completely eliminate possibility of issuing NCQ tags. If you want you can take part and help covering the costs by having a look at my profile page. Auto Offline Data Collection: Enabled.

Quote Report Content Go to Page Top blublub Intermediate Likes Received 8 Posts 378 3 Dec 19th 2014, 10:06am this one: ? However, I admit that I might not be reading that figures correctly: Code: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-48-generic] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF ST500NM0011 working fine. In the end it had to be an incompatibility between the WD RED firmware and either the SATA Chipset and/or the mainboard itsself - just a pain in the a** !!!!

thx !!!! I don't know why Christopher incompletes it all the time; perhaps: "We don't need to think about things that are not possible." ;-) Just for completeness: since installing 12.04.1 server (adding After replacing the 1st WD Red with the HGST I did not get any error in 12h (OK not that much time I admit, but still strange). So it is either a misunderstanding between the hardware designers and kernel coders or then many SSD drives are just faulty somehow.

A better way to evaluate a certain determinant How to reliably reload package after change? Show 45 replies 1. on my machine this issue was in fact an issue of the HDD: some not-readable sectors. Because the error came up randomly, I guess that I didn't give it enough time to appear again during some of my checks.

It doesn't occur every day, and at the most a couple of times per day (currently we only have logs for 4-5 weeks back). Penalver (penalvch) on 2012-04-02 Changed in linux (Ubuntu): status: Confirmed → Incomplete 71 comments hidden Loading more comments view all 151 comments P. If anybody knows of a workaround to stop the kernel checking the disk and make the system usable... Error logging capability: (0x01) Error logging supported.

First verify that the BIOS settings of your machine are correctly configured. Both drives in the machine check out fine according to the drive tests. Code: #1 You want to keep using memory with any errors? – Daniel Beck♦ Aug 21 '11 at 19:38 source: https://superuser.com/questions/3260...-a-memtest-run TST = Test #5 = Test 5 [Moving inversions, 8 This would explain the other symptoms.

I am using an older OCZ Agility SSD. It's on 1TB Seagate drive that I have running for 4 and a half years now in Mythbuntu setup.