Date: Thu, 09 Mar 2000 10:28:29 +0100 From: Fabrizio Poggi <poggif@casaccia.enea.it> To: Bob K <melange@yip.org>, freebsd-stable@FreeBSD.ORG Subject: Re: OT: Cooling hard drives Message-ID: <3.0.5.32.20000309102829.00926550@infos1.casaccia.enea.it> In-Reply-To: <Pine.BSF.4.21.0003090216180.30352-100000@localhost> References: <20000309021338.A38484@evil.2y.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 02.22 09/03/00 -0500, Bob K wrote: I've seen a hand-crafted solution for cooling: put on the free egde of the removable part of case a hole and an additional fan. It does make a continuos current of air in couple with the classic rear fan coil. There's a possibility that in 3.4-stable is a software mechanism of protection for work with sensors of heat that appear in the new series of motherboard? Regard, Fabrizio >I think there's more "professional" solutions out there at this point, but >I've found that a case fan screwed on to the heatsinks salvaged from two >dead CPU fans sitting on top of the drive works rather nicely. > >On Thu, 9 Mar 2000, Coleman Kane wrote: > >> You may need to air-cool that hard drive, sounds like it's overheating and >> messing up. >> >> --cokane >> >> Cy Schubert - ITSD Open Systems Group had the audacity to say: >> > In message <200003070525.VAA09958@cytosine.dhs.org>, Bhishan Hemrajani >> > writes: >> > > I sometimes have this problem with my pc. >> > > >> > > Usually, a good kick will get it to boot. >> > > >> > > Sometimes on laptops and stuff the hard drive cable gets >> > > loose or something. Or, it's a bad hard drive. >> > > >> > > Try giving is a shove. >> > > >> > > --bhishan >> > >> > It's quite possibly a hardware problem though I'm not entirely >> > convinced that it's a fatal hardware problem. I have an IDE drive, wd2 >> > below, >> > >> > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa >> > wdc0: unit 0 (wd0): <WDC AC22100H>, DMA, 32-bit, multi-block-16 >> > wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S >> > wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa >> > wdc1: unit 0 (wd2): <WDC AC22500L>, DMA, 32-bit, multi-block-16 >> > wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S >> > >> > that occasionally has these errors under heavy load conditions, like >> > fscking a badly damaged filesystem. It's done this since it was brand >> > new over four years ago. The Western Digital diagnostics (just checked >> > last week) reported no grown defects, and the Western Digital firmware >> > utility says it doesn't need a firmware upgrade. >> > >> > Interestingly enough, the errors weren't bad enough to halt the system >> > or abort an fsck. >> > >> > Could it be a software problem? Maybe, maybe not. Notice wd0. It too >> > is a Western Digital drive, just older. It's had no problems, ever. >> > >> > Having said all that, I had a couple of WD Caviar WDAC280 drives that >> > would cause an error message once every two to four years. When they >> > had errors, the Western Digital diagnostics would fix them up and >> > they'd run happily for another few years. Each drive had a couple of >> > grown defects. I retired them after 8 years of service. One is still >> > running in a Windows 3.1 PC, 11 years after I purchased it and the >> > other serves quite well as a paper weight and would probably run nicely >> > if it was still in use. >> > >> > >> > Regards, Phone: (250)387-8437 >> > Cy Schubert Fax: (250)387-5766 >> > Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca >> > Open Systems Group, ITSD, ISTA >> > Province of BC >> > "COBOL IS A WASTE OF CARDS." >> > >> > > >> > > > I've had the same problem. Most people have told me that I have to >> > > > replace the hard drive. >> > > > >> > > > I never had the problem before 3.4. Maybe that's just a coincidence, >> > > > though. >> > > > >> > > > >> > > > -- >> > > > Chris Byrnes (CB5820) >> > > > Network Engineer, High Stability Internet Services >> > > > http://www.highstability.com >> > > > >> > > > On Mon, 6 Mar 2000, Archie Cobbs wrote: >> > > > >> > > > > My laptop running 3.4-RELEASE decided it doesn't want to boot. >> > > > > It was uncleanly shut down via the power switch by someone >> > > > > who thought they were shutting down a different machine. >> > > > > >> > > > > Now when it boots, running fsck gives this result: >> > > > > >> > > > > > chip0: <Intel 82439TX System Controller (MTXC)> rev 0x01 on pci0.0.0 >> > > > > > chip1: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0 >> > > > > > ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1 >> > > > > > ... >> > > > > > wdc0 at 0x1f0-0x3f7 irq 14 on isa >> > > > > > wdc0: unit 0 (wd0): <TOSHIBA MK6409MAV> >> > > > > > wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T 512 B/S >> > > > > > wdc1 at 0x170-0x177 irq 15 on isa >> > > > > > wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, >> > > dma, iordis >> > > > > > ... >> > > > > > # fsck / >> > > > > > *** /dev/rwd0s3a >> > > > > > *** Last Mounted on / >> > > > > > *** Root file system >> > > > > > *** Phase 1 - Check Blocks and Sizes >> > > > > > wd0: interrupt timeout (status 58<rdy,seekdone> error 0) >> > > > > > wd0: wdtimeout DMA status 4 >> > > > > > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >> > > > > > wd0: wdtimeout DMA status 4 >> > > > > > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >> > > > > > wd0: wdtimeout DMA status 4 >> > > > > > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >> > > > > > wd0: wdtimeout DMA status 4 >> > > > > > wd0: interrupt timeout (status 50<rdy,seekdone> error 1<no_dam>) >> > > > > > wd0: wdtimeout DMA status 4 >> > > > > > wd0: Last time I say: interrupt timeout. Probably a portable PC. (stat >> > > us 50<rdy,seekdone> error 1<no_dam>) >> > > > > >> > > > > Well, yes in fact it is a portable PC :-) It just seems to hang >> > > > > at this point, even though there seems to be disk activity (like >> > > > > it's continuously retrying). >> > > > > >> > > > > This machine has run fine under this kernel since I installed >> > > > > 3.4-REL a month ago or so. This same problem happens with the >> > > > > 3.4-REL GENERIC kernel. >> > > > > >> > > > > Before this, it was running fine with a 3.0++ kernel and never >> > > > > had this problem after many power cycles. >> > > > > >> > > > > Is there any hope in getting this machine to work again?? >> > > > > Howabout disabling DMA? Is there some way to do that? >> > > > > >> > > > > Thanks for any pointers.. >> > > > > -Archie >> > > > > >> > > > > _________________________________________________________________________ >> > > __ >> > > > > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.c >> > > om >> > > > > >> > > > > >> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > > > > with "unsubscribe freebsd-stable" in the body of the message >> > > > > >> > > > >> > > > >> > > > >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > > > with "unsubscribe freebsd-hackers" in the body of the message >> > > > >> > > >> > > >> > > >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > > with "unsubscribe freebsd-stable" in the body of the message >> > >> > >> > >> > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > with "unsubscribe freebsd-stable" in the body of the message >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-stable" in the body of the message >> > >Bob <melange@yip.org> >"Don't make the bear smarter when it's asleep" - Ioana Timariu > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20000309102829.00926550>