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 drive through b
> 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 { DriveStatusError }
>
> That's *usually*¹ a sign
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 hard disk is about to die on
18 matches
Mail list logo
