I have noticed something twice now: within 24 hours of starting use of the Folding@Home client on my main desktop, files have become corrupt on my SATA hard drive. I therefore consider 3 possible "causes":
1. Folding@Home does something weird.
2. SATA drive/controller does not like heat produced by 100% CPU
The first time, I thought the drive was bad, sent it back to Seagate for RMA, and got a refurb model. It had thrown a lot of DriveReady SeekComplete Error messages in dmesg.
The second time, not so many errors, so I think I stopped it earlier.
Running "badblocks" finds no problems.
I guess I'm trying to figure out what causes this. I've restored all my data from a backup to another partition (on a PATA drive) and taken the SATA sortof "out of rotation".
My SATA Chipset Information: (lspci -vvv)
0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) SATA Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at efe0
Region 1: I/O ports at efac [size=4]
Region 2: I/O ports at efa0 [size=8]
Region 3: I/O ports at efa8 [size=4]
Region 4: I/O ports at ef90 [size=16]
SATA Drive Infromation:
Vendor: ATA Model: ST3120026AS Rev: 3.18
Kernel SATA-Related data: