Board index Linux Hardware

errors from Seagate IDE hard disk

errors from Seagate IDE hard disk

Post by friedhelm.mehner » Mon, 06 Jul 1998 04:00:00



: Dear hardware gurus,

: I wonder if anyone can help me diagnose the disk errors
: I keep getting.

[snip]

Most likely you are running your harddisk too hot.

Install an additional fan blowing at your harddisk.

It is *designed* to be operated like this.
Without a fan it will die a painful death sooner or
later.

Regards,
Friedhelm

--
Microsoft is NOT the answer. Microsoft is the Question.
The answer is: "NO!"
-------------------------------------------------------------------
Friedhelm Mehnert,  Berliner Allee 42,  22850 Norderstedt,  Germany

-------------------------------------------------------------------

 
 
 
Top

errors from Seagate IDE hard disk

Post by Henrik Carlqvis » Tue, 07 Jul 1998 04:00:00



> I get stuff like:

> Jun 29 10:15:21 ram kernel: hda: write_intr: status=0x58 { DriveReady
> SeekComple
> te DataRequest }
> Jun 29 10:15:21 ram kernel: ide0: reset: success
> Jun 29 10:16:11 ram kernel: hda: status error: status=0x00 { }
> Jun 29 10:16:11 ram kernel: hda: no DRQ after issuing WRITE
> The disk is a Seagate EIDE - ST34340A (Medalist) 4.2 GB

I had this in my logs:

..
Aug 31 20:27:18 draken kernel: hdb: status error: status=0x00 { }
Aug 31 20:27:18 draken kernel: hdb: drive not ready for command
Aug 31 20:27:18 draken kernel: hdb: status error: status=0x00 { }
Aug 31 20:27:18 draken kernel: hdb: drive not ready for command
Aug 31 20:27:18 draken kernel: ide0: reset: success
Aug 31 20:27:18 draken kernel: hdb: status error: status=0x00 { }
Aug 31 20:27:18 draken kernel: hdb: drive not ready for command
Aug 31 20:27:18 draken kernel: hdb: status error: status=0x00 { }
..

In my case it turned out to be a bad IDE cable.

regards Henrik

--
spammer strikeback:


Join LinuxNet RC5! Visit http://www.linuxnet.org for info

 
 
 
Top

errors from Seagate IDE hard disk

Post by Jim Howe » Thu, 09 Jul 1998 04:00:00


[Chomp]

Quote:> I have a TX PCI chipset on a 586ITBD(A+) mother board

A number of Seagate drives (not the most recent, but about 1-2 years
old)
have problems with the TX chipset, because the TX boards have changed
one of the IDE signals slightly.  Instead of 5v, it only sends 3.3v,
which confuses some seagate drives.

Take a look at

        http://www.seagate.com/support/disc/faq/inteltx.shtml

Your disk is among those known to be affected by this problem.

Regards,
Jim

 
 
 
Top

errors from Seagate IDE hard disk

Post by B Benne » Thu, 09 Jul 1998 04:00:00


Thanks to all who replied to my message about the
problem with my hard drive.

I think the problem is probably the incompatibility
(noted by Jim Howes) between my particular drive model
(ST34340A) and the TX chipset. I.e the 3.3v volt signals from
the TX IDE controler are too low for some models of Seagate
disk  which expect a 5v signal.

Anyway the suppliers have agreed to replace the drive with
a new (and somewhat larger!) drive.
So hopefully my frustrations are now over and I shall
have many hours of fun reinstalling linux and setting
it up the same as it was before.

cheers,

Brandon

--
===============================================================
Brandon Bennett
Division of Artificial Intelligence   Tel.: +44 (0)113 233 5878
School of Computer Studies           (home) +44 (0)113 274 6920
University of Leeds                   Fax.: +44 (0)113 233 5468

United Kingdom         WWW: http://www.scs.leeds.ac.uk/brandon/
===============================================================

 
 
 
Top

1. Frequent I/O errors to Seagate IDE hard disk

I bought a new hard disk last week, a Seagate ST34342A (`Medalist
4342').  I got it installed and it worked fine for about a week.
But today, something is wrong.  Starting this morning, I started to
see messages like this in the syslog:

----------------------------------------------------------------
Jul 27 14:04:13 plover kernel: end_request: I/O error, dev 16:42, sector 131100
Jul 27 14:04:16 plover kernel: hdd: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
Jul 27 14:04:16 plover kernel: hdd: read_intr: error=0x40 { UncorrectableError }, LBAsect=6082710, sector=131100

Jul 27 13:43:22 plover kernel: hdd: write_intr: status=0x51 { DriveReady SeekComplete Error }
Jul 27 13:43:22 plover kernel: hdd: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=5951615, sector=5
Jul 27 13:44:00 plover kernel: hdd: write_intr: status=0x51 { DriveReady SeekComplete Error }
Jul 27 13:44:00 plover kernel: hdd: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=6004693, sector=53083
----------------------------------------------------------------

I unmounted the disk soon afterwards, and ran e2fsck, and sure enough,
the filesystem was corrupted.  e2fsck couldn't complete, though,
because many of its reads and writes failed.

The disk geometry is 8894 cylinders, 15 heads, 63 sectors.
I have it partitioned into two filesystems:

        Cylinders    1-6143 (2,902,536 blocks)  /dev/hdd1
        Cylinders 6144-8894 (1,226,610 blocks)  /dev/hdd2

So far I've only  had these problems on the second partition; the
first partition hasn't given me any trouble, but that could be because
I haven't done any I/O to it.

I looked in the faqs and howtos, but I couldn't find any relevant
advice.  I also tried an Alta Vista search.  One message I found
suggested re-seating the cables, but I did that and it didn't seem to
help.  I found another message that seemed to discuss a similar
problem in detail, but it was in Dutch, and I don't read Dutch.
(That's at http://www.nllgg.nl/mailinglists/linux/1996/09/193.html if
yu care to see it.)

Other references I found for this kind of error were from people
asking questions about it, but there were no replies to the questions.
Finally, I read articles in this group that seemed to be related, and
again I found someone asking about the same error message, but there
was no followup.

What does this mean?  What's a likely cause?  Where should I go to
research it?  What is the appropriate way to fix the problem?

--



2. panic: trap

3. Ultra 5 IDE hard disks - can I use any PC hard disk?

4. Hardware trouble

5. write errors with seagate hard disk

6. Solaris 2.5 FNS Postscript Printing

7. Read errors from IDE hard disk with e2fs.

8. Unresolved Symbols

9. Problem installing SCO OpenServer 5.0 with IDE CD-ROM on IDE hard disk

10. Seagate IDE Hard Drives

11. Hard Disk Jumper Question on Maxtor IDE as second disk

12. How Clone a hard disk on a Ultra10 (IDE disks ) ?

13. Seagate Cheeta 36Giga LW hard disk and UP2000


All times are UTC
Board index