Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3519
  • Last Modified:

SBS 2008 boot problems

Hi all ,

got a sbs2008 server in a continued reboot , loads starting windows then gose to a black
 screen  with working mouse 10 sec ,  then reboots

any help would be great.
0
awall2012
Asked:
awall2012
  • 15
  • 3
1 Solution
 
zippybungle2003Commented:
Can you press F8 when it boots and select last known good config.?

if this fails I think you have a faulty device driver.

You will need to boot with an OS CD and disable the driver. lets see if last know config works first.
0
 
notacomputergeekCommented:
What hardware brand? Did it come with diagnostic utilities CD? Did you recently install anything? Can you press F8 and use Safe Mode? F8, disable automatic reboot on error to see the actual error?
0
 
awall2012Author Commented:
systen config (sorry)
intel s5500bc  + zeon 2.27 E5520 + 8 gig ram (4 taken out due to not boot booting at all)
dose boot with 4gig   4 HD raid 1 (one dead (disko with boot bcd)  /removed /replaced)
 still rebuilding  / diskpart move bcd + active boot to mirror OK not starts to boot as above..

Replaced Video card (from on board) and got STOP C00002e2   / 0xc000000F.
replaced ntds from backup and looks OK . still boot error as above.
A


0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
awall2012Author Commented:
Yes can boot to F8 but all option lead to a black screen + mouse then reboot , read some were about VGA being a problem ???

A
0
 
awall2012Author Commented:
>>>>  disable automatic reboot on error to see the actual error
       

   gives > STOP C00002E2 dIRECTORY SERVERS COULD NOT STARTBECAUSE OF THE FOLLOWING ERROR :

THE SYSTEM CANNONT FILE THE FILE SPECIFIED.       ( NO FILE NAME GIVEN)
error status 0xc000000F
please shutdown this system and reboot into directory services restore mode ckeck the event log for more detailed information.....
0
 
awall2012Author Commented:

boot from sbs2008 disk + raid drivers / system repair :-


 startRepair V2
problem sigature 01>systemdisk
02> 6.0.6001.18000.6.0.6001.18000
03> 0
04>65537
05>unknon
06>NoRootCausw
07>0
08>2
09>WrpRepair
10> 161
os version= 6.0.6001.2.1.0.256.1
Locale ID: 1033
0
 
awall2012Author Commented:


boot from sbs dvd + raid drives

command prompt :-
sfc /scannow
error
      windows Resource Protection could not start the repair service

A.
0
 
notacomputergeekCommented:
Did you boot into DSRM and check logs?
http://utools.com/help/DSRM.asp

Were you in the process of installing a virtual server?
0
 
awall2012Author Commented:

Tring this :-
sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

cecked for this Try  removing or renaming  x:\windows\winsxs\pending.xml  also on C:  (not there)

got this :-

      windows Resource protection could not perform the requested operation...
0
 
awall2012Author Commented:
>> Did you boot into DSRM

I did and all disk came back  clean , but did not see the logs b4 moving on as they said clean.

may should have, will run again.

>>Were you in the process of installing a virtual server?     = NO ,the systm is installed on the system as is ,but the bios is enable for said.
a
0
 
awall2012Author Commented:
Oh ,yes forgot about that ,  

reboot into DSRM system come up clean , then as for logon admin/password  (this is the password when the system was setup not the current one ? )

anyway logon > "no login server avalable  system  sits there 1/2min  screen gose blocky ,reboots..
a
0
 
awall2012Author Commented:
using another boot disk (xp based) I got some log files off directery  services

1811 JET_errFileNotFound, File not found was  in the log on the day the server went down.
0
 
notacomputergeekCommented:
Yes. Everything I've seen points to a rebuild, but that would be a last resort. Just depends on how long the server can be down diagnosing the problem. What is Plan B?

Can you build a CD at www.ubcd4win.com giving you tools to work on it remotely, such as remotely accessing regedit for startup files, etc. In the past, I've been able to use a WinXP OS CD without RAID drivers to build the bootable CD and still be able to access a SBS2003 server. Your configuration may need a different OS disk and RAID drivers - try both ways.

This CD would also be able to run a virus scan (I like the Kaspersky add-on), in case your system became infected without you knowing it.

Also, I've read it's possible that an A-V program is capable of quarantining or deleting OS files necessary for the OS to run, therefore crippling it.
0
 
awall2012Author Commented:
Hi all

Well , going to change the NIC as a lott of people out there are pointing to IPV6 / nic problems
causing windows to lock just b4 the logon screen like this server
but not sure how to manual install the driver.  any idear would be great .
a
0
 
awall2012Author Commented:
OK . install new NIC loaded drivers via sbs2008 repair option  

checked errors:-
unspecifed changed to system configuration migh have caused the problem
repair action system file integrity check & repair failed error code 0xa1

a
0
 
awall2012Author Commented:
Well put all hardware back as should be   ie running off system board and still have the same problem
system shows F8 screen ok

safe mode load to crcdisk.sys - black screen with working mouse ..... 30 sec ... reboot

same for all other mode tried .  

Any one got any throught s please ?

Note:- on going Replacement HD (still rebuilding)
have diskpart to mirror for boot etc
 sfc/ scannow will not work (see above)
repair computer error 0xa1 (see above)


a
0
 
awall2012Author Commented:
Bit of an odd one this :-

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\
 for tcpip6 is not there , should it be ?   (to enable/disable) just checking things.

a


0
 
awall2012Author Commented:
HI All ,
well rebuilt the server as  two disks had gone in the same mirror only one held on long enought to backup some bits  ,not bootable & unable to repair the boot bcd  ,and just, just readable

these are seagate "BE WARE" there as some  out there that in the right condution die , normaly a  power related (UPS or not) problem. they are on way back to seagate as they have a 5yw. "es ns range" .
 with my foot prints on.  check you firmwares !

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 15
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now