[Gllug] Disk problems

Walid Shaari ws at melinux.com
Wed Sep 11 09:08:50 UTC 2002


On Wed, 2002-09-11 at 09:42, Daniel Andersson wrote:
> <snip>
> > Sep 10 22:02:12 zebra kernel: hdb: lost interrupt
> > Sep 10 22:02:16 zebra kernel: hdb: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> > Sep 10 22:02:16 zebra kernel: hdb: drive not ready for command
> > Sep 10 22:02:16 zebra kernel: hda: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > Sep 10 22:02:16 zebra kernel: hda: dma_intr: error=0x84 { DriveStatusError
> BadCRC }
> > Sep 10 22:02:36 zebra kernel: hdb: lost interrupt
> > Sep 10 22:02:36 zebra kernel: hdb: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> > Sep 10 22:02:36 zebra kernel: hdb: drive not ready for command
> > Sep 10 22:03:03 zebra kernel: hdb: lost interrupt
> > Sep 10 22:03:04 zebra kernel: hdb: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> > Sep 10 22:03:04 zebra kernel: hdb: drive not ready for command
> </snip>
> 
> my first reaction would be "it's a dead disc"
> but after experiencing more or less the same problem, and finding out that
> the memory was foobar, i'd say "replace the memory first"

why not use memtest86 from http://www.memtest86.com/ first to eliminate
any doubts about memory (also about other things such as motherboard,
processor but I guess not in this case) instead of replacing them

regards

Walid

> 
> sounds like a far reach, i know..



-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug




More information about the GLLUG mailing list