wine users - Apr 2012 - Very Strange and Probably Obscure Problem

Hi...

I really hope that somebody can help me to brainstorm this problem. Please let
me describe my enviornment.

Environment
---------------
Fedora 16 x86_64(fully up-to-date)
Wine 1.5.1 32bit and noarch binaries only
Nvidia GPU - GTS 450
Nvidia Driver - 295.40 (including 32bit libraries)

I've installed Perfectworld International under wine. Everything was running
fine until the most recent major update called (descent). It took awhile to
figure out the requirments and once done. I made a clean install of the game
including a fresh wine prefix. I configured the registry as required.

Now for the longest time I was unable to run the game at all. When I tried to do
it manually, I constantly got the following error message:

  winehq err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr

I stumbled onto a workaround with an uninstall and reinstall of
xorg-x11-drv-nvidia-libs.i686. The game then works for a while without a
problem. But after awhile the game ceases to work. Until I do reinstall of the
library again.

Two things that are very funny about this. First thing is that recently I placed
the hardware into a computer with much more capable hardware. This problem began
in the older hardware and persisted in the newer hardware.

The second thing that's funny about this is that I can run the game without
a problem on a different machine with the exact same OS and software
configuration (see above).

I really do hope that somebody out there can help me to try to figure out
what's going on. Is it a wine problem, glibc problem, kernel problem,
hardware problem........

Please help.

Thanks

Eli Wapniarski

eliwap wrote:
> 
> Two things that are very funny about this. First thing is that recently I
placed the hardware into a computer with much more capable hardware. This
problem began in the older hardware and persisted in the newer hardware.
> 
Exactly what hardware did you move?  

> The second thing that's funny about this is that I can run the game
without a problem on a different machine with the exact same OS and software
configuration (see above).
And what is the difference in hardware?

This sounds like a hardware problem. Whether it's a particular piece of
hardware that's failing, or a problem with a particular model of something,
I can't tell from what you've posted.

k... Thanks for that... I will do these things over the  next couple of days.

They are indeed a very good place to start.

Eli

k... smartd did indeed report a problem. Drat.

So now currently I am running:

badblocks -v /dev/mapper/vg_computer-lv_root > bad-blocks

I intend to then run:

fsck -l bad-blocks /dev/mapper/vg_computer-lv_root > bad-blocks

If I am making a mistake, or there is a better way to do this, then I would
greatly appreciate any advise.

Thank you.

backups have been done. As a matter of fact the problem is having to backup the
backups lol which have also been done.

Oh.... I was thinking. Could a problem like this arise from a corrupted journal.

Would it be wise to try to disable the journal (assuming that it would be
removed) as per http://fenidik.blogspot.com/2010/03/ext4-disable-journal.html
Then enable the journal (assuming that i would be recreated)?

Is there an intermediary step necessary to delete the journal?

Thanks for any input.

Eli

eliwap wrote:
> Oh.... I was thinking. Could a problem like this arise from a corrupted
journal.
> 
If smartctl says your hard drive is failing, it's failing. Modern hard
drives have a reserved area to remap bad sectors to, and they do it
automatically,  without telling the user. When you reach the point that tools
like smartctl report uncorrectable sectors, that means that the drive has
already used up all the reserved space. You have a lot more bad sectors on that
drive than the two smartctl is reporting.

If I am making a mistake, or there is a better way to do this, then I
would greatly appreciate any advise.

Thanks Martin for all your great advise. I ran smartctl -xall /dev/sdb. It came
back with a whole lot of info that I can't make heads or tails of. It said
that there were some kind of errors.

I was wondering if I can post them here and you could take a look at the output?

Eli

James.... I agree with your assessment. But its also a good opportunity to learn
a little something new :)

Martin... Thanks again for yuour help. The output follows:

smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.3.2-6.fc16.x86_64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ==Model Family:     Western Digital Caviar
Green
Device Model:     WDC WD10EADS-00M2B0
Serial Number:    WD-WCAV54491480
LU WWN Device Id: 5 0014ee 258ffb6bd
Firmware Version: 01.00A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Apr 25 07:22:47 2012 IDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ==SMART overall-health self-assessment test
result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command
from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (20760) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off
support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 239) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3037) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   199   156   051    -    68440
  3 Spin_Up_Time            POS--K   122   112   021    -    6891
  4 Start_Stop_Count        -O--CK   100   100   000    -    118
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   089   089   000    -    8509
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    118
192 Power-Off_Retract_Count -O--CK   200   200   000    -    111
193 Load_Cycle_Count        -O--CK   001   001   000    -    932987
194 Temperature_Celsius     -O---K   111   101   000    -    36
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   200   200   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
SMART Log at address 0x01 has    1 sectors [Summary SMART error log]
SMART Log at address 0x02 has    5 sectors [Comprehensive SMART error log]
GP    Log at address 0x03 has    6 sectors [Ext. Comprehensive SMART error log]
SMART Log at address 0x06 has    1 sectors [SMART self-test log]
GP    Log at address 0x07 has    1 sectors [Extended self-test log]
SMART Log at address 0x09 has    1 sectors [Selective self-test log]
GP    Log at address 0x10 has    1 sectors [NCQ Command Error log]
GP    Log at address 0x11 has    1 sectors [SATA Phy Event Counters]
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0xa0 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa1 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa2 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa3 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa4 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa5 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa6 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa7 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa8 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xa9 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xaa has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xab has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xac has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xad has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xae has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xaf has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb0 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb1 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb2 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb3 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb4 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb5 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb6 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb7 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xc0 has    1 sectors [Device vendor specific log]
GP    Log at address 0xc1 has   24 sectors [Device vendor specific log]
GP/S  Log at address 0xe0 has    1 sectors [SCT Command/Status]
GP/S  Log at address 0xe1 has    1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 3011 (device log contains only the most recent 24 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3011 [2] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:48.924  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     09:49:48.923  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     09:49:48.923  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     09:49:48.922  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     09:49:48.922  SET FEATURES [Set
transfer mode]

Error 3010 [1] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:46.304  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     09:49:46.304  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     09:49:46.304  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     09:49:46.302  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     09:49:46.302  SET FEATURES [Set
transfer mode]

Error 3009 [0] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:43.685  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     09:49:43.685  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     09:49:43.685  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     09:49:43.683  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     09:49:43.683  SET FEATURES [Set
transfer mode]

Error 3008 [23] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:41.066  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     09:49:41.066  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     09:49:41.066  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     09:49:41.063  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     09:49:41.063  SET FEATURES [Set
transfer mode]

Error 3007 [22] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:38.446  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     09:49:38.446  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     09:49:38.446  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     09:49:38.444  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     09:49:38.444  SET FEATURES [Set
transfer mode]

Error 3006 [21] occurred at disk power-on lifetime: 8364 hours (348 days + 12
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     09:49:35.839  READ FPDMA QUEUED
  60 00 08 00 00 00 3d 15 00 b3 7f 40 08     09:49:35.822  READ FPDMA QUEUED
  60 01 00 00 08 00 09 08 00 41 a7 40 08     09:49:35.821  READ FPDMA QUEUED
  60 01 00 00 00 00 09 07 00 41 a7 40 08     09:49:35.819  READ FPDMA QUEUED
  60 01 00 00 08 00 09 06 00 41 a7 40 08     09:49:35.818  READ FPDMA QUEUED

Error 3005 [20] occurred at disk power-on lifetime: 8359 hours (348 days + 7
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 01 00 00 08 00 3d 17 00 b3 8f 40 08     04:31:12.286  READ FPDMA QUEUED
  60 00 08 00 00 00 3d 17 00 b3 17 40 08     04:31:12.286  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     04:31:12.286  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     04:31:12.286  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     04:31:12.283  IDENTIFY DEVICE

Error 3004 [19] occurred at disk power-on lifetime: 8359 hours (348 days + 7
hours)
  When the command that caused the error occurred, the device was active or
idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 3d b3 17 1a 40 00  Error: UNC at LBA = 0x3db3171a =
1035147034

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 08 00 3d 17 00 b3 17 40 08     04:31:09.666  READ FPDMA QUEUED
  60 01 00 00 00 00 3d 17 00 b3 8f 40 08     04:31:09.666  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 08     04:31:09.666  SET FEATURES
[Reserved for Serial ATA]
  27 00 00 00 00 00 00 00 00 00 00 e0 08     04:31:09.666  READ NATIVE MAX
ADDRESS EXT
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     04:31:09.664  IDENTIFY DEVICE

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  2
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        SMART Off-line Data Collection executing in
background (4)
Current Temperature:                    36 Celsius
Power Cycle Min/Max Temperature:     35/38 Celsius
Lifetime    Min/Max Temperature:     35/46 Celsius
Under/Over Temperature Limit Count:   0/0
SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (6)

Index    Estimated Time   Temperature Celsius
   7    2012-04-24 23:25    36  *****************
 ...    ..( 21 skipped).    ..  *****************
  29    2012-04-24 23:47    36  *****************
  30    2012-04-24 23:48    35  ****************
  31    2012-04-24 23:49    36  *****************
 ...    ..( 26 skipped).    ..  *****************
  58    2012-04-25 00:16    36  *****************
  59    2012-04-25 00:17    35  ****************
  60    2012-04-25 00:18    36  *****************
 ...    ..( 51 skipped).    ..  *****************
 112    2012-04-25 01:10    36  *****************
 113    2012-04-25 01:11    37  ******************
 ...    ..(  3 skipped).    ..  ******************
 117    2012-04-25 01:15    37  ******************
 118    2012-04-25 01:16    36  *****************
 119    2012-04-25 01:17    37  ******************
 ...    ..(  8 skipped).    ..  ******************
 128    2012-04-25 01:26    37  ******************
 129    2012-04-25 01:27    36  *****************
 ...    ..( 69 skipped).    ..  *****************
 199    2012-04-25 02:37    36  *****************
 200    2012-04-25 02:38    35  ****************
 201    2012-04-25 02:39    36  *****************
 ...    ..( 14 skipped).    ..  *****************
 216    2012-04-25 02:54    36  *****************
 217    2012-04-25 02:55    35  ****************
 218    2012-04-25 02:56    36  *****************
 ...    ..( 18 skipped).    ..  *****************
 237    2012-04-25 03:15    36  *****************
 238    2012-04-25 03:16    35  ****************
 239    2012-04-25 03:17    36  *****************
 ...    ..( 44 skipped).    ..  *****************
 284    2012-04-25 04:02    36  *****************
 285    2012-04-25 04:03    35  ****************
 286    2012-04-25 04:04    36  *****************
 ...    ..( 25 skipped).    ..  *****************
 312    2012-04-25 04:30    36  *****************
 313    2012-04-25 04:31    35  ****************
 314    2012-04-25 04:32    36  *****************
 ...    ..(141 skipped).    ..  *****************
 456    2012-04-25 06:54    36  *****************
 457    2012-04-25 06:55    35  ****************
 458    2012-04-25 06:56    36  *****************
 ...    ..( 17 skipped).    ..  *****************
 476    2012-04-25 07:14    36  *****************
 477    2012-04-25 07:15    35  ****************
   0    2012-04-25 07:16    36  *****************
 ...    ..(  5 skipped).    ..  *****************
   6    2012-04-25 07:22    36  *****************

Warning: device does not support SCT Error Recovery Control command
SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x000a  2           10  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x8000  4       519997  Vendor specific

Martin and James, thanks to you both for helping me to figure out what the
problem with my system is and the resolution to the problem.

Eli