| View previous topic :: View next topic |
| Author |
Message |
wgbennett
n00b
Joined: 11 Sep 2008
Posts: 11
Location: owensboro, ky
|
 Posted: Tue Jun 02, 2009 9:58 pm Post subject: SATA Error: UnrecovData |
 |
|
Hello,
My drive was checked on the last boot, and an error occured. The computer still booted fine, and the disk appears to be working fine, but I was wondering what exactly the error means. Is this a sign that my disk is going bad? This is a new sata disk. Here is the error:
| Code: |
[ 667.590902] ata4.00: exception Emask 0x50 SAct 0x2 SErr 0x280900 action 0x6 frozen
[ 667.590988] ata4.00: irq_stat 0x08000000, interface fatal error
[ 667.591055] ata4: SError: { UnrecovData HostInt 10B8B BadCRC }
[ 667.591124] ata4.00: cmd 60/06:08:a9:3a:fe/00:00:46:00:00/40 tag 1 ncq 3072 in
[ 667.591124] res 40/00:0c:a9:3a:fe/00:00:46:00:00/40 Emask 0x50 (ATA bus error)
[ 667.591307] ata4.00: status: { DRDY }
[ 667.591372] ata4: hard resetting link
[ 668.072022] ata4: softreset failed (device not ready)
[ 668.072090] ata4: failed due to HW bug, retry pmp=0
[ 668.236026] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 668.237519] ata4.00: configured for UDMA/133
[ 668.237527] ata4: EH complete
[ 668.237578] sd 3:0:0:0: [sdb] 1465149168 512-byte hardware sectors: (750 GB/698 GiB)
[ 668.237588] sd 3:0:0:0: [sdb] Write Protect is off
[ 668.237590] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 668.237602] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
|
The Libata Error Wiki shows that the error is UnrecovData, and that it means: "Data integrity error occurred, interface did not recover." What exactly does this mean?
When I run | Code: | | smartctl -a /dev/sdb |
it shows that no errors have been logged.
Any thoughts?
Thanks for any help,
Will Bennett |
|
| Back to top |
|
 |
pappy_mcfae
Watchman
Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.
|
| Posted: Wed Jun 03, 2009 5:47 am Post subject: |
|
|
Other than telling you to keep a close eye on it, and make sure you step up your backup procedures' frequency, I'd say you might have had a momentary cable-related glitch. If this problem becomes more steady, I'd say you have a bad drive.
One bad sector does not a fried drive make. However, if it's a new drive, replace it before the warranty has time to die.
Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
