I realise that this thread has gone stale, but I thought I'd make some observations anyway.
The Load Cycle Count is 11336, but your Start/Stop Count is only 94. The cooked value of the former has already dropped from 100 to 95, after only 356 powered-on hours. At this rate you will hit 0 in about 7000 hours (= 19 x 356).
Attribute 188 is indicating 4 Command Timeouts.
Attributes 240, 241, and 242 appear to be multi-byte values that are probably best observed in hexadecimal.
240 -> 8203387535671 -> 0x077600000137
241 -> 1507067261 -> 0x000059d4057d
242 -> 749646730 -> 0x00002caeb38a
Attribute 240 (Head Flying Hours) appears to consist of two values, 0x0776 and 0x0137 (or 0x00000137).
Now 0x0137 = 311 decimal, and Power_On_Hours = 356. I'm guessing that this means that the heads were over the platters for 311 hours out of the 356 hours that the drive was powered up, and were parked for the remaining 45 hours.
Attribute 190 (Airflow Temperature) seems to be directly related to attribute 194 (Temperature_Celsius):
42 + 58 = 100
44 + 56 = 100
The raw Seek Error Rate figure reflects 0 errors in 9377755 seeks, ie a perfect score.
Here is an example showing 1 error in 4 million seeks:
http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=8732#M8732
The cooked value of Raw_Read_Error_rate is 111 which is also very good. The raw value of 36984705 is not an error rate -- it is a sector count. My understanding is that Seagate computes the error rate by counting the number of read errors in each block of 250 million sectors. The sector count then rolls over to 0 and continues counting up to 250 million. The cooked value is incremented or decremented according to the number of errors detected in each block.
