Ultradma crc errors 199

ultradma crc errors 199

Generally, hard disks record problem(s) occured in their lifetime and these error counters do not clear automatically (for example when you. forum.hddguru.com › viewtopic. That usually indicates an issue with the SATA cable or connectors, so I would replace the cable with a good one, and check ALL cable connections (both ends of. ultradma crc errors 199

Advise you: Ultradma crc errors 199

Drg-50857 oracle error in dreii0fsh
HAVIJ RUNTIME ERROR
Multiscatter 1.1.07a error code 998
PRIOR COMMAND
5 9644 hours UNKNOWN ERROR READ FPDMA QUEUED
4 9633 hours UNKNOWN ERROR READ FPDMA QUEUED
3 9625 hours UNKNOWN ERROR READ FPDMA QUEUED
2 9625 hours UNKNOWN ERROR READ FPDMA QUEUED
1 9620 hours UNKNOWN ERROR READ FPDMA QUEUED


=== DRIVE SELF-TEST LOG ===
#

About a month ago my PC (running Win 10 Pro) started to crash randomly and when copying some files, I noticed there was an issue with file corruption on the target drive. This then behaved for a few days and then escalated to the system freezing completely. When the system wouldn't restart, I was forced to manually reset the PC, and this then prompted a lengthy DOS check disk on boot up. The screen was running with what seemed forever showing "Deleting extended attribute set due to the presence of reparse point in file ######" No bad clusters were found. But the system was still unstable and crashed a few more times after this.

I then booted into Win 7 on my other HDD on this system to see if I could figure out what was going on. I ran HD Tune and let it do a full media scan, no errors on disk surface, but in the health section it showed a high value for the Ultra DMA CRC Error Count (this eventually increased as I continued battling to pull data off the affected drive). I also have to point out that both the affected Win 10 Ultradma crc errors 199 and the Win 7 HDD are both the same type, that being WD 1TB Blue SATA, the former being less than 3 years old and the latter a little over a year old now.

After reading that it could be a SATA cable issue, or bad clusters, or vba error 2042 HDD controller on the drive, and then realising that ultradma crc errors 199 warranty for these drives is only 2 years now, ultradma crc errors 199, I decided to play around with the cables and troubleshoot a bit. Since disconnecting and reconnecting the SATA cable to the affected drive, I have also done a full reinstallation of Win 10 Pro after formating this drive with newly created partitions from the Win 10 Pro installation. So far, the Ultra DMA CRC Error Count has not changed since I played around with the cable, and the OS on the drive appears to be running stable.

When the drive started to act up, it was running a bit low on space, but not to the point where it could no longer function - is it possible that this was all caused simply due to the cable and the way it was plugged in at the moment? Maybe some dust? I do clean my PC from time to time, but it does sometimes become a bit dusty. HD Tune shows the overall health as OK, and all the attributes apart from the Ultra DMA CRC Error Count (Current 200, Worst 1, Threshold 0, Data 403274) appear normal. The WD Lifeguard diagnostics app also shows the drive as being in perfect ultradma crc errors 199, and in fact doesn't even show anything wrong with the Ultra DMA CRC Error Count.

 

TEST TYPE LIFETIME (H) STATUS

Drive DX scan on my Hard drive reveals UDMA CRC Error count. What does this mean?

I scanned my HD with DriveDX and it revealed a "199 UDMA CRC Error Count". There's s checksum error defaults loaded an error message saying:

"Total ultradma crc errors 199 of errors in data transfer via the interface cable, ultradma crc errors 199. Each time the error is detected, controller requests a retransmission, thus slowing down the overall transfer speed. Increase of raw value could indicate problem with the power supply or data cable."

Is there anything I should do? Here is the full system report. I've also attached the drive health indicator report:

### SYSTEM INFORMATION ###


Application Name : DriveDx
Application Version : 1.5.1.530
Application SubBuild : 0
Application Edition : Standalone
Application Website : https://binaryfruit.com/drivedx
DriveDx Knowledge Base Revision : 6/6


Computer Model : MacBookPro8,1


OS Name : macOS
OS Version : 10.10.5
OS Build : 14F2109
OS Kernel Version : Darwin 14.5.0

SAT SMART Driver Version : N/A
ATA Command Support Tolerance : verypermissive
N of drives with S.M.A.R.T support : 1



### DRIVE 1 OF 1 ###
Last Checked : May 1, ultradma crc errors 199, 2017 4:58:42 PM EDT
Last Checked (ISO 8601 format) : 2017-05-01T16:58:42

Advanced SMART Status : OK
Overall Health Rating : AVERAGE 52.7%
Overall Performance Rating : AVERAGE 52.7%
Issues found : 1


Volumes : Macintosh HD
Device Path : /dev/disk0
Total Capacity : 1.0 TB (1,000,204,886,016 Bytes)
Model Family : HGST Travelstar 7K1000
Model : HGST HTS721010A9E630
Form Factor : 2.5 inches
Firmware Version : JB0OA3J0
Drive Type : HDD 7200 rpm

Power On Time : 9,648 hours (13 months 12 days 0 hours)
Power Cycles Count : 643
Current Power Cycle Time : 0.7 hours



=== DEVICE CAPABILITIES ===
S.M.A.R.T. support enabled : yes
DriveDx Active Diagnostic Config : Base config [hdd.default]
Sector Logical Size : 512
Sector Physical Size : nokia n9 error su_get_update_status_req Physical Interconnect : SATA
Removable : no
Ejectable : no
ATA Version : ATA8-ACS T13/1699-D revision 6
SATA Version : SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Bay # : 1
I/O Path :
Attributes Data Structure Revision : 16
SMART Command Transport (SCT) flags : 0x3d
SCT Status supported : yes
SCT Feature Control supported : yes
SCT Data Table supported : yes
Error logging capabilities : 0x1
Self-tests supported : yes
Offline Data Collection capabilities : 0x5b
Offline Data Collection status : 0x0
Auto Offline Data Collection flags : 0x0
[Known device ]: yes
[Drive State Flags ]: 0x40000100
[Last State Change Timestamp ]: 2017-05-01T16:21:43
[Last State Change Flags ]: 0x40000100
[Last State Change Diff Flags ]: 0x400


=== CURRENT POWER CYCLE STATISTICS ===
Data Read : 3.3 GB
Data Written : 1.8 GB
Data Read/Write Ratio : 1.87
Average Throughput (Read) : 2.0 MB/s
Average Throughput (Write) : 1.7 MB/s

Operations (Read) : 133,275
Operations (Write) : 41,345
Operations Read/Write Ratio : 3
Throughput per operation (Read) : 26.3 KB/Op
Throughput per operation (Write) : 45.4 KB/Op

Latency Time (Read) : 0 ns
Latency Time (Write) : 0 ns
Retries (Read) : 0
Retries (Write) : 0
Errors (Read) : 0
Errors (Write) : 0


=== PROBLEMS SUMMARY ===
Failed Indicators (life-span / pre-fail) : 0 (0 / 0)
Failing Indicators (life-span / pre-fail) : 0 (0 / 0)
Warnings (life-span / pre-fail) : 1 (1 / 0)
Recently failed Self-tests (Short / Full) : 0 (0 / 0)
I/O Errors Count : 0 (0 / 0)
Time in Under temperature : 0 minutes
Time in Over temperature : 0 minutes


=== IMPORTANT HEALTH INDICATORS ===
ID NAME RAW VALUE STATUS
5 Reallocated Sector Count 0 100% OK
197 Current Pending Sectors Count 0 100% OK
198 Offline Uncorrectable Sector Count 0 100% OK
199 UDMA CRC Error Count 768 100% Warning


=== TEMPERATURE INFORMATION (CELSIUS) ===
Current Temperature : 35
Power Cycle Min Temperature : 21
Power Cycle Max Temperature : 35
Lifetime Min Temperature : 15
Lifetime Max Temperature : 47
Recommended Min Temperature : 0
Recommended Max Temperature : 60
Ultradma crc errors 199 Min Limit : -40
Temperature Max Limit : 65




=== DRIVE ERROR LOG ===
#

1 Comments

  1. I regret, that I can not participate in discussion now. I do not own the necessary information. But with pleasure I will watch this theme.

Leave a Comment