Home
Friday, June 23, 2017
6:38:09 PM
Users online: 0   You are here >> Home > Building and Trouble Shooting

Forums | Building and Trouble Shooting Forums search
Forum FAQ
   
  1  
Documents and Settings mysteriously vanished!
Doctor Orange 
4/9/08 12:08:14 PM
Titan

A couple of days ago I got a call. Apparently one of the computers in an office I work for couldn't connect to a network drive. I showed up today to find the network drive no longer existed (hence the broken shortcut), remade it and it all worked.

Now I find that Outlook (ick) cannot find the PST files for either of it's profiles. It shows this error on load.

Sure enough, the folder which is supposed to contain the outlook data is empty, except for one file, extend.dat.
C:/Documents and Settings/Andrew/Local Settings/Application Data/Microsoft/Outlook/

That folder contains no .pst files, or any other files.
A windows search turns up no pst files anywhere on the computer. The recycle bin hs not been emptied for some time, and they are not in there.

Then I find that the entire My Documents folder for this account is gone. Just not there...

I suppose that something killed the My Docs, Outlook files, and Network Drive. Presumably some other things are gone too; I'm just yet to find out.

A file Scavenger (data recovery) search turns up some PST files which I think are the ones.
\found.004\dir0002.chk\Application Data\Microsoft\Outlook

My question is: what the hell is going on?
I don't think anybody went on a deleting spree, and if they did the files would be in the recycle bin.

I'm scanning for viruses now.

What might cause this sort of thing?
System Restore a good idea?

Thanks a lot for your help!

EDIT-

Some other 'settings' files have remained intact. This firefox profile for example is all here.

MS Outlook autocomplete files (NK2) are in their correct place.
"C:\Documents and Settings\Andrew\Application Data\Microsoft\Outlook"


Edited by Doctor Orange: 4/9/2008 12:30:32 PM

-----
http://www.freerainbowtables.com/

Doctor Orange 
4/9/08 2:32:45 PM
Titan

Chkdsk is the culprit!

From a couple of days ago:
 
Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Deleting orphan file record segment 10308.
Deleting orphan file record segment 10309.
Deleting orphan file record segment 10310.
Deleting orphan file record segment 10311.
Deleting orphan file record segment 10312.
Deleting orphan file record segment 10313.
Deleting orphan file record segment 10314.
Deleting orphan file record segment 10315.
Deleting orphan file record segment 10316.
Deleting orphan file record segment 10317.
Deleting orphan file record segment 10318.
Deleting orphan file record segment 10319.
The object id index entry in file 0x19 points to file 0x2845
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0x284d
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
Index entry Local Settings of index $I30 in file 0x27ca points to unused file 0x2846.
Deleting index entry Local Settings in index $I30 of file 10186.
Index entry LOCALS~1 of index $I30 in file 0x27ca points to unused file 0x2846.
Deleting index entry LOCALS~1 in index $I30 of file 10186.
Index entry My Documents of index $I30 in file 0x27ca points to unused file 0x2845.
Deleting index entry My Documents in index $I30 of file 10186.
Index entry MYDOCU~1 of index $I30 in file 0x27ca points to unused file 0x2845.
Deleting index entry MYDOCU~1 in index $I30 of file 10186.
Index entry NetHood of index $I30 in file 0x27ca points to unused file 0x2844.
Deleting index entry NetHood in index $I30 of file 10186.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

78140128 KB total disk space.
11987036 KB in 100058 files.
38400 KB in 13232 indexes.
0 KB in bad sectors.
182432 KB in use by the system.
65536 KB occupied by the log file.
65932260 KB available on disk.

4096 bytes in each allocation unit.
19535032 total allocation units on disk.
16483065 allocation units available on disk.

Internal Info:
e0 bc 01 00 89 ba 01 00 c8 ce 02 00 00 00 00 00 ................
c7 00 00 00 00 00 00 00 40 02 00 00 00 00 00 00 ........@.......
ce 16 13 08 00 00 00 00 90 c9 fd 57 00 00 00 00 ...........W....
e6 aa 35 0c 00 00 00 00 00 00 00 00 00 00 00 00 ..5.............
00 00 00 00 00 00 00 00 bc d7 7c 8a 00 00 00 00 ..........|.....
99 9e 36 00 00 00 00 00 78 38 07 00 da 86 01 00 ..6.....x8......
00 00 00 00 00 70 a1 db 02 00 00 00 b0 33 00 00 .....p.......3..

Windows has finished checking your disk.
Please wait while your computer restarts.



Dear MS,
Please make some software that isn't a total shitheap.
Regards,
Doctor Orange.


I've recovered most of the files with File Scavenger, but am still not sure what really happened and if there's anything I can do to clean up or prevent it from happening again. Any advice is welcome.

-----
http://www.freerainbowtables.com/

Jeruselem 
4/9/08 2:58:42 PM
Guru

If chkdsk starts doing that regularly, please keep an eye on the hard driving dying.


Edited by Jeruselem: 4/9/2008 02:58:59 PM

-----
PC 1: XP Home SP2, Opty 165@1.8Ghz, GEIL 1GB PC3200, 320GB SATA Cuda ES,XFX 9600GSO 580/700x2/1450, Seasonic S12+ 550W
PC 2: XP Home SP3, XP 3000+@2.24 Ghz, 1GB PC3200, 80GB IDE,ASUS nVidia 6800 512MB, Antec PlanetWatts 380W

tantryl 
4/9/08 3:15:44 PM
SuperHero
Immortal


Geez, I hope IT isn't your profession.

As above, this is generally caused by hardware faults or improper shutdown while files are open.

Most likely it'll happen again, as the HDD is physically failing.

-----
"It is the war we cannot win, nor can we lose nor drop. There is evidence of an instability of ideas, a floating series of judgements, our policy of nervous conciliation which is very disturbing."
- US Senator Hugh Scott

Jeruselem 
4/9/08 3:49:43 PM
Guru

Quote by tantryl
Geez, I hope IT isn't your profession.

As above, this is generally caused by hardware faults or improper shutdown while files are open.

Most likely it'll happen again, as the HDD is physically failing.



I used the word "regularly". Yes I work in IT and from experience, if chkdsk keeps on running every boot-up ... the disk is going.


Edited by Jeruselem: 4/9/2008 03:52:07 PM

-----
PC 1: XP Home SP2, Opty 165@1.8Ghz, GEIL 1GB PC3200, 320GB SATA Cuda ES,XFX 9600GSO 580/700x2/1450, Seasonic S12+ 550W
PC 2: XP Home SP3, XP 3000+@2.24 Ghz, 1GB PC3200, 80GB IDE,ASUS nVidia 6800 512MB, Antec PlanetWatts 380W

SceptreCore 
4/9/08 6:25:46 PM
Guru

Quote by Jeruselem
Quote by tantryl
Geez, I hope IT isn't your profession.

As above, this is generally caused by hardware faults or improper shutdown while files are open.

Most likely it'll happen again, as the HDD is physically failing.



I used the word "regularly". Yes I work in IT and from experience, if chkdsk keeps on running every boot-up ... the disk is going.


Edited by Jeruselem: 4/9/2008 03:52:07 PM


He didn't mean you!

/I think

-----
Greatest Sayings Of Our Time:
Quote by osama_bin_athlon
What a whore! I guess my e-penis mustn't be big enough....he'll be crying when I upgrade next month.....beware the turkey slap!



strifus 
4/9/08 7:23:00 PM
Charge
i think he meant the thread starter. im guessing your not the tech support guy for your company orange, or youd be one of the worst ive ever seen.

and yes, as most of the guys above me, id watch out for your HDD going kaput quite soon.

-----

tantryl 
4/9/08 9:21:32 PM
SuperHero
Immortal


Quote by SceptreCore
Quote by Jeruselem
Quote by tantryl
Geez, I hope IT isn't your profession.

As above, this is generally caused by hardware faults or improper shutdown while files are open.

Most likely it'll happen again, as the HDD is physically failing.



I used the word "regularly". Yes I work in IT and from experience, if chkdsk keeps on running every boot-up ... the disk is going.


Edited by Jeruselem: 4/9/2008 03:52:07 PM


He didn't mean you!

/I think



You think correctly, was talking to the OP.

-----
"It is the war we cannot win, nor can we lose nor drop. There is evidence of an instability of ideas, a floating series of judgements, our policy of nervous conciliation which is very disturbing."
- US Senator Hugh Scott

SceptreCore 
5/9/08 12:28:10 AM
Guru

Quote by tantryl
You think correctly, was talking to the OP.


So I can do something right!

-----
Greatest Sayings Of Our Time:
Quote by osama_bin_athlon
What a whore! I guess my e-penis mustn't be big enough....he'll be crying when I upgrade next month.....beware the turkey slap!



Doctor Orange 
6/9/08 10:19:36 PM
Titan

Hmm. Thanks for your comments. I'll replace the disk asap.

I'm a little unsure what makes me the worst IT support ever... I was called in to solve the problem, successfully diagnosed it and recovered the lost files.

Call me insecure, but I'm not sure what makes me look such a fool in this story. Do tell. :)

-----
http://www.freerainbowtables.com/

tantryl 
6/9/08 10:35:58 PM
SuperHero
Immortal


Any time there's a found.xxx pr dirxxxx.chk folder it means either a failing HDD (physical HDD fault) or file system damage (usually caused by improper shutdown or a program freeze).

Yours actually looks like file system damage, which doesn't indicate a faulty drive (no bad sectors registered in that chkdsk log), however you should make sure by running a full SeaTools or WD DLG scan on it.

Although it's possible something is causing recurring file system damage, again likely associated with improper shutdown or program freezing. So make sure next time you run chkdsk /f /x it doesn't pick up more index/MFT errors.

Worst support ever? Nope. I don't believe anyone said that. But not recognising that problem the second you spot a found.xxx or dirxxxx.chk folder, and not checking out the HDD once you've found any chkdsk related errors shows a certain lack of experience.


Edited by tantryl: 6/9/2008 10:37:47 PM

-----
"It is the war we cannot win, nor can we lose nor drop. There is evidence of an instability of ideas, a floating series of judgements, our policy of nervous conciliation which is very disturbing."
- US Senator Hugh Scott

Doctor Orange 
6/9/08 11:01:02 PM
Titan

Okay, I was just unsure if I'd missed some very obvious blunder on my part! Doesn't seem so to me.

strifus did say: "youd be one of the worst ive ever seen."

In my defense, it was the advanced file recovery software that found the found.004 folder, so I was already checking for HDD errors. This was after I ran a chkdsk of my own (which was clean) - so I had checked the disk before I found the errors in the log and the found.xxx folder.

Hey, computer troubleshooting isn't my trade, I'm a web designer.

Still, it seems that I suspected the disk, checked it, recovered the lost files and found the cause of the problem in the event log. That I'm not familiar with "found.xxx" is not bothering me. I think it does indicate a lack of experience with disk errors - don't think it warrants strifus' input...

Anyway, thanks for the advice.

-----
http://www.freerainbowtables.com/

  1  
Forums | Building and Trouble Shooting