As promised here's the summary of a weird day: -drive mentioned in my earlier discussion checked out completely 100% good after repair done by dlgdiag (dos) program from WD -managed to reduce hda: irq timeout messages to 2-3 during the dselect process; quite a nice time improvement too -swapped ide cables - no change -brought cables and HDD to an K6-2 500 on an AOpen mobo, HDD is hda and CDROM is hdb -> no irq messages, a perfect load!
Is it the Biostar mobo or is is the disk? I played with bios settings, cables, and disks combinations all day. At the end of the day, drive in question went belly-up. Nuts! I took my remaining parts and built a machine (Biostar mobo and WD HDD) and loaded another distro with 2.2.12 - no disk errors. I used dlgdiag on the drive and found no problems. I think I'll get an IBM HDD to replace the busted WD. Is there any way that Debian could be at odds with the Biostar MoBo? Should I just ignore those pesky messages? Where do those messages come from? The kernel or some driver? Could it be a 2.2.19pre17 issue? Mike ----- Original Message ----- From: "Michael Mueller" <[EMAIL PROTECTED]> To: <[email protected]>; "Hugo van der Merwe" <[EMAIL PROTECTED]> Sent: Friday, August 10, 2001 2:20 PM Subject: Re: hard drive problems... misconfiguration? > I am getting the same kind of errors shown below from your email (see mail > with subject "deselect and hda: irq timeout" 10-9 ... 10-10). > > I have a brand-new Western Digital WB100EB. I downloaded a diagnostic > program from www.wdc.com. It detected and repaired errors. Now I am > writing zeros to the drive and that is taking a long time. When I'm done, I > will repartition and try loading again. > > I'll report findings shortly. > > Mike > > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > ide0: reset: success > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > ide0: reset: success > hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=524418, > sector=524355 > end_request: I/O error, dev 03:01 (hda), sector 524355 > EXT2-fs error (device ide0(3,1)): ext2_write_inode: unable to read inode > block - inode=28353, block=65544 > > -- > To send me private (non-world-readable) mail, GPG encrypt it. > 1024D/60715698: 5F2E 8EC2 E0A4 5D25 0569 F281 4A6C D76D 6071 5698 > > ----- Original Message ----- > From: "Hugo van der Merwe" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, August 10, 2001 10:09 AM > Subject: hard drive problems... misconfiguration? > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
