sammy5575
Topic Starter
Hi Everybody,
This problem has me totally confused perhaps somebody could outline what exactly has happened here.
First off its a fairly old Windows XP Pro desktop pc that i use for older apps etc. i only use it occasionally,it's got a gig of ram and runs pretty good. The other day during a session the machine was running really slow,not inclined to complete any task. So i rebooted and got an error telling me the hal.dll was corrupt or missing. I tried to run bootcfg /rebuild from the Windows Recovery console but i just got more error messages.
I tried to run restore from the command prompt and that didn't work. Then i began to get ntldr missing or corrupt error messages.
From this point i couldn't really access anything on the hard drive. The recovery console would open,but it did not give the option of logging on to the c: drive.
I tried a repair instal and that failed too.
I booted from a UBCD and discovered that the C: drive was now only 10MB in size and its second partition was showing itself as a drive but without any details. The C: was now a FAT partition and i'm pretty sure it was NTFS originally. The disc is actually 60GB and is partitioned c: @37GB and e: @20ish Gb
I also discovered at this stage that there was a floppy disc in the floppy drive,and WinXP had rebooted with that disc in the floppy drive and always in the past i would get the 'non system disc' error if that happened, on this occasion the machine did not throw up that error message, would this be significant??
So i took out the hdd and on another machine i changed it's file system to NTFS, on both partitions and then i made one partition out of them, i ran chkdsk in UBCD and it has repaired some errors, i have listed some of the repairs it carried out:
Repaired unreadable security descriptors data stream
Corrected errors in the uppercase file adding 24812 bad clusters to the Bad Clusters file
Corrected errors in the Master File Tables (MFT) bitmap attribute
Corrected errors in the volume Bitmap
Windows has made corrections to the file system
Looks like this drive was chewed up
If Windows XP re-installs ok, can i still trust this drive? or should i just chuck it in the bin………..or is it not as bad as it looks:-)
I would really appreciate any help in understanding what has happened here.
Thank you
This problem has me totally confused perhaps somebody could outline what exactly has happened here.
First off its a fairly old Windows XP Pro desktop pc that i use for older apps etc. i only use it occasionally,it's got a gig of ram and runs pretty good. The other day during a session the machine was running really slow,not inclined to complete any task. So i rebooted and got an error telling me the hal.dll was corrupt or missing. I tried to run bootcfg /rebuild from the Windows Recovery console but i just got more error messages.
I tried to run restore from the command prompt and that didn't work. Then i began to get ntldr missing or corrupt error messages.
From this point i couldn't really access anything on the hard drive. The recovery console would open,but it did not give the option of logging on to the c: drive.
I tried a repair instal and that failed too.
I booted from a UBCD and discovered that the C: drive was now only 10MB in size and its second partition was showing itself as a drive but without any details. The C: was now a FAT partition and i'm pretty sure it was NTFS originally. The disc is actually 60GB and is partitioned c: @37GB and e: @20ish Gb
I also discovered at this stage that there was a floppy disc in the floppy drive,and WinXP had rebooted with that disc in the floppy drive and always in the past i would get the 'non system disc' error if that happened, on this occasion the machine did not throw up that error message, would this be significant??
So i took out the hdd and on another machine i changed it's file system to NTFS, on both partitions and then i made one partition out of them, i ran chkdsk in UBCD and it has repaired some errors, i have listed some of the repairs it carried out:
Repaired unreadable security descriptors data stream
Corrected errors in the uppercase file adding 24812 bad clusters to the Bad Clusters file
Corrected errors in the Master File Tables (MFT) bitmap attribute
Corrected errors in the volume Bitmap
Windows has made corrections to the file system
Looks like this drive was chewed up
If Windows XP re-installs ok, can i still trust this drive? or should i just chuck it in the bin………..or is it not as bad as it looks:-)
I would really appreciate any help in understanding what has happened here.
Thank you