CHKDSK is verifying files (stage 1 of 3)
File record segment 7372 is unreadable.
Errors found.

Concurrently, I'm getting the same flash player error again.
Unfortunately, this time using Adobe's uninstall routine is not
correcting the problem. Using Firefox 8.0.1. Last time it seemed
to have been something to do with upgrading Firefox. But then, now
there is the SDD CHKDSK disk error.

I don't understand the CHKDSK error, but I'm not confident that
hardware is at fault. The SDD drive SMART shows no errors.
Apparently it's Adobe flash player related (plugin-container.exe),
but I suppose it could have to do with the SDD drive as well. One
and/or the other seems to be at fault.

I might try one of the suggestions in a much more recent thread,
to update the SDD firmware. Or I will revert back to a Firefox 3
install, my prior (next recent) copy of Windows, I just upgraded
to Firefox 8. A third possibility is to ditch the SDD and reinsert
the Western Digital Raptor as primary drive.

First things first, make fresh backups...

I meant "SSD".

Also... Macrium Reflect reports an error when trying to copy
Windows. But recently that has been resolved somehow, too busy to
remember how.



--
FWIW. Constructive comments are welcome, but I am not necessarily
asking for help at this time. Recording this partly to help with
accurate troubleshooting of what might be a difficult system
problem (as in "maybe SSD drives are fishy").

> CHKDSK is verifying files (stage 1 of 3)
> File record segment 7372 is unreadable.
> Errors found.

So I booted to the Macrium Reflect CD and restored a prior copy of
Windows. And the (SSD) CHKDSK error is gone. I guess that suggests it
was not a hardware problem. Weird IMO.

John Doe <(E-Mail Removed)> wrote in news:4ef5883d$0$22275$c3e8da3
$(E-Mail Removed):

>> CHKDSK is verifying files (stage 1 of 3)
>> File record segment 7372 is unreadable.
>> Errors found.
>
> So I booted to the Macrium Reflect CD and restored a prior copy of
> Windows. And the (SSD) CHKDSK error is gone. I guess that suggests it
> was not a hardware problem. Weird IMO.
>

No, it suggests that the disk segment is currently unused.
You have a timebomb waiting to go off.

Sjouke Burry <s b> wrote:

> John Doe <jdoe usenetlove.invalid> wrote

>>> CHKDSK is verifying files (stage 1 of 3)
>>> File record segment 7372 is unreadable.
>>> Errors found.
>>
>> So I booted to the Macrium Reflect CD and restored a prior copy
>> of Windows. And the (SSD) CHKDSK error is gone. I guess that
>> suggests it was not a hardware problem. Weird IMO.
>>
>
> No, it suggests that the disk segment is currently unused. You
> have a timebomb waiting to go off.

31262458 KB total disk space.
31124644 KB in 41851 files.
12344 KB in 5544 indexes.
0 KB in bad sectors.
122658 KB in use by the system.
65536 KB occupied by the log file.
2812 KB available on disk.

4096 bytes in each allocation unit.
7815614 total allocation units on disk.
703 allocation units available on disk.





--
Use a fixed size font for proper viewing.

On 24 Dec 2011 18:01:19 GMT, John Doe <(E-Mail Removed)> wrote:

>Sjouke Burry <s b> wrote:
>
>> John Doe <jdoe usenetlove.invalid> wrote
>
>>>> CHKDSK is verifying files (stage 1 of 3)
>>>> File record segment 7372 is unreadable.
>>>> Errors found.
>>>
>>> So I booted to the Macrium Reflect CD and restored a prior copy
>>> of Windows. And the (SSD) CHKDSK error is gone. I guess that
>>> suggests it was not a hardware problem. Weird IMO.
>>>
>>
>> No, it suggests that the disk segment is currently unused. You
>> have a timebomb waiting to go off.
>
>31262458 KB total disk space.
>31124644 KB in 41851 files.
> 12344 KB in 5544 indexes.
> 0 KB in bad sectors.
> 122658 KB in use by the system.
> 65536 KB occupied by the log file.
> 2812 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 7815614 total allocation units on disk.
> 703 allocation units available on disk.

So the bad sector isn't marked as such. Do a surface test and see
what happens.

On Sat, 24 Dec 2011 08:07:25 +0000, John Doe rearranged some electrons to
say:

>> CHKDSK is verifying files (stage 1 of 3)
>> File record segment 7372 is unreadable. Errors found.
>
> So I booted to the Macrium Reflect CD and restored a prior copy of
> Windows. And the (SSD) CHKDSK error is gone. I guess that suggests it
> was not a hardware problem. Weird IMO.

Not necessarily. If your SSD has a bad bit on it, you may have just not
written to it when you restored the drive. It may show up again if you
try to write to that particular spot in the future.

david <none nospam.com> wrote:

> John Doe rearranged some electrons to say:
>
>>> CHKDSK is verifying files (stage 1 of 3) File record segment
>>> 7372 is unreadable. Errors found.
>>
>> So I booted to the Macrium Reflect CD and restored a prior copy
>> of Windows. And the (SSD) CHKDSK error is gone. I guess that
>> suggests it was not a hardware problem. Weird IMO.
>
> Not necessarily. If your SSD has a bad bit on it, you may have
> just not written to it when you restored the drive. It may show
> up again if you try to write to that particular spot in the
> future.

31262458 KB total disk space.
31124644 KB in 41851 files.
12344 KB in 5544 indexes.
0 KB in bad sectors.
122658 KB in use by the system.
65536 KB occupied by the log file.
2812 KB available on disk.

4096 bytes in each allocation unit.
7815614 total allocation units on disk.
703 allocation units available on disk.





--
Use a fixed size font for proper viewing.

Loren Pechtel <lorenpechtel hotmail.com> wrote:

> John Doe <jdoe usenetlove.invalid> wrote:
>> Sjouke Burry <s b> wrote:
>>> John Doe <jdoe usenetlove.invalid> wrote
>>
>>>>> CHKDSK is verifying files (stage 1 of 3) File record segment
>>>>> 7372 is unreadable. Errors found.
>>>>
>>>> So I booted to the Macrium Reflect CD and restored a prior
>>>> copy of Windows. And the (SSD) CHKDSK error is gone. I guess
>>>> that suggests it was not a hardware problem. Weird IMO.
>>>>
>>>
>>> No, it suggests that the disk segment is currently unused. You
>>> have a timebomb waiting to go off.
>>
>>31262458 KB total disk space. 31124644 KB in 41851 files.
>> 12344 KB in 5544 indexes.
>> 0 KB in bad sectors.
>> 122658 KB in use by the system.
>> 65536 KB occupied by the log file.
>> 2812 KB available on disk.
>>
>> 4096 bytes in each allocation unit.
>> 7815614 total allocation units on disk.
>> 703 allocation units available on disk.
>
> So the bad sector isn't marked as such. Do a surface test and
> see what happens.

Nothing catastrophic has happened, but had some weird system
behavior and another disk error popped up (at least three so far).
Disconnected the SDD and used Macrium Reflect to put windows back
on my Raptor. Oh well, apparently another OCZ Vertex SDD bites the
dust.

Before buying another SDD, will pay attention to whether improper
shutdown (hard reset, whatever) can damage it.

After noticing the first CHKDSK errors, I re-applied the most
current firmware. The behavior is fishy. Conceivably, it could
need a firmware upgrade, one that they haven't supplied.

"TimDrouillard" <(E-Mail Removed)> wrote:

> Before replacing the SSD, visit the manufactures web site and look for a
> firmware upgrade.
>
> I have a Crucial M4 SSD that started disappearing from the systems after
> about 20min use, and I was ready to replace it with a new SSD, but a quick
> trip to their web site showed it was a know issue and they had a
> non-destructive firmware upgrade that solved the problem.
>
> I've had earlier Vertexes that needed firmware upgrades as well.
>
>
> "John Doe" wrote in message
> news:4f245161$0$396$c3e8da3$(E-Mail Removed)...
>
> Loren Pechtel <lorenpechtel hotmail.com> wrote:
>
>> John Doe <jdoe usenetlove.invalid> wrote:
>>> Sjouke Burry <s b> wrote:
>>>> John Doe <jdoe usenetlove.invalid> wrote
>>>
>>>>>> CHKDSK is verifying files (stage 1 of 3) File record segment
>>>>>> 7372 is unreadable. Errors found.
>>>>>
>>>>> So I booted to the Macrium Reflect CD and restored a prior
>>>>> copy of Windows. And the (SSD) CHKDSK error is gone. I guess
>>>>> that suggests it was not a hardware problem. Weird IMO.
>>>>>
>>>>
>>>> No, it suggests that the disk segment is currently unused. You
>>>> have a timebomb waiting to go off.
>>>
>>>31262458 KB total disk space. 31124644 KB in 41851 files.
>>> 12344 KB in 5544 indexes.
>>> 0 KB in bad sectors.
>>> 122658 KB in use by the system.
>>> 65536 KB occupied by the log file.
>>> 2812 KB available on disk.
>>>
>>> 4096 bytes in each allocation unit.
>>> 7815614 total allocation units on disk.
>>> 703 allocation units available on disk.
>>
>> So the bad sector isn't marked as such. Do a surface test and
>> see what happens.
>
> Nothing catastrophic has happened, but had some weird system
> behavior and another disk error popped up (at least three so far).
> Disconnected the SDD and used Macrium Reflect to put windows back
> on my Raptor. Oh well, apparently another OCZ Vertex SDD bites the
> dust.
>
> Before buying another SDD, will pay attention to whether improper
> shutdown (hard reset, whatever) can damage it.
>
>