You are not logged in.

#1 2012-02-16 01:59:36

AugustePop
Member
Registered: 2010-04-27
Posts: 95

[SOLVED] is this a hardware failure?

i noticed this message come up repeatedly in console and found it in everything.log. is there anything i can do to it? or i just need a new hard drive?

EDIT: this turned out to be a true hardware failure after further investigation. thus mark this thread solved.

Feb 15 22:25:47 pop kernel: [  813.404886] ata1.00: exception Emask 0x0 SAct 0x1f SErr 0x0 action 0x0
Feb 15 22:25:47 pop kernel: [  813.404891] ata1.00: irq_stat 0x40000001
Feb 15 22:25:47 pop kernel: [  813.404894] ata1.00: failed command: READ FPDMA QUEUED
Feb 15 22:25:47 pop kernel: [  813.404900] ata1.00: cmd 60/28:00:bd:e4:fd/00:00:15:00:00/40 tag 0 ncq 20480 in
Feb 15 22:25:47 pop kernel: [  813.404901]          res 41/40:28:dc:e4:fd/00:00:15:00:00/65 Emask 0x409 (media error) <F>
Feb 15 22:25:47 pop kernel: [  813.404904] ata1.00: status: { DRDY ERR }
Feb 15 22:25:47 pop kernel: [  813.404906] ata1.00: error: { UNC }
Feb 15 22:25:47 pop kernel: [  813.404909] ata1.00: failed command: WRITE FPDMA QUEUED
Feb 15 22:25:47 pop kernel: [  813.404914] ata1.00: cmd 61/60:08:fd:6c:13/01:00:06:00:00/40 tag 1 ncq 180224 out
Feb 15 22:25:47 pop kernel: [  813.404915]          res 41/04:10:c5:82:b0/00:00:12:00:00/40 Emask 0x1 (device error)
Feb 15 22:25:47 pop kernel: [  813.404918] ata1.00: status: { DRDY ERR }
Feb 15 22:25:47 pop kernel: [  813.404920] ata1.00: error: { ABRT }
Feb 15 22:25:47 pop kernel: [  813.404922] ata1.00: failed command: READ FPDMA QUEUED
Feb 15 22:25:47 pop kernel: [  813.404927] ata1.00: cmd 60/08:10:c5:82:b0/00:00:12:00:00/40 tag 2 ncq 4096 in
Feb 15 22:25:47 pop kernel: [  813.404929]          res 41/04:10:c5:82:b0/00:00:12:00:00/40 Emask 0x1 (device error)
Feb 15 22:25:47 pop kernel: [  813.404931] ata1.00: status: { DRDY ERR }
Feb 15 22:25:47 pop kernel: [  813.404933] ata1.00: error: { ABRT }
Feb 15 22:25:47 pop kernel: [  813.404936] ata1.00: failed command: WRITE FPDMA QUEUED
Feb 15 22:25:47 pop kernel: [  813.404941] ata1.00: cmd 61/38:18:05:5e:36/00:00:1e:00:00/40 tag 3 ncq 28672 out
Feb 15 22:25:47 pop kernel: [  813.404942]          res 41/04:10:c5:82:b0/00:00:12:00:00/40 Emask 0x1 (device error)
Feb 15 22:25:47 pop kernel: [  813.404945] ata1.00: status: { DRDY ERR }
Feb 15 22:25:47 pop kernel: [  813.404947] ata1.00: error: { ABRT }
Feb 15 22:25:47 pop kernel: [  813.404949] ata1.00: failed command: READ FPDMA QUEUED
Feb 15 22:25:47 pop kernel: [  813.404954] ata1.00: cmd 60/00:20:c5:98:8c/02:00:20:00:00/40 tag 4 ncq 262144 in
Feb 15 22:25:47 pop kernel: [  813.404955]          res 41/04:10:c5:82:b0/00:00:12:00:00/40 Emask 0x1 (device error)
Feb 15 22:25:47 pop kernel: [  813.404962] ata1.00: status: { DRDY ERR }
Feb 15 22:25:47 pop kernel: [  813.404965] ata1.00: error: { ABRT }
Feb 15 22:25:47 pop kernel: [  813.406975] ata1.00: configured for UDMA/100
Feb 15 22:25:47 pop kernel: [  813.406995] ata1: EH complete

Last edited by AugustePop (2012-02-18 05:06:22)

Offline

#2 2012-02-16 02:08:18

AugustePop
Member
Registered: 2010-04-27
Posts: 95

Re: [SOLVED] is this a hardware failure?

here is the related output of lspci -vv

00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
    Subsystem: Dell Device 0451
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Capabilities: <access denied>

00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0])
    Subsystem: Dell Device 0451
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin C routed to IRQ 44
    Region 0: I/O ports at 6e70 [size=8]
    Region 1: I/O ports at 6e78 [size=4]
    Region 2: I/O ports at 6e80 [size=8]
    Region 3: I/O ports at 6e88 [size=4]
    Region 4: I/O ports at 6ea0 [size=32]
    Region 5: Memory at fed1c800 (32-bit, non-prefetchable) [size=2K]
    Capabilities: <access denied>
    Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
    Subsystem: Dell Device 0451
    Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin B routed to IRQ 18
    Region 0: Memory at f6afbf00 (64-bit, non-prefetchable) [size=256]
    Region 4: I/O ports at 1100 [size=32]
    Kernel driver in use: i801_smbus

Offline

#3 2012-02-16 02:14:29

lagagnon
Member
From: an Island in the Pacific...
Registered: 2009-12-10
Posts: 1,087
Website

Re: [SOLVED] is this a hardware failure?

Looks like hardware to me. What I would do is go into your BIOS setup and reset all to BIOS defaults, check to see if BIOS is detecting the drive OK, save the settings and shutdown. Then open the case and double check the cables to the drive (or reseat the drive if it is in a laptop). Then reboot and see if you get same errors. If you do burn a copy of the UltimateBootCD and do a complete drive test on that drive (you need to know the manufacturer).


Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.

Offline

#4 2012-02-16 02:21:31

AugustePop
Member
Registered: 2010-04-27
Posts: 95

Re: [SOLVED] is this a hardware failure?

i'll try to reset bios first. this problem does not occur on boot. it happens randomly.

Offline

#5 2012-02-16 02:49:09

AugustePop
Member
Registered: 2010-04-27
Posts: 95

Re: [SOLVED] is this a hardware failure?

it is still recognized by bios after resetting. i asked here if it's a hardware problem because i thought if it's a hard disk failure, there should be something about reallocating sectors in my log, which i can not find.

Offline

Board footer

Powered by FluxBB