Hi,
I just bought a new Dell Power Edge Server. It has a Dual core Xeon
3.0 Gig processor and 4gb of ram. It has 3 250gb drives in a Raid 5
configuration. I just installed windows 2003 and every time it boots
up, it sits at the windows loading screen with the bar moving across
for about 5 minutes. It gets to the login screen immediately and I can
login right away. What could be causing this? It is attached to a
domain and no UPS services. Thanks.
Try booting in Safe mode and see which files it is booting the slowest.
--
Jabez Gan
Microsoft MVP
Windows Server: File System
http://www.msblog.org
"Robert" <robert.b.walden@gmail.com> wrote in message
news:1169597405.858684.32470@h3g2000cwc.googlegroups.com...
> Hi,
>
> I just bought a new Dell Power Edge Server. It has a Dual core Xeon
> 3.0 Gig processor and 4gb of ram. It has 3 250gb drives in a Raid 5
> configuration. I just installed windows 2003 and every time it boots
> up, it sits at the windows loading screen with the bar moving across
> for about 5 minutes. It gets to the login screen immediately and I can
> login right away. What could be causing this? It is attached to a
> domain and no UPS services. Thanks.
>
"Jabez Gan [MVP]" <mingteikg@blizNOSPAMhosting.com> wrote in message
news:0C91090A-2B94-4393-AF6E-4FF72F7ABE23@microsoft.com...
> Try booting in Safe mode and see which files it is booting the slowest.
Also try enabling the /SOS switch on the Boot.INI (from System Control
Panel startup options) to monitor visually which services seems to be
hanging.
You cannot really tell because of the way the SCM (service control
manager) starts some services (letting them run, and they call back to
say "OK, I am fine") but it might give you a hint.
Chances are it is something from networking...hopefully it is NOT
a bad hard drive or controller but that seems unlikely.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
Hello and thanks for the suggestions. I tried safe mode and it zips
through all the files and then just sits there for 5-10 minutes, then
flashes to login screen for safe mode. It doesn't get stuck on any one
file that I can see. I tried adding /SOS to boot.ini as well. It
boots up, flashes a screen with files similar to booting up in safe
mode, for half a second. Then it goes to a gray screen that says
windows 2003 in the top right. It has the windows version, processor
and ram specs but nothing else. It sits there for 5-10 minutes, then
it flashed a screen that said something about checking drive c, d, e
and f or something. The screen flashed and was gone in less then a
second and then I was at the login screen. So I still haven't been
able to get any more of a hint where the problem is. Can anyone else
suggest a next step? I've checked out the raid configuration and it
says everything is setup right and healthy. Any ideas? Thanks.
On Jan 23, 11:35 pm, "Herb Martin" <n...@learnquick.com> wrote:
> "Jabez Gan [MVP]" <mingte...@blizNOSPAMhosting.com> wrote in messagenews:0C91090A-2B94-4393-AF6E-4FF72F7ABE23@microsoft.com...
>
> > Try booting in Safe mode and see which files it is booting the slowest.Also try enabling the /SOS switch on the Boot.INI (from System Control
> Panel startup options) to monitor visually which services seems to be
> hanging.
>
> You cannot really tell because of the way the SCM (service control
> manager) starts some services (letting them run, and they call back to
> say "OK, I am fine") but it might give you a hint.
>
> Chances are it is something from networking...hopefully it is NOT
> a bad hard drive or controller but that seems unlikely.
>
> --
> Herb Martin, MCSE, MVPhttp://www.LearnQuick.Com
> (phone on web site)
Robert wrote:
> Hello and thanks for the suggestions. I tried safe mode and it zips
> through all the files and then just sits there for 5-10 minutes, then
> flashes to login screen for safe mode. It doesn't get stuck on any one
> file that I can see. I tried adding /SOS to boot.ini as well. It
> boots up, flashes a screen with files similar to booting up in safe
> mode, for half a second. Then it goes to a gray screen that says
> windows 2003 in the top right. It has the windows version, processor
> and ram specs but nothing else. It sits there for 5-10 minutes, then
> it flashed a screen that said something about checking drive c, d, e
> and f or something. The screen flashed and was gone in less then a
> second and then I was at the login screen. So I still haven't been
> able to get any more of a hint where the problem is. Can anyone else
> suggest a next step? I've checked out the raid configuration and it
> says everything is setup right and healthy. Any ideas? Thanks.
>
Is this a member server or a DC? What is it using for DNS? Also are any
events logged in the event viewer once the server does log in?
"Robert" <robert.b.walden@gmail.com> wrote in message
news:1169656654.952271.233880@v33g2000cwv.googlegroups.com...
> Hello and thanks for the suggestions. I tried safe mode and it zips
> through all the files and then just sits there for 5-10 minutes, then
> flashes to login screen for safe mode. It doesn't get stuck on any one
> file that I can see. I tried adding /SOS to boot.ini as well. It
> boots up, flashes a screen with files similar to booting up in safe
> mode, for half a second.
So you are getting past the System and Boot drivers ( I believe)
> Then it goes to a gray screen that says
> windows 2003 in the top right. It has the windows version, processor
> and ram specs but nothing else. It sits there for 5-10 minutes, then
> it flashed a screen that said something about checking drive c, d, e
> and f or something.
That is the chkdsk screen (autocheck actually) which should EITHER
check the drives and show that or should finish quickly.
Could be a (slow to respond) disk controller or drive problem....
Double check event logs for disk/controller errors.
Do explicit chkdsk and let it do full reboot checks.
> The screen flashed and was gone in less then a
> second and then I was at the login screen. So I still haven't been
> able to get any more of a hint where the problem is. Can anyone else
> suggest a next step? I've checked out the raid configuration and it
> says everything is setup right and healthy. Any ideas? Thanks.
>
> On Jan 23, 11:35 pm, "Herb Martin" <n...@learnquick.com> wrote:
>> "Jabez Gan [MVP]" <mingte...@blizNOSPAMhosting.com> wrote in
>> messagenews:0C91090A-2B94-4393-AF6E-4FF72F7ABE23@microsoft.com...
>>
>> > Try booting in Safe mode and see which files it is booting the
>> > slowest.Also try enabling the /SOS switch on the Boot.INI (from System
>> > Control
>> Panel startup options) to monitor visually which services seems to be
>> hanging.
>>
>> You cannot really tell because of the way the SCM (service control
>> manager) starts some services (letting them run, and they call back to
>> say "OK, I am fine") but it might give you a hint.
>>
>> Chances are it is something from networking...hopefully it is NOT
>> a bad hard drive or controller but that seems unlikely.
>>
>> --
>> Herb Martin, MCSE, MVPhttp://www.LearnQuick.Com
>> (phone on web site)
>
It's now a member of the domain. It is not a DC. DNS is set to obtain
automatically. This problem has been happening before it was plugged
into the network. The only event log error I see is below and it
happens once in awhile. Anymore advice would really be appreciated. I
want to make an image of this server, but cannot until this issue is
resolved. Thanks!
Event Type: Error
Event Source: percsas
Event Category: None
Event ID: 9
Date: 1/23/2007
Time: 9:54:29 AM
User: N/A
Computer: PROJECTSERVER
Description:
The device, \Device\RaidPort0, did not respond within the timeout
period.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 10 00 01 00 68 00 ......h.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 08 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 00 00 00 00 ........
0030: ff ff ff 00 09 00 04 c0 ÿÿÿ....À
There is also an event log warning under system:
Event Type: Warning
Event Source: percsas
Event Category: None
Event ID: 129
Date: 1/23/2007
Time: 12:52:00 AM
User: N/A
Computer: MACHINENAME
Description:
The description for Event ID ( 129 ) in Source ( percsas ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: \Device\RaidPort0.
Data:
0000: 0f 00 10 00 01 00 68 00 ......h.
0008: 00 00 00 00 81 00 04 80 ......€
0010: 04 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 81 00 04 80 ......€
On Jan 24, 8:48 am, Smokey <smo...@aol.com> wrote:
> Robert wrote:
> > Hello and thanks for the suggestions. I tried safe mode and it zips
> > through all the files and then just sits there for 5-10 minutes, then
> > flashes to login screen for safe mode. It doesn't get stuck on any one
> > file that I can see. I tried adding /SOS to boot.ini as well. It
> > boots up, flashes a screen with files similar to booting up in safe
> > mode, for half a second. Then it goes to a gray screen that says
> > windows 2003 in the top right. It has the windows version, processor
> > and ram specs but nothing else. It sits there for 5-10 minutes, then
> > it flashed a screen that said something about checking drive c, d, e
> > and f or something. The screen flashed and was gone in less then a
> > second and then I was at the login screen. So I still haven't been
> > able to get any more of a hint where the problem is. Can anyone else
> > suggest a next step? I've checked out the raid configuration and it
> > says everything is setup right and healthy. Any ideas? Thanks.Is thisa member server or a DC? What is it using for DNS? Also are any
> events logged in the event viewer once the server does log in?
Thanks for the reply Herb. Don't the event log errors I listed have
something to do with the controller? The event source is percsas which
is the Dell Perc Raid Controller. Also it says The device,
\Device\RaidPort0, did not respond within the timeout
period. I am not sure why to try here. Should I reinstall the Raid
drivers? I'm not sure how to proceed.
On Jan 24, 8:59 am, "Herb Martin" <n...@learnquick.com> wrote:
> "Robert" <robert.b.wal...@gmail.com> wrote in messagenews:1169656654.952271.233880@v33g2000cwv.googlegroups.com...
>
> > Hello and thanks for the suggestions. I tried safe mode and it zips
> > through all the files and then just sits there for 5-10 minutes, then
> > flashes to login screen for safe mode. It doesn't get stuck on any one
> > file that I can see. I tried adding /SOS to boot.ini as well. It
> > boots up, flashes a screen with files similar to booting up in safe
> > mode, for half a second.So you are getting past the System and Boot drivers ( I believe)
>
> > Then it goes to a gray screen that says
> > windows 2003 in the top right. It has the windows version, processor
> > and ram specs but nothing else. It sits there for 5-10 minutes, then
> > it flashed a screen that said something about checking drive c, d, e
> > and f or something.That is the chkdsk screen (autocheck actually) which should EITHER
> check the drives and show that or should finish quickly.
>
> Could be a (slow torespond) disk controller or drive problem....
>
> Double check event logs for disk/controller errors.
>
> Do explicit chkdsk and let it do full reboot checks.
>
> > The screen flashed and was gone in less then a
> > second and then I was at the login screen. So I still haven't been
> > able to get any more of a hint where the problem is. Can anyone else
> > suggest a next step? I've checked out the raid configuration and it
> > says everything is setup right and healthy. Any ideas? Thanks.
>
> > On Jan 23, 11:35 pm, "Herb Martin" <n...@learnquick.com> wrote:
> >> "Jabez Gan [MVP]" <mingte...@blizNOSPAMhosting.com> wrote in
> >> messagenews:0C91090A-2B94-4393-AF6E-4FF72F7ABE23@microsoft.com...
>
> >> > Try booting in Safe mode and see which files it is booting the
> >> > slowest.Also try enabling the /SOS switch on the Boot.INI (from System
> >> > Control
> >> Panel startup options) to monitor visually which services seems to be
> >> hanging.
>
> >> You cannot really tell because of the way the SCM (service control
> >> manager) starts some services (letting them run, and they call back to
> >> say "OK, I am fine") but it might give you a hint.
>
> >> Chances are it is something from networking...hopefully it isNOT
> >> a bad hard drive or controller but that seems unlikely.
>
> >> --
> >> Herb Martin, MCSE, MVPhttp://www.LearnQuick.Com
> >> (phone on web site)
Robert wrote:
> Thanks for the reply Herb. Don't the event log errors I listed have
> something to do with the controller? The event source is percsas which
> is the Dell Perc Raid Controller. Also it says The device,
> \Device\RaidPort0, did not respond within the timeout
> period. I am not sure why to try here. Should I reinstall the Raid
> drivers? I'm not sure how to proceed.
>
At that point I would call Dell and see what they have to say, if it is
a newer server I would assume they could run some utils to test the RAID
controller
"Smokey" <smokey@aol.com> wrote in message
news:12rf8ehrknvac1f@news.supernews.com...
> Robert wrote:
>> Thanks for the reply Herb. Don't the event log errors I listed have
>> something to do with the controller? The event source is percsas which
>> is the Dell Perc Raid Controller. Also it says The device,
>> \Device\RaidPort0, did not respond within the timeout
>> period. I am not sure why to try here. Should I reinstall the Raid
>> drivers? I'm not sure how to proceed.
>>
>
> At that point I would call Dell and see what they have to say, if it is a
> newer server I would assume they could run some utils to test the RAID
> controller
Me too (i.e., call Dell). (I didn't see you have these errors listed
before.)
You have a new server; contact the vendor and get it fixed.
I've been working with them and even had a dell tech come out but no
results. They suck. I may just ask them to replace it. I really need
this up and running now.
On Jan 24, 10:39 am, "Herb Martin" <n...@learnquick.com> wrote:
> "Smokey" <smo...@aol.com> wrote in messagenews:12rf8ehrknvac1f@news.supernews.com...
>
> > Robert wrote:
> >> Thanks for the reply Herb. Don't the event log errors I listed have
> >> something to do with the controller? The event source is percsas which
> >> is the Dell Perc Raid Controller. Also it says Thedevice,
> >> \Device\RaidPort0,didnotrespondwithinthetimeout
> >> period. I amnotsure why to try here. Should I reinstall the Raid
> >> drivers? I'mnotsure how to proceed.
>
> > At that point I would call Dell and see what they have to say, if it is a
> > newer server I would assume they could run some utils to test the RAID
> > controllerMe too (i.e., call Dell). (I didn't see you have these errors listed
> before.)
>
> You have a new server; contact the vendor and get it fixed.
Robert wrote:
> I've been working with them and even had a dell tech come out but no
> results. They suck. I may just ask them to replace it. I really need
> this up and running now.
>
> On Jan 24, 10:39 am, "Herb Martin" <n...@learnquick.com> wrote:
>> "Smokey" <smo...@aol.com> wrote in messagenews:12rf8ehrknvac1f@news.supernews.com...
>>
>>> Robert wrote:
>>>> Thanks for the reply Herb. Don't the event log errors I listed have
>>>> something to do with the controller? The event source is percsas which
>>>> is the Dell Perc Raid Controller. Also it says Thedevice,
>>>> \Device\RaidPort0,didnotrespondwithinthetimeout
>>>> period. I amnotsure why to try here. Should I reinstall the Raid
>>>> drivers? I'mnotsure how to proceed.
>>> At that point I would call Dell and see what they have to say, if it is a
>>> newer server I would assume they could run some utils to test the RAID
>>> controllerMe too (i.e., call Dell). (I didn't see you have these errors listed
>> before.)
>>
>> You have a new server; contact the vendor and get it fixed.
>
Are the errors still being produced? If so then yeah, I would say either
fix it or replace it...
Dell is replacing it. What a hunk of junk and 2 weeks wasted.
On Jan 24, 12:55 pm, Smokey <smo...@aol.com> wrote:
> Robert wrote:
> > I've been working with them and even had a dell tech come out but no
> > results. They suck. I may just ask them to replace it. I really need
> > this up and running now.
>
> > On Jan 24, 10:39 am, "Herb Martin" <n...@learnquick.com> wrote:
> >> "Smokey" <smo...@aol.com> wrote in messagenews:12rf8ehrknvac1f@news.supernews.com...
>
> >>> Robert wrote:
> >>>> Thanks for the reply Herb. Don't the event log errors I listed have
> >>>> something to do with the controller? The event source is percsas which
> >>>> is the Dell Perc Raid Controller. Also it says Thedevice,
> >>>> \Device\RaidPort0,didnotrespondwithinthetimeout
> >>>> period. I amnotsure why to try here. Should I reinstall the Raid
> >>>> drivers? I'mnotsure how to proceed.
> >>> At that point I would call Dell and see what they have to say, if it is a
> >>> newer server I would assume they could run some utils to test the RAID
> >>> controllerMe too (i.e., call Dell). (I didn't see you have these errors listed
> >> before.)
>
> >> You have a new server; contact the vendor and get it fixed.Are the errors still being produced? If so then yeah, I would say either
> fix it or replace it...
FYI , google replaced the box and the new box works great. Must have
been the raid controller or one of the drives.
On Jan 25, 12:44 pm, "Robert" <robert.b.wal...@gmail.com> wrote:
> Dell is replacing it. What a hunk of junk and 2 weeks wasted.
>
> On Jan 24, 12:55 pm, Smokey <smo...@aol.com> wrote:
>
> > Robert wrote:
> > > I've been working with them and even had a dell tech come out but no
> > > results. They suck. I may just ask them to replace it. I really need
> > > this up and running now.
>
> > > On Jan 24, 10:39 am, "Herb Martin" <n...@learnquick.com> wrote:
> > >> "Smokey" <smo...@aol.com> wrote in messagenews:12rf8ehrknvac1f@news.supernews.com...
>
> > >>> Robert wrote:
> > >>>> Thanks for the reply Herb. Don't the event log errors I listed have
> > >>>> something to do with the controller? The event source is percsas which
> > >>>> is the Dell Perc Raid Controller. Also it says Thedevice,
> > >>>> \Device\RaidPort0,didnotrespondwithinthetimeout
> > >>>> period. I amnotsure why to try here. Should I reinstall the Raid
> > >>>> drivers? I'mnotsure how to proceed.
> > >>> At that point I would call Dell and see what they have to say, if it is a
> > >>> newer server I would assume they could run some utils to test the RAID
> > >>> controllerMe too (i.e., call Dell). (I didn't see you have these errors listed
> > >> before.)
>
> > >> You have a new server; contact the vendor and get it fixed.Are the errors still being produced? If so then yeah, I would say either
> > fix it or replace it...
"Robert" <robert.b.walden@gmail.com> wrote in message
news:1170127245.118101.233060@v33g2000cwv.googlegroups.com...
> FYI , google replaced the box and the new box works great. Must have
> been the raid controller or one of the drives.
Great news.
I wonder if Google will do anything for my refrigerator? <grin>
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
Posting Permissions
Reply With Quote
Bookmarks