Re: Windows 2003 Server hangs at splash screen / acpitabl.dat afte

I've got a backup, but I would need to install the opsys and the backup
program in order to restore the original opsys, wouldn't I?

"Pegasus (MVP)" wrote:

Sorry, I should have placed my thoughts in a different order. Here
they are again:

1. By far the best method to restore your server is to
perform a restoration from a tested backup.
2. If you failed to make a backup prior to ther upgrade, you're
stuck.
3. To create moderately useable backup, use ntbackup.exe.
4. To create a more useable backup, use an imaging product.
5. Alternatively, if your disks are mirrored, split the mirror prior
to the upgrade in order to retain your existing installation on
one of the disks.
6. If you believe that a restoration of update will solve your
problem, give it a try but make sure to back up the
original version first. If you cannot do this under the Recovery
Console, do it under a Bart PE boot.
7. When I did my most recent service pack installation, I did
not burn my wings. Instead I followed the stern warnings
I had received from my local user group about creating
and testing a full backup first. This was for a humble one-server
business with just 12 staff.


"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.






.

Relevant Pages

  • Re: RAID, SCHMAID.......
    ... And risky to change it later without a full image backup. ... partition, & then restore only the OS, but still verydoable. ... partition before an install of something you havent installed before, ... but so many ppl make a mess of things esp with today's big drives. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Restore to Larger Hard Drives Install from DVD
    ... And I'm not so sure the Susan Bradley's install steps either. ... The main point you need to verify is that your new installation level needs to be same as your backup installation level. ... As you have installed R2 and SQL 2005, if you have other components installed in your backup version, and you haven't installed on your new server, you need to install them before restore. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: RAID, SCHMAID.......
    ... And risky to change it later without a full image backup. ... partition, & then restore only the OS, but still verydoable. ... And to work out the complexitys with a canned OS install ... but so many ppl make a mess of things esp with today's big drives. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Major Version Upgrade - 4.11 to 5.x
    ... support) for you to upgrade? ... It is a general rule of thumb to do a clean install between ... > Other than the obvious advice to start with a good backup, ... leave the production system running and begin the ...
    (freebsd-questions)
  • Re: Windows Media Player BLINDSIDE update!
    ... WMP10 that was actually an "upgrade" to WMP11. ... machine without having a complete Ghost Backup before starting ... computer industry - and nobody inside the industry is taking ... assume that every update you install is suspect until proven otherwise. ...
    (microsoft.public.windowsxp.general)
Loading