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
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
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
hdb: DMA disabled
ide0: reset: success
I used to get these messages several months back. I s
mplete 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 SeekCo
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 p
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
lete 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
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
On Tuesday 03 June 2003 03:37, Paul Johnson wrote:
> On Mon, Jun 02, 2003 at 11:58:09PM +0200, Nicos Gollan wrote:
> > hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdc: drive_cmd: error=0x04 { DriveStatusError }
>
> Drive is dead. Expect serious proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jun 02, 2003 at 11:58:09PM +0200, Nicos Gollan wrote:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { DriveStatusError }
Drive is dead. Expect serious problems to develop quickly from this
* Nicos Gollan ([EMAIL PROTECTED]) [030602 15:19]:
> Hi all...
>
> After messages about "error" messages like
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { DriveStatusError }
>
> showing up in syslog got rather
Hi all...
After messages about "error" messages like
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { DriveStatusError }
showing up in syslog got rather common over the last months and I had one of
those today, here's something I found
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
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 (
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 /de
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 wh
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
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
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 machi
meout: 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:
Hello
I once had the error mentioned in the subject line with an
IBM DAQA4030 4GB drive (which smoked up some month ago...)
I fixed it by suplying something similar to the following
options "ide0=noautotune"
to my /etc/lilo.conf. Then it was quiet.
Hope it helps.
bye,
-christian-
--
> -Original Message-
> From: B. Szyszka [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 28, 1999 3:21 PM
> To: Stephen R. Gore
> Cc: debian-user@lists.debian.org
> Subject: RE: DriveReady SeekComplete Error and DriveStatusError
>
> Well "buy something el
The best thing really to do is go to the drive manufacturer's website, and
find and download their diagnostic software for your hard drive.
Unfortunately, you'll need some kind of DOS-bootable floppy or hard drive
partition to RUN the software. I just had two hard drives go to a series
of brownout
I am kind of catching up on old email so I do not know if this problem got
resolved but go into your BIOS and set the IDE controller to PIO Mode 3 or
LOWER and it will work. This is a problem with some UDMA drives. I used to get
them all the time ... constantly as a matter of fact until I turned o
> OK, but for me it remains the only convincing test.
> As it happens I have a couple of old pentium 75 motherboards at home and
> I just imagined that maybe you or somebody you knew also had stuff like
> that that you could use for a test, temporarily.
The other motherboard I have is from an old 4
B. Szyszka wrote:
>
> Like I said, I can't afford to
OK, but for me it remains the only convincing test.
As it happens I have a couple of old pentium 75 motherboards at home and
I just imagined that maybe you or somebody you knew also had stuff like
that that you could use for a test, temporarily
Hi Bart,
> running into some error messages:
> hdb: write_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: write_intr: error=0x04 { DriveStatusError }
Not sure if anyone else has mentioned these yet, here are a few things
you could check:
i) Is there a power down of the driv
> I cannot give you any other suggestions ATM, because you haven't deigned
> to list /any/ of your hardware. Since this seems to be a hardware-related
> problem, the idea that anyone could solve it for you w/o hardware specicfic
> information is ludicrous.
All you had to do was ask, then. Some of
B. Szyszka wrote:
> > Personally, I find it difficult to troubleshoot problems when the only
> > data I'm given is "These things cost money". Give us something to work
> > with.
>
> Well "buy something else" isn't exactly a very good solution to a problem
> either. I cited two error messages and
On Tue, Sep 28, 1999 at 06:20:36PM -0400, B. Szyszka wrote:
> > Personally, I find it difficult to troubleshoot problems when the only
> > data I'm given is "These things cost money". Give us something to work
> > with.
>
> Well "buy something else" isn't exactly a very good solution to a problem
> Personally, I find it difficult to troubleshoot problems when the only
> data I'm given is "These things cost money". Give us something to work
> with.
Well "buy something else" isn't exactly a very good solution to a problem
either. I cited two error messages and asked what they could be cause
On Tue, 28 Sep 1999, B. Szyszka wrote:
: > > Well I can't afford to just go out and get a new harddrive, especially
since
: > > the two that I have no have more than enough space. Is there a way to
: > > run a check on the harddrive that could prove whether or not the
harddrive
: > > itself
B. Szyszka wrote:
> > > Well I can't afford to just go out and get a new harddrive, especially
> > > since
> > > the two that I have no have more than enough space. Is there a way to
> > > run a check on the harddrive that could prove whether or not the harddrive
> > > itself is the problem?
> > T
> > Well I can't afford to just go out and get a new harddrive, especially since
> > the two that I have no have more than enough space. Is there a way to
> > run a check on the harddrive that could prove whether or not the harddrive
> > itself is the problem?
> The surest test would be to use it w
"B. Szyszka" wrote:
>
> Well I can't afford to just go out and get a new harddrive, especially since
> the two that I have no have more than enough space. Is there a way to
> run a check on the harddrive that could prove whether or not the harddrive
> itself is the problem?
The surest test would
> That's *usually*¹ a sign that your hard disk is about to die on you. Do a
> backup, buy a new drive, and copy the stuff over to that one.
Well I can't afford to just go out and get a new harddrive, especially since
the two that I have no have more than enough space. Is there a way to
run a check
peter karlsson wrote:
> B. Szyszka:
>
> > I've reinstalled Debian to try to get a cleaner setup going, but am
> > running into some error messages:
> > hdb: write_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: write_intr: error=0x04 { DriveStatusEr
B. Szyszka:
> I've reinstalled Debian to try to get a cleaner setup going, but am
> running into some error messages:
> hdb: write_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: write_intr: error=0x04 { DriveStatusError }
That's *usually*¹ a sign that your har
Hello,
I've reinstalled Debian to try to get a cleaner setup going, but am
running into some error messages:
hdb: write_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: write_intr: error=0x04 { DriveStatusError }
They show up randomly. Sometimes while I do apt-get or run some
> I have tried several ways of istalling debian, I have formatted my disk
> with BIOS, with fdisk, with fips. I am getting an error message that
> repeats its self:
>
> had: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: unexpected_intr: status=0x41
Hi again!
I have tried several ways of istalling debian, I have formatted my disk
with BIOS, with fdisk, with fips. I am getting an error message that
repeats its self:
had: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
hda: unexpected_intr: status=0x41 { DriveStatusError
41 matches
Mail list logo
