| 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 | ||
| 420737 | 2006-01-13 10:24:00 | Ok, here's how it happened: I tried installing ubuntu linux to my already set up harddrive (bad idea, I guess) - ran the live CD and used the partition manager program to resize my windows XP partition 5GB smaller and tried formatting 4.5GB of the new space for ubuntu (Ext3), and 500MB for swap space. Clicked apply and from then everything went downhill - the program told me it could not perform the specified actions on the Ext3 partition (or something, can't really remember now) anyway I put everything back how it was and clicked apply, which seemed to work and rebooting into windows worked fine too. I decided to run chkdsk to see if I had munted anything, and i got this: WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. 199133675 KB total disk space. 69803780 KB in 97370 files. 36804 KB in 6444 indexes. 0 KB in bad sectors. 176491 KB in use by the system. 65536 KB occupied by the log file. 129116600 KB available on disk. 4096 bytes in each allocation unit. 49783418 total allocation units on disk. 32279150 allocation units available on disk. So I ran CHKDSK /F, restarted like it asked me and it told me there was nothing wrong with the drive (typical microsoft) Went back into windows, ran chkdsk read only and got the same error. Booted off recovery console and ran chkdsk /r, it said it fixed errors then I loaded XP again and ran chkdsk read only again, where I get this error: CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is recovering lost files. Recovering orphaned file m[1].gif (1672) into directory file 62828. Recovering orphaned file M_1_~1.GIF (1672) into directory file 62828. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. 199133675 KB total disk space. 69803780 KB in 97370 files. 36804 KB in 6444 indexes. 0 KB in bad sectors. 176491 KB in use by the system. 65536 KB occupied by the log file. 129116600 KB available on disk. 4096 bytes in each allocation unit. 49783418 total allocation units on disk. 32279150 allocation units available on disk. I have also managed to get: CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is recovering lost files. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. and where it comes up with lots of files and says: Errors found. CHKDSK cannot continue in read-only mode: WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Deleting index entry 2cents[1].gif in index $I30 of file 62828. Deleting index entry 2CENTS~1.GIF in index $I30 of file 62828. Deleting index entry lol[1].gif in index $I30 of file 62828. Deleting index entry LOL_1_~1.GIF in index $I30 of file 62828. Deleting index entry tongue[1].gif in index $I30 of file 84455. Deleting index entry TONGUE~1.GIF in index $I30 of file 84455. Deleting index entry wink[1].gif in index $I30 of file 84455. Deleting index entry WINK_1~1.GIF in index $I30 of file 84455. Deleting index entry angry[1].gif in index $I30 of file 95948. Deleting index entry ANGRY_~1.GIF in index $I30 of file 95948. Deleting index entry puppy_dog_eyes[1].gif in index $I30 of file 95948. Deleting index entry PUPPY_~1.GIF in index $I30 of file 95948. Deleting index entry badpc[1].gif in index $I30 of file 96031. Deleting index entry BADPC_~1.GIF in index $I30 of file 96031. Deleting index entry pressf1;dcopt=ist;abr=!webtv;sz=760x120;ptile=1;or d=(new%20 Date())[1].getTime() in index $I30 of file 96031. Deleting index entry PRESSF~1.GET in index $I30 of file 96031. Index verification completed. Errors found. CHKDSK cannot continue in read-only mode. What have I done??? is it fixable??? |
Agent_24 (57) | ||
| 420738 | 2006-01-13 20:02:00 | Probably not. I'm not the expert on Linux installs but I think you've stuffed Windows. Retrieve whatever you can and reinstall. |
pctek (84) | ||
| 420739 | 2006-01-13 20:09:00 | This is why (as a newbie to Linux) I never install Linux on the same hard drive that I have Windows installed. Prevents a lot of headaches that way. As pctek said... you'd be better off, retrieving whatever you can off Windows and then re-installing. cheers chiefnz |
chiefnz (545) | ||
| 420740 | 2006-01-13 21:20:00 | and 500MB for swap space.Can't help at all with your main problem, but for future reference you're not going to benefit from putting your swap file on a seperate partition. It's only useful to have it off your C drive when you place it on a literal second hard drive. | Greg (193) | ||
| 420741 | 2006-01-13 23:28:00 | Probably not. I'm not the expert on Linux installs but I think you've stuffed Windows. Retrieve whatever you can and reinstall. yea, I thought as much... well I guess reinstalling is what windows is all about :lol: Can't help at all with your main problem, but for future reference you're not going to benefit from putting your swap file on a seperate partition. It's only useful to have it off your C drive when you place it on a literal second hard drive. Well I did that because I also set linux up on another computer (with blank harddrive) when It came to partition setup in the install, I chose 'automatically setup partitions' and it made a 9.5GB for install and a 500MB for swap (on one 10GB drive) - which Is why I tried it on the other one... Well, at least now I think I know what i'm doing :o By the way, is it possible to do that activation backup trick with SP2?? I don't want to ring M$ again... |
Agent_24 (57) | ||
| 420742 | 2006-01-13 23:46:00 | Can't help at all with your main problem, but for future reference you're not going to benefit from putting your swap file on a seperate partition. It's only useful to have it off your C drive when you place it on a literal second hard drive. Linux always has its own partition for a swap file. Linux handles disks very differently from windows |
mikebartnz (21) | ||
| 420743 | 2006-01-14 10:34:00 | This may not be the problem but, Iv'e had heaps of failed linux installs and it nearly always wrecks the Master Boot Record. 90% of the time I get everything back to normal by running FIXMBR in the windows recovery console. Hope this helps. Ian |
i-gordon (962) | ||
| 420744 | 2006-01-14 13:32:00 | This may not be the problem but, Iv'e had heaps of failed linux installs and it nearly always wrecks the Master Boot Record. 90% of the time I get everything back to normal by running FIXMBR in the windows recovery console. Hope this helps. Ian LOL, after I reinstall windows Only thing is - the problem is still here!!! :help: :help: :help: I will try FIXMBR to see what happens.... |
Agent_24 (57) | ||
| 420745 | 2006-01-14 13:44:00 | :help: well FIXMBR didn't work! ran chkdsk, 1st time it came up clean... 2nd time (after loading this site) I get this crap again: The type of the file system is NTFS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Deleting index entry AAEF2A~1.TXT in index $I30 of file 9578. Deleting index entry user@cgi-bin[1].txt in index $I30 of file 9578. Index verification completed. Errors found. CHKDSK cannot continue in read-only mode. How can I fix this?? I deleted all partitons and did a full reformat with windows setup... have I broken my harddrive somehow?? |
Agent_24 (57) | ||
| 420746 | 2006-01-14 20:10:00 | According to this site ( . blogspot . com/2004_10_01_win-xp-sp_archive . html" target="_blank">win-xp-sp . blogspot . com) 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 ( . microsoft . com/kb/q314058/" target="_blank">support . microsoft . com) |
Speedy Gonzales (78) | ||
| 1 2 | |||||