Windows Home Server: NTLDR is corrupt

2StepSteve · 7 Jan 2011 at 18:02

Not sure what happened today I got home to find my WHS had crashed.

Tried a manual restart and now I am getting 'NTLDR is currupt' message on boot up.

Any ideas how I can fix this?

Many many thanks

Jacko197 · 7 Jan 2011 at 18:07

Hi mate, ive used this method a few times with good results. I know it says XP but ive used on Windows Server 2003 so it should work for WHS.

http://www.computerhope.com/issues/ch000465.htm

2StepSteve · 7 Jan 2011 at 18:13

Jacko197 said:
Hi mate, ive used this method a few times with good results. I know it says XP but ive used on Windows Server 2003 so it should work for WHS.

http://www.computerhope.com/issues/ch000465.htm

Should I follow the part where it states to use a XP install disc and copy over the files:

copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\

Many thanks

matthab · 7 Jan 2011 at 18:27

Interestingly just check the status of your drives? (Do they pass the diagnostic tests)

2StepSteve · 7 Jan 2011 at 18:53

In the BIOS they both look OK

TheKnat · 7 Jan 2011 at 19:32

Pretty sure I had this exact same problem where it randomly happened with no apparant cause. The way I fixed it was boot a Windows Server 2003 DVD (this is what WHS is based on) and use the automatic repair feature.

Jacko197 · 7 Jan 2011 at 19:59

2StepSteve said:
Should I follow the part where it states to use a XP install disc and copy over the files:

copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\

Many thanks

TheKnat said:
Pretty sure I had this exact same problem where it randomly happened with no apparant cause. The way I fixed it was boot a Windows Server 2003 DVD (this is what WHS is based on) and use the automatic repair feature.

Sorry been messing with my new build!

Windows server CD/DVD should sort is as above

2StepSteve · 7 Jan 2011 at 20:26

Not sure if I should trust it? I know WHS is built on Server 2003.. but I feel slightly worried using an automatic repair feature that isn't supposed to be for WHS..

Jacko197 · 7 Jan 2011 at 20:28

2StepSteve said:
Not sure if I should trust it? I know WHS is built on Server 2003.. but I feel slightly worried using an automatic repair feature that isn't supposed to be for WHS..

Try just restoring the file via a Windows Server 2003 CD/DVD first mate, then if that fails give it a go

2StepSteve · 7 Jan 2011 at 20:47

I'm not having a very good Friday evening.

Tried Windows Server 2003 CD and it causes the system to restart right before the options of 'do I want to install Server 2003' or 'run recovery' etc..

TheKnat · 8 Jan 2011 at 14:08

Could be that it has incorrect drivers for your sata controllers. It has happened to me previously where it uses incorrect drivers and then randomly restarts. I had to put the correct drivers on a USB stick and then use the F6 option when booting the CD to load the correct ones.

2StepSteve · 17 Jan 2011 at 16:27

I can't believe this! Shortly before this problem occurred I installed some new RAM.

I just swapped back the original RAM and behold the server boots fine! It was the new RAM which was faulty causing this error.

I would never of guessed in a million years that a RAM fault would throw up such a hard drive related error.

Crazy!

3dcandy · 17 Jan 2011 at 16:39

2StepSteve said:
I can't believe this! Shortly before this problem occurred I installed some new RAM.

I just swapped back the original RAM and behold the server boots fine! It was the new RAM which was faulty causing this error.

I would never of guessed in a million years that a RAM fault would throw up such a hard drive related error.

Crazy!

Why not? I've had it before....

2StepSteve · 17 Jan 2011 at 18:56

Never come across it before.

3dcandy · 17 Jan 2011 at 19:05

yeah, some really weird stuff happens when memory goes bad. recently had a system that would only crash whilst playing Wow. Duff memory in the end, though it never ever crashed unless playing WoW!