Link to home
Start Free TrialLog in
Avatar of dpacheco
dpacheco

asked on

Sbs 2008 won't boot after dirty shutdown.

Client called saying they couldn't figure out how to restart the server after updates so they just turned it off. Now it wont boot, says there' a problem with hardware device or software, option is to run a repair, memory diags or command prompt. Running a repair does nothing, had them run chkdsk with no options, says no file errors. There's an option to restore, we do have sbs backup on RD1000 cartridge from last night. Not sure the best way to proceed - boot from sbs cd and try repair that way?
Avatar of wolfcamel
wolfcamel
Flag of Australia image

sometimes copying the system & config files from the repair folder to the system32 folder (renaming the originals) can solve this
Avatar of dpacheco
dpacheco

ASKER

Where is the repair folder located? I'm wondering if last known configuration might work?
Avatar of ronnypot
The repair folder is something that we had with windows 2003 and XP but it doesn't exist anymore since windows 2008.

Trying the last known good couldn't harm. Can you boot in safe mode? where in the boot process does the error appear?
If it is a hardware error start removing all attached and not needed hardware and look if the server will start.

For a restore from the sbs backup you could look here: http://blogs.technet.com/b/sbs/archive/2010/06/11/how-to-perform-a-bare-metal-restore-on-small-business-server-2008.aspx

sorry - totally missed the 2008/2003 thing,
last known good is probably your best option
Im at the site now  Last known didn't work. Safe mode just restates it.
Just restarted from sbs cd, chose repair but get same options- complete restore, mem diags or command prompt.
Problem comes up after bios, shows window atbottom Microsoft Corp....then prompt to repair.
I can go to command prompt and see the data and drives.
I have a full sbs backup from thursday night on dell rd1000
Should I attempt to restore c?
You could try a chkdsk before you go for the restore.
You could try a chkdsk before you go for the restore.
You could try a chkdsk before you go for the restore.
Just ran chkdsk with no options on c, error in an index.
Previously had client run it and no errors but they ran it on x drive, utility partition.
Run it with /f? won't hurt will it?
yes do it with the /f option
Appeared to recover orphaned files but says failed to transfer logged message to the event log with status 50. I'm assuming because the c drive is not mounted. Restarted and same prompt-repair or start normally, tried start normally but it just restarts. In repair only options are restore, mem diags, command prompt
Run chkdsk /f again ?
Ran chkdsk again, no go, last known no go. Running startrep from utility partition now.
Startrep ran for a while but said it couldn't repair
Wrote down the details but nothing helpful there, just NoRootCause
Looks like restore is next unless there are other suggestions?
restore would be you best shot I think
Yes getting ready to do that now
ASKER CERTIFIED SOLUTION
Avatar of dpacheco
dpacheco

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
None of the fixing options worked, restored from backup.