Jump to content
Posted 09 October 2011 - 09:18 PM
Posted 09 October 2011 - 09:47 PM
Edited by €nígмä, 09 October 2011 - 09:49 PM.
Posted 09 October 2011 - 09:49 PM
Just try chkdsk /r without the c: you have been using.
I've tried to run it from command prompt (run->cmd) by typing in chkdsk c: /r
Edited by noknojon, 09 October 2011 - 09:51 PM.
Posted 09 October 2011 - 09:53 PM
sfc /scannowis also a good one. You can run this command within the OS, or in safe mode without a winxp cd.
Edited by €nígмä, 09 October 2011 - 09:53 PM.
Posted 09 October 2011 - 11:30 PM
Posted 09 October 2011 - 11:58 PM
Posted 10 October 2011 - 08:35 AM
Posted 10 October 2011 - 11:46 PM
I think my problem may be fixed.
After I ran sfc /scannow last night, I shut down my computer for the night. When I started my computer this morning, chkdsk ran on start up! It was great. I'm not sure what happened last night (I walked away while it was running) but it seems to have fixed the problem. Thanks for the help, everyone!!! :D
Posted 11 October 2011 - 06:21 AM
AA in Computer Networking Technology
BS in Information Technology
Comptia A+, Project+, L+
Posted 18 April 2018 - 10:42 PM
Just wanted to add here that I had a similar problem with chkdsk not running on bootup and doing sfc /scannow seems to have solved the problem.
I was seeking to do a chkdsk on an NTFS partition for a Windows XP installation on an old ThinkPad X41. I wanted to resize and shrink down the XP filesystem and partition so that I could put Linux installation(s) on the same disk.
But when I ran ntfsresize the ntfs filesystem failed the integrity check.
In my case it didn't seem to work necessarily right after running sfc /scannow. When I booted it up normally the first time I didn't see any blue background chkdsk screen.
But then I tried rebooting into Safe Mode with Command Prompt. So I pushed F8 and picked that and it seemed to run the chkdsk.
So when I picked Safe Mode with Command Prompt I saw some text scrolling on the screen which looked like perhaps different files being loaded. Then it just paused for a while and I could hear the disk whirring. It was taking longer than before to boot up to the command prompt, but since the disk was whirring I figured something was going on which might be the chkdsk. It wasn't reporting back though that that is what it was doing. Then it rebooted and I saw the BIOS screens again.
I think I booted Windows XP normally and when I did fsutil dirty query c: it said that it was NOT dirty.
I set the dirty bit again with fsutil dirty set c: and rebooted again using F8 into Safe Mode with Command Prompt. The same thing happened where it paused after those files scrolled by. I figured if it ran the chkdsk again the second time it wouldn't take as long because any errors would have been fixed the first time.
So again when I did fsutil dirty query c: it said that it was NOT dirty.
I figured it was good to go and when I tried ntfsresize it worked! :-)
One final thing I could add is that in trying to get it to work I found this page on Super User:
And so one person commented:
There are so many solutions: use a PE boot disk, windows to go... or Hiren's boot if your computer is old enough. You can even put a Windows installation disk and select recovery. Newer Windows version already has the recovery option builtin and you can just select it from the boot menu. – Lưu Vĩnh Phúc
I checked out Hiren's BootCD, but I didn't understand how it could have a mini Windows XP without some kind of specific relationship with Microsoft? (which I didn't see on the website)
I didn't really understand that.
Maybe some of the intellectual property on Windows XP has expired or something?
I don't know if that would be a re-implementation or not.
What people were saying there on Super User is that there isn't any Linux equivalent to the Microsoft Windows chkdsk. I wondered then if that functionality is actually rather complicated and so it would take a lot of effort to implement it for Linux.
Posted 19 April 2018 - 05:38 AM
When you schedule a chkdsk with error correction (chkdsk /r) on the next reboot AND then you boot into Safe Mode as the files and things are loading and scrolling by the last thing you are likely to see is MUP.SYS and after that, the chkdsk with error correction is going to run until it completes.
When people see this they assume that there is something wrong with MUP.SYS and go through all kinds of gyrations to try to replace the file but fail to understand that MUP.SYS has already loaded and the system appears to be "hung" on what comes after MUP.SYS and what come after is the check to see if chdsk /r needs to be run.
If the volume is "dirty" of course chkdsk with error correction is going to run on the reboot to try to fix the problem - so if folks use Safe Mode as troubleshooting they will think their system is hung or broken on MUP.SYS when they really just need to wait it out.
So while the system appears to be hung on MUP.SYS and if you can see/hear/feel that the HDD is doing something (perhaps an LED access indicator) you need to wait it out as the chkdsk with error correction will finish sooner or later one way or another.
The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.
Posted 19 April 2018 - 08:19 AM
There is a linux equivalent to chkdsk but it cannot correct every problem chkdsk does. The command is ntfsfix. It will attempt to fix some errors but what it does, at least in my experience, is force Windows into a chkdsk on the next boot.
At one point BC refused to let a person offer links to Hirens because of the XP mini issue. That went away and I did find an author for a Microsoft Press book reference Hirens. So, it seems Microsoft isn't very worried about it. But, Hirens cannot boot on a UEFI computer. UEFI needs to be set to Legacy or CSM mode before Hirens can boot. I initially thought it could not read GPT disks because XP cannot but Hirens includes a GPT driver which allows Hirens to read and write to GPT disks which are required when booting from UEFI.
Edited by JohnC_21, 19 April 2018 - 08:26 AM.
0 members, 1 guests, 0 anonymous users