Corrupt NTFS filesystem

[Rod Speed]

After getting corrupt NTFS volumes a couple times a day, including a
BSOD, I have gone a couple days with nothing going wrong. That's
because I used Perfect Disk to defrag both online and offline. I have
noticed this before. I expect in about 3-5 days I will begin seeing
the lone corruption followed in intensity by more and finally a BSOD
or two before I defrag again and it all stops for about a week.

What does that tell you about the cause of this?

Nothing much. Your description is as vague as always, but it looks like its
mostly varying with disk activity which isnt that surprising and not new info.

Doesnt provide any useful information about the two obvious
possibilitys, hardware problem or ****ed OS install.

The real test for those two possibilitys has been spelt out endlessly now.

 

[Citizen Bob]

After getting corrupt NTFS volumes a couple times a day, including a
BSOD, I have gone a couple days with nothing going wrong. That's
because I used Perfect Disk to defrag both online and offline. I have
noticed this before. I expect in about 3-5 days I will begin seeing
the lone corruption followed in intensity by more and finally a BSOD
or two before I defrag again and it all stops for about a week.

What does that tell you about the cause of this?

I have gone several days without any corruption. I have cycled all
three cloned disks. This is why I do not believe it's the removable
drive bays.

Here's what I did:

1) I changed the pagefile to 512MB/1500MB per Kony's recommendation.

2) I ran PerfectDisk defragment both online and offline. In the past
this has extended the period with no corruption.

3) I have run CHKDSK without the F several times each day.

4) I changed the signature on each clone with Win98SE fdisk/mbr. I
also deleted all the keys in HKLM/System/MountedDevices. Then I
Installed the "new device" when Win2K was rebooted.

That's it. Nothing else is different. I have run the same applications
I always run.

This does not mean that corruption won't occur sometime soon. But for
now there is absolutely no corruption whatsoever.


--

"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the world."
--Clarence Darrow

 

[Rod Speed]

(e-mail address removed) (Citizen Bob) wrote

I have gone several days without any corruption.

No new info, you've had that before.

I have cycled all three cloned disks. This is why
I do not believe it's the removable drive bays.

Thats a stupid way to test that possibility.

Here's what I did:

1) I changed the pagefile to 512MB/1500MB per Kony's recommendation.

It wont be that, its already FAR bigger than you
need and wont be what is corrupting the MFT.

2) I ran PerfectDisk defragment both online and offline.
In the past this has extended the period with no corruption.

You have previously claimed that you can get corruption
of the MFT just by running it. You cant have it both ways.

3) I have run CHKDSK without the F several times each day.

Presumably you mean that it doesnt report any problems.
Then you have confirmed that the corruption is occuring
at boot or shutdown time, except for the corruption you
claimed you produced by just running PD.

4) I changed the signature on each clone with Win98SE fdisk/mbr.
I also deleted all the keys in HKLM/System/MountedDevices.
Then I Installed the "new device" when Win2K was rebooted.

That's it. Nothing else is different. I have
run the same applications I always run.

We already know that the fault is intermittent.

This does not mean that corruption won't occur sometime soon.
But for now there is absolutely no corruption whatsoever.

Since you have gone that long without corruption in the past, that proves nothing.

You have to test intermittent faults more rigorously
than that, because they are intermittent.

You've now wasted FAR more time than it would have taken to
do the two basic tests that would at least distinguish between a
hardware problem and a ****ed OS install, running with the drive
directly connected and trying a clean install of XP on a spare
hard drive using the files and settings transfer wizard.

If you find that say the XP install works fine, you dont necessarily
have to use it, you can decide that you have the proof that its a
****ed OS install and put more time into a clean 2K install if you want.

 

[Citizen Bob]

I have gone several days without any corruption. I have cycled all
three cloned disks. This is why I do not believe it's the removable
drive bays.

Now it's Nov. 11, and still no corruption NTFS partition.

The only significant change I can think of was making the pagefile
smaller - 512MB/1.5GB.

I have cycled all three removable hard disks, so it is not the
removeable bays causing the problem. At least I avoided that merry
chase.

Why does a larger pagefile cause a corrupt NTFS volume? I still
believe its tied in with those two devices per hard disk partition.

I am a bit surprised that no one has been able to figure out what is
causing two devices to show up for each partition. It sounds like
something to do with mirroring. There is a special kind of mounting
scheme used for mirroring but I forgot its name. Maybe that's what's
going on - the partition is being used in this special way.


--

"First and last, it's a question of money. Those men who own the earth
make the laws to protect what they have. They fix up a sort of fence or
pen around what they have, and they fix the law so the fellow on the
outside cannot get in. The laws are really organized for the protection of
the men who rule the world. They were never organized or enforced to do
justice. We have no system for doing justice, not the slightest in the world."
--Clarence Darrow

 

[Rod Speed]

(e-mail address removed) (Citizen Bob) wrote

Now it's Nov. 11, and still no corruption NTFS partition.

Have you tried repeatedly using PD the way you used to
be able to produce corruption when JUST running that ?

The only significant change I can think of was
making the pagefile smaller - 512MB/1.5GB.

Very unlikely to have been due to that and even you should
be able to work out how to prove that now, by putting it back
to what it used to be when you were getting corruption.

I have cycled all three removable hard disks, so it
is not the removeable bays causing the problem.

You dont know that either. ALL you know is that is gone away for a week.

Not unusual with a hardware problem.

At least I avoided that merry chase.

You dont know that either.

Why does a larger pagefile cause a corrupt NTFS volume?

You dont know that it does and its completely trivial to prove whether its that.

I still believe its tied in with those two devices per hard disk partition.

Based on absolutely nothing, as always.

ALL you actually know is that those shouldnt be there.

I am a bit surprised that no one has been able to figure out
what is causing two devices to show up for each partition.

Hardly surprising if it was what that ****ed mirror hardware produced
when hardly anyone ever used that ****ed hardware approach.

It sounds like something to do with mirroring. There is a special kind
of mounting scheme used for mirroring but I forgot its name. Maybe
that's what's going on - the partition is being used in this special way.

And your nose was rubbed in how to prove if its that or not.

But you're such a terminal bone head that you wont do the obvious tests.