LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   DMA I/O or Hard Disk error I am confused : Dell Latitude D400 (Typical Installation) (https://www.linuxquestions.org/questions/linux-newbie-8/dma-i-o-or-hard-disk-error-i-am-confused-dell-latitude-d400-typical-installation-4175427647/)

charging-ibis 09-17-2012 10:12 AM

DMA I/O or Hard Disk error I am confused : Dell Latitude D400 (Typical Installation)
 
Note: This question may appear to be a distro discussion but a assure it isn't.

Hello everybody, I am now having this problem since I tried to install Arch linux on my laptop.
I have tried to install other distros but at the command line while booting up a live disstro or
installing. I am getting these messages that automaticaly populates the screen preventing any kind
of installation and then the system just hangs. I am using a Dell D400 laptop, RAM (PC2100) 512 MB.

Is this a I/O error, or DMA error, Hard Drive error. How can this be resolved. do I need to do so by
using 'fsck' command? May I also get a good explanation on what is happening as well?



Code:

[221.979285] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[221.979375] ata1.00: fialed command: READ DMA
[221.979434] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[221.979436]          res 40/00:01:d4:89:bb/00:00:00:00:00/e0 Emask 0x4 (timeout)
[221.979599] ata1.00: status: {DRDY}
[252.291953] ata1.00: exception Emask 0x0 SAct 0x0 Serr0x0 action 0x0
[252.292053] ata1.00: BMDMA stat 0x25
[252.292100] ata1.00: fialed command: READ DMA
[252.292158] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[252.292160]          res 51/01:62:5b:87:bb/00:00:00:00:00/e0 Emask 0x4 (device error)
[282.910326] ata1.00: status: {DRDY ERR}
[282.910302] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[282.910496] ata1.00: fialed command: READ DMA
[282.910628] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[282.910633]          res 40/00:62:5b:87:bb/00:00:00:00:00/e0 Emask 0x4 (timeout)
[282.910999] ata1.00: status: {DRDY}
[311.012069] ata1.00: exception Emask 0x0 SAct 0x0 Serr0x0 action 0x0
[311.012241] ata1.00: BMDMA stat 0x25
[311.012341] ata1.00: fialed command: READ DMA
[311.012471] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[311.012476]          res 51/01:1b:a2:87:bb/00:00:00:00:00/e0 Emask 0x4 (device error)
[342.012852] ata1.00: status: {DRDY ERR}
[342.028474] ata1.00: exception Emask 0x0 SAct 0x0 Serr0x0 action 0x6
[342.028649] ata1.00: BMDMA stat 0x25
[342.028749] ata1.00: fialed command: READ DMA
[342.028880] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[342.028885]          res 51/01:1a:a3:87:bb/00:00:00:00:00/e0 Emask 0x4 (device error)
[342.029261] ata1.00: status: {DRDY ERR}
[373.151274] ata1.00: exception Emask 0x0 SAct 0x0 Serr0x0 action 0x0 frozenata1.00: fialed command: READ DMA
[373.151470] ata1.00: cmd c8/00:00:bd:86:bb/00:00:00:00:00/e0 tag 0 dma 131072 in
[373.151601]          res 40/00:1a:a3:87:bb/00:00:00:00:00/e0 Emask 0x4 (timeout)
[373.151606] ata1.00: status: {DRDY}
[373.151973] end_request: I/O error, dev sda, sector 12289725
[373.360926] buffer I/O error on device sda2, logical block 0
[373.361080] buffer I/O error on device sda2, logical block 1
[373.361238] buffer I/O error on device sda2, logical block 2
[373.366871] buffer I/O error on device sda2, logical block 3
[373.372220] buffer I/O error on device sda2, logical block 4
[373.377457] buffer I/O error on device sda2, logical block 5
[373.382591] buffer I/O error on device sda2, logical block 6
[373.382591] buffer I/O error on device sda2, logical block 7
[373.392529] buffer I/O error on device sda2, logical block 8
[373.397322] buffer I/O error on device sda2, logical block 9

Help is most appriciated.

~Cheers

TobiSGD 09-17-2012 10:42 AM

This in fact looks like a hardware error. I would recommend to test the harddisk with its manufacturer's diagnosis tool.

charging-ibis 09-17-2012 10:48 AM

Hey thanks.

smeezekitty 09-17-2012 05:04 PM

I agree it looking like a dieing or dead hard disk but it could also be a flaky motherboard.


All times are GMT -5. The time now is 02:46 AM.