From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Strange IDE errors
Date: Wed, 21 Jan 2004 10:33:07 +0100 [thread overview]
Message-ID: <yw1xn08hlk8c.fsf@ford.guide> (raw)
After 13 days uptime without a glitch, my Alpha SX164 running Linux
2.6.0 threw the errors below at me. The disks are Seagate Barracuda
120 GB disks hooked up to a Highpoint hpt374 with SATA bridges. The
hdi disk was recently replaced since the old disk would fail randomly
and mysteriously. Is something in my machine destroying hdi? Apart
from the lines about hdk below, there has been no trouble with the
other disks. As usual, SMART doesn't tell me anything useful,
i.e. there are no errors logged and all attributes seem OK. After a
reboot everything seems to work properly. The question is for how
long. Could the controller be faulty?
hdi: dma_intr: status=0x00 { }
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: DMA disabled
hdi: drive not ready for command
ide4: reset: success
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
ide4: reset: success
hdi: status error: status=0x00 { }
hdi: no DRQ after issuing WRITE
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
ide4: reset: success
hdi: status error: status=0x00 { }
hdi: no DRQ after issuing WRITE
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
ide4: reset: success
hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdi: drive not ready for command
hdi: status error: status=0xd0 { Busy }
hdi: drive not ready for command
ide4: reset: master: error (0x00?)
hdk: dma_timer_expiry: dma status == 0x00
hdk: DMA timeout retry
hdk: timeout waiting for DMA
hdk: status timeout: status=0xd0 { Busy }
hdk: drive not ready for command
ide5: reset: success
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
hdi: status error: status=0x00 { }
hdi: drive not ready for command
ide4: reset: success
hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdi: drive not ready for command
hdi: status error: status=0xd0 { Busy }
hdi: drive not ready for command
ide4: reset: success
hdi: lost interrupt
hdi: lost interrupt
hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdi: drive not ready for command
hdi: status error: status=0xd0 { Busy }
hdi: drive not ready for command
ide4: reset: master: error (0x00?)
hdi: lost interrupt
hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdi: drive not ready for command
hdi: status error: status=0xd0 { Busy }
hdi: drive not ready for command
ide4: reset: master: error (0x00?)
end_request: I/O error, dev hdi, sector 11297617
raid1: Disk failure on md3, disabling device.
Operation continuing on 1 devices
raid1: md3: rescheduling sector 22049024
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:md2
disk 1, wo:1, o:0, dev:md3
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:md2
raid1: md2: redirecting sector 22049024 to another mirror
end_request: I/O error, dev hdi, sector 226111
raid1: Disk failure on md1, disabling device.
Operation continuing on 1 devices
raid1: md1: rescheduling sector 452096
end_request: I/O error, dev hdi, sector 226127
raid1: md1: rescheduling sector 452112
end_request: I/O error, dev hdi, sector 226143
raid1: md1: rescheduling sector 452128
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:md0
disk 1, wo:1, o:0, dev:md1
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:md0
raid1: md0: redirecting sector 452096 to another mirror
raid1: md0: redirecting sector 452112 to another mirror
raid1: md0: redirecting sector 452128 to another mirror
--
Måns Rullgård
mru@kth.se
reply other threads:[~2004-01-21 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xn08hlk8c.fsf@ford.guide \
--to=mru@kth.se \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox