Error 40 Uncorrectable
- READ_DMA « previous next » Print Pages: [1] Go Down Author Topic: How to correct FAILURE - READ_DMA (Read 7780 times) 0 Members and 2 Guests are viewing this topic. Summer Jr. Member Posts: 61 Karma: +0/-0 How to correct FAILURE - uncorrectable error count READ_DMA « on: September 05, 2011, 03:57:54 am » Upgraded from 1.2.3 to 2.0RC3, after
Uncorrectable Error Imgburn
few days got:Sep 5 04:02:21 tbfirewall kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=3919Sep 5 04:02:21 tbfirewall kernel: g_vfs_done():ad0s1a[READ(offset=1966080, length=16384)]error = uncorrectable error in data 5Sep 5 04:02:22 tbfirewall kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=3919Sep 5 04:02:22 tbfirewall kernel: g_vfs_done():ad0s1a[READ(offset=1966080, length=16384)]error = 5Sep 5 04:02:23 tbfirewall kernel: ad0: FAILURE - READ_DMA status=51 error=40 LBA=3919Sep 5 04:02:23 tbfirewall kernel: g_vfs_done():ad0s1a[READ(offset=1966080,
Uncorrectable Error Count Fail
length=16384)]error = 5SMART Attributes Data Structure revision number: 11Vendor Specific SMART Attributes with Thresholds:ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0029 100 253 020 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 080 079 020 Pre-fail Always - 2585 4 Start_Stop_Count 0x0032 096 whea uncorrectable error 096 008 Old_age Always - 3044 5 Reallocated_Sector_Ct 0x0033 100 100 020 Pre-fail Always - 2 7 Seek_Error_Rate 0x000b 093 024 023 Pre-fail Always - 1 9 Power_On_Hours 0x0012 087 087 001 Old_age Always - 878710 Spin_Retry_Count 0x0026 100 100 000 Old_age Always - 011 Calibration_Retry_Count 0x0013 100 100 020 Pre-fail Always - 012 Power_Cycle_Count 0x0032 096 096 008 Old_age Always - 303513 Read_Soft_Error_Rate 0x000b 100 100 023 Pre-fail Always - 0195 Hardware_ECC_Recovered 0x001a 100 001 000 Old_age Always - 176692277196 Reallocated_Event_Count 0x0010 100 100 020 Old_age Offline - 0197 Current_Pending_Sector 0x0032 100 100 020 Old_age Always - 2198 Offline_Uncorrectable 0x0010 100 253 000 Old_age Offline - 0199 UDMA_CRC_Error_Count 0x001a 077 077 000 Old_age Always - 123Warning: device does not support Error LoggingSMART Error Log Version: 0No Errors LoggedWarning: device does not support Self Test Logging
are giving users trouble, in particular the Sandisk 4GB 30MB/s cards seem to be problematic. The cards may
Whea Uncorrectable Error Startup
function properly, but will often generate an error in the logs such
Whea Uncorrectable Error Windows 7
as: ad0: FAILURE - READ status=51 error=10 LBA=7813119 ad0: FAILURE - READ status=51 error=10 LBA=7813119 This normal and whea uncorrectable error prime95 safe to ignore. It has nothing to do with image size, a 1 GB image can be used on a 4 GB card and they still do that. From https://forum.pfsense.org/index.php?topic=40596.0 what I've been able to gather on that, the cards report they have a larger usable size than they do, and when the FreeBSD ATA code initializes it tries to read the end of the disk even if its partition is nowhere near that, which the CF is reporting doesn't actually exist, which is what that log message https://doc.pfsense.org/index.php/DMA_and_LBA_Errors says. "according to ATA-7 specification, Section 6.59.6 is: "IDNF shall be set to one if a user-accessible address could not be found. IDNF shall be set to one if an address outside of the range of user-accessible addresses is requested if command aborted is not returned." FreeBSD labels this bit as NID_NOT_FOUND" Summarized from this forum post. SETFEATURES Error Newer snapshots and releases of pfSense (after 2.0.1) also attempt to setup APM for an ATA hard drive at boot. Sometimes the detection yields a non-fatal error when trying to find if the value is supported, or when the drive claims it's supported but can't set it. That error is: ad0: FAILURE - SETFEATURES 0x85 status=41 error=4 It should only be seen once at bootup on such systems, and can safely be ignored. Fatal Errors The following errors would indicate more serious problems such as a faulty HDD/CF, faulty cable/controller, a faulty CF/SATA/IDE converter, a device out of space, or possibly that DMA needs disabled on that combination of hardware. ad0: FAILURE - READ_DMA status=51Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Display Modes #1 http://daemonforums.org/showthread.php?t=1681 (View Single Post) 9th August 2008 PeterSteele Port Guard Join Date: Jul 2008 Posts: 43 What is best way to monitor for bad sectors? We are developing an appliance based on FreeBSD 7.0. We will be running a custom FS on top of both UFS and raw partitions and will need to have a way to deal with bad uncorrectable error sectors. Ideally we'd like to be able to subscribe to a system event and have FreeBSD alert us when a bad sector is detected. I don't think there is a mechanism to do this though. We've noted that the system does seem to log a message in /var/log/dmesg when a bad sector is encountered, for example, these messages are occurring on whea uncorrectable error one of ours systems right now: ad8: FAILURE - READ_DMA48 status=51 error=40 LBA=343237347 g_vfs_done():ad8s1d[READ(offset=143525234688, length=2048)]error = 5 ad8: FAILURE - READ_DMA48 status=51 error=40 LBA=343237347 g_vfs_done():ad8s1d[READ(offset=143525234688, length=2048)]error = 5 ad8: FAILURE - READ_DMA48 status=51 error=40 LBA=343237347 g_vfs_done():ad8s1d[READ(offset=143525234688, length=2048)]error = 5 I assume these are due to bad sectors. So we thought one alternative could simply be to have a process that polls and scans /var/log/dmesg periodically and reports back to our management system when one of these errors are detected. Is this a reliable/reasonable approach? Is there a better way to monitor a system for bad sectors? I should add that we do have SMART installed and operational, but our experience so far with SMART is that it will not alert us to a sector that goes bad without warning. If we're mistaken about this, we'd appreciate some feedback. Thanks. Last edited by PeterSteele; 9th August 2008 at 10:57 PM. PeterSteele View Public Profile Find all posts by PeterSteele #2 (View Single Post) 10th August 2008 PeterSteele Port Guard Join Date: Jul 2008 Posts: 43 I should