Hello, We have a windows vps running for a few days, today after we rebooted this vps, it never started, and I got this message from the vnc console. Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll Please re-install a copy of the above file. the OS is windows 2003 std 32bits with GPLPV 0.10.0.138, and hypervisor is xen 3.4.1, and we are using LVM paritions. Any one know why does this happen? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Nov-22 12:08 UTC
RE: [Xen-users] windows vps can not start after a reboot
> Hello, > We have a windows vps running for a few days, today after we rebooted > this vps, it never started, and I got this message from the vnc > console. > > Windows could not start because the following file is missing orcorrupt:> <Windows root>\system32\hal.dll > Please re-install a copy of the above file. > > the OS is windows 2003 std 32bits with GPLPV 0.10.0.138, > and hypervisor is xen 3.4.1, and we are using LVM paritions. > > Any one know why does this happen?What was the reason for the reboot? Was it applying updates? Did it reboot cleanly as far as you know? What backend are you using? In using tap:aio I have seen similar problems, but on an LVM volume I assume you are using phy, can you confirm? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, its using phy, I guess the system automated applied a few updates, but I''m not sure, and I rebooted the vps manually after changing host name. On Sun, Nov 22, 2009 at 1:08 PM, James Harper <james.harper@bendigoit.com.au> wrote:>> Hello, >> We have a windows vps running for a few days, today after we rebooted >> this vps, it never started, and I got this message from the vnc >> console. >> >> Windows could not start because the following file is missing or > corrupt: >> <Windows root>\system32\hal.dll >> Please re-install a copy of the above file. >> >> the OS is windows 2003 std 32bits with GPLPV 0.10.0.138, >> and hypervisor is xen 3.4.1, and we are using LVM paritions. >> >> Any one know why does this happen? > > What was the reason for the reboot? Was it applying updates? > > Did it reboot cleanly as far as you know? > > What backend are you using? In using tap:aio I have seen similar > problems, but on an LVM volume I assume you are using phy, can you > confirm? > > James > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Windows could not start because the following file is missing or corrupt: > <Windows root>\system32\hal.dll > Please re-install a copy of the above file.That''s probably the first dll that windows tries to find on bootup, and basically means it couldn''t even find the correct windows partition. Assuming this is not a new install of the gplpv drivers, and that you have previously booted correctly with them on, there is another possibility. When it happened to me, it was because my boot.ini file got altered. Instead of something like ''multi(0)disk(0)rdisk(0)partition(1)'' in the various lines, it had the wrong partition number. Double check it. With the vps shutdown, try mounting the partition (losetup + kpartx + mount for a file: backed vbd, or simply kpartx + mount for a phy: device, like an lvm partition), and correct it if necessary. Good luck. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dustin Henning
2009-Nov-23 13:18 UTC
RE: [Xen-users] windows vps can not start after a reboot
I haven''t seen any other messages in this thread, so forgive me if this has been said already, but I believe NTLDR is the first file loaded from the Windows partition. If you have an HD with a boot sector and wipe the Windows partition (or lose the Windows HDD that is separate), you will get something to the effect of "NTLDR is missing." That said, I suspect that your error implies that something has messed up or corrupteh your Windows partition. If you were using GPLPV drivers and something went wrong, they could be the culprit. That isn''t to say you shouldn''t use the drivers, just that you should always have a good backup, as is often stated regarding said drivers (and best practices in general). Dustin -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of jim burns Sent: Sunday, November 22, 2009 11:39 To: xen-users@lists.xensource.com Subject: Re: [Xen-users] windows vps can not start after a reboot> Windows could not start because the following file is missing or corrupt: > <Windows root>\system32\hal.dll > Please re-install a copy of the above file.That''s probably the first dll that windows tries to find on bootup, and basically means it couldn''t even find the correct windows partition. Assuming this is not a new install of the gplpv drivers, and that you have previously booted correctly with them on, there is another possibility. When it happened to me, it was because my boot.ini file got altered. Instead of something like ''multi(0)disk(0)rdisk(0)partition(1)'' in the various lines, it had the wrong partition number. Double check it. With the vps shutdown, try mounting the partition (losetup + kpartx + mount for a file: backed vbd, or simply kpartx + mount for a phy: device, like an lvm partition), and correct it if necessary. Good luck. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I still have this issue for many VPSes, here are more information I have right now. When the windows vps can not boot up, it will report that some files are missed, or corrupt. Usually I boot up the vps with windows installation cd, and enter the repair mode, and execute the command chkdsk /r Then after this the system will boot up again, but after a few reboots, the issue will appear again, Do you have any idea about this? ONE MORE THING is that we do not install the OS manually, we just use ntfsclone to clone the drive C to a new VPS, and boot it up. On Sun, Nov 22, 2009 at 1:11 PM, Jingyun He <jingyun.ho@gmail.com> wrote:> Yes, its using phy, > I guess the system automated applied a few updates, but I''m not sure, > and I rebooted the vps manually after changing host name. > > On Sun, Nov 22, 2009 at 1:08 PM, James Harper > <james.harper@bendigoit.com.au> wrote: >>> Hello, >>> We have a windows vps running for a few days, today after we rebooted >>> this vps, it never started, and I got this message from the vnc >>> console. >>> >>> Windows could not start because the following file is missing or >> corrupt: >>> <Windows root>\system32\hal.dll >>> Please re-install a copy of the above file. >>> >>> the OS is windows 2003 std 32bits with GPLPV 0.10.0.138, >>> and hypervisor is xen 3.4.1, and we are using LVM paritions. >>> >>> Any one know why does this happen? >> >> What was the reason for the reboot? Was it applying updates? >> >> Did it reboot cleanly as far as you know? >> >> What backend are you using? In using tap:aio I have seen similar >> problems, but on an LVM volume I assume you are using phy, can you >> confirm? >> >> James >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, Any one have similar problem? I need your help, Thanks. On Tue, Dec 22, 2009 at 11:00 AM, Jingyun He <jingyun.ho@gmail.com> wrote:> Hello, > I still have this issue for many VPSes, here are more information I > have right now. > When the windows vps can not boot up, it will report that some files > are missed, or corrupt. > > Usually I boot up the vps with windows installation cd, and enter the > repair mode, > and execute the command chkdsk /r > Then after this the system will boot up again, but after a few > reboots, the issue will appear again, Do you have any idea about this? > > ONE MORE THING is that we do not install the OS manually, we just use > ntfsclone to clone the drive C to a new VPS, and boot it up. > > > On Sun, Nov 22, 2009 at 1:11 PM, Jingyun He <jingyun.ho@gmail.com> wrote: >> Yes, its using phy, >> I guess the system automated applied a few updates, but I''m not sure, >> and I rebooted the vps manually after changing host name. >> >> On Sun, Nov 22, 2009 at 1:08 PM, James Harper >> <james.harper@bendigoit.com.au> wrote: >>>> Hello, >>>> We have a windows vps running for a few days, today after we rebooted >>>> this vps, it never started, and I got this message from the vnc >>>> console. >>>> >>>> Windows could not start because the following file is missing or >>> corrupt: >>>> <Windows root>\system32\hal.dll >>>> Please re-install a copy of the above file. >>>> >>>> the OS is windows 2003 std 32bits with GPLPV 0.10.0.138, >>>> and hypervisor is xen 3.4.1, and we are using LVM paritions. >>>> >>>> Any one know why does this happen? >>> >>> What was the reason for the reboot? Was it applying updates? >>> >>> Did it reboot cleanly as far as you know? >>> >>> What backend are you using? In using tap:aio I have seen similar >>> problems, but on an LVM volume I assume you are using phy, can you >>> confirm? >>> >>> James >>> >>> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users