f



Is my old IBM Deskstar 60GXP 40 GB HDD dying now?

I need some other opinions from you HDD experts since I don't know about HDD issues. I would think it is dying, 
but I can't seem to get the symptoms:

The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA 4in1 drivers) acting funny. I checked the event 
viewer logs and saw:

Event Type:	Warning
Event Source:	Disk
Event Category:	None
Event ID:	51
Date:		5/18/2006
Time:		10:00:04 PM
User:		N/A
Computer:	MyCompy
Description:
An error was detected on device \Device\Harddisk2\D during a paging operation.For more information, see Help and 
Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 b6 00   ..h...?.
0008: 00 00 00 00 33 00 04 80   ....3..?
0010: 2d 01 00 00 00 00 00 00   -.......
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 10 33 06 00 00 00 00 00   .3......
0030: ff ff ff ff 03 00 00 00   ????....
0038: 40 00 00 04 00 00 00 00   @.......
0040: ff 20 0a 12 80 03 20 40   ? ..?. @
0048: 00 00 01 00 0a 00 00 00   ........
0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
0058: 00 00 00 00 d0 99 45 87   ....??E?
0060: 00 00 00 00 6e ff 93 0c   ....n??.
0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
0070: 80 00 00 00 00 00 00 00   ?.......
0078: 00 00 00 00 00 00 00 00   ........
0080: 00 00 00 00 00 00 00 00   ........
0088: 00 00 00 00 00 00 00 00   ........

Event Type:	Error
Event Source:	viamraid
Event Category:	None
Event ID:	9
Date:		5/18/2006
Time:		10:00:04 PM
User:		N/A
Computer:	MyCompy
Description:
The device, \Device\Scsi\viamraid1, did not respond within the timeout period.For more information, see Help and 
Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 6a 00   ......j.
0008: 00 00 00 00 09 00 04 c0   .......?
0010: 00 01 00 00 00 00 00 00   ........
0018: 94 05 00 00 00 00 00 00   ?.......
0020: 00 00 00 00 00 00 00 00   ........
0028: 00 00 00 00 00 00 00 00   ........
0030: 00 00 00 00 07 00 00 00   ........


Event Type:    Warning
Event Source:    Disk
Event Category:    None
Event ID:    51
Date:        5/17/2006
Time:        7:56:48 PM
User:        N/A
Computer:    MyCompy
Description:
An error was detected on device \Device\Harddisk2\D during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 68 00 01 00 b6 00   ..h...?.
0008: 00 00 00 00 33 00 04 80   ....3..?
0010: 2d 01 00 00 00 00 00 00   -.......
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 53 97 54 00 00 00 00 00   S?T.....
0030: ff ff ff ff 03 00 00 00   ????....
0038: 40 00 00 04 00 00 00 00   @.......
0040: ff 20 0a 12 80 03 20 40   ? ..?. @
0048: 00 00 01 00 0a 00 00 00   ........
0050: 00 00 00 00 68 46 55 87   ....hFU?
0058: 00 00 00 00 a0 d2 30 87   .... ?0?
0060: 00 00 00 00 16 55 e2 0a   .....U?.
0068: 2a 00 0a e2 55 16 00 00   *..?U...
0070: 80 00 00 00 00 00 00 00   ?.......
0078: 00 00 00 00 00 00 00 00   ........
0080: 00 00 00 00 00 00 00 00   ........
0088: 00 00 00 00 00 00 00 00   ........

Event Type:    Error
Event Source:    viamraid
Event Category:    None
Event ID:    9
Date:        5/17/2006
Time:        7:56:48 PM
User:        N/A
Computer:    MyCompy
Description:
The device, \Device\Scsi\viamraid1, did not respond within the timeout period.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 6a 00   ......j.
0008: 00 00 00 00 09 00 04 c0   .......?
0010: 00 01 00 00 00 00 00 00   ........
0018: 38 00 00 00 00 00 00 00   8.......
0020: 00 00 00 00 00 00 00 00   ........
0028: 00 00 00 00 00 00 00 00   ........
0030: 00 00 00 00 07 00 00 00   ........

Note: Yes, I have a paging file here.


HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:

HD Tune: IC35L040AVER07-0 Health

ID                              Current  Worst    ThresholdData      Status   
(01) Raw Read Error Rate        100      100      60       65536     Ok       
(02) Throughput Performance     100      100      50       0         Ok       
(03) Spin Up Time               113      113      24       12910783  Ok       
(04) Start/Stop Count           100      100      0        784       Ok       
(05) Reallocated Sector Count   100      100      5        3         Ok       
(07) Seek Error Rate            100      100      67       0         Ok       
(08) Seek Time Performance      100      100      20       0         Ok       
(09) Power On Hours Count       99       99       0        13487     Ok       
(0A) Spin Retry Count           100      100      60       0         Ok       
(0C) Power Cycle Count          100      100      0        740       Ok       
(C0) Power Off Retract Count    100      100      50       784       Ok       
(C1) Load Cycle Count           100      100      50       784       Ok       
(C2) Temperature                98       98       0        1179704   Ok       
(C4) Reallocated Event Count    100      100      0        3         Ok       
(C5) Current Pending Sector     100      100      0        1         Ok       
(C6) Offline Uncorrectable      100      100      0        0         Ok       
(C7) Ultra DMA CRC Error Count  200      200      0        0         Ok       

Power On Time         : 13487
Health Status         : Ok

Note: 05 was highlighted yellow.

--

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>chkdsk d:
The type of the file system is NTFS.
Volume label is AFA64-D.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.

  10490412 KB total disk space.
   5964844 KB in 9376 files.
      3392 KB in 570 indexes.
         0 KB in bad sectors.
     30828 KB in use by the system.
      4096 KB occupied by the log file.
   4491348 KB available on disk.

      4096 bytes in each allocation unit.
   2622603 total allocation units on disk.
   1122837 allocation units available on disk.

C:\>chkdsk g:
The type of the file system is NTFS.
Volume label is AFA64-G.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.

   9229308 KB total disk space.
   2797308 KB in 6018 files.
      2792 KB in 294 indexes.
         4 KB in bad sectors.
     27548 KB in use by the system.
      4096 KB occupied by the log file.
   6401656 KB available on disk.

      4096 bytes in each allocation unit.
   2307327 total allocation units on disk.
   1600414 allocation units available on disk.

Notes: This 4 KB was from last year (don't remember when exactly). D and G: are two partitions on this 
physical HDD.

My computer specifications can be found here: http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary 
one).

I ran chkdsk a few times outside and inside of Windows and ran HD Tune's error scan, but found no new problems. 
Speed looked good too.

Any ideas? Maybe I am not testing enough? Thank you in advance.
-- 
"When many work together for a goal, great things may be accomplished. It is said a lion cub was killed by a single colony of ants." --Saskya Pandita
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/19/2006 10:10:33 AM
comp.sys.mac.hardware.storage 1074 articles. 0 followers. Post Follow

39 Replies
579 Views

Similar Articles

[PageSpeed] 57

Timeout may not necessarily mean the disk itself.
Could be the mobo is the cause, and the disk T/O
is only the symptom.

-- 
 40th Floor - Software  @  http://40th.com/
 iPlay : the ultimate audio player for mobiles
 parametric eq, xfeed, reverb; all on a mobile
0
hel
5/19/2006 2:36:36 PM
<ANTant@zimage.com> wrote:

> Any ideas? Maybe I am not testing enough? 

You need to do a surface scan, not just a file system check; but I
suggest you save some time and just replace the drive. All disks fail
eventually, and you got longer service from your Deskstar 60GXP than
most people did. Show your gratitude by opening up your wallet. (And you
don't need to avoid the "Deskstar" moniker: the current Hitachi drives
are quite good.) 

0
neillmassello
5/19/2006 2:58:20 PM
<ANTant@zimage.com> wrote

> I need some other opinions from you HDD experts since
> I don't know about HDD issues. I would think it is dying,

Yeah, looks like it.

> but I can't seem to get the symptoms:

The problem appears to be the reallocated and pending sectors.

> The last week, I noticed my Windows XP Pro. SP2 (all updates;
> VIA 4in1 drivers) acting funny. I checked the event viewer logs and saw:
>
> Event Type: Warning
> Event Source: Disk
> Event Category: None
> Event ID: 51
> Date: 5/18/2006
> Time: 10:00:04 PM
> User: N/A
> Computer: MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during
> a paging operation. For more information, see Help and
> Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> 0008: 00 00 00 00 33 00 04 80   ....3..?
> 0010: 2d 01 00 00 00 00 00 00   -.......
> 0018: 00 00 00 00 00 00 00 00   ........
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 10 33 06 00 00 00 00 00   .3......
> 0030: ff ff ff ff 03 00 00 00   ????....
> 0038: 40 00 00 04 00 00 00 00   @.......
> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> 0048: 00 00 01 00 0a 00 00 00   ........
> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
> 0058: 00 00 00 00 d0 99 45 87   ....??E?
> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
> 0070: 80 00 00 00 00 00 00 00   ?.......
> 0078: 00 00 00 00 00 00 00 00   ........
> 0080: 00 00 00 00 00 00 00 00   ........
> 0088: 00 00 00 00 00 00 00 00   ........
>
> Event Type: Error
> Event Source: viamraid
> Event Category: None
> Event ID: 9
> Date: 5/18/2006
> Time: 10:00:04 PM
> User: N/A
> Computer: MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within
> the timeout period.For more information, see Help and
> Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> 0008: 00 00 00 00 09 00 04 c0   .......?
> 0010: 00 01 00 00 00 00 00 00   ........
> 0018: 94 05 00 00 00 00 00 00   ?.......
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 00 00 00 00 00 00 00 00   ........
> 0030: 00 00 00 00 07 00 00 00   ........
>
>
> Event Type:    Warning
> Event Source:    Disk
> Event Category:    None
> Event ID:    51
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during a paging operation.
> For more information, see Help and Support Center
> at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> 0008: 00 00 00 00 33 00 04 80   ....3..?
> 0010: 2d 01 00 00 00 00 00 00   -.......
> 0018: 00 00 00 00 00 00 00 00   ........
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 53 97 54 00 00 00 00 00   S?T.....
> 0030: ff ff ff ff 03 00 00 00   ????....
> 0038: 40 00 00 04 00 00 00 00   @.......
> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> 0048: 00 00 01 00 0a 00 00 00   ........
> 0050: 00 00 00 00 68 46 55 87   ....hFU?
> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
> 0070: 80 00 00 00 00 00 00 00   ?.......
> 0078: 00 00 00 00 00 00 00 00   ........
> 0080: 00 00 00 00 00 00 00 00   ........
> 0088: 00 00 00 00 00 00 00 00   ........
>
> Event Type:    Error
> Event Source:    viamraid
> Event Category:    None
> Event ID:    9
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
> For more information, see Help and Support Center
> at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> 0008: 00 00 00 00 09 00 04 c0   .......?
> 0010: 00 01 00 00 00 00 00 00   ........
> 0018: 38 00 00 00 00 00 00 00   8.......
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 00 00 00 00 00 00 00 00   ........
> 0030: 00 00 00 00 07 00 00 00   ........

> Note: Yes, I have a paging file here.

> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:

> HD Tune: IC35L040AVER07-0 Health

> ID                              Current  Worst    ThresholdData      Status
> (01) Raw Read Error Rate        100      100      60       65536     Ok
> (02) Throughput Performance     100      100      50       0         Ok
> (03) Spin Up Time               113      113      24       12910783  Ok
> (04) Start/Stop Count           100      100      0        784       Ok
> (05) Reallocated Sector Count   100      100      5        3         Ok

Thats not good.

> (07) Seek Error Rate            100      100      67       0         Ok
> (08) Seek Time Performance      100      100      20       0         Ok
> (09) Power On Hours Count       99       99       0        13487     Ok
> (0A) Spin Retry Count           100      100      60       0         Ok
> (0C) Power Cycle Count          100      100      0        740       Ok
> (C0) Power Off Retract Count    100      100      50       784       Ok
> (C1) Load Cycle Count           100      100      50       784       Ok
> (C2) Temperature                98       98       0        1179704   Ok
> (C4) Reallocated Event Count    100      100      0        3         Ok
> (C5) Current Pending Sector     100      100      0        1         Ok

And neither are those two.

> (C6) Offline Uncorrectable      100      100      0        0         Ok
> (C7) Ultra DMA CRC Error Count  200      200      0        0         Ok

> Power On Time         : 13487
> Health Status         : Ok

> Note: 05 was highlighted yellow.

And so it should, it indicates that the drive has a problem.

> --
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\>chkdsk d:
> The type of the file system is NTFS.
> Volume label is AFA64-D.
>
> WARNING!  F parameter not specified.
> Running CHKDSK in read-only mode.
>
> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3 of 3)...
> Security descriptor verification completed.
>
>  10490412 KB total disk space.
>   5964844 KB in 9376 files.
>      3392 KB in 570 indexes.
>         0 KB in bad sectors.
>     30828 KB in use by the system.
>      4096 KB occupied by the log file.
>   4491348 KB available on disk.
>
>      4096 bytes in each allocation unit.
>   2622603 total allocation units on disk.
>   1122837 allocation units available on disk.
>
> C:\>chkdsk g:
> The type of the file system is NTFS.
> Volume label is AFA64-G.
>
> WARNING!  F parameter not specified.
> Running CHKDSK in read-only mode.
>
> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3 of 3)...
> Security descriptor verification completed.
>
>   9229308 KB total disk space.
>   2797308 KB in 6018 files.
>      2792 KB in 294 indexes.
>         4 KB in bad sectors.
>     27548 KB in use by the system.
>      4096 KB occupied by the log file.
>   6401656 KB available on disk.
>
>      4096 bytes in each allocation unit.
>   2307327 total allocation units on disk.
>   1600414 allocation units available on disk.

> Notes: This 4 KB was from last year (don't remember when
> exactly). D and G: are two partitions on this physical HDD.

> My computer specifications can be found here:
> http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> (primary one).

> I ran chkdsk a few times outside and inside of Windows and ran HD
> Tune's error scan, but found no new problems. Speed looked good too.

> Any ideas? Maybe I am not testing enough? Thank you in advance.

Try Hitachi's DFT, they bought IBM's hard drive operation.
http://www.hitachigst.com/hdd/support/download.htm#DFT

Thats one of the infamous Deathstars, likely its dying. 


0
Rod
5/19/2006 7:01:39 PM
This is a multi-part message in MIME format.

------=_NextPart_000_007D_01C67B95.4B6B3AE0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

<ANTant@zimage.com> wrote in message news:icydnRqG7dYEBPDZRVn-qw@mminternet.net
> I need some other opinions from you HDD experts since I don't know about HDD issues. I would think it is dying,
> but I can't seem to get the symptoms:
> 
> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA 4in1 drivers) acting funny. I checked the event
> viewer logs and saw:
> 
> Event Type: Warning
> Event Source: Disk
> Event Category: None
> Event ID: 51
> Date: 5/18/2006
> Time: 10:00:04 PM
> User: N/A
> Computer: MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during a paging operation.
>
[snip]
>
> Event Type: Error
> Event Source: viamraid
> Event Category: None
> Event ID: 9
> Date: 5/18/2006
> Time: 10:00:04 PM
> User: N/A
> Computer: MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
>
[snip]
> 
> Event Type:    Warning
> Event Source:    Disk
> Event Category:    None
> Event ID:    51
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during a paging operation.
> 
[snip]
> 
> Event Type:    Error
> Event Source:    viamraid
> Event Category:    None
> Event ID:    9
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
> 
[snip]
> 
> Note: Yes, I have a paging file here.
> 
> 
> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
> 
> HD Tune: IC35L040AVER07-0 Health
> 
> ID                              Current  Worst    ThresholdData      Status
> (01) Raw Read Error Rate        100      100      60       65536     Ok
> (02) Throughput Performance     100      100      50       0         Ok
> (03) Spin Up Time               113      113      24       12910783  Ok
> (04) Start/Stop Count           100      100      0        784       Ok
> (05) Reallocated Sector Count   100      100      5        3         Ok
> (07) Seek Error Rate            100      100      67       0         Ok
> (08) Seek Time Performance      100      100      20       0         Ok
> (09) Power On Hours Count       99       99       0        13487     Ok
> (0A) Spin Retry Count           100      100      60       0         Ok
> (0C) Power Cycle Count          100      100      0        740       Ok
> (C0) Power Off Retract Count    100      100      50       784       Ok
> (C1) Load Cycle Count           100      100      50       784       Ok
> (C2) Temperature                98       98       0        1179704   Ok
> (C4) Reallocated Event Count    100      100      0        3         Ok
> (C5) Current Pending Sector     100      100      0        1         Ok
> (C6) Offline Uncorrectable      100      100      0        0         Ok
> (C7) Ultra DMA CRC Error Count  200      200      0        0         Ok

Looks fine to me.
You may have (or have had) a problem (with) powersupply or an overheating problem.

> 
> Power On Time         : 13487
> Health Status         : Ok
> 
> Note: 05 was highlighted yellow.
> 
> --
> 
[snip]
> 
> C:\>chkdsk g:
> The type of the file system is NTFS.
> Volume label is AFA64-G.
> 
> WARNING!  F parameter not specified.
> Running CHKDSK in read-only mode.
> 
> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3 of 3)...
> Security descriptor verification completed.
> 
>    9229308 KB total disk space.
>    2797308 KB in 6018 files.
>       2792 KB in 294 indexes.
>          4 KB in bad sectors.
>      27548 KB in use by the system.
>       4096 KB occupied by the log file.
>    6401656 KB available on disk.
> 
>       4096 bytes in each allocation unit.
>    2307327 total allocation units on disk.
>    1600414 allocation units available on disk.

> Notes: This 4 KB was from last year (don't remember when exactly). D and G: are two partitions on this
> physical HDD.

That may be the pending bad sector in that cluster. 
It stays pending because it is not read nor written to anymore.

> 
> My computer specifications can be found here: http://alpha.zimage.com/~ant/antfarm/about/computers.txt 
> (primary one).
> 
> I ran chkdsk a few times outside and inside of Windows and ran HD Tune's error scan, but found no new problems.
> Speed looked good too.
> 
> Any ideas? Maybe I am not testing enough? Thank you in advance.
> > > o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
>    \ _ /                        Please remove ANT if replying by e-mail.
>     ( )
------=_NextPart_000_007D_01C67B95.4B6B3AE0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><LINK href=3D"D:\Program Files\OE-QuoteFix\styles.css" =
rel=3Dstylesheet>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1543" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3Dq0>&lt;<A class=3D0=20
href=3D"mailto:ANTant@zimage.com">ANTant@zimage.com</A>&gt; wrote in =
message <A=20
class=3D0=20
href=3D"news:icydnRqG7dYEBPDZRVn-qw@mminternet.net">news:icydnRqG7dYEBPDZ=
RVn-qw@mminternet.net</A><BR></SPAN><SPAN=20
class=3Dq1><FONT face=3D"Courier New"><FONT face=3D"Comic Sans MS">&gt; =
I need some=20
other opinions from you HDD experts since I don't know about HDD issues. =
I would=20
think it is dying,<BR>&gt; but I can't seem to get the symptoms:<BR>&gt; =

<BR>&gt; The last week, I noticed my Windows XP Pro. SP2 (all updates; =
VIA 4in1=20
drivers) acting funny. I checked the event<BR>&gt; viewer logs and=20
saw:<BR></FONT><FONT size=3D2>&gt; <BR>&gt; Event Type: Warning<BR>&gt; =
Event=20
Source: Disk<BR>&gt; Event Category: None<BR>&gt; Event ID: 51<BR>&gt; =
Date:=20
5/18/2006<BR>&gt; Time: 10:00:04 PM<BR>&gt; User: N/A<BR>&gt; Computer:=20
MyCompy<BR>&gt; Description:<BR>&gt; An error was detected on device=20
\Device\Harddisk2\D during a paging =
operation.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New" =
size=3D2>&gt;</FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1>[snip]</SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New" =
size=3D2>&gt;</FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New" size=3D2>&gt; Event =
Type:=20
Error<BR>&gt; Event Source: viamraid<BR>&gt; Event Category: =
None<BR>&gt; Event=20
ID: 9<BR>&gt; Date: 5/18/2006<BR>&gt; Time: 10:00:04 PM<BR>&gt; User:=20
N/A<BR>&gt; Computer: MyCompy<BR>&gt; Description:<BR>&gt; The device,=20
\Device\Scsi\viamraid1, did not respond within the timeout=20
period.</FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New" =
size=3D2>&gt;</FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1>[snip]</SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New"><FONT size=3D2>&gt; =
<BR>&gt; Event=20
Type:&nbsp;&nbsp;&nbsp; Warning<BR>&gt; Event Source:&nbsp;&nbsp;&nbsp;=20
Disk<BR>&gt; Event Category:&nbsp;&nbsp;&nbsp; None<BR>&gt; Event=20
ID:&nbsp;&nbsp;&nbsp; 51<BR>&gt; =
Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5/17/2006<BR>&gt; Time:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7:56:48=20
PM<BR>&gt; User:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A<BR>&gt;=20
Computer:&nbsp;&nbsp;&nbsp; MyCompy<BR>&gt; Description:<BR>&gt; An =
error was=20
detected on device \Device\Harddisk2\D during a paging =
operation.<BR>&gt;=20
<BR></FONT></FONT><FONT face=3D"Comic Sans =
MS">[snip]</FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New" size=3D2>&gt; <BR>&gt; =
Event=20
Type:&nbsp;&nbsp;&nbsp; Error<BR>&gt; Event Source:&nbsp;&nbsp;&nbsp;=20
viamraid<BR>&gt; Event Category:&nbsp;&nbsp;&nbsp; None<BR>&gt; Event=20
ID:&nbsp;&nbsp;&nbsp; 9<BR>&gt; =
Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5/17/2006<BR>&gt; Time:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7:56:48=20
PM<BR>&gt; User:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A<BR>&gt;=20
Computer:&nbsp;&nbsp;&nbsp; MyCompy<BR>&gt; Description:<BR>&gt; The =
device,=20
\Device\Scsi\viamraid1, did not respond within the timeout =
period.<BR>&gt;=20
<BR></FONT>[snip]</SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New"><FONT face=3D"Comic =
Sans MS">&gt;=20
<BR>&gt; Note: Yes, I have a paging file here.<BR>&gt; <BR></FONT><FONT=20
size=3D2>&gt; <BR>&gt; HDD Tune v2.51 said on 5/18/2006 10:45 PM =
PDT:<BR>&gt;=20
<BR>&gt; HD Tune: IC35L040AVER07-0 Health<BR>&gt; <BR>&gt;=20
ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Current&nbsp; Worst&nbsp;&nbsp;&nbsp;=20
ThresholdData&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status<BR>&gt; (01) Raw Read =
Error=20
Rate&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

65536&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (02) Throughput=20
Performance&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (03) Spin =
Up=20
Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
113&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 113&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
24&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 12910783&nbsp; Ok<BR>&gt; (04) =
Start/Stop=20
Count&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
784&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (05) Reallocated =
Sector=20
Count&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (07) Seek =
Error=20
Rate&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
67&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (08) Seek =
Time=20
Performance&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 20&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (09) Power =
On Hours=20
Count&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
99&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
99&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13487&nbsp;&nbsp;&nbsp;&nbsp;=20
Ok<BR>&gt; (0A) Spin Retry=20
Count&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
60&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (0C) Power =
Cycle=20
Count&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
740&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (C0) Power Off =
Retract=20
Count&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

784&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (C1) Load Cycle=20
Count&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
784&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Ok<BR>&gt; (C2)=20
Temperature&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
98&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
98&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1179704&nbsp;&nbsp; =
Ok<BR>&gt; (C4)=20
Reallocated Event Count&nbsp;&nbsp;&nbsp; =
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (C5) =
Current=20
Pending Sector&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (C6) =
Offline=20
Uncorrectable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ok<BR>&gt; (C7) Ultra =
DMA CRC=20
Error Count&nbsp; 200&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
200&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Ok</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier =
New"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3Dq1>Looks fine to me.</SPAN></DIV>
<DIV><SPAN class=3Dq1><FONT face=3D"Courier New"><FONT face=3D"Comic =
Sans MS">You may=20
have (or have had)&nbsp;a problem (with) powersupply or an overheating=20
problem.</FONT></DIV>
<DIV><BR><FONT size=3D2>&gt; <BR>&gt; Power On=20
Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 13487<BR>&gt; =
Health=20
Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Ok<BR>&gt;=20
<BR></FONT></FONT><FONT face=3D"Comic Sans MS">&gt; Note: 05 was =
highlighted=20
yellow.<BR>&gt; <BR>&gt; --<BR>&gt; <BR>[snip]</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS">&gt; <BR>&gt; C:\&gt;chkdsk g:<BR>&gt; =
The type=20
of the file system is NTFS.<BR>&gt; Volume label is AFA64-G.<BR>&gt; =
<BR>&gt;=20
WARNING!&nbsp; F parameter not specified.<BR>&gt; Running CHKDSK in =
read-only=20
mode.<BR>&gt; <BR>&gt; CHKDSK is verifying files (stage 1 of =
3)...<BR>&gt; File=20
verification completed.<BR>&gt; CHKDSK is verifying indexes (stage 2 of=20
3)...<BR>&gt; Index verification completed.<BR>&gt; CHKDSK is verifying =
security=20
descriptors (stage 3 of 3)...<BR>&gt; Security descriptor verification=20
completed.<BR>&gt; <BR>&gt;&nbsp;&nbsp;&nbsp; 9229308 KB total disk=20
space.<BR>&gt;&nbsp;&nbsp;&nbsp; 2797308 KB in 6018=20
files.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2792 KB in 294=20
indexes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4 =
KB in=20
bad sectors.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 27548 KB in use by =
the=20
system.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096 KB occupied by =
the log=20
file.<BR>&gt;&nbsp;&nbsp;&nbsp; 6401656 KB available on disk.<BR>&gt;=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4096 bytes in each =
allocation=20
unit.<BR>&gt;&nbsp;&nbsp;&nbsp; 2307327 total allocation units on=20
disk.<BR>&gt;&nbsp;&nbsp;&nbsp; 1600414 allocation units available on=20
disk.<BR></FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS">&gt; Notes: This 4 KB was from last =
year (don't=20
remember when exactly). D and G: are two partitions on this<BR>&gt; =
physical=20
HDD.</FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS"></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Comic Sans MS">That may be the pending bad sector in =
that=20
cluster. </FONT></DIV>
<DIV><FONT face=3D"Comic Sans MS">It stays pending because it is not =
read</FONT>=20
nor<FONT face=3D"Comic Sans MS"> written to anymore.</DIV>
<DIV><BR>&gt; <BR>&gt; My computer specifications can be found here: =
</FONT><A=20
class=3D1=20
href=3D"http://alpha.zimage.com/~ant/antfarm/about/computers.txt">http://=
alpha.zimage.com/~ant/antfarm/about/computers.txt</A>=20
</DIV>
<DIV>&gt; (primary one).<BR>&gt; <BR>&gt; I ran chkdsk a few times =
outside and=20
inside of Windows and ran HD Tune's error scan, but found no new=20
problems.<BR>&gt; Speed looked good too.<BR>&gt; <BR>&gt; Any ideas? =
Maybe I am=20
not testing enough? Thank you in advance.<BR></SPAN><SPAN =
class=3Dq3><FONT=20
face=3D"Courier New" size=3D2>&gt; &gt; &gt; o&nbsp;&nbsp; o|=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ant's Quality =
Foraged=20
Links (AQFL): </FONT><A class=3D3 href=3D"http://aqfl.net"><FONT =
face=3D"Courier New"=20
size=3D2>http://aqfl.net</FONT></A><BR></SPAN><SPAN class=3Dq1><FONT=20
face=3D"Courier New" size=3D2>&gt;&nbsp;&nbsp;&nbsp; \ _=20
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Please remove ANT if replying by e-mail.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
(=20
)</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_007D_01C67B95.4B6B3AE0--

0
Folkert
5/19/2006 8:40:57 PM
OK, I did more digging. I moved my page swap off the G: drive to E drive, but still had 
problems. For the heck of it, I tried defragging on my I: drive and man I got lots of disk 
errors (timeouts, disconnected, freezes/pauses). I know it was a bad idea, but then it is my 
video HDD (already saw my TV shows).

I think I am going to have to do disk test on this Seagate drive first outside of Windows.


In alt.comp.periphs.hdd ANTant@zimage.com wrote:
> I need some other opinions from you HDD experts since I don't know about HDD issues. I would think it is dying, 
> but I can't seem to get the symptoms:

> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA 4in1 drivers) acting funny. I checked the event 
> viewer logs and saw:

> Event Type:     Warning
> Event Source:   Disk
> Event Category: None
> Event ID:       51
> Date:           5/18/2006
> Time:           10:00:04 PM
> User:           N/A
> Computer:       MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during a paging operation.For more information, see Help and 
> Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> 0008: 00 00 00 00 33 00 04 80   ....3..?
> 0010: 2d 01 00 00 00 00 00 00   -.......
> 0018: 00 00 00 00 00 00 00 00   ........
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 10 33 06 00 00 00 00 00   .3......
> 0030: ff ff ff ff 03 00 00 00   ????....
> 0038: 40 00 00 04 00 00 00 00   @.......
> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> 0048: 00 00 01 00 0a 00 00 00   ........
> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
> 0058: 00 00 00 00 d0 99 45 87   ....??E?
> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
> 0070: 80 00 00 00 00 00 00 00   ?.......
> 0078: 00 00 00 00 00 00 00 00   ........
> 0080: 00 00 00 00 00 00 00 00   ........
> 0088: 00 00 00 00 00 00 00 00   ........

> Event Type:     Error
> Event Source:   viamraid
> Event Category: None
> Event ID:       9
> Date:           5/18/2006
> Time:           10:00:04 PM
> User:           N/A
> Computer:       MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within the timeout period.For more information, see Help and 
> Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> 0008: 00 00 00 00 09 00 04 c0   .......?
> 0010: 00 01 00 00 00 00 00 00   ........
> 0018: 94 05 00 00 00 00 00 00   ?.......
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 00 00 00 00 00 00 00 00   ........
> 0030: 00 00 00 00 07 00 00 00   ........


> Event Type:    Warning
> Event Source:    Disk
> Event Category:    None
> Event ID:    51
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> An error was detected on device \Device\Harddisk2\D during a paging operation.

> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> 0008: 00 00 00 00 33 00 04 80   ....3..?
> 0010: 2d 01 00 00 00 00 00 00   -.......
> 0018: 00 00 00 00 00 00 00 00   ........
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 53 97 54 00 00 00 00 00   S?T.....
> 0030: ff ff ff ff 03 00 00 00   ????....
> 0038: 40 00 00 04 00 00 00 00   @.......
> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> 0048: 00 00 01 00 0a 00 00 00   ........
> 0050: 00 00 00 00 68 46 55 87   ....hFU?
> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
> 0070: 80 00 00 00 00 00 00 00   ?.......
> 0078: 00 00 00 00 00 00 00 00   ........
> 0080: 00 00 00 00 00 00 00 00   ........
> 0088: 00 00 00 00 00 00 00 00   ........

> Event Type:    Error
> Event Source:    viamraid
> Event Category:    None
> Event ID:    9
> Date:        5/17/2006
> Time:        7:56:48 PM
> User:        N/A
> Computer:    MyCompy
> Description:
> The device, \Device\Scsi\viamraid1, did not respond within the timeout period.

> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> 0008: 00 00 00 00 09 00 04 c0   .......?
> 0010: 00 01 00 00 00 00 00 00   ........
> 0018: 38 00 00 00 00 00 00 00   8.......
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 00 00 00 00 00 00 00 00   ........
> 0030: 00 00 00 00 07 00 00 00   ........

> Note: Yes, I have a paging file here.


> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:

> HD Tune: IC35L040AVER07-0 Health

> ID                              Current  Worst    ThresholdData      Status   
> (01) Raw Read Error Rate        100      100      60       65536     Ok       
> (02) Throughput Performance     100      100      50       0         Ok       
> (03) Spin Up Time               113      113      24       12910783  Ok       
> (04) Start/Stop Count           100      100      0        784       Ok       
> (05) Reallocated Sector Count   100      100      5        3         Ok       
> (07) Seek Error Rate            100      100      67       0         Ok       
> (08) Seek Time Performance      100      100      20       0         Ok       
> (09) Power On Hours Count       99       99       0        13487     Ok       
> (0A) Spin Retry Count           100      100      60       0         Ok       
> (0C) Power Cycle Count          100      100      0        740       Ok       
> (C0) Power Off Retract Count    100      100      50       784       Ok       
> (C1) Load Cycle Count           100      100      50       784       Ok       
> (C2) Temperature                98       98       0        1179704   Ok       
> (C4) Reallocated Event Count    100      100      0        3         Ok       
> (C5) Current Pending Sector     100      100      0        1         Ok       
> (C6) Offline Uncorrectable      100      100      0        0         Ok       
> (C7) Ultra DMA CRC Error Count  200      200      0        0         Ok       

> Power On Time         : 13487
> Health Status         : Ok

> Note: 05 was highlighted yellow.

> --

> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.

> C:\>chkdsk d:
> The type of the file system is NTFS.
> Volume label is AFA64-D.

> WARNING!  F parameter not specified.
> Running CHKDSK in read-only mode.

> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3 of 3)...
> Security descriptor verification completed.

>   10490412 KB total disk space.
>    5964844 KB in 9376 files.
>       3392 KB in 570 indexes.
>          0 KB in bad sectors.
>      30828 KB in use by the system.
>       4096 KB occupied by the log file.
>    4491348 KB available on disk.

>       4096 bytes in each allocation unit.
>    2622603 total allocation units on disk.
>    1122837 allocation units available on disk.

> C:\>chkdsk g:
> The type of the file system is NTFS.
> Volume label is AFA64-G.

> WARNING!  F parameter not specified.
> Running CHKDSK in read-only mode.

> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Index verification completed.
> CHKDSK is verifying security descriptors (stage 3 of 3)...
> Security descriptor verification completed.

>    9229308 KB total disk space.
>    2797308 KB in 6018 files.
>       2792 KB in 294 indexes.
>          4 KB in bad sectors.
>      27548 KB in use by the system.
>       4096 KB occupied by the log file.
>    6401656 KB available on disk.

>       4096 bytes in each allocation unit.
>    2307327 total allocation units on disk.
>    1600414 allocation units available on disk.

> Notes: This 4 KB was from last year (don't remember when exactly). D and G: are two partitions on this 
> physical HDD.

> My computer specifications can be found here: http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary 
> one).

> I ran chkdsk a few times outside and inside of Windows and ran HD Tune's error scan, but found no new problems. 
> Speed looked good too.

> Any ideas? Maybe I am not testing enough? Thank you in advance.
-- 
"When many work together for a goal, great things may be accomplished. It is said a lion cub was killed by a single colony of ants." --Saskya Pandita
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/19/2006 8:57:57 PM
In alt.comp.periphs.hdd hel@40th.com wrote:
> Timeout may not necessarily mean the disk itself.
> Could be the mobo is the cause, and the disk T/O
> is only the symptom.

Like what? Old age? I haven't changed anytrhing for months in my computer (hardware).
-- 
"When many work together for a goal, great things may be accomplished. It is said a lion cub was killed by a single colony of ants." --Saskya Pandita
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/19/2006 8:58:38 PM
In alt.comp.periphs.hdd Neill Massello <neillmassello@earthlink.net> wrote:
> <ANTant@zimage.com> wrote:

> > Any ideas? Maybe I am not testing enough? 

> You need to do a surface scan, not just a file system check; but I
> suggest you save some time and just replace the drive. All disks fail
> eventually, and you got longer service from your Deskstar 60GXP than
> most people did. Show your gratitude by opening up your wallet. (And you
> don't need to avoid the "Deskstar" moniker: the current Hitachi drives
> are quite good.) 

Doesn't chkdsk /r /f do surface scan? If not, then what do you suggest I use? The disk 
utilities from manufactures?
-- 
"When many work together for a goal, great things may be accomplished. It is said a lion cub was killed by a single colony of ants." --Saskya Pandita
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/19/2006 8:59:52 PM
> <ANTant@zimage.com> wrote in message news:icydnRqG7dYEBPDZRVn-qw@mminternet.net
> > I need some other opinions from you HDD experts since I don't know about HDD issues. I would think it is dying,
> > but I can't seem to get the symptoms:
> > 
> > The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA 4in1 drivers) acting funny. I checked the event
> > viewer logs and saw:
> > 
> > Event Type: Warning
> > Event Source: Disk
> > Event Category: None
> > Event ID: 51
> > Date: 5/18/2006
> > Time: 10:00:04 PM
> > User: N/A
> > Computer: MyCompy
> > Description:
> > An error was detected on device \Device\Harddisk2\D during a paging operation.
> >
> [snip]
> >
> > Event Type: Error
> > Event Source: viamraid
> > Event Category: None
> > Event ID: 9
> > Date: 5/18/2006
> > Time: 10:00:04 PM
> > User: N/A
> > Computer: MyCompy
> > Description:
> > The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
> >
> [snip]
> > 
> > Event Type:    Warning
> > Event Source:    Disk
> > Event Category:    None
> > Event ID:    51
> > Date:        5/17/2006
> > Time:        7:56:48 PM
> > User:        N/A
> > Computer:    MyCompy
> > Description:
> > An error was detected on device \Device\Harddisk2\D during a paging operation.
> > 
> [snip]
> > 
> > Event Type:    Error
> > Event Source:    viamraid
> > Event Category:    None
> > Event ID:    9
> > Date:        5/17/2006
> > Time:        7:56:48 PM
> > User:        N/A
> > Computer:    MyCompy
> > Description:
> > The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
> > 
> [snip]
> > 
> > Note: Yes, I have a paging file here.
> > 
> > 
> > HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
> > 
> > HD Tune: IC35L040AVER07-0 Health
> > 
> > ID                              Current  Worst    ThresholdData      Status
> > (01) Raw Read Error Rate        100      100      60       65536     Ok
> > (02) Throughput Performance     100      100      50       0         Ok
> > (03) Spin Up Time               113      113      24       12910783  Ok
> > (04) Start/Stop Count           100      100      0        784       Ok
> > (05) Reallocated Sector Count   100      100      5        3         Ok
> > (07) Seek Error Rate            100      100      67       0         Ok
> > (08) Seek Time Performance      100      100      20       0         Ok
> > (09) Power On Hours Count       99       99       0        13487     Ok
> > (0A) Spin Retry Count           100      100      60       0         Ok
> > (0C) Power Cycle Count          100      100      0        740       Ok
> > (C0) Power Off Retract Count    100      100      50       784       Ok
> > (C1) Load Cycle Count           100      100      50       784       Ok
> > (C2) Temperature                98       98       0        1179704   Ok
> > (C4) Reallocated Event Count    100      100      0        3         Ok
> > (C5) Current Pending Sector     100      100      0        1         Ok
> > (C6) Offline Uncorrectable      100      100      0        0         Ok
> > (C7) Ultra DMA CRC Error Count  200      200      0        0         Ok

> Looks fine to me.
> You may have (or have had) a problem (with) powersupply or an overheating problem.

It did get really warm a few days ago, but the recent symptoms wasn't that warm.
-- 
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )

0
ANTant
5/19/2006 9:03:02 PM
Aa [Fri, 19 May 2006 15:58:38 -0500]:
 >Like what? Old age? I haven't changed anytrhing for months in my computer (ha

Like what?  Are you looking for alternatives,
or do you already know it's the disk?  If the
disk is bad, replace it.  It'll be the easiest
thing to do.
-- 
 40th Floor - Software  @  http://40th.com/
 iPlay : the ultimate audio player for mobiles
 parametric eq, xfeed, reverb; all on a mobile
0
hel
5/19/2006 9:13:33 PM
ANTant@zimage.com wrote
> hel@40th.com wrote

>> Timeout may not necessarily mean the disk itself.

Correct. But he does have reallocated sectors in the SMART report.

>> Could be the mobo is the cause,
>> and the disk T/O is only the symptom.

> Like what? Old age?

Yes, you can get bad caps on the motherboard. Those
are the usually blue or black plastic covered post like
things sticking up from the motherboard. The tops should
be flat and any that have bulged or leaked have failed.

> I haven't changed anytrhing for months in my computer (hardware).

You dont need to have done with a cap failure or the
failure that those 60gxp drives are notorious for.

They are called deathstars for a reason.
That produced a full class action suit.


0
Rod
5/19/2006 9:17:42 PM
ANTant@zimage.com wrote:

> OK, I did more digging. I moved my page swap
> off the G: drive to E drive, but still had problems.

Fine.

> For the heck of it, I tried defragging on my I: drive and
> man I got lots of disk errors (timeouts, disconnected,
> freezes/pauses). I know it was a bad idea, but then it
> is my video HDD (already saw my TV shows).

That does suggest that it might be a problem outside the
drive, like motherboard/power supply/overheating etc.

In fact on a closer look, the drive temperature would be
worth checking with Everest, HDTune doesnt appear to
be showing it properly. Show the Seagate SMART data too.

> I think I am going to have to do disk test on
> this Seagate drive first outside of Windows.

And check the SMART data for that drive too.


> In alt.comp.periphs.hdd ANTant@zimage.com wrote:
>> I need some other opinions from you HDD experts since I don't know
>> about HDD issues. I would think it is dying, but I can't seem to get
>> the symptoms:
>
>> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA
>> 4in1 drivers) acting funny. I checked the event viewer logs and saw:
>
>> Event Type:     Warning
>> Event Source:   Disk
>> Event Category: None
>> Event ID:       51
>> Date:           5/18/2006
>> Time:           10:00:04 PM
>> User:           N/A
>> Computer:       MyCompy
>> Description:
>> An error was detected on device \Device\Harddisk2\D during a paging
>> operation.For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>> 0010: 2d 01 00 00 00 00 00 00   -.......
>> 0018: 00 00 00 00 00 00 00 00   ........
>> 0020: 00 00 00 00 00 00 00 00   ........
>> 0028: 10 33 06 00 00 00 00 00   .3......
>> 0030: ff ff ff ff 03 00 00 00   ????....
>> 0038: 40 00 00 04 00 00 00 00   @.......
>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>> 0048: 00 00 01 00 0a 00 00 00   ........
>> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
>> 0058: 00 00 00 00 d0 99 45 87   ....??E?
>> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
>> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
>> 0070: 80 00 00 00 00 00 00 00   ?.......
>> 0078: 00 00 00 00 00 00 00 00   ........
>> 0080: 00 00 00 00 00 00 00 00   ........
>> 0088: 00 00 00 00 00 00 00 00   ........
>
>> Event Type:     Error
>> Event Source:   viamraid
>> Event Category: None
>> Event ID:       9
>> Date:           5/18/2006
>> Time:           10:00:04 PM
>> User:           N/A
>> Computer:       MyCompy
>> Description:
>> The device, \Device\Scsi\viamraid1, did not respond within the
>> timeout period.For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>> 0008: 00 00 00 00 09 00 04 c0   .......?
>> 0010: 00 01 00 00 00 00 00 00   ........
>> 0018: 94 05 00 00 00 00 00 00   ?.......
>> 0020: 00 00 00 00 00 00 00 00   ........
>> 0028: 00 00 00 00 00 00 00 00   ........
>> 0030: 00 00 00 00 07 00 00 00   ........
>
>
>> Event Type:    Warning
>> Event Source:    Disk
>> Event Category:    None
>> Event ID:    51
>> Date:        5/17/2006
>> Time:        7:56:48 PM
>> User:        N/A
>> Computer:    MyCompy
>> Description:
>> An error was detected on device \Device\Harddisk2\D during a paging
>> operation.
>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>> 0010: 2d 01 00 00 00 00 00 00   -.......
>> 0018: 00 00 00 00 00 00 00 00   ........
>> 0020: 00 00 00 00 00 00 00 00   ........
>> 0028: 53 97 54 00 00 00 00 00   S?T.....
>> 0030: ff ff ff ff 03 00 00 00   ????....
>> 0038: 40 00 00 04 00 00 00 00   @.......
>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>> 0048: 00 00 01 00 0a 00 00 00   ........
>> 0050: 00 00 00 00 68 46 55 87   ....hFU?
>> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
>> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
>> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
>> 0070: 80 00 00 00 00 00 00 00   ?.......
>> 0078: 00 00 00 00 00 00 00 00   ........
>> 0080: 00 00 00 00 00 00 00 00   ........
>> 0088: 00 00 00 00 00 00 00 00   ........
>
>> Event Type:    Error
>> Event Source:    viamraid
>> Event Category:    None
>> Event ID:    9
>> Date:        5/17/2006
>> Time:        7:56:48 PM
>> User:        N/A
>> Computer:    MyCompy
>> Description:
>> The device, \Device\Scsi\viamraid1, did not respond within the
>> timeout period.
>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>> 0008: 00 00 00 00 09 00 04 c0   .......?
>> 0010: 00 01 00 00 00 00 00 00   ........
>> 0018: 38 00 00 00 00 00 00 00   8.......
>> 0020: 00 00 00 00 00 00 00 00   ........
>> 0028: 00 00 00 00 00 00 00 00   ........
>> 0030: 00 00 00 00 07 00 00 00   ........
>
>> Note: Yes, I have a paging file here.
>
>
>> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
>
>> HD Tune: IC35L040AVER07-0 Health
>
>> ID                              Current  Worst    ThresholdData
>> Status (01) Raw Read Error Rate        100      100      60
>> 65536     Ok (02) Throughput Performance     100      100      50
>> 0         Ok (03) Spin Up Time               113      113      24
>> 12910783  Ok (04) Start/Stop Count           100      100      0
>> 784       Ok (05) Reallocated Sector Count   100      100      5
>> 3         Ok (07) Seek Error Rate            100      100      67
>> 0         Ok (08) Seek Time Performance      100      100      20
>> 0         Ok (09) Power On Hours Count       99       99       0
>> 13487     Ok (0A) Spin Retry Count           100      100      60
>> 0         Ok (0C) Power Cycle Count          100      100      0
>> 740       Ok (C0) Power Off Retract Count    100      100      50
>> 784       Ok (C1) Load Cycle Count           100      100      50
>> 784       Ok (C2) Temperature                98       98       0
>> 1179704   Ok (C4) Reallocated Event Count    100      100      0
>> 3         Ok (C5) Current Pending Sector     100      100      0
>> 1         Ok (C6) Offline Uncorrectable      100      100      0
>> 0         Ok (C7) Ultra DMA CRC Error Count  200      200      0
>> 0         Ok
>
>> Power On Time         : 13487
>> Health Status         : Ok
>
>> Note: 05 was highlighted yellow.
>
>> --
>
>> Microsoft Windows XP [Version 5.1.2600]
>> (C) Copyright 1985-2001 Microsoft Corp.
>
>> C:\>chkdsk d:
>> The type of the file system is NTFS.
>> Volume label is AFA64-D.
>
>> WARNING!  F parameter not specified.
>> Running CHKDSK in read-only mode.
>
>> CHKDSK is verifying files (stage 1 of 3)...
>> File verification completed.
>> CHKDSK is verifying indexes (stage 2 of 3)...
>> Index verification completed.
>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>> Security descriptor verification completed.
>
>>   10490412 KB total disk space.
>>    5964844 KB in 9376 files.
>>       3392 KB in 570 indexes.
>>          0 KB in bad sectors.
>>      30828 KB in use by the system.
>>       4096 KB occupied by the log file.
>>    4491348 KB available on disk.
>
>>       4096 bytes in each allocation unit.
>>    2622603 total allocation units on disk.
>>    1122837 allocation units available on disk.
>
>> C:\>chkdsk g:
>> The type of the file system is NTFS.
>> Volume label is AFA64-G.
>
>> WARNING!  F parameter not specified.
>> Running CHKDSK in read-only mode.
>
>> CHKDSK is verifying files (stage 1 of 3)...
>> File verification completed.
>> CHKDSK is verifying indexes (stage 2 of 3)...
>> Index verification completed.
>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>> Security descriptor verification completed.
>
>>    9229308 KB total disk space.
>>    2797308 KB in 6018 files.
>>       2792 KB in 294 indexes.
>>          4 KB in bad sectors.
>>      27548 KB in use by the system.
>>       4096 KB occupied by the log file.
>>    6401656 KB available on disk.
>
>>       4096 bytes in each allocation unit.
>>    2307327 total allocation units on disk.
>>    1600414 allocation units available on disk.
>
>> Notes: This 4 KB was from last year (don't remember when exactly). D
>> and G: are two partitions on this
>> physical HDD.
>
>> My computer specifications can be found here:
>> http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary
>> one).
>
>> I ran chkdsk a few times outside and inside of Windows and ran HD
>> Tune's error scan, but found no new problems. Speed looked good too.
>
>> Any ideas? Maybe I am not testing enough? Thank you in advance.
>>> o   o| |          Ant's Quality Foraged Links (AQFL):
>>> http://aqfl.net
>   \ _ /                        Please remove ANT if replying by
>    e-mail. ( ) 


0
Rod
5/19/2006 9:23:14 PM
The IBM Deskstar drives were notorious for failures.  IBM's solution to 
their short life was to say that they shouldn't be used for more than a 
couple of hours day, though warranty replacements for early drives could 
still be used continuously without voiding the warranty.  IBM sold their 
sinking hard drive business to Hitachi.

I gave up on regular warranty replacements after a while.  I don't have 
much that I want to put on such an unreliable drive.  Most died within 6 
to 18 months.  Only one out of maybe 6 still works today.
0
Kevin
5/20/2006 3:21:20 AM
In article <4d6j0mF1732kmU1@individual.net>,
 "Rod Speed" <rod.speed.aaa@gmail.com> wrote:

> Thats one of the infamous Deathstars, likely its dying. 

Note that every drive is a Deathstar at the end of its life, 
effectively.  They were pretty good when new.

-- 
Life is toxic. It leads to death and
too much of it at once can kill you.
0
Howard
5/20/2006 4:09:33 AM
Howard S Shubs <howard@shubs.net> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote

>> Thats one of the infamous Deathstars, likely its dying.

> Note that every drive is a Deathstar at the end of its life, effectively.

No they arent, I have plenty that work fine,
they're just too small to be any use anymore.

> They were pretty good when new.

Like hell they were, there's a reason for the full class action suit. 


0
Rod
5/20/2006 4:46:01 AM
<ANTant@zimage.com> wrote in message news:CpadnfOrQv8br_PZnZ2dnUVZ_sidnZ2d@mminternet.net
> > <ANTant@zimage.com> wrote in message news:icydnRqG7dYEBPDZRVn-qw@mminternet.net
[bigsnip]
> 
> It did get really warm a few days ago, but the recent symptoms wasn't that warm.

Doesn't matter. The errors are introduced when the power supply is marginal
or temperature is high. It can be quite some time before you run in to them if 
you don't access the files they are in frequently or don't do surface scans often.
Once introduced, (write)errors stay, even if the system returns to normal.
These errors are corrected/disappear when the 'bad' sectors are re/over-written.
0
Folkert
5/20/2006 5:52:12 AM
In article <4d7l8cF1969njU1@individual.net>,
 "Rod Speed" <rod.speed.aaa@gmail.com> wrote:

> Like hell they were, there's a reason for the full class action suit. 

I must've missed that bit.

-- 
Life is toxic. It leads to death and
too much of it at once can kill you.
0
Howard
5/21/2006 4:49:46 AM
In article <howard-B219CD.00093320052006@news.supernews.com>,
 Howard S Shubs <howard@shubs.net> wrote:

> In article <4d6j0mF1732kmU1@individual.net>,
>  "Rod Speed" <rod.speed.aaa@gmail.com> wrote:
> 
> > Thats one of the infamous Deathstars, likely its dying. 
> 
> Note that every drive is a Deathstar at the end of its life, 
> effectively.  They were pretty good when new.

Deathstars were a disaster.  Many batches of them started loosing blocks 
or completely failing after few months.  Of those that survived, a 
slight bump to your computer could cause a catastrophic head crash.

IBM actually changed the specifications to say that Deskstars must not 
be used continuously.  I was told on the phone that my warranty 
replacements should not be powered on more than 2 hours a day.

Yes, IBM was hit with a class action suit for advertising the drives as 
highly reliable giving false MTBF specifications.
0
Kevin
5/21/2006 7:26:52 AM
haha, talk about a yarn...  slight bump, yeah,
right.  2 hours a day, yeah, right.  "False"
MTBF, yeah, right.  Anyway, here it is about
seven years later and it's still running. hah


Kevin McMurtrie [Sun, 21 May 2006 00:26:52 -0700]:
 >slight bump to your computer could cause a catastrophic head crash.
 >replacements should not be powered on more than 2 hours a day.
 >highly reliable giving false MTBF specifications.


-- 
 40th Floor - Software  @  http://40th.com/
 iPlay : the ultimate audio player for mobiles
 parametric eq, xfeed, reverb; all on a mobile
0
hel
5/21/2006 10:58:57 AM
Previously hel@40th.com wrote:
> haha, talk about a yarn...  slight bump, yeah,
> right.  2 hours a day, yeah, right.  "False"
> MTBF, yeah, right.  Anyway, here it is about
> seven years later and it's still running. hah

They have a high failure probability. They do not have ensured early
failure. I have personally seen 3 of 3 I used fail in different
computers and have seen others fail. When our department IT people
decided to swap them all out, most had already failed (of about 15 or
so).

Of course some people are lucky and teirs run forever. But that is
not what MTBF is about. I think you are statistically challenged.

Arno

 


> Kevin McMurtrie [Sun, 21 May 2006 00:26:52 -0700]:
>  >slight bump to your computer could cause a catastrophic head crash.
>  >replacements should not be powered on more than 2 hours a day.
>  >highly reliable giving false MTBF specifications.


> -- 
>  40th Floor - Software  @  http://40th.com/
>  iPlay : the ultimate audio player for mobiles
>  parametric eq, xfeed, reverb; all on a mobile
0
Arno
5/21/2006 1:20:32 PM
The point is, none of what he claimed is true.
It was all BS, but then, haha, what's so unusual
about that here?  I suppose you "know" what MTBF
is all about (haha, yeah, right).

AW [21 May 2006 13:20:32 GMT]:
 >not what MTBF is about. I think you are statistically challenged.

-- 
 40th Floor - Software  @  http://40th.com/
 iPlay : the ultimate audio player for mobiles
 parametric eq, xfeed, reverb; all on a mobile
0
hel
5/21/2006 1:47:16 PM
Previously hel@40th.com wrote:
> The point is, none of what he claimed is true.
> It was all BS, but then, haha, what's so unusual
> about that here?  I suppose you "know" what MTBF
> is all about (haha, yeah, right).

> AW [21 May 2006 13:20:32 GMT]:
>  >not what MTBF is about. I think you are statistically challenged.

> -- 
>  40th Floor - Software  @  http://40th.com/
>  iPlay : the ultimate audio player for mobiles
>  parametric eq, xfeed, reverb; all on a mobile
0
Arno
5/21/2006 7:52:56 PM
Previously hel@40th.com wrote:
> The point is, none of what he claimed is true.
> It was all BS, but then, haha, what's so unusual
> about that here?  I suppose you "know" what MTBF
> is all about (haha, yeah, right).

> AW [21 May 2006 13:20:32 GMT]:
>  >not what MTBF is about. I think you are statistically challenged.

You know, top-posting is impolite. 

And you are righ now only adding to the noise level here.
It is not difficult to find out what MTBF is. That you 
obviously have not bothered to speaks volumes on the value
of your comment.

Arno
0
Arno
5/21/2006 7:54:36 PM
"Arno Wagner" <me@privacy.net> wrote in message news:4dbursF19pgtvU3@individual.net
> Previously hel@40th.com wrote:
> > The point is, none of what he claimed is true.
> > It was all BS, but then, haha, what's so unusual
> > about that here?  I suppose you "know" what MTBF
> > is all about (haha, yeah, right).
> 
> > AW [21 May 2006 13:20:32 GMT]:
> >  > not what MTBF is about. I think you are statistically challenged.
> 
> You know, top-posting is impolite.

So is posting your name in the middle of an article.

> 
> And you are righ now only adding to the noise level here.

He a brother of yours, babblemouth?

> It is not difficult to find out what MTBF is. That you obviously 
> have not bothered to speaks volumes on the value of your comment.
> 
> Arno
0
Folkert
5/21/2006 8:14:23 PM
In comp.sys.ibm.pc.hardware.storage hel@40th.com wrote:
> Aa [Fri, 19 May 2006 15:58:38 -0500]:
>  >Like what? Old age? I haven't changed anytrhing for months in my computer (ha

> Like what?  Are you looking for alternatives,
> or do you already know it's the disk?  If the
> disk is bad, replace it.  It'll be the easiest
> thing to do.

Actually, it doesn't seem like IBM drive. It is probably the controller or the Seagate drive. I moved the pagefile 
away from this IBM drive and I still get errors. 
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:20:44 AM
In comp.sys.ibm.pc.hardware.storage Rod Speed <rod.speed.aaa@gmail.com> wrote:
> ANTant@zimage.com wrote
> > hel@40th.com wrote

> >> Timeout may not necessarily mean the disk itself.

> Correct. But he does have reallocated sectors in the SMART report.

> >> Could be the mobo is the cause,
> >> and the disk T/O is only the symptom.

> > Like what? Old age?

> Yes, you can get bad caps on the motherboard. Those
> are the usually blue or black plastic covered post like
> things sticking up from the motherboard. The tops should
> be flat and any that have bulged or leaked have failed.

> > I haven't changed anytrhing for months in my computer (hardware).

> You dont need to have done with a cap failure or the
> failure that those 60gxp drives are notorious for.

Is that common? I noticed my last machine (not this one I mentioned) died because of my PSU (250 watts) was the 
borderline (it ran for almost a year without problems too), and decided to stop (heard it spin down and power off 
the machine). Then, the horrible odor (no smokes) and my old Quantum HDD's controller died (wouldn't spin 
anymore).


> They are called deathstars for a reason.
> That produced a full class action suit.

Is it too late for me to get my money back? I had it since 9/9/2001, but I don't think I have the receipt anymore 
(long gone).
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:23:30 AM
In comp.sys.ibm.pc.hardware.storage Folkert Rienstra <see_reply-to@myweb.nl> wrote:
> <ANTant@zimage.com> wrote in message news:CpadnfOrQv8br_PZnZ2dnUVZ_sidnZ2d@mminternet.net
> > > <ANTant@zimage.com> wrote in message news:icydnRqG7dYEBPDZRVn-qw@mminternet.net
> [bigsnip]
> > 
> > It did get really warm a few days ago, but the recent symptoms wasn't that warm.

> Doesn't matter. The errors are introduced when the power supply is marginal
> or temperature is high. It can be quite some time before you run in to them if 

Hmm, is there a way to check this? I only had this 500 watts Seasonic S12 PSU since 11/25/2005. Is it not powerful
enough? Heat could be a thing. My small room can get over 85 degrees(F) during heat waves (L.A. area) and my
motherboard sensor says 112F and CPU says 151F. However, it didn't get that high recently (probably since October
2005). I already have HDD coolers, extra case fans, etc. in this old full-tower ATX case (got it in 1998 I think).


> you don't access the files they are in frequently or don't do surface scans often.
> Once introduced, (write)errors stay, even if the system returns to normal.
> These errors are corrected/disappear when the 'bad' sectors are re/over-written.

I am going to try more SpinRite tonight. So far, various disk utilites said no problems.
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:29:40 AM
In comp.sys.ibm.pc.hardware.storage Rod Speed <rod.speed.aaa@gmail.com> wrote:
> ANTant@zimage.com wrote:

> > OK, I did more digging. I moved my page swap
> > off the G: drive to E drive, but still had problems.

> Fine.

> > For the heck of it, I tried defragging on my I: drive and
> > man I got lots of disk errors (timeouts, disconnected,
> > freezes/pauses). I know it was a bad idea, but then it
> > is my video HDD (already saw my TV shows).

> That does suggest that it might be a problem outside the
> drive, like motherboard/power supply/overheating etc.

> In fact on a closer look, the drive temperature would be
> worth checking with Everest, HDTune doesnt appear to
> be showing it properly. Show the Seagate SMART data too.

> > I think I am going to have to do disk test on
> > this Seagate drive first outside of Windows.

> And check the SMART data for that drive too.

I don't think I can get the Seagate HDD's SMART sensor data due to the VIA SATA Controller. Even SpinRite can't
show it. The reason for this setup is because I have three internal HDDs and two CD/DVD drives (one is a burner).
Also, using the onboard Promise controller seems to fail to boot up my Windows XP 100% of the times (no idea why). 
It is like those external USB HDDs. No SMART sensor datas, etc. Any ideas why controller does this? Maybe this
setup is a bad idea but then I didn't have this problem before last week! <end of my reply>


> > In alt.comp.periphs.hdd ANTant@zimage.com wrote:
> >> I need some other opinions from you HDD experts since I don't know
> >> about HDD issues. I would think it is dying, but I can't seem to get
> >> the symptoms:
> >
> >> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA
> >> 4in1 drivers) acting funny. I checked the event viewer logs and saw:
> >
> >> Event Type:     Warning
> >> Event Source:   Disk
> >> Event Category: None
> >> Event ID:       51
> >> Date:           5/18/2006
> >> Time:           10:00:04 PM
> >> User:           N/A
> >> Computer:       MyCompy
> >> Description:
> >> An error was detected on device \Device\Harddisk2\D during a paging
> >> operation.For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> >> 0008: 00 00 00 00 33 00 04 80   ....3..?
> >> 0010: 2d 01 00 00 00 00 00 00   -.......
> >> 0018: 00 00 00 00 00 00 00 00   ........
> >> 0020: 00 00 00 00 00 00 00 00   ........
> >> 0028: 10 33 06 00 00 00 00 00   .3......
> >> 0030: ff ff ff ff 03 00 00 00   ????....
> >> 0038: 40 00 00 04 00 00 00 00   @.......
> >> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> >> 0048: 00 00 01 00 0a 00 00 00   ........
> >> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
> >> 0058: 00 00 00 00 d0 99 45 87   ....??E?
> >> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
> >> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
> >> 0070: 80 00 00 00 00 00 00 00   ?.......
> >> 0078: 00 00 00 00 00 00 00 00   ........
> >> 0080: 00 00 00 00 00 00 00 00   ........
> >> 0088: 00 00 00 00 00 00 00 00   ........
> >
> >> Event Type:     Error
> >> Event Source:   viamraid
> >> Event Category: None
> >> Event ID:       9
> >> Date:           5/18/2006
> >> Time:           10:00:04 PM
> >> User:           N/A
> >> Computer:       MyCompy
> >> Description:
> >> The device, \Device\Scsi\viamraid1, did not respond within the
> >> timeout period.For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> >> 0008: 00 00 00 00 09 00 04 c0   .......?
> >> 0010: 00 01 00 00 00 00 00 00   ........
> >> 0018: 94 05 00 00 00 00 00 00   ?.......
> >> 0020: 00 00 00 00 00 00 00 00   ........
> >> 0028: 00 00 00 00 00 00 00 00   ........
> >> 0030: 00 00 00 00 07 00 00 00   ........
> >
> >
> >> Event Type:    Warning
> >> Event Source:    Disk
> >> Event Category:    None
> >> Event ID:    51
> >> Date:        5/17/2006
> >> Time:        7:56:48 PM
> >> User:        N/A
> >> Computer:    MyCompy
> >> Description:
> >> An error was detected on device \Device\Harddisk2\D during a paging
> >> operation.
> >
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> >> 0008: 00 00 00 00 33 00 04 80   ....3..?
> >> 0010: 2d 01 00 00 00 00 00 00   -.......
> >> 0018: 00 00 00 00 00 00 00 00   ........
> >> 0020: 00 00 00 00 00 00 00 00   ........
> >> 0028: 53 97 54 00 00 00 00 00   S?T.....
> >> 0030: ff ff ff ff 03 00 00 00   ????....
> >> 0038: 40 00 00 04 00 00 00 00   @.......
> >> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> >> 0048: 00 00 01 00 0a 00 00 00   ........
> >> 0050: 00 00 00 00 68 46 55 87   ....hFU?
> >> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
> >> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
> >> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
> >> 0070: 80 00 00 00 00 00 00 00   ?.......
> >> 0078: 00 00 00 00 00 00 00 00   ........
> >> 0080: 00 00 00 00 00 00 00 00   ........
> >> 0088: 00 00 00 00 00 00 00 00   ........
> >
> >> Event Type:    Error
> >> Event Source:    viamraid
> >> Event Category:    None
> >> Event ID:    9
> >> Date:        5/17/2006
> >> Time:        7:56:48 PM
> >> User:        N/A
> >> Computer:    MyCompy
> >> Description:
> >> The device, \Device\Scsi\viamraid1, did not respond within the
> >> timeout period.
> >
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> >> 0008: 00 00 00 00 09 00 04 c0   .......?
> >> 0010: 00 01 00 00 00 00 00 00   ........
> >> 0018: 38 00 00 00 00 00 00 00   8.......
> >> 0020: 00 00 00 00 00 00 00 00   ........
> >> 0028: 00 00 00 00 00 00 00 00   ........
> >> 0030: 00 00 00 00 07 00 00 00   ........
> >
> >> Note: Yes, I have a paging file here.
> >
> >
> >> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
> >
> >> HD Tune: IC35L040AVER07-0 Health
> >
> >> ID                              Current  Worst    ThresholdData
> >> Status (01) Raw Read Error Rate        100      100      60
> >> 65536     Ok (02) Throughput Performance     100      100      50
> >> 0         Ok (03) Spin Up Time               113      113      24
> >> 12910783  Ok (04) Start/Stop Count           100      100      0
> >> 784       Ok (05) Reallocated Sector Count   100      100      5
> >> 3         Ok (07) Seek Error Rate            100      100      67
> >> 0         Ok (08) Seek Time Performance      100      100      20
> >> 0         Ok (09) Power On Hours Count       99       99       0
> >> 13487     Ok (0A) Spin Retry Count           100      100      60
> >> 0         Ok (0C) Power Cycle Count          100      100      0
> >> 740       Ok (C0) Power Off Retract Count    100      100      50
> >> 784       Ok (C1) Load Cycle Count           100      100      50
> >> 784       Ok (C2) Temperature                98       98       0
> >> 1179704   Ok (C4) Reallocated Event Count    100      100      0
> >> 3         Ok (C5) Current Pending Sector     100      100      0
> >> 1         Ok (C6) Offline Uncorrectable      100      100      0
> >> 0         Ok (C7) Ultra DMA CRC Error Count  200      200      0
> >> 0         Ok
> >
> >> Power On Time         : 13487
> >> Health Status         : Ok
> >
> >> Note: 05 was highlighted yellow.
> >
> >> --
> >
> >> Microsoft Windows XP [Version 5.1.2600]
> >> (C) Copyright 1985-2001 Microsoft Corp.
> >
> >> C:\>chkdsk d:
> >> The type of the file system is NTFS.
> >> Volume label is AFA64-D.
> >
> >> WARNING!  F parameter not specified.
> >> Running CHKDSK in read-only mode.
> >
> >> CHKDSK is verifying files (stage 1 of 3)...
> >> File verification completed.
> >> CHKDSK is verifying indexes (stage 2 of 3)...
> >> Index verification completed.
> >> CHKDSK is verifying security descriptors (stage 3 of 3)...
> >> Security descriptor verification completed.
> >
> >>   10490412 KB total disk space.
> >>    5964844 KB in 9376 files.
> >>       3392 KB in 570 indexes.
> >>          0 KB in bad sectors.
> >>      30828 KB in use by the system.
> >>       4096 KB occupied by the log file.
> >>    4491348 KB available on disk.
> >
> >>       4096 bytes in each allocation unit.
> >>    2622603 total allocation units on disk.
> >>    1122837 allocation units available on disk.
> >
> >> C:\>chkdsk g:
> >> The type of the file system is NTFS.
> >> Volume label is AFA64-G.
> >
> >> WARNING!  F parameter not specified.
> >> Running CHKDSK in read-only mode.
> >
> >> CHKDSK is verifying files (stage 1 of 3)...
> >> File verification completed.
> >> CHKDSK is verifying indexes (stage 2 of 3)...
> >> Index verification completed.
> >> CHKDSK is verifying security descriptors (stage 3 of 3)...
> >> Security descriptor verification completed.
> >
> >>    9229308 KB total disk space.
> >>    2797308 KB in 6018 files.
> >>       2792 KB in 294 indexes.
> >>          4 KB in bad sectors.
> >>      27548 KB in use by the system.
> >>       4096 KB occupied by the log file.
> >>    6401656 KB available on disk.
> >
> >>       4096 bytes in each allocation unit.
> >>    2307327 total allocation units on disk.
> >>    1600414 allocation units available on disk.
> >
> >> Notes: This 4 KB was from last year (don't remember when exactly). D
> >> and G: are two partitions on this
> >> physical HDD.
> >
> >> My computer specifications can be found here:
> >> http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary
> >> one).
> >
> >> I ran chkdsk a few times outside and inside of Windows and ran HD
> >> Tune's error scan, but found no new problems. Speed looked good too.
> >
> >> Any ideas? Maybe I am not testing enough? Thank you in advance.
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:35:20 AM
In comp.sys.ibm.pc.hardware.storage Kevin McMurtrie <mcmurtri@dslextreme.com> wrote:
> The IBM Deskstar drives were notorious for failures.  IBM's solution to 
> their short life was to say that they shouldn't be used for more than a 
> couple of hours day, though warranty replacements for early drives could 
> still be used continuously without voiding the warranty.  IBM sold their 
> sinking hard drive business to Hitachi.

> I gave up on regular warranty replacements after a while.  I don't have 
> much that I want to put on such an unreliable drive.  Most died within 6 
> to 18 months.  Only one out of maybe 6 still works today.

Wow. That's crazy.
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:35:53 AM
ANTant@zimage.com wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote
>> ANTant@zimage.com wrote
>>> hel@40th.com wrote

>>>> Timeout may not necessarily mean the disk itself.

>> Correct. But he does have reallocated sectors in the SMART report.

>>>> Could be the mobo is the cause,
>>>> and the disk T/O is only the symptom.

>>> Like what? Old age?

>> Yes, you can get bad caps on the motherboard. Those
>> are the usually blue or black plastic covered post like
>> things sticking up from the motherboard. The tops should
>> be flat and any that have bulged or leaked have failed.

>>> I haven't changed anytrhing for months in my computer (hardware).

>> You dont need to have done with a cap failure or the
>> failure that those 60gxp drives are notorious for.

> Is that common?

Is what common ?  Bad caps isnt that uncommon.

60gxp drives dying was so common that it generated a class action suit.

> I noticed my last machine (not this one I mentioned)
> died because of my PSU (250 watts) was the borderline
> (it ran for almost a year without problems too), and decided
> to stop (heard it spin down and power off the machine).
> Then, the horrible odor (no smokes)

Thats just the power supply dying, not due to the rating.

> and my old Quantum HDD's controller died (wouldn't spin anymore).

Yeah, it isnt that uncommon for a PSU failure to
kill some of what is powered from it. It basically
over voltages some of the rails when dying.

Is that the same motherboard ?  You may just be
seeing a failure of the motherboard now. Over voltages
dont  necessarily kill things stone dead immediately.

>> They are called deathstars for a reason.
>> That produced a full class action suit.

> Is it too late for me to get my money back?

That wasnt the result of the class action suit.

The settlement only appears to apply to the 75GXP and the
settlement is the usual pathetic result in your case anyway.

--------------------------------------
There are two categories of benefits with respect to each Qualifying Deskstar 75 GXP, and 
each Class Member may request and is eligible to receive only one of these categories of 
benefits. The categories are: (1) all Class Members who purchased a Qualifying Deskstar 
75GXP and have experienced a �disk drive failure� (an actual material problem with its 
performance, as evidenced by a record either in (a) IBM�s Technical Support Center 
database; (b) IBM�s Return Material Authorization database; or (c) the �IBM 75GXP� 
database maintained by the Sheller Ludwig & Badey law firm as of February 15, 2005) and 
meet the other Settlement eligibility criteria are eligible to receive a check for $100; 
and (2) all Class Members who purchased a Qualifying Deskstar 75GXP and have not 
experienced disk drive failure are eligible to receive their choice of either 25 blank 
CD-ROMs (with jewel cases) or a 15% Discount Certificate for a future purchase at IBM.com.

--------------------------------------------
> I had it since 9/9/2001, but I don't think
> I have the receipt anymore (long gone).

Could be a problem, but its academic anyway since the settlement is only for the 75GXP.


0
Rod
5/22/2006 6:37:19 AM
ANTant@zimage.com wrote
> Folkert Rienstra <see_reply-to@myweb.nl> wrote
>> <ANTant@zimage.com> wrote
>>>> <ANTant@zimage.com> wrote

>>> It did get really warm a few days ago, but
>>> the recent symptoms wasn't that warm.

>> Doesn't matter. The errors are introduced when the
>> power supply is marginal or temperature is high.

> Hmm, is there a way to check this?

Make sure the temperature and power are fine now and run
the hard drive manufacturer's diagnostic and do what quite
a few call a low level format and see what happens to the
SMART data. That will lose the data on the drive tho.

That should recheck all the sectors on the drive with writing.

> I only had this 500 watts Seasonic S12 PSU
> since 11/25/2005. Is it not powerful enough?

Very unlikely to no be powerful enough.

> Heat could be a thing. My small room can get over 85
> degrees(F) during heat waves (L.A. area) and my
> motherboard sensor says 112F and CPU says 151F.

What does the drive SMART temperature show then ?

> However, it didn't get that high recently (probably since October 2005).

See what the drive SMART temp data actually is
with a better SMART display, that drive looks like
its keeping the max temp ever seen in that value.

> I already have HDD coolers, extra case fans, etc.
> in this old full-tower ATX case (got it in 1998 I think).

The drive temp likely was fine.

Starting to look like a motherboard problem if that was
the motherboard that was in the system when the previous
250W PSU died. Likely it got killed by that failure.

>> It  can be quite some time before you run in to them if you don't
>> access the files they are in frequently or don't do surface scans often.

>> Once introduced, (write)errors stay, even if the system returns to normal.
>> These errors are corrected/disappear when the 'bad' sectors are re/over-written.

> I am going to try more SpinRite tonight.
> So far, various disk utilites said no problems.

What does the full SMART scan show using
smartctl  from a knoppix bootable CD ?

If thats fine too, and that motherboard was the one used
when the 250W PSU died, very likely that motherboard
got damaged by the over voltage that killed the Quantum. 


0
Rod
5/22/2006 6:53:50 AM
> >>>> Timeout may not necessarily mean the disk itself.

> >> Correct. But he does have reallocated sectors in the SMART report.

> >>>> Could be the mobo is the cause,
> >>>> and the disk T/O is only the symptom.

> >>> Like what? Old age?

> >> Yes, you can get bad caps on the motherboard. Those
> >> are the usually blue or black plastic covered post like
> >> things sticking up from the motherboard. The tops should
> >> be flat and any that have bulged or leaked have failed.

> >>> I haven't changed anytrhing for months in my computer (hardware).

> >> You dont need to have done with a cap failure or the
> >> failure that those 60gxp drives are notorious for.

> > Is that common?

> Is what common ?  Bad caps isnt that uncommon.

Sorry, I meant the bad caps. Man, I have been a computer user since TI 99/4A and they sure don't make quality 
computers anymore. :(


> 60gxp drives dying was so common that it generated a class action suit.

> > I noticed my last machine (not this one I mentioned)
> > died because of my PSU (250 watts) was the borderline
> > (it ran for almost a year without problems too), and decided
> > to stop (heard it spin down and power off the machine).
> > Then, the horrible odor (no smokes)

> Thats just the power supply dying, not due to the rating.

> > and my old Quantum HDD's controller died (wouldn't spin anymore).

> Yeah, it isnt that uncommon for a PSU failure to
> kill some of what is powered from it. It basically
> over voltages some of the rails when dying.

> Is that the same motherboard ?  You may just be
> seeing a failure of the motherboard now. Over voltages
> dont  necessarily kill things stone dead immediately.

Nope, that motherboard totally die (wouldn't boot up and had burned marks) and out of warranty. So, I got a 
refurbished MSI KT4AV-L (Socket A/Socket 462; VIA KT400A) motherboard.


> >> They are called deathstars for a reason.
> >> That produced a full class action suit.

> > Is it too late for me to get my money back?

> That wasnt the result of the class action suit.

> The settlement only appears to apply to the 75GXP and the
> settlement is the usual pathetic result in your case anyway.

Rats. :(


> --------------------------------------
> There are two categories of benefits with respect to each Qualifying Deskstar 75 GXP, and 
> each Class Member may request and is eligible to receive only one of these categories of 
> benefits. The categories are: (1) all Class Members who purchased a Qualifying Deskstar 
> 75GXP and have experienced a ?disk drive failure? (an actual material problem with its 
> performance, as evidenced by a record either in (a) IBM?s Technical Support Center 
> database; (b) IBM?s Return Material Authorization database; or (c) the ?IBM 75GXP? 
> database maintained by the Sheller Ludwig & Badey law firm as of February 15, 2005) and 
> meet the other Settlement eligibility criteria are eligible to receive a check for $100; 
> and (2) all Class Members who purchased a Qualifying Deskstar 75GXP and have not 
> experienced disk drive failure are eligible to receive their choice of either 25 blank 
> CD-ROMs (with jewel cases) or a 15% Discount Certificate for a future purchase at IBM.com.

> --------------------------------------------
> > I had it since 9/9/2001, but I don't think
> > I have the receipt anymore (long gone).

> Could be a problem, but its academic anyway since the settlement is only for the 75GXP.

Were 60 and 75 models identical with the symptoms, failure rates, etc.? I assume 75 is the newer and bigger model.

-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 6:54:05 AM
ANTant@zimage.com wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote
>> ANTant@zimage.com wrote

>>> OK, I did more digging. I moved my page swap
>>> off the G: drive to E drive, but still had problems.

>> Fine.

>>> For the heck of it, I tried defragging on my I: drive and
>>> man I got lots of disk errors (timeouts, disconnected,
>>> freezes/pauses). I know it was a bad idea, but then it
>>> is my video HDD (already saw my TV shows).

>> That does suggest that it might be a problem outside the
>> drive, like motherboard/power supply/overheating etc.

>> In fact on a closer look, the drive temperature would be
>> worth checking with Everest, HDTune doesnt appear to
>> be showing it properly. Show the Seagate SMART data too.

>>> I think I am going to have to do disk test on
>>> this Seagate drive first outside of Windows.

>> And check the SMART data for that drive too.

> I don't think I can get the Seagate HDD's SMART sensor data
> due to the VIA SATA Controller. Even SpinRite can't show it.

smartctl from a knoppix bootable CD should be able to show it.

> The reason for this setup is because I have three internal
> HDDs and two CD/DVD drives (one is a burner). Also,
> using the onboard Promise controller seems to fail to boot
> up my Windows XP 100% of the times (no idea why).

Maybe thats more evidence of the motherboard having
been zapped by the overvoltage seen when the 250W
PSU died and killed the Quantum hard drive, particularly
if that used to work before the PSU died.

> It is like those external USB HDDs. No SMART sensor datas, etc.

Yeah, tho smartctl can usually see what
Everest cant see with internal drives.

> Any ideas why controller does this?

I havent looked too closely at that, just use smartctl when necessary.

> Maybe this setup is a bad idea but then
> I didn't have this problem before last week!

Yeah, might be a workaround for a partially failed motherboard.

> <end of my reply>

<end of mine too>

>>> In alt.comp.periphs.hdd ANTant@zimage.com wrote:
>>>> I need some other opinions from you HDD experts since I don't know
>>>> about HDD issues. I would think it is dying, but I can't seem to
>>>> get the symptoms:
>>>
>>>> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA
>>>> 4in1 drivers) acting funny. I checked the event viewer logs and
>>>> saw:
>>>
>>>> Event Type:     Warning
>>>> Event Source:   Disk
>>>> Event Category: None
>>>> Event ID:       51
>>>> Date:           5/18/2006
>>>> Time:           10:00:04 PM
>>>> User:           N/A
>>>> Computer:       MyCompy
>>>> Description:
>>>> An error was detected on device \Device\Harddisk2\D during a paging
>>>> operation.For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>>>> 0010: 2d 01 00 00 00 00 00 00   -.......
>>>> 0018: 00 00 00 00 00 00 00 00   ........
>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>> 0028: 10 33 06 00 00 00 00 00   .3......
>>>> 0030: ff ff ff ff 03 00 00 00   ????....
>>>> 0038: 40 00 00 04 00 00 00 00   @.......
>>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>>>> 0048: 00 00 01 00 0a 00 00 00   ........
>>>> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
>>>> 0058: 00 00 00 00 d0 99 45 87   ....??E?
>>>> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
>>>> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
>>>> 0070: 80 00 00 00 00 00 00 00   ?.......
>>>> 0078: 00 00 00 00 00 00 00 00   ........
>>>> 0080: 00 00 00 00 00 00 00 00   ........
>>>> 0088: 00 00 00 00 00 00 00 00   ........
>>>
>>>> Event Type:     Error
>>>> Event Source:   viamraid
>>>> Event Category: None
>>>> Event ID:       9
>>>> Date:           5/18/2006
>>>> Time:           10:00:04 PM
>>>> User:           N/A
>>>> Computer:       MyCompy
>>>> Description:
>>>> The device, \Device\Scsi\viamraid1, did not respond within the
>>>> timeout period.For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>>>> 0008: 00 00 00 00 09 00 04 c0   .......?
>>>> 0010: 00 01 00 00 00 00 00 00   ........
>>>> 0018: 94 05 00 00 00 00 00 00   ?.......
>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>> 0028: 00 00 00 00 00 00 00 00   ........
>>>> 0030: 00 00 00 00 07 00 00 00   ........
>>>
>>>
>>>> Event Type:    Warning
>>>> Event Source:    Disk
>>>> Event Category:    None
>>>> Event ID:    51
>>>> Date:        5/17/2006
>>>> Time:        7:56:48 PM
>>>> User:        N/A
>>>> Computer:    MyCompy
>>>> Description:
>>>> An error was detected on device \Device\Harddisk2\D during a paging
>>>> operation.
>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>>>> 0010: 2d 01 00 00 00 00 00 00   -.......
>>>> 0018: 00 00 00 00 00 00 00 00   ........
>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>> 0028: 53 97 54 00 00 00 00 00   S?T.....
>>>> 0030: ff ff ff ff 03 00 00 00   ????....
>>>> 0038: 40 00 00 04 00 00 00 00   @.......
>>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>>>> 0048: 00 00 01 00 0a 00 00 00   ........
>>>> 0050: 00 00 00 00 68 46 55 87   ....hFU?
>>>> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
>>>> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
>>>> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
>>>> 0070: 80 00 00 00 00 00 00 00   ?.......
>>>> 0078: 00 00 00 00 00 00 00 00   ........
>>>> 0080: 00 00 00 00 00 00 00 00   ........
>>>> 0088: 00 00 00 00 00 00 00 00   ........
>>>
>>>> Event Type:    Error
>>>> Event Source:    viamraid
>>>> Event Category:    None
>>>> Event ID:    9
>>>> Date:        5/17/2006
>>>> Time:        7:56:48 PM
>>>> User:        N/A
>>>> Computer:    MyCompy
>>>> Description:
>>>> The device, \Device\Scsi\viamraid1, did not respond within the
>>>> timeout period.
>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> Data:
>>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>>>> 0008: 00 00 00 00 09 00 04 c0   .......?
>>>> 0010: 00 01 00 00 00 00 00 00   ........
>>>> 0018: 38 00 00 00 00 00 00 00   8.......
>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>> 0028: 00 00 00 00 00 00 00 00   ........
>>>> 0030: 00 00 00 00 07 00 00 00   ........
>>>
>>>> Note: Yes, I have a paging file here.
>>>
>>>
>>>> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
>>>
>>>> HD Tune: IC35L040AVER07-0 Health
>>>
>>>> ID                              Current  Worst    ThresholdData
>>>> Status (01) Raw Read Error Rate        100      100      60
>>>> 65536     Ok (02) Throughput Performance     100      100      50
>>>> 0         Ok (03) Spin Up Time               113      113      24
>>>> 12910783  Ok (04) Start/Stop Count           100      100      0
>>>> 784       Ok (05) Reallocated Sector Count   100      100      5
>>>> 3         Ok (07) Seek Error Rate            100      100      67
>>>> 0         Ok (08) Seek Time Performance      100      100      20
>>>> 0         Ok (09) Power On Hours Count       99       99       0
>>>> 13487     Ok (0A) Spin Retry Count           100      100      60
>>>> 0         Ok (0C) Power Cycle Count          100      100      0
>>>> 740       Ok (C0) Power Off Retract Count    100      100      50
>>>> 784       Ok (C1) Load Cycle Count           100      100      50
>>>> 784       Ok (C2) Temperature                98       98       0
>>>> 1179704   Ok (C4) Reallocated Event Count    100      100      0
>>>> 3         Ok (C5) Current Pending Sector     100      100      0
>>>> 1         Ok (C6) Offline Uncorrectable      100      100      0
>>>> 0         Ok (C7) Ultra DMA CRC Error Count  200      200      0
>>>> 0         Ok
>>>
>>>> Power On Time         : 13487
>>>> Health Status         : Ok
>>>
>>>> Note: 05 was highlighted yellow.
>>>
>>>> --
>>>
>>>> Microsoft Windows XP [Version 5.1.2600]
>>>> (C) Copyright 1985-2001 Microsoft Corp.
>>>
>>>> C:\>chkdsk d:
>>>> The type of the file system is NTFS.
>>>> Volume label is AFA64-D.
>>>
>>>> WARNING!  F parameter not specified.
>>>> Running CHKDSK in read-only mode.
>>>
>>>> CHKDSK is verifying files (stage 1 of 3)...
>>>> File verification completed.
>>>> CHKDSK is verifying indexes (stage 2 of 3)...
>>>> Index verification completed.
>>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>>>> Security descriptor verification completed.
>>>
>>>>   10490412 KB total disk space.
>>>>    5964844 KB in 9376 files.
>>>>       3392 KB in 570 indexes.
>>>>          0 KB in bad sectors.
>>>>      30828 KB in use by the system.
>>>>       4096 KB occupied by the log file.
>>>>    4491348 KB available on disk.
>>>
>>>>       4096 bytes in each allocation unit.
>>>>    2622603 total allocation units on disk.
>>>>    1122837 allocation units available on disk.
>>>
>>>> C:\>chkdsk g:
>>>> The type of the file system is NTFS.
>>>> Volume label is AFA64-G.
>>>
>>>> WARNING!  F parameter not specified.
>>>> Running CHKDSK in read-only mode.
>>>
>>>> CHKDSK is verifying files (stage 1 of 3)...
>>>> File verification completed.
>>>> CHKDSK is verifying indexes (stage 2 of 3)...
>>>> Index verification completed.
>>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>>>> Security descriptor verification completed.
>>>
>>>>    9229308 KB total disk space.
>>>>    2797308 KB in 6018 files.
>>>>       2792 KB in 294 indexes.
>>>>          4 KB in bad sectors.
>>>>      27548 KB in use by the system.
>>>>       4096 KB occupied by the log file.
>>>>    6401656 KB available on disk.
>>>
>>>>       4096 bytes in each allocation unit.
>>>>    2307327 total allocation units on disk.
>>>>    1600414 allocation units available on disk.
>>>
>>>> Notes: This 4 KB was from last year (don't remember when exactly).
>>>> D and G: are two partitions on this
>>>> physical HDD.
>>>
>>>> My computer specifications can be found here:
>>>> http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary
>>>> one).
>>>
>>>> I ran chkdsk a few times outside and inside of Windows and ran HD
>>>> Tune's error scan, but found no new problems. Speed looked good
>>>> too.
>>>
>>>> Any ideas? Maybe I am not testing enough? Thank you in advance.
>>> o   o| |          Ant's Quality Foraged Links (AQFL):
>>> http://aqfl.net
>   \ _ /                        Please remove ANT if replying by
>    e-mail. ( ) 


0
Rod
5/22/2006 6:59:41 AM
ANTant@zimage.com wrote:
> In comp.sys.ibm.pc.hardware.storage Kevin McMurtrie
> <mcmurtri@dslextreme.com> wrote:
>> The IBM Deskstar drives were notorious for failures.  IBM's solution
>> to their short life was to say that they shouldn't be used for more
>> than a couple of hours day, though warranty replacements for early
>> drives could still be used continuously without voiding the
>> warranty.  IBM sold their sinking hard drive business to Hitachi.
>
>> I gave up on regular warranty replacements after a while.  I don't
>> have much that I want to put on such an unreliable drive.  Most died
>> within 6 to 18 months.  Only one out of maybe 6 still works today.
>
> Wow. That's crazy.

Yeah, thats what produced the class action suit. 


0
Rod
5/22/2006 7:00:26 AM
In comp.sys.ibm.pc.hardware.storage Rod Speed <rod.speed.aaa@gmail.com> wrote:
> ANTant@zimage.com wrote
> > Folkert Rienstra <see_reply-to@myweb.nl> wrote
> >> <ANTant@zimage.com> wrote
> >>>> <ANTant@zimage.com> wrote

> >>> It did get really warm a few days ago, but
> >>> the recent symptoms wasn't that warm.

> >> Doesn't matter. The errors are introduced when the
> >> power supply is marginal or temperature is high.

> > Hmm, is there a way to check this?

> Make sure the temperature and power are fine now and run
> the hard drive manufacturer's diagnostic and do what quite
> a few call a low level format and see what happens to the
> SMART data. That will lose the data on the drive tho.

> That should recheck all the sectors on the drive with writing.

> > I only had this 500 watts Seasonic S12 PSU
> > since 11/25/2005. Is it not powerful enough?

> Very unlikely to no be powerful enough.

> > Heat could be a thing. My small room can get over 85
> > degrees(F) during heat waves (L.A. area) and my
> > motherboard sensor says 112F and CPU says 151F.

> What does the drive SMART temperature show then ?

Well, it is cooler now (77 F degrees in my room; CPU: 61C/141F; Mobo: 42/107F). HD Tune says:
1. Quantum FireballP LM (15 GB) has no temperature sensors (probably too old)
2. IBM IC35L040AVER07-0 (41 GB) says 56C/132F
3. Seagate ST3120026A (120 GB) says 45C/113F


> > However, it didn't get that high recently (probably since October 2005).

> See what the drive SMART temp data actually is
> with a better SMART display, that drive looks like
> its keeping the max temp ever seen in that value.

> > I already have HDD coolers, extra case fans, etc.
> > in this old full-tower ATX case (got it in 1998 I think).

> The drive temp likely was fine.

> Starting to look like a motherboard problem if that was
> the motherboard that was in the system when the previous
> 250W PSU died. Likely it got killed by that failure.

Actually, that was my other machine (Enlight 340 watts PSU after 250 watts). This one (SeaSonic PSU) is using a
refurbished ASUS K8V SE Deluxe (had to send in my original one because its BIOS firmware upgrade failed even
though it said success!)..


> >> It  can be quite some time before you run in to them if you don't
> >> access the files they are in frequently or don't do surface scans often.

> >> Once introduced, (write)errors stay, even if the system returns to normal.
> >> These errors are corrected/disappear when the 'bad' sectors are re/over-written.

> > I am going to try more SpinRite tonight.
> > So far, various disk utilites said no problems.

> What does the full SMART scan show using
> smartctl  from a knoppix bootable CD ?

Crap, I forgot to run that, but I doubt it will tell me about Seagate drive which is a prime suspect to me. Again, 
I doubt I can get that information if SpinRite, HD Tune, etc. can't get the information.


> If thats fine too, and that motherboard was the one used
> when the 250W PSU died, very likely that motherboard
> got damaged by the over voltage that killed the Quantum. 

See http://alpha.zimage.com/~ant/antfarm/about/computers.txt that I haev two desktops. Don't get both mixxed up. 
:)
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 7:20:54 AM
In comp.sys.ibm.pc.hardware.storage Rod Speed <rod.speed.aaa@gmail.com> wrote:
> ANTant@zimage.com wrote
> > Rod Speed <rod.speed.aaa@gmail.com> wrote
> >> ANTant@zimage.com wrote

> >>> OK, I did more digging. I moved my page swap
> >>> off the G: drive to E drive, but still had problems.

> >> Fine.

> >>> For the heck of it, I tried defragging on my I: drive and
> >>> man I got lots of disk errors (timeouts, disconnected,
> >>> freezes/pauses). I know it was a bad idea, but then it
> >>> is my video HDD (already saw my TV shows).

> >> That does suggest that it might be a problem outside the
> >> drive, like motherboard/power supply/overheating etc.

> >> In fact on a closer look, the drive temperature would be
> >> worth checking with Everest, HDTune doesnt appear to
> >> be showing it properly. Show the Seagate SMART data too.

> >>> I think I am going to have to do disk test on
> >>> this Seagate drive first outside of Windows.

> >> And check the SMART data for that drive too.

> > I don't think I can get the Seagate HDD's SMART sensor data
> > due to the VIA SATA Controller. Even SpinRite can't show it.

> smartctl from a knoppix bootable CD should be able to show it.

Really. Are there any Windows programs or DOS programs that can do it too (if smartcl can do it)? I will have to
check that out. I hope v4.0.2 can do it. I don't have 5.x since it is not publicly released yet.


> > The reason for this setup is because I have three internal
> > HDDs and two CD/DVD drives (one is a burner). Also,
> > using the onboard Promise controller seems to fail to boot
> > up my Windows XP 100% of the times (no idea why).

> Maybe thats more evidence of the motherboard having
> been zapped by the overvoltage seen when the 250W
> PSU died and killed the Quantum hard drive, particularly
> if that used to work before the PSU died.

Uhh, that's the other computer. :) You're getting confused with my two machines: 
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...


> > It is like those external USB HDDs. No SMART sensor datas, etc.

> Yeah, tho smartctl can usually see what
> Everest cant see with internal drives.

Interesting. I wonder why??


> > Any ideas why controller does this?

> I havent looked too closely at that, just use smartctl when necessary.

OK.


> > Maybe this setup is a bad idea but then
> > I didn't have this problem before last week!

> Yeah, might be a workaround for a partially failed motherboard.

> > <end of my reply>

> <end of mine too>

:) [again end of reply]


> >>> In alt.comp.periphs.hdd ANTant@zimage.com wrote:
> >>>> I need some other opinions from you HDD experts since I don't know
> >>>> about HDD issues. I would think it is dying, but I can't seem to
> >>>> get the symptoms:
> >>>
> >>>> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA
> >>>> 4in1 drivers) acting funny. I checked the event viewer logs and
> >>>> saw:
> >>>
> >>>> Event Type:     Warning
> >>>> Event Source:   Disk
> >>>> Event Category: None
> >>>> Event ID:       51
> >>>> Date:           5/18/2006
> >>>> Time:           10:00:04 PM
> >>>> User:           N/A
> >>>> Computer:       MyCompy
> >>>> Description:
> >>>> An error was detected on device \Device\Harddisk2\D during a paging
> >>>> operation.For more information, see Help and Support Center at
> >>>> http://go.microsoft.com/fwlink/events.asp.
> >>>> Data:
> >>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> >>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
> >>>> 0010: 2d 01 00 00 00 00 00 00   -.......
> >>>> 0018: 00 00 00 00 00 00 00 00   ........
> >>>> 0020: 00 00 00 00 00 00 00 00   ........
> >>>> 0028: 10 33 06 00 00 00 00 00   .3......
> >>>> 0030: ff ff ff ff 03 00 00 00   ????....
> >>>> 0038: 40 00 00 04 00 00 00 00   @.......
> >>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> >>>> 0048: 00 00 01 00 0a 00 00 00   ........
> >>>> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
> >>>> 0058: 00 00 00 00 d0 99 45 87   ....??E?
> >>>> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
> >>>> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
> >>>> 0070: 80 00 00 00 00 00 00 00   ?.......
> >>>> 0078: 00 00 00 00 00 00 00 00   ........
> >>>> 0080: 00 00 00 00 00 00 00 00   ........
> >>>> 0088: 00 00 00 00 00 00 00 00   ........
> >>>
> >>>> Event Type:     Error
> >>>> Event Source:   viamraid
> >>>> Event Category: None
> >>>> Event ID:       9
> >>>> Date:           5/18/2006
> >>>> Time:           10:00:04 PM
> >>>> User:           N/A
> >>>> Computer:       MyCompy
> >>>> Description:
> >>>> The device, \Device\Scsi\viamraid1, did not respond within the
> >>>> timeout period.For more information, see Help and Support Center at
> >>>> http://go.microsoft.com/fwlink/events.asp.
> >>>> Data:
> >>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> >>>> 0008: 00 00 00 00 09 00 04 c0   .......?
> >>>> 0010: 00 01 00 00 00 00 00 00   ........
> >>>> 0018: 94 05 00 00 00 00 00 00   ?.......
> >>>> 0020: 00 00 00 00 00 00 00 00   ........
> >>>> 0028: 00 00 00 00 00 00 00 00   ........
> >>>> 0030: 00 00 00 00 07 00 00 00   ........
> >>>
> >>>
> >>>> Event Type:    Warning
> >>>> Event Source:    Disk
> >>>> Event Category:    None
> >>>> Event ID:    51
> >>>> Date:        5/17/2006
> >>>> Time:        7:56:48 PM
> >>>> User:        N/A
> >>>> Computer:    MyCompy
> >>>> Description:
> >>>> An error was detected on device \Device\Harddisk2\D during a paging
> >>>> operation.
> >>>
> >>>> For more information, see Help and Support Center at
> >>>> http://go.microsoft.com/fwlink/events.asp.
> >>>> Data:
> >>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
> >>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
> >>>> 0010: 2d 01 00 00 00 00 00 00   -.......
> >>>> 0018: 00 00 00 00 00 00 00 00   ........
> >>>> 0020: 00 00 00 00 00 00 00 00   ........
> >>>> 0028: 53 97 54 00 00 00 00 00   S?T.....
> >>>> 0030: ff ff ff ff 03 00 00 00   ????....
> >>>> 0038: 40 00 00 04 00 00 00 00   @.......
> >>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
> >>>> 0048: 00 00 01 00 0a 00 00 00   ........
> >>>> 0050: 00 00 00 00 68 46 55 87   ....hFU?
> >>>> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
> >>>> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
> >>>> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
> >>>> 0070: 80 00 00 00 00 00 00 00   ?.......
> >>>> 0078: 00 00 00 00 00 00 00 00   ........
> >>>> 0080: 00 00 00 00 00 00 00 00   ........
> >>>> 0088: 00 00 00 00 00 00 00 00   ........
> >>>
> >>>> Event Type:    Error
> >>>> Event Source:    viamraid
> >>>> Event Category:    None
> >>>> Event ID:    9
> >>>> Date:        5/17/2006
> >>>> Time:        7:56:48 PM
> >>>> User:        N/A
> >>>> Computer:    MyCompy
> >>>> Description:
> >>>> The device, \Device\Scsi\viamraid1, did not respond within the
> >>>> timeout period.
> >>>
> >>>> For more information, see Help and Support Center at
> >>>> http://go.microsoft.com/fwlink/events.asp.
> >>>> Data:
> >>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
> >>>> 0008: 00 00 00 00 09 00 04 c0   .......?
> >>>> 0010: 00 01 00 00 00 00 00 00   ........
> >>>> 0018: 38 00 00 00 00 00 00 00   8.......
> >>>> 0020: 00 00 00 00 00 00 00 00   ........
> >>>> 0028: 00 00 00 00 00 00 00 00   ........
> >>>> 0030: 00 00 00 00 07 00 00 00   ........
> >>>
> >>>> Note: Yes, I have a paging file here.
> >>>
> >>>
> >>>> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
> >>>
> >>>> HD Tune: IC35L040AVER07-0 Health
> >>>
> >>>> ID                              Current  Worst    ThresholdData
> >>>> Status (01) Raw Read Error Rate        100      100      60
> >>>> 65536     Ok (02) Throughput Performance     100      100      50
> >>>> 0         Ok (03) Spin Up Time               113      113      24
> >>>> 12910783  Ok (04) Start/Stop Count           100      100      0
> >>>> 784       Ok (05) Reallocated Sector Count   100      100      5
> >>>> 3         Ok (07) Seek Error Rate            100      100      67
> >>>> 0         Ok (08) Seek Time Performance      100      100      20
> >>>> 0         Ok (09) Power On Hours Count       99       99       0
> >>>> 13487     Ok (0A) Spin Retry Count           100      100      60
> >>>> 0         Ok (0C) Power Cycle Count          100      100      0
> >>>> 740       Ok (C0) Power Off Retract Count    100      100      50
> >>>> 784       Ok (C1) Load Cycle Count           100      100      50
> >>>> 784       Ok (C2) Temperature                98       98       0
> >>>> 1179704   Ok (C4) Reallocated Event Count    100      100      0
> >>>> 3         Ok (C5) Current Pending Sector     100      100      0
> >>>> 1         Ok (C6) Offline Uncorrectable      100      100      0
> >>>> 0         Ok (C7) Ultra DMA CRC Error Count  200      200      0
> >>>> 0         Ok
> >>>
> >>>> Power On Time         : 13487
> >>>> Health Status         : Ok
> >>>
> >>>> Note: 05 was highlighted yellow.
> >>>
> >>>> --
> >>>
> >>>> Microsoft Windows XP [Version 5.1.2600]
> >>>> (C) Copyright 1985-2001 Microsoft Corp.
> >>>
> >>>> C:\>chkdsk d:
> >>>> The type of the file system is NTFS.
> >>>> Volume label is AFA64-D.
> >>>
> >>>> WARNING!  F parameter not specified.
> >>>> Running CHKDSK in read-only mode.
> >>>
> >>>> CHKDSK is verifying files (stage 1 of 3)...
> >>>> File verification completed.
> >>>> CHKDSK is verifying indexes (stage 2 of 3)...
> >>>> Index verification completed.
> >>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
> >>>> Security descriptor verification completed.
> >>>
> >>>>   10490412 KB total disk space.
> >>>>    5964844 KB in 9376 files.
> >>>>       3392 KB in 570 indexes.
> >>>>          0 KB in bad sectors.
> >>>>      30828 KB in use by the system.
> >>>>       4096 KB occupied by the log file.
> >>>>    4491348 KB available on disk.
> >>>
> >>>>       4096 bytes in each allocation unit.
> >>>>    2622603 total allocation units on disk.
> >>>>    1122837 allocation units available on disk.
> >>>
> >>>> C:\>chkdsk g:
> >>>> The type of the file system is NTFS.
> >>>> Volume label is AFA64-G.
> >>>
> >>>> WARNING!  F parameter not specified.
> >>>> Running CHKDSK in read-only mode.
> >>>
> >>>> CHKDSK is verifying files (stage 1 of 3)...
> >>>> File verification completed.
> >>>> CHKDSK is verifying indexes (stage 2 of 3)...
> >>>> Index verification completed.
> >>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
> >>>> Security descriptor verification completed.
> >>>
> >>>>    9229308 KB total disk space.
> >>>>    2797308 KB in 6018 files.
> >>>>       2792 KB in 294 indexes.
> >>>>          4 KB in bad sectors.
> >>>>      27548 KB in use by the system.
> >>>>       4096 KB occupied by the log file.
> >>>>    6401656 KB available on disk.
> >>>
> >>>>       4096 bytes in each allocation unit.
> >>>>    2307327 total allocation units on disk.
> >>>>    1600414 allocation units available on disk.
> >>>
> >>>> Notes: This 4 KB was from last year (don't remember when exactly).
> >>>> D and G: are two partitions on this
> >>>> physical HDD.
> >>>
> >>>> My computer specifications can be found here:
> >>>> http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary
> >>>> one).
> >>>
> >>>> I ran chkdsk a few times outside and inside of Windows and ran HD
> >>>> Tune's error scan, but found no new problems. Speed looked good
> >>>> too.
> >>>
> >>>> Any ideas? Maybe I am not testing enough? Thank you in advance.
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 7:24:30 AM
ANTant@zimage.com wrote

>>>>>> Timeout may not necessarily mean the disk itself.

>>>> Correct. But he does have reallocated sectors in the SMART report.

>>>>>> Could be the mobo is the cause,
>>>>>> and the disk T/O is only the symptom.

>>>>> Like what? Old age?

>>>> Yes, you can get bad caps on the motherboard. Those
>>>> are the usually blue or black plastic covered post like
>>>> things sticking up from the motherboard. The tops should
>>>> be flat and any that have bulged or leaked have failed.

>>>>> I haven't changed anytrhing for months in my computer (hardware).

>>>> You dont need to have done with a cap failure or the
>>>> failure that those 60gxp drives are notorious for.

>>> Is that common?

>> Is what common ?  Bad caps isnt that uncommon.

> Sorry, I meant the bad caps. Man, I have been a computer user since
> TI 99/4A and they sure don't make quality computers anymore. :(

It was a serious problem there for a while, basically some massive
brain fart by someone in taiwan that affected a hell of a lot of electronics.

Not just motherboards, I've seen it with Humax satellite TV STBs, seen
with most of the Humaxes I know about, just one cap in the power supply.

>> 60gxp drives dying was so common that it generated a class action suit.

>>> I noticed my last machine (not this one I mentioned)
>>> died because of my PSU (250 watts) was the borderline
>>> (it ran for almost a year without problems too), and decided
>>> to stop (heard it spin down and power off the machine).
>>> Then, the horrible odor (no smokes)

>> Thats just the power supply dying, not due to the rating.

>>> and my old Quantum HDD's controller died (wouldn't spin anymore).

>> Yeah, it isnt that uncommon for a PSU failure to
>> kill some of what is powered from it. It basically
>> over voltages some of the rails when dying.

>> Is that the same motherboard ?  You may just be
>> seeing a failure of the motherboard now. Over voltages
>> dont  necessarily kill things stone dead immediately.

> Nope, that motherboard totally die (wouldn't boot up and had burned
> marks) and out of warranty. So, I got a refurbished MSI KT4AV-L
> (Socket A/Socket 462; VIA KT400A) motherboard.

Bugger, there goes that theory.

Corse its possible that motherboard always did have a fault and
thats why it was refurbished and they never did resolve it properly.

>>>> They are called deathstars for a reason.
>>>> That produced a full class action suit.

>>> Is it too late for me to get my money back?

>> That wasnt the result of the class action suit.

>> The settlement only appears to apply to the 75GXP and the
>> settlement is the usual pathetic result in your case anyway.

> Rats. :(

Yeah, the only winners from class action suits are the legal parasites.

>> --------------------------------------
>> There are two categories of benefits with respect to each Qualifying
>> Deskstar 75 GXP, and each Class Member may request and is eligible
>> to receive only one of these categories of benefits. The categories
>> are: (1) all Class Members who purchased a Qualifying Deskstar 75GXP
>> and have experienced a ?disk drive failure? (an actual material
>> problem with its performance, as evidenced by a record either in (a)
>> IBM?s Technical Support Center database; (b) IBM?s Return Material
>> Authorization database; or (c) the ?IBM 75GXP? database maintained
>> by the Sheller Ludwig & Badey law firm as of February 15, 2005) and
>> meet the other Settlement eligibility criteria are eligible to
>> receive a check for $100; and (2) all Class Members who purchased a
>> Qualifying Deskstar 75GXP and have not experienced disk drive
>> failure are eligible to receive their choice of either 25 blank
>> CD-ROMs (with jewel cases) or a 15% Discount Certificate for a
>> future purchase at IBM.com.
>
>> --------------------------------------------
>>> I had it since 9/9/2001, but I don't think
>>> I have the receipt anymore (long gone).

>> Could be a problem, but its academic anyway
>> since the settlement is only for the 75GXP.

> Were 60 and 75 models identical with the symptoms,

Yes.

> failure rates, etc.?

Nope, the 60gxp failure rate wasnt as
utterly obscene as was seen with the 75gxp.

> I assume 75 is the newer and bigger model.

Nope, the reverse.


0
Rod
5/22/2006 7:32:28 AM
ANTant@zimage.com wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote
>> ANTant@zimage.com wrote
>>> Folkert Rienstra <see_reply-to@myweb.nl> wrote
>>>> <ANTant@zimage.com> wrote
>>>>>> <ANTant@zimage.com> wrote

>>>>> It did get really warm a few days ago, but
>>>>> the recent symptoms wasn't that warm.

>>>> Doesn't matter. The errors are introduced when the
>>>> power supply is marginal or temperature is high.

>>> Hmm, is there a way to check this?

>> Make sure the temperature and power are fine now and run
>> the hard drive manufacturer's diagnostic and do what quite
>> a few call a low level format and see what happens to the
>> SMART data. That will lose the data on the drive tho.

>> That should recheck all the sectors on the drive with writing.

>>> I only had this 500 watts Seasonic S12 PSU
>>> since 11/25/2005. Is it not powerful enough?

>> Very unlikely to no be powerful enough.

>>> Heat could be a thing. My small room can get over 85
>>> degrees(F) during heat waves (L.A. area) and my
>>> motherboard sensor says 112F and CPU says 151F.

>> What does the drive SMART temperature show then ?

> Well, it is cooler now (77 F degrees in my room;
> CPU: 61C/141F;
> Mobo: 42/107F).

> HD Tune says:
> 1. Quantum FireballP LM (15 GB) has no temperature sensors (probably too old)

Yep, they never had them.

> 2. IBM IC35L040AVER07-0 (41 GB) says 56C/132F

Urk thats very high with that room temp.

> 3. Seagate ST3120026A (120 GB) says 45C/113F

Thats a bit on the high side with that room temp too,
bet its pretty obscene with a room temp of say 30C/86F

>>> However, it didn't get that high recently
>>> (probably since October 2005).

>> See what the drive SMART temp data actually is
>> with a better SMART display, that drive looks like
>> its keeping the max temp ever seen in that value.

>>> I already have HDD coolers, extra case fans, etc.
>>> in this old full-tower ATX case (got it in 1998 I think).

>> The drive temp likely was fine.

Less clear on that now tho.

>> Starting to look like a motherboard problem if that was
>> the motherboard that was in the system when the previous
>> 250W PSU died. Likely it got killed by that failure.

> Actually, that was my other machine (Enlight 340 watts PSU after 250
> watts). This one (SeaSonic PSU) is using a refurbished ASUS K8V SE
> Deluxe (had to send in my original one because its BIOS firmware
> upgrade failed even though it said success!)..

OK.

>>>> It  can be quite some time before you run in to them if you don't
>>>> access the files they are in frequently or don't do surface scans often.

>>>> Once introduced, (write)errors stay, even if the system returns to
>>>> normal. These errors are corrected/disappear when the 'bad'
>>>> sectors are re/over-written.

>>> I am going to try more SpinRite tonight.
>>> So far, various disk utilites said no problems.

>> What does the full SMART scan show using
>> smartctl  from a knoppix bootable CD ?

> Crap, I forgot to run that, but I doubt it will tell me about Seagate
> drive which is a prime suspect to me. Again, I doubt I can get that
> information if SpinRite, HD Tune, etc. can't get the information.

I havent seen smartctl fail yet, be interesting to see.

>> If thats fine too, and that motherboard was the one used
>> when the 250W PSU died, very likely that motherboard
>> got damaged by the over voltage that killed the Quantum.

> See http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> that I haev two desktops. Don't get both mixxed up. :)

Yeah, I now realise that thats the one the ants use |-) 


0
Rod
5/22/2006 7:38:10 AM
ANTant@zimage.com wrote:
> In comp.sys.ibm.pc.hardware.storage Rod Speed
> <rod.speed.aaa@gmail.com> wrote:
>> ANTant@zimage.com wrote
>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>> ANTant@zimage.com wrote
>
>>>>> OK, I did more digging. I moved my page swap
>>>>> off the G: drive to E drive, but still had problems.
>
>>>> Fine.
>
>>>>> For the heck of it, I tried defragging on my I: drive and
>>>>> man I got lots of disk errors (timeouts, disconnected,
>>>>> freezes/pauses). I know it was a bad idea, but then it
>>>>> is my video HDD (already saw my TV shows).
>
>>>> That does suggest that it might be a problem outside the
>>>> drive, like motherboard/power supply/overheating etc.
>
>>>> In fact on a closer look, the drive temperature would be
>>>> worth checking with Everest, HDTune doesnt appear to
>>>> be showing it properly. Show the Seagate SMART data too.
>
>>>>> I think I am going to have to do disk test on
>>>>> this Seagate drive first outside of Windows.
>
>>>> And check the SMART data for that drive too.
>
>>> I don't think I can get the Seagate HDD's SMART sensor data
>>> due to the VIA SATA Controller. Even SpinRite can't show it.
>
>> smartctl from a knoppix bootable CD should be able to show it.
>
> Really. Are there any Windows programs or DOS programs that can do it
> too (if smartcl can do it)? I will have to check that out. I hope
> v4.0.2 can do it. I don't have 5.x since it is not publicly released
> yet.
>
>
>>> The reason for this setup is because I have three internal
>>> HDDs and two CD/DVD drives (one is a burner). Also,
>>> using the onboard Promise controller seems to fail to boot
>>> up my Windows XP 100% of the times (no idea why).
>
>> Maybe thats more evidence of the motherboard having
>> been zapped by the overvoltage seen when the 250W
>> PSU died and killed the Quantum hard drive, particularly
>> if that used to work before the PSU died.
>
> Uhh, that's the other computer. :) You're getting confused with my
> two machines:
> http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...
>
>
>>> It is like those external USB HDDs. No SMART sensor datas, etc.
>
>> Yeah, tho smartctl can usually see what
>> Everest cant see with internal drives.

> Interesting. I wonder why??

Its always been the controller the drive is on.

>>> Any ideas why controller does this?

>> I havent looked too closely at that, just use smartctl when
>> necessary.

> OK.
>
>
>>> Maybe this setup is a bad idea but then
>>> I didn't have this problem before last week!
>
>> Yeah, might be a workaround for a partially failed motherboard.
>
>>> <end of my reply>
>
>> <end of mine too>
>
> :) [again end of reply]

Ditto in spades |-)

>>>>> In alt.comp.periphs.hdd ANTant@zimage.com wrote:
>>>>>> I need some other opinions from you HDD experts since I don't
>>>>>> know about HDD issues. I would think it is dying, but I can't
>>>>>> seem to get the symptoms:
>>>>>
>>>>>> The last week, I noticed my Windows XP Pro. SP2 (all updates; VIA
>>>>>> 4in1 drivers) acting funny. I checked the event viewer logs and
>>>>>> saw:
>>>>>
>>>>>> Event Type:     Warning
>>>>>> Event Source:   Disk
>>>>>> Event Category: None
>>>>>> Event ID:       51
>>>>>> Date:           5/18/2006
>>>>>> Time:           10:00:04 PM
>>>>>> User:           N/A
>>>>>> Computer:       MyCompy
>>>>>> Description:
>>>>>> An error was detected on device \Device\Harddisk2\D during a
>>>>>> paging operation.For more information, see Help and Support
>>>>>> Center at http://go.microsoft.com/fwlink/events.asp.
>>>>>> Data:
>>>>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>>>>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>>>>>> 0010: 2d 01 00 00 00 00 00 00   -.......
>>>>>> 0018: 00 00 00 00 00 00 00 00   ........
>>>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>>>> 0028: 10 33 06 00 00 00 00 00   .3......
>>>>>> 0030: ff ff ff ff 03 00 00 00   ????....
>>>>>> 0038: 40 00 00 04 00 00 00 00   @.......
>>>>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>>>>>> 0048: 00 00 01 00 0a 00 00 00   ........
>>>>>> 0050: 00 00 00 00 a8 6f 3d 87   ....?o=?
>>>>>> 0058: 00 00 00 00 d0 99 45 87   ....??E?
>>>>>> 0060: 00 00 00 00 6e ff 93 0c   ....n??.
>>>>>> 0068: 2a 00 0c 93 ff 6e 00 00   *..??n..
>>>>>> 0070: 80 00 00 00 00 00 00 00   ?.......
>>>>>> 0078: 00 00 00 00 00 00 00 00   ........
>>>>>> 0080: 00 00 00 00 00 00 00 00   ........
>>>>>> 0088: 00 00 00 00 00 00 00 00   ........
>>>>>
>>>>>> Event Type:     Error
>>>>>> Event Source:   viamraid
>>>>>> Event Category: None
>>>>>> Event ID:       9
>>>>>> Date:           5/18/2006
>>>>>> Time:           10:00:04 PM
>>>>>> User:           N/A
>>>>>> Computer:       MyCompy
>>>>>> Description:
>>>>>> The device, \Device\Scsi\viamraid1, did not respond within the
>>>>>> timeout period.For more information, see Help and Support Center
>>>>>> at http://go.microsoft.com/fwlink/events.asp.
>>>>>> Data:
>>>>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>>>>>> 0008: 00 00 00 00 09 00 04 c0   .......?
>>>>>> 0010: 00 01 00 00 00 00 00 00   ........
>>>>>> 0018: 94 05 00 00 00 00 00 00   ?.......
>>>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>>>> 0028: 00 00 00 00 00 00 00 00   ........
>>>>>> 0030: 00 00 00 00 07 00 00 00   ........
>>>>>
>>>>>
>>>>>> Event Type:    Warning
>>>>>> Event Source:    Disk
>>>>>> Event Category:    None
>>>>>> Event ID:    51
>>>>>> Date:        5/17/2006
>>>>>> Time:        7:56:48 PM
>>>>>> User:        N/A
>>>>>> Computer:    MyCompy
>>>>>> Description:
>>>>>> An error was detected on device \Device\Harddisk2\D during a
>>>>>> paging operation.
>>>>>
>>>>>> For more information, see Help and Support Center at
>>>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>>> Data:
>>>>>> 0000: 04 00 68 00 01 00 b6 00   ..h...?.
>>>>>> 0008: 00 00 00 00 33 00 04 80   ....3..?
>>>>>> 0010: 2d 01 00 00 00 00 00 00   -.......
>>>>>> 0018: 00 00 00 00 00 00 00 00   ........
>>>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>>>> 0028: 53 97 54 00 00 00 00 00   S?T.....
>>>>>> 0030: ff ff ff ff 03 00 00 00   ????....
>>>>>> 0038: 40 00 00 04 00 00 00 00   @.......
>>>>>> 0040: ff 20 0a 12 80 03 20 40   ? ..?. @
>>>>>> 0048: 00 00 01 00 0a 00 00 00   ........
>>>>>> 0050: 00 00 00 00 68 46 55 87   ....hFU?
>>>>>> 0058: 00 00 00 00 a0 d2 30 87   .... ?0?
>>>>>> 0060: 00 00 00 00 16 55 e2 0a   .....U?.
>>>>>> 0068: 2a 00 0a e2 55 16 00 00   *..?U...
>>>>>> 0070: 80 00 00 00 00 00 00 00   ?.......
>>>>>> 0078: 00 00 00 00 00 00 00 00   ........
>>>>>> 0080: 00 00 00 00 00 00 00 00   ........
>>>>>> 0088: 00 00 00 00 00 00 00 00   ........
>>>>>
>>>>>> Event Type:    Error
>>>>>> Event Source:    viamraid
>>>>>> Event Category:    None
>>>>>> Event ID:    9
>>>>>> Date:        5/17/2006
>>>>>> Time:        7:56:48 PM
>>>>>> User:        N/A
>>>>>> Computer:    MyCompy
>>>>>> Description:
>>>>>> The device, \Device\Scsi\viamraid1, did not respond within the
>>>>>> timeout period.
>>>>>
>>>>>> For more information, see Help and Support Center at
>>>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>>> Data:
>>>>>> 0000: 0f 00 10 00 01 00 6a 00   ......j.
>>>>>> 0008: 00 00 00 00 09 00 04 c0   .......?
>>>>>> 0010: 00 01 00 00 00 00 00 00   ........
>>>>>> 0018: 38 00 00 00 00 00 00 00   8.......
>>>>>> 0020: 00 00 00 00 00 00 00 00   ........
>>>>>> 0028: 00 00 00 00 00 00 00 00   ........
>>>>>> 0030: 00 00 00 00 07 00 00 00   ........
>>>>>
>>>>>> Note: Yes, I have a paging file here.
>>>>>
>>>>>
>>>>>> HDD Tune v2.51 said on 5/18/2006 10:45 PM PDT:
>>>>>
>>>>>> HD Tune: IC35L040AVER07-0 Health
>>>>>
>>>>>> ID                              Current  Worst    ThresholdData
>>>>>> Status (01) Raw Read Error Rate        100      100      60
>>>>>> 65536     Ok (02) Throughput Performance     100      100      50
>>>>>> 0         Ok (03) Spin Up Time               113      113      24
>>>>>> 12910783  Ok (04) Start/Stop Count           100      100      0
>>>>>> 784       Ok (05) Reallocated Sector Count   100      100      5
>>>>>> 3         Ok (07) Seek Error Rate            100      100      67
>>>>>> 0         Ok (08) Seek Time Performance      100      100      20
>>>>>> 0         Ok (09) Power On Hours Count       99       99       0
>>>>>> 13487     Ok (0A) Spin Retry Count           100      100      60
>>>>>> 0         Ok (0C) Power Cycle Count          100      100      0
>>>>>> 740       Ok (C0) Power Off Retract Count    100      100      50
>>>>>> 784       Ok (C1) Load Cycle Count           100      100      50
>>>>>> 784       Ok (C2) Temperature                98       98       0
>>>>>> 1179704   Ok (C4) Reallocated Event Count    100      100      0
>>>>>> 3         Ok (C5) Current Pending Sector     100      100      0
>>>>>> 1         Ok (C6) Offline Uncorrectable      100      100      0
>>>>>> 0         Ok (C7) Ultra DMA CRC Error Count  200      200      0
>>>>>> 0         Ok
>>>>>
>>>>>> Power On Time         : 13487
>>>>>> Health Status         : Ok
>>>>>
>>>>>> Note: 05 was highlighted yellow.
>>>>>
>>>>>> --
>>>>>
>>>>>> Microsoft Windows XP [Version 5.1.2600]
>>>>>> (C) Copyright 1985-2001 Microsoft Corp.
>>>>>
>>>>>> C:\>chkdsk d:
>>>>>> The type of the file system is NTFS.
>>>>>> Volume label is AFA64-D.
>>>>>
>>>>>> WARNING!  F parameter not specified.
>>>>>> Running CHKDSK in read-only mode.
>>>>>
>>>>>> CHKDSK is verifying files (stage 1 of 3)...
>>>>>> File verification completed.
>>>>>> CHKDSK is verifying indexes (stage 2 of 3)...
>>>>>> Index verification completed.
>>>>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>>>>>> Security descriptor verification completed.
>>>>>
>>>>>>   10490412 KB total disk space.
>>>>>>    5964844 KB in 9376 files.
>>>>>>       3392 KB in 570 indexes.
>>>>>>          0 KB in bad sectors.
>>>>>>      30828 KB in use by the system.
>>>>>>       4096 KB occupied by the log file.
>>>>>>    4491348 KB available on disk.
>>>>>
>>>>>>       4096 bytes in each allocation unit.
>>>>>>    2622603 total allocation units on disk.
>>>>>>    1122837 allocation units available on disk.
>>>>>
>>>>>> C:\>chkdsk g:
>>>>>> The type of the file system is NTFS.
>>>>>> Volume label is AFA64-G.
>>>>>
>>>>>> WARNING!  F parameter not specified.
>>>>>> Running CHKDSK in read-only mode.
>>>>>
>>>>>> CHKDSK is verifying files (stage 1 of 3)...
>>>>>> File verification completed.
>>>>>> CHKDSK is verifying indexes (stage 2 of 3)...
>>>>>> Index verification completed.
>>>>>> CHKDSK is verifying security descriptors (stage 3 of 3)...
>>>>>> Security descriptor verification completed.
>>>>>
>>>>>>    9229308 KB total disk space.
>>>>>>    2797308 KB in 6018 files.
>>>>>>       2792 KB in 294 indexes.
>>>>>>          4 KB in bad sectors.
>>>>>>      27548 KB in use by the system.
>>>>>>       4096 KB occupied by the log file.
>>>>>>    6401656 KB available on disk.
>>>>>
>>>>>>       4096 bytes in each allocation unit.
>>>>>>    2307327 total allocation units on disk.
>>>>>>    1600414 allocation units available on disk.
>>>>>
>>>>>> Notes: This 4 KB was from last year (don't remember when
>>>>>> exactly). D and G: are two partitions on this
>>>>>> physical HDD.
>>>>>
>>>>>> My computer specifications can be found here:
>>>>>> http://alpha.zimage.com/~ant/antfarm/about/computers.txt (primary
>>>>>> one).
>>>>>
>>>>>> I ran chkdsk a few times outside and inside of Windows and ran HD
>>>>>> Tune's error scan, but found no new problems. Speed looked good
>>>>>> too.
>>>>>
>>>>>> Any ideas? Maybe I am not testing enough? Thank you in advance.
>>> o   o| |          Ant's Quality Foraged Links (AQFL):
>>> http://aqfl.net
>   \ _ /                        Please remove ANT if replying by
>    e-mail. ( ) 


0
Rod
5/22/2006 7:54:51 AM
In comp.sys.ibm.pc.hardware.storage Rod Speed <rod.speed.aaa@gmail.com> wrote:
> ANTant@zimage.com wrote
> > Rod Speed <rod.speed.aaa@gmail.com> wrote
> >> ANTant@zimage.com wrote
> >>> Folkert Rienstra <see_reply-to@myweb.nl> wrote
> >>>> <ANTant@zimage.com> wrote
> >>>>>> <ANTant@zimage.com> wrote

> >>>>> It did get really warm a few days ago, but
> >>>>> the recent symptoms wasn't that warm.

> >>>> Doesn't matter. The errors are introduced when the
> >>>> power supply is marginal or temperature is high.

> >>> Hmm, is there a way to check this?

> >> Make sure the temperature and power are fine now and run
> >> the hard drive manufacturer's diagnostic and do what quite
> >> a few call a low level format and see what happens to the
> >> SMART data. That will lose the data on the drive tho.

> >> That should recheck all the sectors on the drive with writing.

> >>> I only had this 500 watts Seasonic S12 PSU
> >>> since 11/25/2005. Is it not powerful enough?

> >> Very unlikely to no be powerful enough.

> >>> Heat could be a thing. My small room can get over 85
> >>> degrees(F) during heat waves (L.A. area) and my
> >>> motherboard sensor says 112F and CPU says 151F.

> >> What does the drive SMART temperature show then ?

> > Well, it is cooler now (77 F degrees in my room;
> > CPU: 61C/141F;
> > Mobo: 42/107F).

> > HD Tune says:
> > 1. Quantum FireballP LM (15 GB) has no temperature sensors (probably too old)

> Yep, they never had them.

> > 2. IBM IC35L040AVER07-0 (41 GB) says 56C/132F

> Urk thats very high with that room temp.

> > 3. Seagate ST3120026A (120 GB) says 45C/113F

> Thats a bit on the high side with that room temp too,
> bet its pretty obscene with a room temp of say 30C/86F

Yeah, it's hard to cool this upstair room (heat rises too). I can't seem to add more cooling unless I want to be 
crazy to do water/liquid cooling. :) But that won't happen. I am not that crazy nor do I want to maintain the 
computers that often.


> >>> However, it didn't get that high recently
> >>> (probably since October 2005).

> >> See what the drive SMART temp data actually is
> >> with a better SMART display, that drive looks like
> >> its keeping the max temp ever seen in that value.

> >>> I already have HDD coolers, extra case fans, etc.
> >>> in this old full-tower ATX case (got it in 1998 I think).

> >> The drive temp likely was fine.

> Less clear on that now tho.

> >> Starting to look like a motherboard problem if that was
> >> the motherboard that was in the system when the previous
> >> 250W PSU died. Likely it got killed by that failure.

> > Actually, that was my other machine (Enlight 340 watts PSU after 250
> > watts). This one (SeaSonic PSU) is using a refurbished ASUS K8V SE
> > Deluxe (had to send in my original one because its BIOS firmware
> > upgrade failed even though it said success!)..

> OK.

> >>>> It  can be quite some time before you run in to them if you don't
> >>>> access the files they are in frequently or don't do surface scans often.

> >>>> Once introduced, (write)errors stay, even if the system returns to
> >>>> normal. These errors are corrected/disappear when the 'bad'
> >>>> sectors are re/over-written.

> >>> I am going to try more SpinRite tonight.
> >>> So far, various disk utilites said no problems.

> >> What does the full SMART scan show using
> >> smartctl  from a knoppix bootable CD ?

> > Crap, I forgot to run that, but I doubt it will tell me about Seagate
> > drive which is a prime suspect to me. Again, I doubt I can get that
> > information if SpinRite, HD Tune, etc. can't get the information.

> I havent seen smartctl fail yet, be interesting to see.

> >> If thats fine too, and that motherboard was the one used
> >> when the 250W PSU died, very likely that motherboard
> >> got damaged by the over voltage that killed the Quantum.

> > See http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> > that I haev two desktops. Don't get both mixxed up. :)

> Yeah, I now realise that thats the one the ants use |-) 

Heh.
-- 
"Be thine enemy an ant, see in him an elephant." --Turkish Proverb
  /\___/\                                                    
 / /\ /\ \      Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |          Ant's Quality Foraged Links (AQFL): http://aqfl.net
   \ _ /                        Please remove ANT if replying by e-mail.
    ( )
0
ANTant
5/22/2006 8:08:35 AM
Reply: