Re: CHKDSK /F I'll be darned

On 9/10/21 5:15 PM, philo wrote:
> On 9/10/21 4:54 PM, Paul wrote:
>> philo wrote:
>>> I have a multi-drive machine and one has an XP drive that I rarely 
>>> use, but still I want it to be in good condition as there is one 
>>> piece of software that will not run on Win10.
>>> On each boot CHKDSK /F runs and *never* finds a problem.
>>>
>>>
>>> If that drive is in the machine and I run Win10, it too will run 
>>> CHKDSK /F on that XP drive.
>>>
>>>
>>> I suspect the drive itself has some defect so I cloned it to another 
>>> drive.
>>>
>>> Though it did run CHKDSK /F the first time, after that it behaved 
>>> normally so I plan to simply set the original drive aside.
>>>
>>> Just curious what could be wrong.
>>>
>>> I ran the Seagate short test and it found no problems nor had SMART 
>>> been tripped.
>>>
>>>
>>> I am now running the long test.
>>>
>>> There is also an option to run an acoustical test.
>>> What the heck is that?
>>>
>>> Might as well run that one too.
>>>
>>
>> I don't rely on the Windows 10 CHKDSK.
>>
>> I use the Windows 7 one, as a compromise between
>> the old and the new.
>>
>> Windows 7 CHKDSK tends to dwell (spend too much time on)
>> XATTR items. It might even be converting something Win10
>> specific into the nearest Win7 construct. On a WinXP drive,
>> I would not expect an excess of strange features, to trip up
>> the Windows 7 CHKDSK.
>>
>> Also, the CHKDSK on the installer DVD (troubleshooting, command
>> prompt), sometimes that has additional options. You need to
>> compare versions of CHKDSK for features. A couple of the
>> features I've located, make no sense, but, the CHKDSK run
>> does seem to have a different result (more thorough).
>>
>> I can't say I've exactly made a science out of this,
>> as all this version test is a bore.
>>
>>     Paul
> 
>



Ran Win7 (from a live utility cd) CHKDSK /F and it found a few 
"unidentified" files


Don't know what it did from them but all is well.

No more CHKDSK /F on startup


Thanks again Paul