• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 470
  • Last Modified:

Non-system Disk Error

Got a PC here and when trying to boot up ,message displays Non-Sytem Disk Error -replace disk and restart. When I slaved the hard disk to another PC and check only Windows folder was there.All the other folders were somehow deleted/errased.No boot up file etc...
How did the files go missing ,and how to retreive them?
1 Solution
Is there anything in the CD or floppy drive for this computer? If so, remove it as this may cause problems also.

Was the PC being worked on before? Just to be sure, select the option to view all hidden files and operating system files to see if there are any other files in the root folder.

From the sound of it, you might have to reinstall Windows if it still won't bootup. You can try running a repair install which will install over itself, but I recommend doing a clean install. It's just a cleaner way of doing things and you don't need to worry about problems that may arise from an "upgrade install". If there is any data that you can backup, do so before reinstalling Windows. If you only see the Windows folder, then you are most likely out of luck as XP stores the user documents/files in Documents and Settings folder in the main/root drive.
John HurstBusiness Consultant (Owner)Commented:
I don't know that you can. I can think of two possibilities at first glance:

1. Serious malware has deleted things.
2. A hardware error has caused a hard drive corruption, thus losing data. This has happened to me.

Best course of action (if you wish to keep the machine) is to get another hard drive (maybe bigger) and reload Windows. Then slave the old drive and recover what you can.

... Thinkpads_User
Infra_DS4Author Commented:
Thanks guys .I will do what you have put forward..

Sometimes an unclean shutdown (e.g. due to a power outage) can cause filesystem corruption, but assuming NTFS is used, it is fairly rare for such serious corruption to occur due to the use of the transaction journal. Windows 2000 is in my experience more prone to this than XP/2003 and later.

In any case, running chkdsk /f (from another machine or using Recovery Console or similar) may help. It also may very well not help, but it's a simple thing to try before having to do a reinstall.
Infra_DS4Author Commented:
Well its good for now theres nothing much we could do here.Thanks alot

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now