Date: Tue, 24 Nov 1998 01:46:27 +0200 (EET) From: Florin Nicolescu <fnicoles@pcnet.pcnet.ro> To: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Subject: Re: sever ide hdd crash Message-ID: <199811232346.BAA00552@nick.ro>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hello, I posted about two weeks ago a possible kernel bug regarding the hdd crush I have experienced. I couldn't continue this discussion earlier, because I couldn't make my computer running until now. All the answers suggested something like >What you have there sounds like a plain, old-fashioned, simple, hard disk failure. Not >space aliens, not the ghost of Elvis trying to communicate with the living through your >hard drive, but what the spanish call "el seagate muerte" Your drive is dead, Jim. Maybe I was exaggerating a little (I had just lost my two month work in a quite big project), but it wasn't so simple. After two days, I changed my burned hdd (Quantum Fireball 4.3Gb) with a brand new IBM 4.3Gb. When I came home and start reinstalling the os, I just witness the second hdd crash. I changed again the hdd (also a IBM 4.3 Gb) together (as suggested by my supplier) with the ide atapi cdrom (the two crashes happened during cdrom copy) and with the cables. Again, trying to install my box, I start receiving messages like: wd0: interrupt timeout: wd0: status 50<rdy,seekdone,drq,index> error 0 wd0: interrupt timeout: wd0: status 50<rdy,seekdone> error 1<no_dam> I canceled everything. After rebooting, for about five minutes the hdd wasn't seen by bios, and after that was seen being 435Mb. After a low level format it was ok. Finally, I succeeded installing my box using a lpt Iomega ZIP drive (I got the dist copied on ZIP, than I put it on a dos partition, ...). With this occasion, I saw the famous blue error window of M$ Windows stating hdd write error during cdrom access. Now I changed everything in my computer (except the ATX case and the CPU) but I am seeing the same errors (the only thing that is quasi-the-same is the cdrom brand, the rest is brand new - I insisted in breaking the seal personally). Does anyone have any clue about this? I traced some previous threads about wd timeouts, but they were no help. The only chance to have it accessing the cdrom for more that 1 minute (but finally get the same error) is to disable both UDMA and PIO mode for wd and wcd. Thanks, Florin. BTW: I don't belive in aliens nor in ghosts or vampires :) - -- - ------------------------------------------------------------------ | Florin-Nicolae Nicolescu <fnicoles@pcnet.pcnet.ro> | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | - ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | - ------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNlnzzW95n9Jm9dehAQFO5QQAt/RnQ1HnoLe+k9rrpL11R42o9cWMdkfZ Y90dachRluk2o+n/JjTlxD9UIQv6u3NmKxhTH9eU5qEsPLO4kFp46+JEYkcSMF0o PkDl9XS0ZeN0V6C6xlyXvlyfUuKBsYopmT701m8irwM629p3cxIuH1fUhARoKBgZ 77AGQWhD/6w= =QTWt -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811232346.BAA00552>