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
ning 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 SeekCo
On 08/01/2005 05:42 am, Alvin Oga wrote:
> On Sun, 31 Jul 2005, persall wrote:
> > DriveReady SeekComplete Error
>
> that is usually:
> a) mixture of ide devices on the same ide cable
> - keep cdrom and dvd on its own cable
> - keep ata133 devices on a different cable tha
On Sun, Jul 31, 2005 at 10:12:56PM +, persall wrote :
> DriveReady SeekComplete Error
> I get this error when trying to copy a large file
> from my CD drive. I have Debian 3.1 Sarge.
> It's not the hardware, because I dual boot to Windows
> and I can copy the file I want
On Sun, 31 Jul 2005, persall wrote:
> DriveReady SeekComplete Error
that is usually:
a) mixture of ide devices on the same ide cable
- keep cdrom and dvd on its own cable
- keep ata133 devices on a different cable than ata100 drives
- bad ide driver ( aka motherbo
DriveReady SeekComplete Error
I get this error when trying to copy a large file
from my CD drive. I have Debian 3.1 Sarge.
It's not the hardware, because I dual boot to Windows
and I can copy the file I want using Windows.
In fact, as I recall, I could also copy this file from
this CD drive w
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
'DriveReady SeekComplete Error' ?
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Thanks. I tried
rm -rf /dev/dvd
ln -s /dev/hdc /dev/dvd
... but am not having success in mounting dvd and dmesg is giving me
the output below
which I can't interpret. Can someone te
On Thu, 17 Jun 2004 23:09:44 +1200
Adam Bogacki <[EMAIL PROTECTED]> wrote:
> ... but am not having success in mounting dvd and dmesg is giving me
> the output below
> which I can't interpret. Can someone tell me what
>
> 'DriveReady SeekComplete Error' mean
Thanks. I tried
rm -rf /dev/dvd
ln -s /dev/hdc /dev/dvd
... but am not having success in mounting dvd and dmesg is giving me
the output below
which I can't interpret. Can someone tell me what
'DriveReady SeekComplete Error' means ?
Adam Bogacki,
[EMAIL PROTECTED]
on Sun, Jan 28, 2001 at 11:21:20PM -0800, jdls ([EMAIL PROTECTED]) wrote:
> Hello,
>
> In the middle of reading a disc for package installation of deselect an error
> occurs:
>
> Trunks:/#hdc: cdrom_decode_status:status=0x51
> {DriveReady SeekComplete Error}
> hdc: cd
Hello,
In the middle of reading a disc for package
installation of deselect an error occurs:
Trunks:/#hdc:
cdrom_decode_status:status=0x51
{DriveReady SeekComplete Error}
hdc: cdrom_decode_status: error=0x30
end_request: I/0 error, dev 16:00 (hdc) sector
110248
Is my cd defective or
Fernando:
Yes, check "no" for DMA Enabled in kernel config.
This thread about the message has appeared before.
Opinion was divided whether it signaled a bad hard drive or a minor glitch.
By all means, if you can exchange your hard drive easily, do.
I chose to disable the DMA by default optio
Dear Eric,
Thank you very much for your answer.! The Ttings which are related to DMA
in my present kernel configurations are the following:
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
If I understand correctly your solution, I should say No to
CONFIG_BLK_DEV_IDEDMA. Is that correct?
One thi
Fernando:
I removed the DMA option from my compilation of the kernel. I do not get
those messages anymore.
Eric Wolven
happening is that, already at the boot time, I get the
following message during the partition check:
Partition check:
hda: hda1
hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 >
hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBA
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
38 matches
Mail list logo
