Unsolved

This post is more than 5 years old

2 Posts

6624

May 29th, 2007 18:00

Dell PowerEdge & VMWare Server 1.0.3 or ESX Server 3.0.1 in NTOSKRNL missing issue

hi all,
 
i have a WEIRD problem with this poweredge 1900. the specs are as follows;
 
poweredge 1900
1 x xeon e5310 1.6 ghz quadcore
16gb ram
perc 5/i controller
2 x 73gb sas
4 x 300gb sata
virtualization technology = enabled
 
i initially installed esx 3.0.1 on this box to test out compatability for work. yep all went smooth. then proceeded to install windows xp pro x64. after the text setup finished it rebooted it came up with the standard windows error;
 
windows could not start because the following file is missing or currupt:
\system32\ntoskrnl.exe
 
now this is standard when the boot.ini is pointing to wrong disk or partition. so i tried the recovery console, and no can do. you select the parition and the vm reboots. ok so i went ahead removed it ands tried windows server 2003 x64 and you guessed it, same problem. tried windows 2000 server and same problem, windows xp pro x86, same problem!!!
 
i know the media works as i have used the iso images before, i even tried installation media we use with some other servers and the same problem!
 
so i decied to get rid of esx and install windows 2003 enterprise x64 as the host operating system. all went well. works a treat. installed vmware server 1.0.3 and began to install some vm's again.
 
SAME PROBLEM! missing ntoskrnl.exe!!!!
 
does anyone have any idea what it could be? there obviosuly is somethign wrong with this system as the os has completely changed. have run latest SUU patches and still same problem.
 
please help, it's driving me crazy!!!!! :-(
 
aany ideas people?!?

2 Posts

May 31st, 2007 17:00

to make this story even weirder.... i've re-installed windows 2003 sevrer x64 and x86 as the host and then installed Virtual Server 2005 R2.
 
installed windows and still the same problem!!!!
 
i've replaced memory on the machine thinking it could be that as it was getting page faults. i'm starting to think this is a hardware problem now.
 
anyone got any ideas?
No Events found!

Top