Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm installing SQL Server on Windows Home Server. It failed. It think it is because when it load the master DB it doesn't understand NTFS tombstones--the windows event log seems to think the system has an E: drive and there isn't.

Do any commands exist to check to see if file is a tombstone and where the real file is being held?

share|improve this question

closed as off-topic by HopelessN00b Feb 6 '15 at 10:54

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HopelessN00b
If this question can be reworded to fit the rules in the help center, please edit the question.

If these tombstones are in fact NTFS reparse points or junctions, you might want to try one of the tools mentioned in this KB article:

There's also sysinternals (well, Microsoft) tool called Junction that might help:

share|improve this answer
Junction will show 'UNKNOWN MICROSOFT REPARSE POINT' if the drive is missing (I have Windows Home Server and I'm pulling out each drive in turn and see this for every file) – Simon May 22 '13 at 5:40

Not the answer you're looking for? Browse other questions tagged or ask your own question.