Re: [foxboro] P91 Question
- From: Terry Doucet <doucet427@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 9 May 2012 12:57:09 -0400
Tom,I did not read back far enough to see that you had already done that.
Doing it again is not likely to help. Doing it the first time often helped me
at work and at home with computers. Sorry. Terry
> Subject: Re: [foxboro] P91 Question
> Date: Wed, 9 May 2012 11:57:35 -0400
> From: tchaiket@xxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
>
> Thanks for the feedback, Terry. Reseating all the cards was one of the
> first things we did after the first detection. Would you help me
> understand how doing it again might help?
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Terry Doucet
> Sent: Wednesday, May 09, 2012 11:38 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] P91 Question
>
> On next fail, you could try to re-seat the RAM.
> > Subject: Re: [foxboro] P91 Question
> > Date: Wed, 9 May 2012 11:32:34 -0400
> > From: tchaiket@xxxxxxxx
> > To: foxboro@xxxxxxxxxxxxx
> >
> > Just a quick update, folks.
> >
> > After one more reboot almost right after the last message, the machine
> > stayed on for almost a couple days before starting to crash again
> today.
> > The first crash, we had (kernel_stack_inpage_error) alarm. The second
> > event, we had a windows delay write failed. The latter makes me think
> > of how the controller is talking with the drives.
> >
> > Also, the Device Manager, I found Device 3 to be Intel 5000 Series
> > Chipset PCI Express x4 Port 3-25E3. Nothing is connected to the
> > corresponding PCI E slot.
> >
> > t
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Chaiket, Thom
> > Sent: Monday, May 07, 2012 1:06 PM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] P91 Question
> >
> > Thank you for the feedback, Tim and Shaun.
> >
> > I will check out the H90.
> >
> > No, plenty of space on the machine. Is Device 3 the controller? A
> > power supply?
> >
> > Just more information also. We replaced the battery, and let it
> charge
> > up. It's been 2 days since the replacement, and the machine still
> > crashes.
> >
> > I still would like to consider other options before replacing the
> > machine. Does anyone have experience with replacing the controller
> > (PERC5i to PERC6i)?
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Goldie, Shaun S
> > Sent: Thursday, May 03, 2012 5:02 PM
> > To: 'foxboro@xxxxxxxxxxxxx'
> > Subject: Re: [foxboro] P91 Question
> >
> > Is your P91 close to overloaded, without a RAID battery it has stopped
> > doing buffered writes (cache) and instead all writes are being written
> > directly to the HDD this is a bit slower but should not cause a P91 to
> > crash.
> > So either you are overloaded or there is a problem with a power supply
> /
> > controller as well
> > Shaun
> >
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Chaiket, Thom
> > Sent: Friday, 4 May 2012 6:35 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: [foxboro] P91 Question
> >
> > Folks-
> >
> >
> > I was hoping to get some ideas on tackling a recent problem at our
> > facility.
> >
> >
> >
> > Our P91 (Dell PowerEdge 2900) has been crashing intermittently for the
> > past couple days. We saw the below warnings in the Event Log around
> the
> > time of the first crash. We were able to restore the machine by
> cycling
> > power.
> >
> >
> >
> > Current capacity of the battery is below threshold: Controller 0
> (PERC
> > 5/I Adapter).
> >
> >
> >
> > BBU disabled; changing WB virtual disks to WT: Controller 0 (PERC 5/I
> > Adapter).
> >
> >
> >
> > [The battery mentioned above is connected directly to the Adapter. It
> > looks like it is powering up a memory card that's also connected to
> the
> > Adapter.]
> >
> >
> >
> > The indication on the tower also provides an error message:
> >
> >
> >
> > E171F PCI E Fatal Error B0 D3 F0
> >
> >
> >
> > In the subsequent crashes, we started seeing the below error message:
> >
> >
> >
> > Fatal firmware error: Driver detected possible FW hang, halting FW.:
> > Controller 0 (PERC 5/I Adapter).
> >
> >
> >
> > We are able to restore the machine through power cycling. At this
> > point, we reseated all the network cards. The problem still remains.
> >
> >
> >
> > Based on the Event Log, I am thinking that we have a bad battery or
> > adapter card. My questions for you all:
> >
> >
> >
> > 1. Has anyone encountered this problem and, if so, how did you go
> > about resolving it?
> > 2. Do you order the replacement parts through Dell or Invensys?
> I
> > spoke with Dell and the adapter assembly kit part number is GT281.
> Does
> > anyone know what the corresponding Foxboro P/N is?
> >
> >
> >
> > Any feedback would be greatly appreciated.
> >
> >
> >
> > t
> >
> >
> >
> > Thom Chaiket, PE, PMP
> >
> > SCADA Engineer
> >
> > Bergen County Utilities Authority
> >
> > (o) 201-807-5814
> >
> > (c) 201-954-0301
> >
> > (f) 201-807-8633
> >
> >
> >
> >
> >
> >
> >
> _______________________________________________________________________
> > This mailing list is neither sponsored nor endorsed by Invensys
> Process
> > Systems (formerly The Foxboro Company). Use the info you obtain here
> at
> > your own risks. Read
> http://www.thecassandraproject.org/disclaimer.html
> >
> > foxboro mailing list:
> //www.freelists.org/list/foxboro
> > to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> >
> >
> >
> >
> > NOTICE - This message and any attached files may contain information
> > that is confidential, legally privileged or proprietary. It is
> intended
> > only for use by the intended recipient. If you are not the intended
> > recipient or the person responsible for delivering the message to the
> > intended recipient, be advised that you have received this message in
> > error. Any dissemination, copying, use or re-transmission of this
> > message or attachment, or the disclosure of any information therein,
> is
> > strictly forbidden. BlueScope Steel Limited does not represent or
> > guarantee that this message or attachment is free of errors, virus or
> > interference.
> >
> > If you have received this message in error please notify the sender
> > immediately and delete the message. Any views expressed in this email
> > are not necessarily the views of BlueScope Steel Limited.
> >
> >
> >
> _______________________________________________________________________
> > This mailing list is neither sponsored nor endorsed by Invensys
> Process
> > Systems (formerly The Foxboro Company). Use the info you obtain here
> at
> > your own risks. Read
> http://www.thecassandraproject.org/disclaimer.html
> >
> > foxboro mailing list:
> //www.freelists.org/list/foxboro
> > to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> >
> >
> >
> >
> >
> _______________________________________________________________________
> > This mailing list is neither sponsored nor endorsed by Invensys
> Process
> > Systems (formerly The Foxboro Company). Use the info you obtain here
> at
> > your own risks. Read
> http://www.thecassandraproject.org/disclaimer.html
> >
> > foxboro mailing list:
> //www.freelists.org/list/foxboro
> > to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> >
> >
> >
> >
> _______________________________________________________________________
> > This mailing list is neither sponsored nor endorsed by Invensys
> Process
> > Systems (formerly The Foxboro Company). Use the info you obtain here
> at
> > your own risks. Read
> http://www.thecassandraproject.org/disclaimer.html
> >
> > foxboro mailing list:
> //www.freelists.org/list/foxboro
> > to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> >
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
