Corrupt NTFS filesystem

[Rod Speed]

You really are a pip, aren't you.

We'll see...

I have run chkdsk without "/f" many times
and every time it reports no corruption,

Then clearly the MFT isnt getting corrupted by normal ops, stupid.

Maybe the terminal stupidity of the 2G ram drive is the problem. Maybe
you've been stupid enough to setup a config which requires quite a bit of
work on the boot physical drive at shutdown time and the system is being
powered down before it completes properly or something.

There's only ONE way to work out what is producing the MFT
corruption, eliminate the possibilitys systematically, stupid.

Not a shred of rocket science required at all.

even when a reboot causes one.

Here is the typical report:

+++
The type of the file system is NTFS.
Volume label is System.

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

CHKDSK is verifying files (stage 1 of 3)...
0 percent completed.
1 percent completed.
[...]
100 percent completed.
File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...
0 percent completed.
1 percent completed.
[...]
100 percent completed.
Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...
0 percent completed.
1 percent completed.
[...]
100 percent completed.

Security descriptor verification completed.

78148160 KB total disk space.
23241212 KB in 32949 files.
10300 KB in 2834 indexes.
0 KB in bad sectors.
104564 KB in use by the system.
65536 KB occupied by the log file.
54792084 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
13698021 allocation units available on disk.
+++

 

[Citizen Bob]

Maybe the terminal stupidity of the 2G ram drive is the problem.

It was set at 1.5 GB until recently.

Microsoft states that the pagefile should be 3 times the size of RAM.
I have 1/2 GB of RAM. That has been amplified by many people who claim
to know Windows.

How do you figure that is stupid?


--

"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

 

[Citizen Bob]

Maybe the terminal stupidity of the 2G ram drive is the problem.

Once again it's all ad homs instead of constructive comments.

If you really believed that 2GB is the wrong size, you would have
explained why and made a recommendation. Instead you are dropping ad
homs like turds out of your mouth.



--

"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

 

[kony]

It was set at 1.5 GB until recently.

Microsoft states that the pagefile should be 3 times the size of RAM.
I have 1/2 GB of RAM. That has been amplified by many people who claim
to know Windows.

How do you figure that is stupid?

I don't know about stupid but perhaps misinformed... the
more physical memory you have, the less virtual pagefile
should be needed. 3 * physical memory might make sense if
someone were trying to run Win2k on only 64MB installed
physical memory but upwards of 512MB and more it's not
reasonable to expect to run jobs that might have 2GB total
physical + virtual, so 3 X is a big too much, even the
default that windows uses is only 1.5 X, IIRC.

There is not much need for 1.5GB pagefile with 512MB
physical memory. To page that much would take forever,
you're better off setting a more conservative number like
512MB fixed minimum and a max of 1.5GB (or more). IF you
found yourself frequently exceeding that 512MB figure,
setting it high as then seen necessary would reduce
fragmentation, but overall it's a bit pointless to try and
optimize a 512MB machine for closer to 1GB virtual memory
instead of upgrading the amount of physical memory installed
to more than 512MB.

.... or did I understand this wrong, it's not a 1.5GB
pagefile, rather a 1.5GB ramdrive?

Either way, the OS does support 1.5GB pagefile so if you
choose to do it, that should not account for your problems.

 

[Citizen Bob]

I have run chkdsk without "/f" many times and every time it reports no
corruption, even when a reboot causes chkdsk to run automatically.

Each time I ran chkdsk in the past I did not get a BSOD. This time,
however, I did get a BSOD upon reboot. And this time, in contrast to
all the other times, chkdsk without an F did report corruption in the
security descriptors.

This is the first time out of many times I have run chkdsk without an
F while Win2K was running that I finally trapped BSOD condition before
it happened.

Because the corrupt disk was unbootable I mounted it as D: and used
another disk to boot. Fortunately the corrupt volume did mount. Only
once in the past did it fail to mount and I had to restore a previous
"archive" clone from NTBackup.

In any event, here is the report from chkdsk with an F. This kind of
repair never happens when I don't get a BSOD for a corrupt disk. IOW,
this is major damage, and that must be why chkdsk without an F caught
it.

+++
The type of the file system is NTFS.
Volume label is System.

CHKDSK is verifying files (stage 1 of 3)...
0 percent completed.
Deleted corrupt attribute list entry
with type code 128 in file 9.
Deleting corrupt attribute record (128, $SDS)
from file record segment 1383.
1 percent completed.
[...]
100 percent completed.
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
0 percent completed.
[...]
100 percent completed.
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Repairing the security file record segment.
Deleting an index entry with Id 256 from index $SII of file 9.
Deleting an index entry with Id 277 from index $SII of file 9.
Deleting an index entry with Id 278 from index $SII of file 9.
Deleting an index entry with Id 279 from index $SII of file 9.
Deleting an index entry with Id 280 from index $SII of file 9.
Deleting an index entry with Id 281 from index $SII of file 9.
Deleting an index entry with Id 282 from index $SII of file 9.
Deleting an index entry with Id 283 from index $SII of file 9.
Deleting an index entry with Id 284 from index $SII of file 9.
Deleting an index entry with Id 285 from index $SII of file 9.
Deleting an index entry with Id 286 from index $SII of file 9.
Deleting an index entry with Id 287 from index $SII of file 9.
Deleting an index entry with Id 288 from index $SII of file 9.
Deleting an index entry with Id 289 from index $SII of file 9.
Deleting an index entry with Id 290 from index $SII of file 9.
Deleting an index entry with Id 291 from index $SII of file 9.
Deleting an index entry with Id 292 from index $SII of file 9.
Deleting an index entry with Id 293 from index $SII of file 9.
Deleting an index entry with Id 294 from index $SII of file 9.
Deleting an index entry with Id 295 from index $SII of file 9.
Deleting an index entry with Id 296 from index $SII of file 9.
Deleting an index entry with Id 297 from index $SII of file 9.
Deleting an index entry with Id 298 from index $SII of file 9.
Deleting an index entry with Id 299 from index $SII of file 9.
Deleting an index entry with Id 300 from index $SII of file 9.
Deleting an index entry with Id 301 from index $SII of file 9.
Deleting an index entry with Id 302 from index $SII of file 9.
Deleting an index entry with Id 303 from index $SII of file 9.
Deleting an index entry with Id 304 from index $SII of file 9.
Deleting an index entry with Id 305 from index $SII of file 9.
Deleting an index entry with Id 306 from index $SII of file 9.
Deleting an index entry with Id 307 from index $SII of file 9.
Deleting an index entry with Id 308 from index $SII of file 9.
Deleting an index entry with Id 309 from index $SII of file 9.
Deleting an index entry with Id 310 from index $SII of file 9.
Deleting an index entry with Id 311 from index $SII of file 9.
Deleting an index entry with Id 312 from index $SII of file 9.
Deleting an index entry with Id 313 from index $SII of file 9.
Deleting an index entry with Id 314 from index $SII of file 9.
Deleting an index entry with Id 315 from index $SII of file 9.
Deleting an index entry with Id 316 from index $SII of file 9.
Deleting an index entry with Id 317 from index $SII of file 9.
Deleting an index entry with Id 318 from index $SII of file 9.
Deleting an index entry with Id 319 from index $SII of file 9.
Deleting an index entry with Id 320 from index $SII of file 9.
Deleting an index entry with Id 321 from index $SII of file 9.
Deleting an index entry with Id 322 from index $SII of file 9.
Deleting an index entry with Id 323 from index $SII of file 9.
Deleting an index entry with Id 324 from index $SII of file 9.
Deleting an index entry with Id 325 from index $SII of file 9.
Deleting an index entry with Id 326 from index $SII of file 9.
Deleting an index entry with Id 327 from index $SII of file 9.
Deleting an index entry with Id 328 from index $SII of file 9.
Deleting an index entry with Id 329 from index $SII of file 9.
Deleting an index entry with Id 330 from index $SII of file 9.
Deleting an index entry with Id 331 from index $SII of file 9.
Deleting an index entry with Id 332 from index $SII of file 9.
Deleting an index entry with Id 333 from index $SII of file 9.
Deleting an index entry with Id 334 from index $SII of file 9.
Deleting an index entry with Id 335 from index $SII of file 9.
Deleting an index entry with Id 336 from index $SII of file 9.
Deleting an index entry with Id 337 from index $SII of file 9.
Deleting an index entry with Id 338 from index $SII of file 9.
Deleting an index entry with Id 339 from index $SII of file 9.
Deleting an index entry with Id 340 from index $SII of file 9.
Deleting an index entry with Id 341 from index $SII of file 9.
Deleting an index entry with Id 342 from index $SII of file 9.
Deleting an index entry with Id 343 from index $SII of file 9.
Deleting an index entry with Id 344 from index $SII of file 9.
Deleting an index entry with Id 345 from index $SII of file 9.
Deleting an index entry with Id 346 from index $SII of file 9.
Deleting an index entry with Id 347 from index $SII of file 9.
Deleting an index entry with Id 348 from index $SII of file 9.
Deleting an index entry with Id 349 from index $SII of file 9.
Deleting an index entry with Id 350 from index $SII of file 9.
Deleting an index entry with Id 351 from index $SII of file 9.
Deleting an index entry with Id 352 from index $SII of file 9.
Deleting an index entry with Id 353 from index $SII of file 9.
Deleting an index entry with Id 354 from index $SII of file 9.
Deleting an index entry with Id 355 from index $SII of file 9.
Deleting an index entry with Id 356 from index $SII of file 9.
Deleting an index entry with Id 357 from index $SII of file 9.
Deleting an index entry with Id 358 from index $SII of file 9.
Deleting an index entry with Id 359 from index $SII of file 9.
Deleting an index entry with Id 360 from index $SII of file 9.
Deleting an index entry with Id 361 from index $SII of file 9.
Deleting an index entry with Id 362 from index $SII of file 9.
Deleting an index entry with Id 363 from index $SII of file 9.
Deleting an index entry with Id 364 from index $SII of file 9.
Deleting an index entry with Id 365 from index $SII of file 9.
Deleting an index entry with Id 366 from index $SII of file 9.
Deleting an index entry with Id 367 from index $SII of file 9.
Deleting an index entry with Id 368 from index $SII of file 9.
Deleting an index entry with Id 369 from index $SII of file 9.
Deleting an index entry with Id 370 from index $SII of file 9.
Deleting an index entry with Id 371 from index $SII of file 9.
Deleting an index entry with Id 372 from index $SII of file 9.
Deleting an index entry with Id 373 from index $SII of file 9.
Deleting an index entry with Id 374 from index $SII of file 9.
Deleting an index entry with Id 375 from index $SII of file 9.
Deleting an index entry with Id 376 from index $SII of file 9.
Deleting an index entry with Id 377 from index $SII of file 9.
Deleting an index entry with Id 378 from index $SII of file 9.
Deleting an index entry with Id 379 from index $SII of file 9.
Deleting an index entry with Id 380 from index $SII of file 9.
Deleting an index entry with Id 381 from index $SII of file 9.
Deleting an index entry with Id 382 from index $SII of file 9.
Deleting an index entry with Id 383 from index $SII of file 9.
Deleting an index entry with Id 322 from index $SDH of file 9.
Deleting an index entry with Id 290 from index $SDH of file 9.
Deleting an index entry with Id 372 from index $SDH of file 9.
Deleting an index entry with Id 279 from index $SDH of file 9.
Deleting an index entry with Id 301 from index $SDH of file 9.
Deleting an index entry with Id 303 from index $SDH of file 9.
Deleting an index entry with Id 328 from index $SDH of file 9.
Deleting an index entry with Id 284 from index $SDH of file 9.
Deleting an index entry with Id 285 from index $SDH of file 9.
Deleting an index entry with Id 335 from index $SDH of file 9.
Deleting an index entry with Id 302 from index $SDH of file 9.
Deleting an index entry with Id 306 from index $SDH of file 9.
Deleting an index entry with Id 358 from index $SDH of file 9.
Deleting an index entry with Id 331 from index $SDH of file 9.
Deleting an index entry with Id 357 from index $SDH of file 9.
Deleting an index entry with Id 281 from index $SDH of file 9.
Deleting an index entry with Id 352 from index $SDH of file 9.
Deleting an index entry with Id 381 from index $SDH of file 9.
Deleting an index entry with Id 289 from index $SDH of file 9.
Deleting an index entry with Id 311 from index $SDH of file 9.
Deleting an index entry with Id 256 from index $SDH of file 9.
Deleting an index entry with Id 321 from index $SDH of file 9.
Deleting an index entry with Id 353 from index $SDH of file 9.
Deleting an index entry with Id 330 from index $SDH of file 9.
Deleting an index entry with Id 354 from index $SDH of file 9.
Deleting an index entry with Id 365 from index $SDH of file 9.
Deleting an index entry with Id 333 from index $SDH of file 9.
Deleting an index entry with Id 336 from index $SDH of file 9.
Deleting an index entry with Id 291 from index $SDH of file 9.
Deleting an index entry with Id 378 from index $SDH of file 9.
Deleting an index entry with Id 376 from index $SDH of file 9.
Deleting an index entry with Id 320 from index $SDH of file 9.
Deleting an index entry with Id 343 from index $SDH of file 9.
Deleting an index entry with Id 329 from index $SDH of file 9.
Deleting an index entry with Id 299 from index $SDH of file 9.
Deleting an index entry with Id 315 from index $SDH of file 9.
Deleting an index entry with Id 355 from index $SDH of file 9.
Deleting an index entry with Id 304 from index $SDH of file 9.
Deleting an index entry with Id 338 from index $SDH of file 9.
Deleting an index entry with Id 350 from index $SDH of file 9.
Deleting an index entry with Id 369 from index $SDH of file 9.
Deleting an index entry with Id 307 from index $SDH of file 9.
Deleting an index entry with Id 308 from index $SDH of file 9.
Deleting an index entry with Id 368 from index $SDH of file 9.
Deleting an index entry with Id 296 from index $SDH of file 9.
Deleting an index entry with Id 380 from index $SDH of file 9.
Deleting an index entry with Id 371 from index $SDH of file 9.
Deleting an index entry with Id 370 from index $SDH of file 9.
Deleting an index entry with Id 324 from index $SDH of file 9.
Deleting an index entry with Id 326 from index $SDH of file 9.
Deleting an index entry with Id 318 from index $SDH of file 9.
Deleting an index entry with Id 337 from index $SDH of file 9.
Deleting an index entry with Id 362 from index $SDH of file 9.
Deleting an index entry with Id 282 from index $SDH of file 9.
Deleting an index entry with Id 341 from index $SDH of file 9.
Deleting an index entry with Id 317 from index $SDH of file 9.
Deleting an index entry with Id 316 from index $SDH of file 9.
Deleting an index entry with Id 364 from index $SDH of file 9.
Deleting an index entry with Id 334 from index $SDH of file 9.
Deleting an index entry with Id 374 from index $SDH of file 9.
Deleting an index entry with Id 363 from index $SDH of file 9.
Deleting an index entry with Id 345 from index $SDH of file 9.
Deleting an index entry with Id 361 from index $SDH of file 9.
Deleting an index entry with Id 314 from index $SDH of file 9.
Deleting an index entry with Id 332 from index $SDH of file 9.
Deleting an index entry with Id 349 from index $SDH of file 9.
Deleting an index entry with Id 375 from index $SDH of file 9.
Deleting an index entry with Id 323 from index $SDH of file 9.
Deleting an index entry with Id 347 from index $SDH of file 9.
Deleting an index entry with Id 288 from index $SDH of file 9.
Deleting an index entry with Id 310 from index $SDH of file 9.
Deleting an index entry with Id 360 from index $SDH of file 9.
Deleting an index entry with Id 356 from index $SDH of file 9.
Deleting an index entry with Id 294 from index $SDH of file 9.
Deleting an index entry with Id 377 from index $SDH of file 9.
Deleting an index entry with Id 297 from index $SDH of file 9.
Deleting an index entry with Id 298 from index $SDH of file 9.
Deleting an index entry with Id 342 from index $SDH of file 9.
Deleting an index entry with Id 325 from index $SDH of file 9.
Deleting an index entry with Id 327 from index $SDH of file 9.
Deleting an index entry with Id 344 from index $SDH of file 9.
Deleting an index entry with Id 359 from index $SDH of file 9.
Deleting an index entry with Id 366 from index $SDH of file 9.
Deleting an index entry with Id 346 from index $SDH of file 9.
Deleting an index entry with Id 313 from index $SDH of file 9.
Deleting an index entry with Id 339 from index $SDH of file 9.
Deleting an index entry with Id 287 from index $SDH of file 9.
Deleting an index entry with Id 309 from index $SDH of file 9.
Deleting an index entry with Id 277 from index $SDH of file 9.
Deleting an index entry with Id 312 from index $SDH of file 9.
Deleting an index entry with Id 283 from index $SDH of file 9.
Deleting an index entry with Id 340 from index $SDH of file 9.
Deleting an index entry with Id 280 from index $SDH of file 9.
Deleting an index entry with Id 293 from index $SDH of file 9.
Deleting an index entry with Id 383 from index $SDH of file 9.
Deleting an index entry with Id 305 from index $SDH of file 9.
Deleting an index entry with Id 348 from index $SDH of file 9.
Deleting an index entry with Id 319 from index $SDH of file 9.
Deleting an index entry with Id 295 from index $SDH of file 9.
Deleting an index entry with Id 379 from index $SDH of file 9.
Deleting an index entry with Id 351 from index $SDH of file 9.
Deleting an index entry with Id 286 from index $SDH of file 9.
Deleting an index entry with Id 373 from index $SDH of file 9.
Deleting an index entry with Id 292 from index $SDH of file 9.
Deleting an index entry with Id 382 from index $SDH of file 9.
Deleting an index entry with Id 278 from index $SDH of file 9.
Deleting an index entry with Id 300 from index $SDH of file 9.
Deleting an index entry with Id 367 from index $SDH of file 9.
0 percent completed.
Replacing invalid security id with default security id for file 11.
1 percent completed.
Replacing invalid security id with default security id for file 674.
Replacing invalid security id with default security id for file 676.
Replacing invalid security id with default security id for file 677.
Replacing invalid security id with default security id for file 678.
Replacing invalid security id with default security id for file 679.
Replacing invalid security id with default security id for file 680.
Replacing invalid security id with default security id for file 681.
Replacing invalid security id with default security id for file 682.
Replacing invalid security id with default security id for file 683.
Replacing invalid security id with default security id for file 684.
Replacing invalid security id with default security id for file 685.
Replacing invalid security id with default security id for file 686.
Replacing invalid security id with default security id for file 687.
Replacing invalid security id with default security id for file 688.
Replacing invalid security id with default security id for file 689.
Replacing invalid security id with default security id for file 693.
Replacing invalid security id with default security id for file 695.
Replacing invalid security id with default security id for file 710.
Replacing invalid security id with default security id for file 711.
2 percent completed.
3 percent completed.
Replacing invalid security id with default security id for file 1286.
Replacing invalid security id with default security id for file 1287.
Replacing invalid security id with default security id for file 1288.
Replacing invalid security id with default security id for file 1289.
Replacing invalid security id with default security id for file 1290.
Replacing invalid security id with default security id for file 1291.
Replacing invalid security id with default security id for file 1292.
Replacing invalid security id with default security id for file 1293.
Replacing invalid security id with default security id for file 1295.
Replacing invalid security id with default security id for file 1297.
Replacing invalid security id with default security id for file 1298.
Replacing invalid security id with default security id for file 1300.
Replacing invalid security id with default security id for file 1301.
Replacing invalid security id with default security id for file 1303.
Replacing invalid security id with default security id for file 1304.
Replacing invalid security id with default security id for file 1306.
Replacing invalid security id with default security id for file 1307.
Replacing invalid security id with default security id for file 1308.
Replacing invalid security id with default security id for file 1310.
Replacing invalid security id with default security id for file 1311.
Replacing invalid security id with default security id for file 1312.
Replacing invalid security id with default security id for file 1313.
Replacing invalid security id with default security id for file 1348.
Replacing invalid security id with default security id for file 1349.
Replacing invalid security id with default security id for file 1350.
Replacing invalid security id with default security id for file 1351.
Replacing invalid security id with default security id for file 1352.
Replacing invalid security id with default security id for file 1353.
Replacing invalid security id with default security id for file 1354.
Replacing invalid security id with default security id for file 1355.
Replacing invalid security id with default security id for file 1356.
Replacing invalid security id with default security id for file 1357.
Replacing invalid security id with default security id for file 1360.
Replacing invalid security id with default security id for file 1361.
Replacing invalid security id with default security id for file 1364.
Replacing invalid security id with default security id for file 1365.
Replacing invalid security id with default security id for file 1366.
Replacing invalid security id with default security id for file 1367.
Replacing invalid security id with default security id for file 1368.
Replacing invalid security id with default security id for file 1369.
Replacing invalid security id with default security id for file 1370.
Replacing invalid security id with default security id for file 1371.
Replacing invalid security id with default security id for file 1372.
Replacing invalid security id with default security id for file 1373.
Replacing invalid security id with default security id for file 1374.
Replacing invalid security id with default security id for file 1375.
Replacing invalid security id with default security id for file 1376.
Replacing invalid security id with default security id for file 1378.
Replacing invalid security id with default security id for file 1379.
Replacing invalid security id with default security id for file 1380.
Replacing invalid security id with default security id for file 1381.
Replacing invalid security id with default security id for file 1382.
Replacing invalid security id with default security id for file 1384.
Replacing invalid security id with default security id for file 1385.
Replacing invalid security id with default security id for file 1386.
Replacing invalid security id with default security id for file 1387.
Replacing invalid security id with default security id for file 1388.
Replacing invalid security id with default security id for file 1391.
Replacing invalid security id with default security id for file 1392.
Replacing invalid security id with default security id for file 1393.
Replacing invalid security id with default security id for file 1397.
Replacing invalid security id with default security id for file 1398.
Replacing invalid security id with default security id for file 1399.
Replacing invalid security id with default security id for file 1400.
Replacing invalid security id with default security id for file 1401.
Replacing invalid security id with default security id for file 1402.
Replacing invalid security id with default security id for file 1407.
Replacing invalid security id with default security id for file 1409.
Replacing invalid security id with default security id for file 1414.
Replacing invalid security id with default security id for file 1420.
Replacing invalid security id with default security id for file 1421.
Replacing invalid security id with default security id for file 1422.
Replacing invalid security id with default security id for file 1427.
Replacing invalid security id with default security id for file 1432.
Replacing invalid security id with default security id for file 1434.
Replacing invalid security id with default security id for file 1435.
Replacing invalid security id with default security id for file 1436.
Replacing invalid security id with default security id for file 1437.
Replacing invalid security id with default security id for file 1438.
Replacing invalid security id with default security id for file 1440.
Replacing invalid security id with default security id for file 1441.
Replacing invalid security id with default security id for file 1443.
Replacing invalid security id with default security id for file 1445.
Replacing invalid security id with default security id for file 1446.
Replacing invalid security id with default security id for file 1447.
Replacing invalid security id with default security id for file 1448.
4 percent completed.
Replacing invalid security id with default security id for file 1450.
Replacing invalid security id with default security id for file 1451.
Replacing invalid security id with default security id for file 1452.
Replacing invalid security id with default security id for file 1453.
Replacing invalid security id with default security id for file 1454.
Replacing invalid security id with default security id for file 1455.
Replacing invalid security id with default security id for file 1456.
Replacing invalid security id with default security id for file 1457.
Replacing invalid security id with default security id for file 1458.
Replacing invalid security id with default security id for file 1459.
Replacing invalid security id with default security id for file 1460.
Replacing invalid security id with default security id for file 1461.
Replacing invalid security id with default security id for file 1462.
Replacing invalid security id with default security id for file 1464.
Replacing invalid security id with default security id for file 1465.
Replacing invalid security id with default security id for file 1466.
Replacing invalid security id with default security id for file 1467.
Replacing invalid security id with default security id for file 1468.
Replacing invalid security id with default security id for file 1469.
Replacing invalid security id with default security id for file 1470.
Replacing invalid security id with default security id for file 1471.
Replacing invalid security id with default security id for file 1472.
Replacing invalid security id with default security id for file 1473.
Replacing invalid security id with default security id for file 1474.
Replacing invalid security id with default security id for file 1475.
Replacing invalid security id with default security id for file 1476.
Replacing invalid security id with default security id for file 1477.
Replacing invalid security id with default security id for file 1478.
Replacing invalid security id with default security id for file 1479.
Replacing invalid security id with default security id for file 1481.
Replacing invalid security id with default security id for file 1482.
Replacing invalid security id with default security id for file 1485.
Replacing invalid security id with default security id for file 1486.
Replacing invalid security id with default security id for file 1487.
5 percent completed.
6 percent completed.
Replacing invalid security id with default security id for file 2284.
Replacing invalid security id with default security id for file 2285.
Replacing invalid security id with default security id for file 2289.
Replacing invalid security id with default security id for file 2292.
Replacing invalid security id with default security id for file 2293.
Replacing invalid security id with default security id for file 2294.
Replacing invalid security id with default security id for file 2295.
Replacing invalid security id with default security id for file 2298.
Replacing invalid security id with default security id for file 2299.
Replacing invalid security id with default security id for file 2300.
Replacing invalid security id with default security id for file 2331.
Replacing invalid security id with default security id for file 2381.
Replacing invalid security id with default security id for file 2382.
Replacing invalid security id with default security id for file 2435.
Replacing invalid security id with default security id for file 2465.
7 percent completed.
8 percent completed.
9 percent completed.
10 percent completed.
11 percent completed.
12 percent completed.
13 percent completed.
14 percent completed.
15 percent completed.
16 percent completed.
17 percent completed.
18 percent completed.
19 percent completed.
20 percent completed.
21 percent completed.
22 percent completed.
Replacing invalid security id with default security id for file 8160.
Replacing invalid security id with default security id for file 8165.
Replacing invalid security id with default security id for file 8259.
23 percent completed.
Replacing invalid security id with default security id for file 8387.
Replacing invalid security id with default security id for file 8398.
Replacing invalid security id with default security id for file 8403.
24 percent completed.
25 percent completed.
26 percent completed.
27 percent completed.
28 percent completed.
29 percent completed.
30 percent completed.
31 percent completed.
32 percent completed.
33 percent completed.
34 percent completed.
35 percent completed.
36 percent completed.
Replacing invalid security id with default security id for file 13173.
Replacing invalid security id with default security id for file 13174.
Replacing invalid security id with default security id for file 13175.
Replacing invalid security id with default security id for file 13176.
Replacing invalid security id with default security id for file 13177.
Replacing invalid security id with default security id for file 13178.
Replacing invalid security id with default security id for file 13179.
Replacing invalid security id with default security id for file 13180.
Replacing invalid security id with default security id for file 13181.
Replacing invalid security id with default security id for file 13182.
Replacing invalid security id with default security id for file 13183.
Replacing invalid security id with default security id for file 13184.
Replacing invalid security id with default security id for file 13185.
Replacing invalid security id with default security id for file 13186.
Replacing invalid security id with default security id for file 13187.
Replacing invalid security id with default security id for file 13188.
Replacing invalid security id with default security id for file 13189.
Replacing invalid security id with default security id for file 13190.
Replacing invalid security id with default security id for file 13191.
Replacing invalid security id with default security id for file 13192.
Replacing invalid security id with default security id for file 13193.
Replacing invalid security id with default security id for file 13194.
Replacing invalid security id with default security id for file 13195.
37 percent completed.
38 percent completed.
39 percent completed.
40 percent completed.
41 percent completed.
42 percent completed.
43 percent completed.
44 percent completed.
Replacing invalid security id with default security id for file 16088.
45 percent completed.
46 percent completed.
47 percent completed.
48 percent completed.
49 percent completed.
Replacing invalid security id with default security id for file 17761.
Replacing invalid security id with default security id for file 17848.
50 percent completed.
51 percent completed.
52 percent completed.
53 percent completed.
Replacing invalid security id with default security id for file 19459.
54 percent completed.
55 percent completed.
56 percent completed.
57 percent completed.
58 percent completed.
59 percent completed.
60 percent completed.
Replacing invalid security id with default security id for file 21860.
Replacing invalid security id with default security id for file 21893.
Replacing invalid security id with default security id for file 21925.
Replacing invalid security id with default security id for file 21942.
61 percent completed.
62 percent completed.
63 percent completed.
64 percent completed.
65 percent completed.
66 percent completed.
Replacing invalid security id with default security id for file 24249.
Replacing invalid security id with default security id for file 24251.
67 percent completed.
Replacing invalid security id with default security id for file 24264.
68 percent completed.
Replacing invalid security id with default security id for file 24636.
Replacing invalid security id with default security id for file 24663.
Replacing invalid security id with default security id for file 24664.
69 percent completed.
70 percent completed.
71 percent completed.
72 percent completed.
73 percent completed.
74 percent completed.
75 percent completed.
Replacing invalid security id with default security id for file 27518.
76 percent completed.
Replacing invalid security id with default security id for file 27528.
77 percent completed.
78 percent completed.
79 percent completed.
80 percent completed.
Replacing invalid security id with default security id for file 29012.
81 percent completed.
Replacing invalid security id with default security id for file 29532.
82 percent completed.
Replacing invalid security id with default security id for file 29703.
Replacing invalid security id with default security id for file 29704.
Replacing invalid security id with default security id for file 29705.
Replacing invalid security id with default security id for file 29706.
Replacing invalid security id with default security id for file 29707.
Replacing invalid security id with default security id for file 29708.
Replacing invalid security id with default security id for file 29709.
Replacing invalid security id with default security id for file 29710.
Replacing invalid security id with default security id for file 29719.
Replacing invalid security id with default security id for file 29720.
Replacing invalid security id with default security id for file 29722.
Replacing invalid security id with default security id for file 29983.
83 percent completed.
Replacing invalid security id with default security id for file 30060.
Replacing invalid security id with default security id for file 30298.
Replacing invalid security id with default security id for file 30299.
Replacing invalid security id with default security id for file 30300.
Replacing invalid security id with default security id for file 30301.
Replacing invalid security id with default security id for file 30302.
Replacing invalid security id with default security id for file 30303.
Replacing invalid security id with default security id for file 30304.
Replacing invalid security id with default security id for file 30329.
Replacing invalid security id with default security id for file 30341.
84 percent completed.
Replacing invalid security id with default security id for file 30493.
Replacing invalid security id with default security id for file 30496.
Replacing invalid security id with default security id for file 30513.
Replacing invalid security id with default security id for file 30639.
Replacing invalid security id with default security id for file 30640.
Replacing invalid security id with default security id for file 30641.
85 percent completed.
Replacing invalid security id with default security id for file 30905.
Replacing invalid security id with default security id for file 30907.
Replacing invalid security id with default security id for file 30910.
Replacing invalid security id with default security id for file 30911.
Replacing invalid security id with default security id for file 30941.
86 percent completed.
87 percent completed.
Replacing invalid security id with default security id for file 31639.
Replacing invalid security id with default security id for file 31675.
Replacing invalid security id with default security id for file 31676.
88 percent completed.
89 percent completed.
90 percent completed.
91 percent completed.
92 percent completed.
93 percent completed.
94 percent completed.
95 percent completed.
96 percent completed.
Replacing invalid security id with default security id for file 35060.
Replacing invalid security id with default security id for file 35071.
Replacing invalid security id with default security id for file 35077.
Replacing invalid security id with default security id for file 35078.
Replacing invalid security id with default security id for file 35079.
Replacing invalid security id with default security id for file 35080.
Replacing invalid security id with default security id for file 35081.
Replacing invalid security id with default security id for file 35082.
Replacing invalid security id with default security id for file 35083.
Replacing invalid security id with default security id for file 35084.
Replacing invalid security id with default security id for file 35085.
Replacing invalid security id with default security id for file 35086.
Replacing invalid security id with default security id for file 35087.
Replacing invalid security id with default security id for file 35088.
Replacing invalid security id with default security id for file 35089.
Replacing invalid security id with default security id for file 35090.
Replacing invalid security id with default security id for file 35091.
Replacing invalid security id with default security id for file 35092.
Replacing invalid security id with default security id for file 35093.
Replacing invalid security id with default security id for file 35094.
Replacing invalid security id with default security id for file 35095.
Replacing invalid security id with default security id for file 35096.
Replacing invalid security id with default security id for file 35097.
Replacing invalid security id with default security id for file 35098.
Replacing invalid security id with default security id for file 35099.
Replacing invalid security id with default security id for file 35100.
Replacing invalid security id with default security id for file 35101.
Replacing invalid security id with default security id for file 35102.
Replacing invalid security id with default security id for file 35103.
Replacing invalid security id with default security id for file 35104.
Replacing invalid security id with default security id for file 35105.
Replacing invalid security id with default security id for file 35106.
Replacing invalid security id with default security id for file 35107.
Replacing invalid security id with default security id for file 35108.
Replacing invalid security id with default security id for file 35109.
Replacing invalid security id with default security id for file 35110.
Replacing invalid security id with default security id for file 35111.
Replacing invalid security id with default security id for file 35112.
Replacing invalid security id with default security id for file 35113.
Replacing invalid security id with default security id for file 35114.
Replacing invalid security id with default security id for file 35115.
Replacing invalid security id with default security id for file 35116.
Replacing invalid security id with default security id for file 35117.
Replacing invalid security id with default security id for file 35118.
Replacing invalid security id with default security id for file 35119.
Replacing invalid security id with default security id for file 35121.
Replacing invalid security id with default security id for file 35122.
Replacing invalid security id with default security id for file 35123.
97 percent completed.
Replacing invalid security id with default security id for file 35124.
Replacing invalid security id with default security id for file 35125.
Replacing invalid security id with default security id for file 35126.
Replacing invalid security id with default security id for file 35127.
Replacing invalid security id with default security id for file 35128.
Replacing invalid security id with default security id for file 35129.
Replacing invalid security id with default security id for file 35130.
Replacing invalid security id with default security id for file 35131.
Replacing invalid security id with default security id for file 35132.
Replacing invalid security id with default security id for file 35133.
Replacing invalid security id with default security id for file 35134.
Replacing invalid security id with default security id for file 35139.
Replacing invalid security id with default security id for file 35158.
Replacing invalid security id with default security id for file 35165.
Replacing invalid security id with default security id for file 35166.
Replacing invalid security id with default security id for file 35170.
Replacing invalid security id with default security id for file 35172.
Replacing invalid security id with default security id for file 35173.
Replacing invalid security id with default security id for file 35174.
Replacing invalid security id with default security id for file 35176.
Replacing invalid security id with default security id for file 35177.
Replacing invalid security id with default security id for file 35178.
Replacing invalid security id with default security id for file 35179.
Replacing invalid security id with default security id for file 35180.
Replacing invalid security id with default security id for file 35183.
Replacing invalid security id with default security id for file 35184.
Replacing invalid security id with default security id for file 35185.
Replacing invalid security id with default security id for file 35186.
Replacing invalid security id with default security id for file 35187.
Replacing invalid security id with default security id for file 35188.
Replacing invalid security id with default security id for file 35189.
Replacing invalid security id with default security id for file 35190.
Replacing invalid security id with default security id for file 35192.
Replacing invalid security id with default security id for file 35193.
Replacing invalid security id with default security id for file 35195.
Replacing invalid security id with default security id for file 35196.
Replacing invalid security id with default security id for file 35197.
Replacing invalid security id with default security id for file 35198.
Replacing invalid security id with default security id for file 35203.
Replacing invalid security id with default security id for file 35204.
Replacing invalid security id with default security id for file 35206.
Replacing invalid security id with default security id for file 35207.
Replacing invalid security id with default security id for file 35214.
Replacing invalid security id with default security id for file 35215.
Replacing invalid security id with default security id for file 35216.
Replacing invalid security id with default security id for file 35217.
Replacing invalid security id with default security id for file 35218.
Replacing invalid security id with default security id for file 35219.
Replacing invalid security id with default security id for file 35220.
Replacing invalid security id with default security id for file 35221.
Replacing invalid security id with default security id for file 35222.
Replacing invalid security id with default security id for file 35223.
Replacing invalid security id with default security id for file 35224.
Replacing invalid security id with default security id for file 35225.
Replacing invalid security id with default security id for file 35226.
Replacing invalid security id with default security id for file 35227.
Replacing invalid security id with default security id for file 35228.
Replacing invalid security id with default security id for file 35229.
Replacing invalid security id with default security id for file 35230.
Replacing invalid security id with default security id for file 35231.
Replacing invalid security id with default security id for file 35232.
Replacing invalid security id with default security id for file 35233.
Replacing invalid security id with default security id for file 35234.
Replacing invalid security id with default security id for file 35235.
Replacing invalid security id with default security id for file 35239.
98 percent completed.
99 percent completed.
100 percent completed.
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

78148160 KB total disk space.
23880928 KB in 32965 files.
10312 KB in 2838 indexes.
0 KB in bad sectors.
104564 KB in use by the system.
65536 KB occupied by the log file.
54152356 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
13538089 allocation units available on disk.
+++
--

"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

 

[Citizen Bob]

... or did I understand this wrong, it's not a 1.5GB
pagefile, rather a 1.5GB ramdrive?

I said pagefile. I haven't used a ramdrive since the days of MS-DOS.

Either way, the OS does support 1.5GB pagefile so if you
choose to do it, that should not account for your problems.

That's what I thought.

I can lower the first part of the pagefile and see what happens. I
will use what you suggested: 512 MB/ 1.5 GB.

--

"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]

It was set at 1.5 GB until recently.

The difference is unlikely to be significant.

Microsoft states that the pagefile should be 3 times the size of RAM.

No they dont. And they certainly do not say that it should be in a ram drive.

I have 1/2 GB of RAM. That has been amplified
by many people who claim to know Windows.

'amplified' is meaningless in this context.

How do you figure that is stupid?

Its just plain barking mad to have that big a page file in physical
ram and MS certainly does NOT recommend that stupid config.

And even you should be able to test the normal config with
the page file on a physical drive and see if that makes any
difference to the MFT corruption now that you have said that
you can get MFT corruption when using ImPerfect Disk alone.

 

[Citizen Bob]

Each time I ran chkdsk in the past I did not get a BSOD. This time,
however, I did get a BSOD upon reboot. And this time, in contrast to
all the other times, chkdsk without an F did report corruption in the
security descriptors.

This is a followup to the BSOD I just reported.

I repaired the corrupt volume as you saw in the last post. Then I
booted it and it started just fine - no automatic chkdsk. I then ran
chkdsk without the F and it reported a corrupt MFT and recommended I
run chkdsk with an F. Here is the report:

+++
The type of the file system is NTFS.
Volume label is System.

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

CHKDSK is verifying files (stage 1 of 3)...
0 percent completed.
[...]
100 percent completed.
File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...
0 percent completed.
[...]
100 percent completed.
Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...
0 percent completed.
[...]
100 percent completed.
Security descriptor verification completed.

CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

78148160 KB total disk space.
23878164 KB in 32962 files.
10312 KB in 2837 indexes.
0 KB in bad sectors.
104564 KB in use by the system.
65536 KB occupied by the log file.
54155120 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
13538780 allocation units available on disk.
+++

I did just that and Win2K scheduled it for the next reboot. There was
no report of any "corrupt NTFS volume" in event viewer.

I then rebooted and chkdsk /f ran automatically at boot time, It did
not repair anything. When Win2K came up I checked the EV and there was
no record of any corrupt volume. I ran chkdsk again without an F and
it said everything is fine.

It would appear that Win2K repaired the corrupt disk when it reboot
before it automatically ran chkdsk at boot time.

This is getting very spooky.


--

"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]

Once again it's all ad homs instead of constructive comments.

Corse you never ever do anything like that yourself, eh ? Hypocrite.

If you really believed that 2GB is the wrong size,

I didnt say that.

you would have explained why

It should be obvious that putting the page file in a ram drive is a terminally
stupid approach and not something MS even suggests, let alone recommends.

and made a recommendation.

I did that, I recommended you try without that terminal stupidity
and see if it makes any difference to the MFT corruption.

Corse you arent actually interested in working out what is producing
the MFT corruption, you're only interested in personal attacks.

<reams of your puerile shit flushed where it belongs>

 

[Rod Speed]

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

Each time I ran chkdsk in the past I did not get a BSOD.

Not clear if you mean you ran it without the F or not. If you
ran it with the F, that conflicts with what you have previous
said, so presumably you mean you ran it without the F.

This time, however, I did get a BSOD upon reboot. And
this time, in contrast to all the other times, chkdsk without
an F did report corruption in the security descriptors.

This is the first time out of many times I have run
chkdsk without an F while Win2K was running that
I finally trapped BSOD condition before it happened.

OK, then its clear that whatever is producing the MFT corruption
is intermittent, and that makes it more likely its a hardware problem,
particularly when it cant be a particular app given that you can
produce MFT corruption by JUST running ImPerfect Disk and that
that is intermittent too, whether a PD run corrupts the MFT or not.

Because the corrupt disk was unbootable I mounted it as D:
and used another disk to boot. Fortunately the corrupt volume
did mount. Only once in the past did it fail to mount and I had
to restore a previous "archive" clone from NTBackup.

The fact that it did happen even once means that it can happen again.

In any event, here is the report from chkdsk with an F.
This kind of repair never happens when I don't get a
BSOD for a corrupt disk. IOW, this is major damage,
and that must be why chkdsk without an F caught it.

There isnt any evidence that chkdsk only reports
major damage when used without an F switch.

Have you actually done a binary comparison of the files
it claims to have fixed with the same file out of the archive ?

 

[Citizen Bob]

No they dont. And they certainly do not say that it should be in a ram drive.

Where are you getting this crap about a "ram drive".

Its just plain barking mad to have that big a page file in physical
ram and MS certainly does NOT recommend that stupid config.

Once again you demonstrate just how little you really know about
Windows. Read this and learn something.

http://support.microsoft.com/kb/555223/en-us

+++
Pagefile

RAM is a limited resource, whereas virtual memory is, for most
practical purposes, unlimited. There can be a large number of
processes each with its own 2 GB of private virtual address space.
When the memory in use by all the existing processes exceeds the
amount of RAM available, the operating system will move pages (4 KB
pieces) of one or more virtual address spaces to the computer’s hard
disk, thus freeing that RAM frame for other uses. In Windows systems,
these "paged out" pages are stored in one or more files called
pagefile.sys in the root of a partition. There can be one such file
in each disk partition. The location and size of the page file is
configured in SystemProperties, Advanced, Performance (click the
Settings button).

A frequently asked question is how big should I make the pagefile?
There is no single answer to this question, because it depends on the
amount of installed RAM and how much virtual memory that workload
requires. If there is no other information available,

***the normal recommendation of 1.5 times the amount of RAM in the
computer is a good place to start.***

On server systems, a common objective is to have enough RAM so that
there is never a shortage and the pagefile is essentially, not used.
On these systems, having a really large pagefile may serve no useful
purpose. On the other hand, disk space is usually plentiful, so aving
a large pagefile (e.g. 1.5 times the installed RAM) does not cause a
problem and eliminates the need to fuss over how large to make it.
+++

And even you should be able to test the normal config with
the page file on a physical drive and see if that makes any
difference to the MFT corruption now that you have said that
you can get MFT corruption when using ImPerfect Disk alone.

And even you should be able to read the Microsoft KB.


--

"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

 

[Citizen Bob]

This is a followup to the BSOD I just reported.

I repaired the corrupt volume as you saw in the last post. Then I
booted it and it started just fine - no automatic chkdsk. I then ran
chkdsk without the F and it reported a corrupt MFT and recommended I
run chkdsk with an F. Here is the report:

This is another followup to the above post.

I cloned the current drive with Acronis TI and then I ran Win98 fdisk
/mbr on the new clone to clear the first 4 bytes of the disk
signature. Then I booted the new clone and Win2K said there was a new
device and to reboot. The EV had the following:

+++
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 10/30/2006
Time: 3:10:35 PM
User: N/A
Computer: RCK
Description:
The following boot-start or system-start driver(s) failed to load:
PCLEPCI
+++

After I rebooted as instructed by Win2K, there was no further
reference in EV about any PCLEPCI. Apparently when Win2K tries to load
a new device, it screws up PCLEPCI.


--

"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]

Where are you getting this crap about a "ram drive".

You said

http://groups.google.com/group/alt.comp.hardware/msg/c8ae14937b12957a

Once again you demonstrate just how little you really know about Windows.

We'll see, again...

Read this and learn something.

http://support.microsoft.com/kb/555223/en-us

+++
Pagefile

RAM is a limited resource, whereas virtual memory is, for most
practical purposes, unlimited. There can be a large number of
processes each with its own 2 GB of private virtual address space.
When the memory in use by all the existing processes exceeds the
amount of RAM available, the operating system will move pages (4 KB
pieces) of one or more virtual address spaces to the computer’s hard
disk, thus freeing that RAM frame for other uses. In Windows systems,
these "paged out" pages are stored in one or more files called
pagefile.sys in the root of a partition. There can be one such file
in each disk partition. The location and size of the page file is
configured in SystemProperties, Advanced, Performance (click the
Settings button).

A frequently asked question is how big should I make the pagefile?
There is no single answer to this question, because it depends on the
amount of installed RAM and how much virtual memory that workload
requires.

So much for your stupid pig ignorant claim that MS actually says
to have the page file 3 times bigger than the amount of physical ram.

If there is no other information available,

You cant ignore that, stupid.

***the normal recommendation of 1.5 times the amount
of RAM in the computer is a good place to start.***

Doesnt even say that stupid 3 times you claim.

On server systems, a common objective is to have
enough RAM so that there is never a shortage and
the pagefile is essentially, not used. On these systems,
having a really large pagefile may serve no useful purpose.

Funny that.

On the other hand, disk space is usually plentiful, so aving a large
pagefile (e.g. 1.5 times the installed RAM) does not cause a
problem and eliminates the need to fuss over how large to make it.
+++

Nothing even remotely resembling anything like what you pig
ignorantly claimed about what MS says to have page file wise.

AND your stupid pig ignorant claim about THREE TIMES doesnt even get a mention.

And even you should be able to read the Microsoft KB.

Yep, pity it doesnt say anything even remotely resembling
anything like that lie of yours now right at the top.

 

[Citizen Bob]

Doesnt even say that stupid 3 times you claim.

Picky, picky.


--

"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]

Picky, picky.

Pathetic, pathetic.

Never ever could bullshit its way out of a wet paper bag.

 

[Citizen Bob]

Pathetic, pathetic.

It says "good place to start". Every good engineer knows to double
minimum specifications to include a margin for error.

Never ever could bullshit its way out of a wet paper bag.

<yawn>

--

"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

 

[Citizen Bob]

On Mon, 30 Oct 2006 15:27:22 GMT, (e-mail address removed) (Citizen Bob) wrote:

He's so stupid that he cant even manage to work out what
chkdsk is about and how to check whether corruption of the MFT
is actually happening at other than boot time or shutdown time.

You really are a stupid bonehead, aren't you.

I just ran chkdsk without an F inside Win2K, and it reported NO
problems whatsoever. EV did not show any problems either.

I then rebooted and Win2K automatically ran chkdsk with an F during
the boot process. There were some security descripters that were
repaired but nowhere near the number that typically get repaired when
I get a BSOD. There was no repair of the MFT or anything else.

Once I was in Win2K (the repair was successful) EV showed a corrupt
NTFS volume had occurred between shutdown and reboot.

So much for running chkdsk without an F. It is worthless, as I had
determined before. But you insisted I do it, so maybe now you have
learned more about Windows at my expense.

Next time listen to me. Enough of the merry chases - if you don't know
how to fix this problem, then admit it. Maybe then you will use your
analytical skills to look at the data I am providing instead of
indulging your considerable prejudices.


--

"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]

It says "good place to start".

It ACTUALLY says

IF THERE IS NO OTHER INFORMATION AVAILABLE

you pathological liar/pathetic excuse for a lying bullshit artist.

In fact we know that with Win2K with 512MB of physical
ram, you dont need anything like 2G of page file, or 1.5G
either, and its completely trivial for anyone with a clue to
check how much of the page file is actually used by that
system and discover that its nothing like 2G, or 1.5G either.

AND in the next para it ALSO says

On server systems, a common objective is to have enough RAM so
that there is never a shortage and the pagefile is essentially, not used.
On these systems, having a really large pagefile may serve no useful purpose.

Corse you are such a bone head that you cant manage to read and
comprehend such simple advice, or even consider the basics for yourself,
that the more physical ram you have, the LESS page file you need.

It may make some sense to initially try a page of 1.5 times the
physical ram with a 64M Win2K system, but it makes absolutely no
sense whatever to have a 2G page file with 512MB of physical ram.

Every good engineer knows to double minimum
specifications to include a margin for error.

Pity it isnt even the minimum specification,
you pathetic excuse for a bullshit artist.

No wonder you got the bums rush.

 

[Rod Speed]

You really are a stupid bonehead, aren't you.

Cant even manage its own lines, or anything else at all, either.

I just ran chkdsk without an F inside Win2K, and it reported NO
problems whatsoever. EV did not show any problems either.

And that indicates that the corruption didnt
occur with normal ops at that time, stupid.

I then rebooted and Win2K automatically ran chkdsk with an F during
the boot process. There were some security descripters that were
repaired but nowhere near the number that typically get repaired
when I get a BSOD. There was no repair of the MFT or anything else.

And that indicates that either the shutdown or the boot
process may well have been what corrupted the MFT, stupid.

Once I was in Win2K (the repair was successful) EV showed a
corrupt NTFS volume had occurred between shutdown and reboot.

Must be one of those rocket scientist stupids.

So much for running chkdsk without an F. It is worthless,

Pity you stupidly claimed that it wasnt possible to run chkdsk to
determine whether corruption was occurring during normal ops or
whether it was occuring during shutdown or boot. YOU WERE WRONG.

as I had determined before.

Lying, as always.

But you insisted I do it,

Lying, as always. I JUST RUBBED YOU NOSE IN THE FACT THAT
YOUR CLAIM THAT IT WASNT POSSIBLE TO RUN CHKDSK AT
OTHER THAN BOOT TIME WAS CLEARLY JUST PLAIN WRONG.

so maybe now you have learned more about Windows at my expense.

Never ever could bullshit its way out of a wet paper bag.

Next time listen to me.

No way, you're so stupid that you couldnt even manage to work out how
to run chkdsk at other than boot time to see if the MFT gets corrupted at
other than reboot time and you're so stupid that you cant even manage to
work out that the only viable option when you terminal stupidity is exposed
for the world to laugh at, that the only viable option is to keep your silly trap
shut and hope that everyone forgets that terminal stupidity as quickly as possible.

Enough of the merry chases - if you don't know how to fix this problem, then admit it.

I do know how to systematically eliminate the possibiltys on what is
corrupting the MFT thanks, and I also know what is the most efficient
sequence to test, first starting with the test that require minimal effort.

You're so stupid and bone headed that you cant manage something
as basic as that ? YOUR problem. You're the one that will have to
spend the next year or two manually fixing the corruption that you
claim happens every week and the high level of backups by cloning that
you need to do when the MFT is getting corrupted at that rate.

Maybe then you will use your analytical skills to look at the data
I am providing instead of indulging your considerable prejudices.

There are no magic wands to wave with the pathetically inadequate
description of the config of your system. The only viable option is to
systematically eliminate the possibilitys, and even someone as stupid
as you should be able to grasp that 3 of those WILL TAKE MUCH
LESS EFFORT THE STUPID APPROACH YOU HAVE CHOSEN
TO TAKE FOR A WHOLE YEAR NOW TO KLUDGE AROUND
THAT VERY FUNDAMENTAL PROBLEM YOU HAVE.

No wonder you got the bums rush, even they noticed how useless you are.

 

[Citizen Bob]

And that indicates that either the shutdown or the boot
process may well have been what corrupted the MFT, stupid.

That's what I said earlier.

Pity you stupidly claimed that it wasnt possible to run chkdsk to
determine whether corruption was occurring during normal ops or
whether it was occuring during shutdown or boot. YOU WERE WRONG.

I just told you that running chkdsk without an F is useless because it
gives false information. I gave you one example of how it says that
the volume is corrupt yet it wasnt, and one example of how it says the
volume is not corrupt yet it is when I rebooted.

Therefore "it wasnt possible to run chkdsk to determine whether
corruption was occurring during normal ops"

Lying, as always. I JUST RUBBED YOU NOSE

That's why you deliberately distort what I say. You do not have a
desire to help, you just like "rubbing my nose" into your
misinterpretations of what I say.

I never said you can't run chkdsk other than boot time. I said you
can't run chkdsk with an F to determine whether there is a corrupt
disk when Win2K is running. You need to pay closer attention to what I
say.

No way, you're so stupid that you couldnt even manage to work out how
to run chkdsk at other than boot time to see if the MFT gets corrupted at
other than reboot time

I just showed you that running chkdsk other than at boot time will not
tell you if the MFT gets corrupted.

No wonder you got the bums rush, even they noticed how useless you are.

Once again you do not know what you are talking about.

When I bought the Enermax DynaBacker I asked the head of tech support
whether Directron knew if it would work properly. He said it was a new
product for Directron, so I told him to include a clause in my invoice
that stipulated that I could return it for a full cash refund anytime
within 1 year, which is the normal Directron warranty period.

When I started getting corrupt NTFS volumes with the DynaBacker I
contacted the Product Line Manager (PLM) at Enermax in California, who
is the importer/distributor. He told me to contact the PLM at Enermax
in Taiwan. He also gave me the link to the website of the OEM who
makes the unit, a company also in Taiwan not affiliated with Enermax.

I contacted the PLM at Enermax in Taiwan and she told me she was
involved with the development of the unit. She told me that she was
going to take the information I gave her and fix the problem. In the
meantime I took a look at the OEM's website and saw that it was the
company who developed the unit. The software on the website was
identical to the software that came with the unit. I wrote them twice
but no one responded.

Then after several exchanges of information with the PLM at Enermax
Taiwan she informs me that they are not going to fix anything. That
was the last I heard from her. I called Enermax in California and
talked to the Sales Manager and he told me I could return the unit.

I then called the head of tech support at Directron and he in turn
called Enermax California. Then he called me and advised me to return
the unit for a full cash refund because he found out that Enermax is
thinking about dropping the product. I returned the unit and got a
full refund.

Later I discovered that Directron dropped the unit from its product
offering, that Enermax California also dropped the unit from its
product offering, and that Enermax Taiwan also dropped the unit from
its product offering and that the OEM website disappeared altogether.

So much for getting the bum's rush. No such thing happened.

You have lost all credibility.




--

"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