Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Sun, 16 Sep 2007 20:26:32 +0200
A general comment: I have a number of server systems under
management and I am painfully aware how the productivity of
my clients would be affected if their server fell over. Servers
can fail for a number of reasons, e.g. hardware failure, OS
corruption, an update gone wrong, human error (which is the
most likely cause). It is for this reason that I always maintain
a system backup. I test it twice each year so that I can tell my
client with confidence that the worst system outage he could
expect would be half a day.
See below for further comments.
"GrantEllsworth" <GrantEllsworth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B7344A0D-35F7-42BC-9268-A54565E0A65B@xxxxxxxxxxxxxxxx
OK - I got the point - find a way to test the SP before installing it on
the
production system. however, if the test machine and te production server
are
not the same hardware, then some incompatibles can slip thru - that is -
nothing breaks the test machine but something breaks the target. Seems
impractcal - but, if we could afford the mirror machine, I'd do it that
way
for sure. The downtime to restore a backup to a different disk might be a
little hard to take - but certainly means less hardware cost.
You already had the means with your mirrored disks. The downtime
to test this method would have been minimal.
The idea about "restoring" update.sys to RTM(0) level came from some
threads
I read about symptoms similar to what I experienced - that is, a hang a
loading acpitabl.dat when booting in safe mode while haning at splash
screen
in normal boot up mode.
If I undrstand you both (Mr. Pegasus and Mr. Chateau), I get the message
that the only way out of this pickle is to find some way to restore from
backups (which we do have). However, to restore, I need to (re-)install
the
opsys, install the backup program, re-catog or locate and reuse the
catalogs
of the backup media, and then restore the system folders from the backups.
Yes, that's the drawback of ntbackup.exe. This is why I use
different backup methods. They let me restore a system onto
a blank disk without first loading an auxiliary version of Windows.
"Mathieu CHATEAU" wrote:
Why do you involve restoring update.sys ? you do not mention any error
about
it
--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com
"GrantEllsworth" <GrantEllsworth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:E7902FCC-D3D2-42D8-B436-93C2A2DB44B7@xxxxxxxxxxxxxxxx
Your answer is a bit confusing. On the one hand you're telling me
"Sorry
that installing our updates hang your server so severely that you will
need
to rebuild and restore"; then you write something about backups and
using
a
drive imaging tool like Ghost, etc., and then to use a separate system
to
test an upgrade - was that for future reference? This is scarcely
practical
for a one-server small business.
What constitutes an upgrade that would trigger such a complex
procedure?
MS
advises us to install updates they recommend.
Mr. Pegasus, your wings are getting burnt!
I need a better solution.
Does anybody in the august elite community of MS Tech experts have any
comments about a solution that involves restoring
%sysdir\system32\drivers\update.sys" from the recovery console?
"Pegasus (MVP)" wrote:
"GrantEllsworth" <GrantEllsworth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:50F07909-B59A-45B2-99B3-5874AA90CB83@xxxxxxxxxxxxxxxx
After installing win2k3 sp2 on win2k3 server which had no prior sp1,
update
to dot.net framework 3.0 hung and I had to power down/restart
server.
In
normal boot, it hangs at spash screen; in safe mode, it hangs at
acpitabl.dat. What can I do to fix without having to rebuild the
server?
We are running win2k3 on a HP Proliant ML150 G2 with win2k3 mirrored
80G
SATA drives.
Your best bet is probably to restore the server from
your most recent backup. If you do not have one then
you may have to rebuild it. It would be a painful reminder
to adopt this procedure for significant upgrades:
1. Back up the server.
2. Restore it to a different disk.
3. Test it.
4. If successful, proceed with the upgrade.
Other than the native ntbackup tool (which makes restoration
to a new disk difficult) there are several third party tools
such as Acronis or Ghost. In your case you could even do
this:
1. Remove the primary disk from your mirror set.
2. Boot the machine with a floppy disk, using the
second half of the mirror.
3. If successful, upgrade the first half of the mirror.
4. If the upgrade is successful, rebuild the mirror.
5. If the upgrade fails, boot the machine as per Step 2
above, then rebuild the mirror from the second half.
.
- References:
- Re: Windows 2003 Server hangs at splash screen / acpitabl.dat after SP
- From: Pegasus \(MVP\)
- Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- From: Mathieu CHATEAU
- Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- From: GrantEllsworth
- Re: Windows 2003 Server hangs at splash screen / acpitabl.dat after SP
- Prev by Date: Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- Next by Date: Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- Previous by thread: Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- Next by thread: Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte
- Index(es):
Relevant Pages
|
