badCRC
from messages:
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jan 19 10:19:25 dam-main kernel: ide: failed opcode was: unknown
My hda holds grub, a XP partition and /
my home partition is on a md1 using hde5 and hdf5
what is the best way to replace hda and get the grub MBR, XP and /
transfered over. Re-install?
on a possibly related subject, I can not authenticate against root
user. I can sudo su. I can set root passwd, but I can not su to root.
Could this be related or a seperate issue?
--
Damon L. Chesser
[EMAIL PROTECTED]
404-271-8699
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: badCRC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/08 10:00, Damon L. Chesser wrote:
from messages:
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jan 19 10:19:25 dam-main kernel: ide: failed opcode was: unknown
My hda holds grub, a XP partition and /
my home partition is on a md1 using hde5 and hdf5
what is the best way to replace hda and get the grub MBR, XP and /
transfered over. Re-install?
I'd backup my /home and any other data partitions, then install from
scratch and restore home+data.
on a possibly related subject, I can not authenticate against root
user. I can sudo su. I can set root passwd, but I can not su to root.
Could this be related or a seperate issue?
Can you log in as root?
- --
Ron Johnson, Jr.
Jefferson LA USA
I'm not a vegetarian because I love animals, I'm a vegetarian
because I hate vegetables!
unknown
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHkidjS9HxQb37XmcRArEGAKDRouffRwmKhn9O3SJIO40K09g+wwCfay+Z
9LPQHiZDNPRoCO/Lk7HsOWo=
=m8uX
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: badCRC
Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/08 10:00, Damon L. Chesser wrote:
from messages:
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Jan 19 10:19:25 dam-main kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jan 19 10:19:25 dam-main kernel: ide: failed opcode was: unknown
My hda holds grub, a XP partition and /
my home partition is on a md1 using hde5 and hdf5
what is the best way to replace hda and get the grub MBR, XP and /
transfered over. Re-install?
I'd backup my /home and any other data partitions, then install from
scratch and restore home+data.
on a possibly related subject, I can not authenticate against root
user. I can sudo su. I can set root passwd, but I can not su to root.
Could this be related or a seperate issue?
Can you log in as root?
yes, tty1 lets me log in. I can not log in as root from gnome gui, SID
current from gnome-terminal, but can log in using sudo su.
- --
Ron Johnson, Jr.
Jefferson LA USA
I'm not a vegetarian because I love animals, I'm a vegetarian
because I hate vegetables!
unknown
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHkidjS9HxQb37XmcRArEGAKDRouffRwmKhn9O3SJIO40K09g+wwCfay+Z
9LPQHiZDNPRoCO/Lk7HsOWo=
=m8uX
-END PGP SIGNATURE-
--
Damon L. Chesser
[EMAIL PROTECTED]
404-271-8699
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DriveReady SeekComplete Error DriveStatusError BadCRC
On Tue, Nov 20, 2007 at 03:02:29AM +0100, SPKills wrote: I just (re)installed debian etch on my machine, at the first reboot i got some errors on my harddisk and i don't really know what it's about... But i'm pretty sure it's good at all and i probably have to worry about... I tried to do a fschk -c /dev/hda1 but i got a warning message telling me that my disk is mounted and it's pretty bad to use it on a mounted disk so i aborted. I'm pretty new with those things and really need help. What promted a (re) install? Its either: 1. true hardware error 1.1 the drive is dying 1.2 the cable is loose 1.3 the power cable is loose or power is flaky 2. software error 2.1 bum kernel driver for the drive 2.2 some other kernel problem. Doug. Thx for your help, after many search on the net and verifying all my cable, testing the drive on another machine it seems that's my harddisk is dying... B. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DriveReady SeekComplete Error DriveStatusError BadCRC
Hi,
I just (re)installed debian etch on my machine, at the first reboot i
got some errors on my harddisk and i don't really know what it's
about... But i'm pretty sure it's good at all and i probably have to
worry about...
I tried to do a fschk -c /dev/hda1 but i got a warning message telling
me that my disk is mounted and it's pretty bad to use it on a mounted
disk so i aborted.
I'm pretty new with those things and really need help.
Here is a part of 'dmesg' command :
debian:~# dmesg
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdb: DMA disabled
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 34030959
Buffer I/O error on device hda1, logical block 4253862
lost page write due to I/O error on hda1
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
Any help should be usefull !
Thx
B.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DriveReady SeekComplete Error DriveStatusError BadCRC
SPKills wrote:
Hi,
I just (re)installed debian etch on my machine, at the first reboot i
got some errors on my harddisk and i don't really know what it's
about... But i'm pretty sure it's good at all and i probably have to
worry about...
I tried to do a fschk -c /dev/hda1 but i got a warning message telling
me that my disk is mounted and it's pretty bad to use it on a mounted
disk so i aborted.
If hda1 does not contain your / partition, then unmount it before
running fsck.
I'm pretty new with those things and really need help.
Here is a part of 'dmesg' command :
debian:~# dmesg
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
snip
hdb: DMA disabled
ide0: reset: success
I used to get these messages several months back. I suspected they might
relate to a failing drive and took a backup of my most critical data.
However after several changes, including upgrading the kernel, fiddling
with the power connectors and the ide cables of the hard-disk, these
errors just stopped occuring.
end_request: I/O error, dev hda, sector 34030959
Buffer I/O error on device hda1, logical block 4253862
lost page write due to I/O error on hda1
This error appears to be more serious than the earlier ones though. The
only time I see this type of error is when there *is* an actual problem
with the hardware. I would recommend a backup as soon as you can manage.
--
Raj Kiran Grandhi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DriveReady SeekComplete Error DriveStatusError BadCRC
On Tue, Nov 20, 2007 at 03:02:29AM +0100, SPKills wrote: I just (re)installed debian etch on my machine, at the first reboot i got some errors on my harddisk and i don't really know what it's about... But i'm pretty sure it's good at all and i probably have to worry about... I tried to do a fschk -c /dev/hda1 but i got a warning message telling me that my disk is mounted and it's pretty bad to use it on a mounted disk so i aborted. I'm pretty new with those things and really need help. What promted a (re) install? Its either: 1. true hardware error 1.1 the drive is dying 1.2 the cable is loose 1.3 the power cable is loose or power is flaky 2. software error 2.1 bum kernel driver for the drive 2.2 some other kernel problem. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BadCRC Drive Errors on Software RAID1
On Thu, Mar 23, 2006 at 05:55:55PM +, Andy wrote:
Hello List,
I am running 2x Seagate 250GB SATA-II 7200.9 disks configured as linux
software RAID-1.
The following errors occasionally appear in /var/log/kern.log:
kernel: ata1: translated ATA stat/err 0x51/84 to SCSI
SK/ASC/ASCQ 0xb/47/00
kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
kernel: ata1: error=0x84 { DriveStatusError BadCRC }
I had assumed I have a bad disk, but the odd thing is when I connect
either disk individually I can use DD to fill it with zeros to its
capacity without any errors.
Do you think I have a bad disk, or should I suspect a problem with my
SATA controller or RAID-1 setup?
Thanks, Andy
I am having the same problem and did a quick google search a couple of
weeks ago. The answer at the time was that it's a bad cable. I haven't
had a chance to check my cable yet, but it made me feel better about
losing any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Error]dma_intr: status=0x51 { DriveReady SeekComplete Error } ,dma_intr: error=0x84 { DriveStatusError BadCRC } with eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x6 length 0 status 00000600!
On Tuesday 07 December 2004 04:45, Adomelf wrote:
Hi,
I meet some errors occasionally ,such as
dma_intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x84 { DriveStatusError BadCRC }
You don't say what version of Linux you are running. I had this problem on an
old motherboard based in the VIA chipset. Can't remember the model right
now. But I also remember reading that a potential bug fix for it was put
into the kernel (somewhere around 2.4.10 I think).
--
Alan Chandler
[EMAIL PROTECTED]
First they ignore you, then they laugh at you,
then they fight you, then you win. --Gandhi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Error]dma_intr: status=0x51 { DriveReady SeekComplete Error } ,dma_intr: error=0x84 { DriveStatusError BadCRC } with eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x6 length 0 status 00000600!
Hi,
I meet some errors occasionally ,such as
dma_intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x84 { DriveStatusError BadCRC }
eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x6
length 0 status 0600!
in the same time.
The frequence of these errors increased with the frequence of IO operations.
That's some information.
1.DMA control
00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20262 (rev 01)
Subsystem: Promise Technology, Inc.: Unknown device 4d33
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at d400 [size=8]
I/O ports at d800 [size=4]
I/O ports at dc00 [size=8]
I/O ports at e000 [size=4]
I/O ports at e400 [size=64]
Memory at e802 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at e400 [disabled] [size=64K]
Capabilities: [58] Power Management version 1
2.my harddisk
/dev/hde:
Model=ST3200021A, FwRev=3.01, SerialNo=3LJ2EQNN
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs RotSpdTol.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 *udma4 udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
3.dmesg
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
4.kernel version
kernel: 2.4.27
using deb 2.4.27-1-686
Thanks a lot for everyone's help.
--
Have a nice day,amigo
--
Have a nice day,amigo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DriveStatusError BadCRC
on Sat, Sep 13, 2003 at 12:18:22PM -0400, Tom Allison ([EMAIL PROTECTED]) wrote:
I need some help.
I have a FIC SD-11 motherboard and a hard drive that keeps dumping out the
above error whenever dma is enabled.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I am running kernel 2.4.14-2.4.22 and they have all seen this problem.
Things that I've done so far:
replaced the IDE cable, no affect.
replaced the hard drive, no affect.
replaced both hard drive and cable and still no affect.
This system was moved into a new case (bigger with better ventalation)
about a year ago. I'm not sure if this is related, but it's something that
happened.
I have two other machines with similar FIC SD-11 motherboards and they seem
to be just fine.
Right now I'm trying to figure out if this is either a bad motherboard or I
have to start wrapping everything in aluminum foil.
Possibly a drive configuration error. hdparm may be able to work around
this, though this sort of error's fix is often elusive.
It's also not impossible that you're encountering a batch of bad disks,
so check message boards, and post your serial or batch number for
comparison.
Another possibility is a bad IDE controller. You might try plugging the
disk into an IDE cotroller add-in card to test this. Borrow if
possible, buy if necessary.
Peace.
--
Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/
What Part of Gestalt don't you understand?
Geek for hire: http://kmself.home.netcom.com/resume.html
pgp0.pgp
Description: PGP signature
DriveStatusError BadCRC
I need some help.
I have a FIC SD-11 motherboard and a hard drive that keeps dumping out the
above error whenever dma is enabled.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I am running kernel 2.4.14-2.4.22 and they have all seen this problem.
Things that I've done so far:
replaced the IDE cable, no affect.
replaced the hard drive, no affect.
replaced both hard drive and cable and still no affect.
This system was moved into a new case (bigger with better ventalation) about
a year ago. I'm not sure if this is related, but it's something that happened.
I have two other machines with similar FIC SD-11 motherboards and they seem
to be just fine.
Right now I'm trying to figure out if this is either a bad motherboard or I
have to start wrapping everything in aluminum foil.
--
Dijkstra probably hates me
(Linus Torvalds, in kernel/sched.c)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DriveStatusError BadCRC on hda
At 22:36 Uhr -0500 18.8.2001, Phil Brutsche wrote: You may want to consider replacing the IDE cable. Thanks, I'll look for another one. What kernel is this? If you're using 2.4.x or 2.2.x with Andre Hedrick's IDE patches this is done automatically. It's 2.4.7 (from kernel.org) hdparm /dev/hda /dev/hda: multcount= 0 (off) I/O support = 1 (32-bit) unmaskirq= 1 (on) using_dma= 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 50800/16/63, sectors = 117266688, start = 0 Do you refer to the I/O 32-bit support thing? (i.e. 32 bits are translated to 66mhz 16 bits on the cable?) This is an Athlon Thunderbird, correct? Yes I think so. Thanks, Christian.
Re: DriveStatusError BadCRC on hda
A long time ago, in a galaxy far, far way, someone said... What kernel is this? If you're using 2.4.x or 2.2.x with Andre Hedrick's IDE patches this is done automatically. It's 2.4.7 (from kernel.org) hdparm /dev/hda /dev/hda: multcount= 0 (off) I/O support = 1 (32-bit) unmaskirq= 1 (on) using_dma= 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 50800/16/63, sectors = 117266688, start = 0 Do you refer to the I/O 32-bit support thing? (i.e. 32 bits are translated to 66mhz 16 bits on the cable?) No - having 32-bit I/O support enabled can help some, but it's not what you're looing for. You're looking for what it says for the using_dma flag. You can also run hdparm -t /dev/hda as root - with UMDA66 you should see results somewhere in the vicinity of 25-30 MB/sec. Phil
Re: DriveStatusError BadCRC on hda
At 15:18 Uhr -0500 19.8.2001, Phil Brutsche wrote: with UMDA66 you should see results somewhere in the vicinity of 25-30 MB/sec. I get 23 MB/sec. (On the 2year old mac it's 12MB/sec) (Hmm I would have thought that with a bus clock of 66Mhz and 16 bit bus width one would get transfer rates of 132MB/sec; why four times less?) chris
DriveStatusError BadCRC on hda
Hello
I've seen some messages in the system log and am wondering what to do
with them:
Aug 14 06:25:53 pflanze kernel: hda: timeout waiting for DMA
Aug 14 06:25:53 pflanze kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
DriveStatusError BadCRC }
Doing a zgrep hda on the old messages logs I get:
messages.0:Aug 6 06:25:47 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 6 06:25:47 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 6 06:25:47 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
messages.0:Aug 8 06:26:24 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 8 06:26:24 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 8 06:26:24 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
messages.0:Aug 12 06:27:50 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 12 06:27:50 pflanze kernel: hda: irq timeout:
status=0x59 { DriveReady SeekComplete DataRequest Error }
messages.0:Aug 12 06:27:50 pflanze kernel: hda: irq timeout:
error=0x84 { DriveStatusError BadCRC }
The machine runs since 2nd of august with a new hard disk (Quantum
fireball). What I'm wondering is why there is no sector listed where
the error occurs (I'm used to scsi error messages where erroneous
sectors are listed). The machine is used as small corporate
server/firewall, it is not used at all at this time (except cron
jobs). I'm running noflushd so the disk is spun down most of the time
during the night.
Is it a read error on the disk (if yes, should I worry about my
reiserfs filesystem?, should I run a bad-blocks test?), or is it some
communication error or so?
Some parts from dmesg that might be relevant:
PCI: PCI BIOS revision 2.10 entry at 0xfb250, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
Found VT82C686A, not applying VIA latency patch.
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
hd0: C/H/S=28741/16/255 from BIOS ignored
hda: QUANTUM FIREBALLP AS60.0, ATA DISK drive
hdb: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive
hdc: ST340824A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 117266688 sectors (60041 MB) w/1902KiB Cache, CHS=116336/16/63, UDMA(66)
BTW: should/could I switch to UDMA/66Mhz or is this done automatically?
BTW II: I also see in dmesg the following - does this really mean
there is only 256k L2 cache?? Even my G3 macintosh from 2 years ago
has 1 MB !! This is a 800Mhz Athlon.
CPU: Before vendor init, caps: 0183f9ff c1c7f9ff , vendor = 2
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183f9ff c1c7f9ff
CPU: After generic, caps: 0183f9ff c1c7f9ff
CPU: Common caps: 0183f9ff c1c7f9ff
CPU: AMD Athlon(tm) Processor stepping 02
Sorry for the lenghty post Thanks for clarification
Christian.
Re: DriveStatusError BadCRC on hda
On Sun, Aug 19, 2001 at 03:05:42AM +0100, Christian Jaeger wrote:
Hello
I've seen some messages in the system log and am wondering what to do
with them:
Aug 14 06:25:53 pflanze kernel: hda: timeout waiting for DMA
Aug 14 06:25:53 pflanze kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
DriveStatusError BadCRC }
With a previous machine, I recall seeing the above when a hard drive
was configured by the BIOS to power down after some period of non-use,
but power management wasn't built into the kernel. There was never any
data loss, only the disturbing messages.
Building a kernel with power support fixed it.
Re: DriveStatusError BadCRC on hda
Thanks for your reply. I've built the kernel with apm as a module. I've modprobe'd the apm module now (/proc/apm reports -1% battery charge :-) ) and installed apmd - i'll see if that changes anything. christian At 20:13 Uhr -0500 18.8.2001, Brian McGroarty wrote: With a previous machine, I recall seeing the above when a hard drive was configured by the BIOS to power down after some period of non-use, but power management wasn't built into the kernel. There was never any data loss, only the disturbing messages. Building a kernel with power support fixed it.
Re: DriveStatusError BadCRC on hda
A long time ago, in a galaxy far, far way, someone said... Hello I've seen some messages in the system log and am wondering what to do with them: You may want to consider replacing the IDE cable. The CRC errors make me suspicious that it may be bad. The sector not found errors may be a side effect of data corruption pointed out by the CRC errors. [...] hda: 117266688 sectors (60041 MB) w/1902KiB Cache, CHS=116336/16/63, UDMA(66) BTW: should/could I switch to UDMA/66Mhz or is this done automatically? It looks like it's done automatically on your computer. What kernel is this? If you're using 2.4.x or 2.2.x with Andre Hedrick's IDE patches this is done automatically. If you have the hdparm package installed you can check this with hdparm /dev/hda as root. Example output on one of my PII systems running kernel 2.4.9 would be: /dev/hda: multcount= 16 (on) I/O support = 0 (default 16-bit) unmaskirq= 0 (off) using_dma= 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 8374/16/63, sectors = 8440992, start = 0 BTW II: I also see in dmesg the following - does this really mean there is only 256k L2 cache?? Even my G3 macintosh from 2 years ago has 1 MB !! This is a 800Mhz Athlon. This is an Athlon Thunderbird, correct? Then, yes it it has only a 256kb L2 cache. There are lots of reasons why a 2 year old G3 Mac has a 1 meg cache and the Athlon has a 256k cache, all of which are irrelevent given the difference between the CPU architectures. Phil
Re: DriveStatusError BadCRC on hda
A long time ago, in a galaxy far, far way, someone said... There are lots of reasons why a 2 year old G3 Mac has a 1 meg cache and the Athlon has a 256k cache, all of which are irrelevent given the difference between the CPU architectures. Um, that shoudl read: There are lots of reasons why a 2 year old G3 Mac has a 1 meg cache and the Athlon has a 256k cache, all of which are totally dependent on the difference between the CPU architectures. Kinda like the can't compare clock speed across CPU architectures argument. Phil
