| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 65299 | 2006-01-13 10:24:00 | help needed with hard drive - what have I done?? | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 420747 | 2006-01-14 23:34:00 | Dont worry your not the only one that had to reinstall windows after a linux installation. I had to reinstall windows 3 times ;) | Prescott (11) | ||
| 420748 | 2006-01-15 05:42:00 | According to this site Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. This is a known issue and the error messages are not actually means that there is problem in your system. You can safely ignore the error messages. The reason you are seeing these errors appear is because when you run CHKDSK in command prompt, it runs in “Read only” mode, and the state of the computer is changing at the time you run the utility. A "read only" chkdsk on an active NTFS volume will result in false positive errors, this is normal. Read-only CHKDSK will abort before it completes all three phases if it encounters errors in earlier phases and is prone to falsely reporting errors when in read-only mode. That is, CHKDSK may report that a disk is corrupted even when there is no real corruption present. This can happen if NTFS happens to modify areas of the disk on behalf of some program activity that CHKDSK is examining at the same time. To verify a volume correctly, the volume must be in a static state, and the only way to guarantee that state is to lock the volume. CHKDSK only locks the volume when it runs before entering Windows or in Recovery Console with /F or /R (which implies "F") is specified. To verify this, you can restart your computer in Recovery Console and run “CHKDSK /f” in there. See if you get any error messages. For more information about how to use Recovery Console, please refer to the following article: Which points to this site Fat lot of good NTFS is then (har har :lol: ) Well I ran CHKDSK /R (CHKDSK /F always gets the computer to reboot but only checks in read only mode) and no errors were reported. Hopefully I won't have to reinstall 3 times!! I don't think I've ever had a problem with read only mode, though - which Is why I thought It was dodgy... |
Agent_24 (57) | ||
| 1 2 | |||||