Duncan wrote: > Raffaele BELARDI <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], > excerpted below, on Tue, 20 Nov 2007 08:47:32 +0100: > > ... You never mentioned exactly what happened to the disk. Mine was > overheating. I live in Phoenix, AZ, and my AC went out in the middle of > the summer, with me gone and the computer left running. With outside > temps often reaching close to 50 C (122 F), the temps inside with the AC > off could have easily reached 60 C (140 F). Ambient case air temps could > therefore have reached 70 C, and with the drive spinning in that... one > can only guess what temps it reached!
Duncan, I never get those high temperatures here, the highest I've seen at home is ~30 C (86 F), no AC. I don't think the failure is temperature related, I always mount a 12cm fan in front of the the HD enclosure, and the HDs aren't even warm. Previously the same HD was mounted in a different box, still AUSUS mobo but VIA chipset instead of NVidia, and different BIOS. In that box the disk was not automounted from fstab and if not mounted manually it was normally completely cold even without the 12cm fan running, so I suspect it was not even spinning (low power mode from BIOS?). I mounted it only to archive movies after viewing them. In the Nvidia box behavior is different, the disk warms up even if not mounted, but with the 12cm fan always running the temp is low. I have no explanation for this failure. The disk was used really little. After (if) I recover data I'll try to read the HD SMART database, if I remember well there are some useful counters there. The HD is less than 3 years old and should still be under warranty, I'll try to get a replacement from Seagate. But my movies are more important now! I'm sure it's not related, but the irony is that just few hours before the failure I had run an e2fsck on that partition, not an error did it report. raffaele PS Thanks for the hint on block size. -- [EMAIL PROTECTED] mailing list
