On Fri, Mar 11, 2011 at 8:51 AM, Simon Matter wrote:
> After decades in the high precision and electronics industry, I can tell
> you for sure that compressed air is not seen as a good choice. It blows
> the dust where it doesn't belong. That may not be a big problem with a
> cheap PC, but it's n
> Am 03/11/2011 03:03 AM, schrieb Nico Kadel-Garcia:
>> On Thu, Mar 10, 2011 at 6:49 PM, B.J.
>> McClure wrote:
>>>
>>> B.J. McClure keepert...@bellsouth.net
>>>
>>> Sent from MacBook-Air
>>>
>>>
>>> On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote:
>>>
On Thu, Mar 10, 2011 at 11:13 AM, M
Am 03/11/2011 03:03 AM, schrieb Nico Kadel-Garcia:
> On Thu, Mar 10, 2011 at 6:49 PM, B.J.
> McClure wrote:
>>
>> B.J. McClure keepert...@bellsouth.net
>>
>> Sent from MacBook-Air
>>
>>
>> On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote:
>>
>>> On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager
On Thu, Mar 10, 2011 at 6:49 PM, B.J. McClure wrote:
>
> B.J. McClure
> keepert...@bellsouth.net
>
> Sent from MacBook-Air
>
>
> On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote:
>
>> On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote:
>>
>>> Previous cleaning have been with canned compres
B.J. McClure
keepert...@bellsouth.net
Sent from MacBook-Air
On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote:
> On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote:
>
>> Previous cleaning have been with canned compressed air.
>> Thanks for the caution about vacuums and static. I may
>
On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote:
> Previous cleaning have been with canned compressed air.
> Thanks for the caution about vacuums and static. I may
> use the vacuum on the case fans from the outside. The
> case should provide an adequate static shield.
I've had good resul
centos-boun...@centos.org wrote:
>> Your board does not support DDR2. (url for MSI KT3 Ultra)
>> "Support 2.5v DDR200/266/333 DDR SDRAM DIMM
>
> The OP says this:
>
>> House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
>
> Somehow, info has gotten crossed...
Possibility... Please excuse...
>Your board does not support DDR2. (url for MSI KT3 Ultra)
>"Support 2.5v DDR200/266/333 DDR SDRAM DIMM
The OP says this:
>House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
Somehow, info has gotten crossed...
___
CentOS mailing list
CentOS@centos.
centos-boun...@centos.org wrote:
> On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager
> wrote:
>> Dr. Ed Morbius wrote:
>>
>>> If the issue is repeated but rare system failures on one of a set of
>>> similarly configured hosts, I'd RMA the box and get a replacement.
>>> End of story.
>>
>> I'll rep
centos-boun...@centos.org wrote:
> Simon Matter wrote:
>
> The MB docs/website don't mention ECC support, but I presume
> it is as part of the DDR2 spec.
> I'll check whether the memory has ECC. If not, this is a reasonable
upgrade.
Your board does not support DDR2.
See
http://service.msicompu
Alexander Arlt wrote:
> Am 03/10/2011 11:04 AM, schrieb Simon Matter:
>> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can
>> really do bad things because it is not a perfect insulator.
>
> Never ever do that. Especially not inside the machine. There is a real
> risk of simply
Simon Matter wrote:
>> One fan is listed as 0 rpm. Something to look into.
>
> Hmm, much has been said now in this thread and I know how difficult it can
> be to find such an issue. However, I suggest not to throw in too many new
> tools in parallel. And, be careful of how to interpret any info
On Thursday, March 10, 2011 05:35:29 am Rudi Ahlers wrote:
> I prefer to use a dust blower instead. It doesn't risk pulling loose
> components with "dry" or loose "soldering"
I use both: antistatic canned air to blow the dust and a metal-tubed vacuum
rested on a part of the case away from any boa
Am 03/10/2011 11:04 AM, schrieb Simon Matter:
> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can
> really do bad things because it is not a perfect insulator.
Never ever do that. Especially not inside the machine. There is a real
risk of simply vacuuming smaller components li
On Thu, Mar 10, 2011 at 12:10 PM, John Hodrien wrote:
> On Thu, 10 Mar 2011, Simon Matter wrote:
>
>> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can
>> really do bad things because it is not a perfect insulator.
>
> Take the wrong vacuum cleaner and static your machine to de
On Thu, 10 Mar 2011, Simon Matter wrote:
> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can
> really do bad things because it is not a perfect insulator.
Take the wrong vacuum cleaner and static your machine to death.
jh
___
CentOS
> compdoc wrote:
>>> According to the man page, it apparently needs a kernel driver
>>> named OpenIMPI, which it claims is installed in standard
>>> distributions. I don't find it on my system.
>>
>>
>> lm_sensors is another, and I think installs ready to use from the repos.
>
> sensors says that
On Wed, 9 Mar 2011, compdoc wrote:
> +36C and +39C are likely your cpu and motherboard temps. You have to look at
> the temps in the cmos and match them.
>
> The +87C is likely just a miss-reading by lm_sensors. Anything running that
> hot won't be stable.
In testing nVidia graphics cards to dest
Dr. Ed Morbius wrote:
>
> You're NOT obliged to repeat information you've already posted (e.g.:
> home-brew system), but it's helpful to front-load data rather than have
> us tease it out of you.
No intention to have anyone tease information out of me.
The subject line says that the system is C
On 03/09/11 4:06 PM, Michael Eager wrote:
> I'll compare the values from lm_sensors with the bios
> temps to see if they are in line.
I find lm_sensors tends to be pretty useless on server grade hardware,
as opposed to desktop. server hardware tends to have an IPMI
management processor, which
>1280C is about the melting point of iron. Wow!
The degree symbol was converted to text after pasting into the email and
became an '0'
It actually shows 128C in lm_sensors.
Great little program, tho.
___
CentOS mailing list
CentOS@centos.org
http
compdoc wrote:
> Err, that should read 128C
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
> Of compdoc
> Sent: Wednesday, March 09, 2011 4:50 PM
> To: 'CentOS mailing list'
> Subject: Re: [CentOS] Se
Rudi Ahlers wrote:
> As far as I can see you were giving a bucked load of advice, which you
> haven't even bothered to follow yet. You're the only one who could
> actually do anything about the problem.
I have followed quite a bit of the advice, which I have
appreciated and noted. I've set up th
On 03/09/11 2:31 PM, Michael Eager wrote:
> I'll repeat: this is a house-made system. There's no vendor to RMA to.
> It seems obvious to me: RMA is not a diagnostic tool.
>
you built it, you get to fix it. sometimes the initial savings in
capital can come back and bite you in time wasted.
_
Err, that should read 128C
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of compdoc
Sent: Wednesday, March 09, 2011 4:50 PM
To: 'CentOS mailing list'
Subject: Re: [CentOS] Server hangs on CentOS 5.5
+36C and +39C are likely yo
+36C and +39C are likely your cpu and motherboard temps. You have to look at
the temps in the cmos and match them.
The +87C is likely just a miss-reading by lm_sensors. Anything running that
hot won't be stable.
I use AMD as well, and lm_sensors tells me something is 128°C.
heh
___
On Mar 9, 2011, at 3:26 PM, compdoc wrote:
>> When we removed the heatsinks, the
>> cpus came up with them, even though
>> the socket lever was down in the lock position.
>
> I've seen that in HP desktops too - the thermal paste became a hardened glue
> and the cpu gets pulled right out .
>
> An
On Thu, Mar 10, 2011 at 1:17 AM, Michael Eager wrote:
> Rudi Ahlers wrote:
>> On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager wrote:
>>> Dr. Ed Morbius wrote:
>>>
If the issue is repeated but rare system failures on one of a set of
similarly configured hosts, I'd RMA the box and get a r
compdoc wrote:
>> According to the man page, it apparently needs a kernel driver
>> named OpenIMPI, which it claims is installed in standard
>> distributions. I don't find it on my system.
>
>
> lm_sensors is another, and I think installs ready to use from the repos.
sensors says that the three
>When we removed the heatsinks, the
>cpus came up with them, even though
>the socket lever was down in the lock position.
I've seen that in HP desktops too - the thermal paste became a hardened glue
and the cpu gets pulled right out .
Another reason to leave the heat sink on.
on 14:31 Wed 09 Mar, Michael Eager (ea...@eagerm.com) wrote:
> Dr. Ed Morbius wrote:
>
> >If the issue is repeated but rare system failures on one of a set of
> >similarly configured hosts, I'd RMA the box and get a replacement. End
> >of story.
>
> I'll repeat: this is a house-made system. Th
On Mar 9, 2011, at 3:06 PM, compdoc wrote:
>> compdoc wrote:
>>> I'll re-seat the CPU, heatsink, and fan on the next downtime.
>>>
>>> Is the CPU overheating? Pointless to reseat the cpu or even remove the
>>> heatsink, if not.
>
>> No evidence to suggest that it is.
>
>
> As much as I love te
Rudi Ahlers wrote:
> On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager wrote:
>> Dr. Ed Morbius wrote:
>>
>>> If the issue is repeated but rare system failures on one of a set of
>>> similarly configured hosts, I'd RMA the box and get a replacement. End
>>> of story.
>> I'll repeat: this is a hous
>According to the man page, it apparently needs a kernel driver
>named OpenIMPI, which it claims is installed in standard
>distributions. I don't find it on my system.
lm_sensors is another, and I think installs ready to use from the repos.
Failing that, you should reboot and look in the mother
> compdoc wrote:
>> I'll re-seat the CPU, heatsink, and fan on the next downtime.
> >
> >Is the CPU overheating? Pointless to reseat the cpu or even remove the
>> heatsink, if not.
>No evidence to suggest that it is.
As much as I love telling anecdotes, I have none to tell you concerning cpu
res
On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager wrote:
> Dr. Ed Morbius wrote:
>
>> If the issue is repeated but rare system failures on one of a set of
>> similarly configured hosts, I'd RMA the box and get a replacement. End
>> of story.
>
> I'll repeat: this is a house-made system. There's n
m.r...@5-cent.us wrote:
> Michael Eager wrote:
>> compdoc wrote:
I'll re-seat the CPU, heatsink, and fan on the next downtime.
>>> Is the CPU overheating? Pointless to reseat the cpu or even remove the
>>> heatsink, if not.
>> No evidence to suggest that it is.
>
> Have you used ipmitool to s
Dr. Ed Morbius wrote:
> If the issue is repeated but rare system failures on one of a set of
> similarly configured hosts, I'd RMA the box and get a replacement. End
> of story.
I'll repeat: this is a house-made system. There's no vendor to RMA to.
It seems obvious to me: RMA is not a diagnos
Michael Eager wrote:
> compdoc wrote:
>>> I'll re-seat the CPU, heatsink, and fan on the next downtime.
>>
>> Is the CPU overheating? Pointless to reseat the cpu or even remove the
>> heatsink, if not.
>
> No evidence to suggest that it is.
Have you used ipmitool to see what the temperatures are?
m.r...@5-cent.us wrote:
> Michael Eager wrote:
>
>> I'll have to stop the server to find out what the installed bios version
>> is and see whether there is an update. Most bios updates appear to only
>> change supported CPUs. Something else for the next downtime.
>
> Nope: dmidecode, or lshw, i
compdoc wrote:
>> I'll re-seat the CPU, heatsink, and fan on the next downtime.
>
> Is the CPU overheating? Pointless to reseat the cpu or even remove the
> heatsink, if not.
No evidence to suggest that it is.
--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-
On 03/09/11 10:29 AM, Michael Eager wrote:
> I'll re-seat the CPU, heatsink, and fan on the next downtime.
do have on hand the suppplies to clean off the old heatsink goo (I use
alcohol pads for this), and some fresh heatsink goop
check all fans when its powered off that they spin easily. I've
> I'll re-seat the CPU, heatsink, and fan on the next downtime.
Is the CPU overheating? Pointless to reseat the cpu or even remove the
heatsink, if not.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
on 10:29 Wed 09 Mar, Michael Eager (ea...@eagerm.com) wrote:
> Les Mikesell wrote:
>
> > Note that overheating can be localized or a bad heat sink mounting or
> > fan on a CPU.
>
> I'll re-seat the CPU, heatsink, and fan on the next downtime.
Very strongly advised. It's a simple and very cheap
On 3/9/2011 12:47 PM, Dr. Ed Morbius wrote:
>
> That represents an accounting failure, as opex is now subsidizing capex.
> Troubleshooting of known bad equipment should be an opex chargeback
> against capex or some capital reserve.
>
> This requires clueful beancounters. Recent economic/business/f
on 11:52 Wed 09 Mar, Les Mikesell (lesmikes...@gmail.com) wrote:
> On 3/9/2011 11:32 AM, Michael Eager wrote:
> Memory diagnostics may take days to catch a problem. Did you check for
> a newer bios for your MB? I mentioned before that it seemed strange,
> but I've seen that fix mysterious prob
Michael Eager wrote:
> I'll have to stop the server to find out what the installed bios version
> is and see whether there is an update. Most bios updates appear to only
> change supported CPUs. Something else for the next downtime.
Nope: dmidecode, or lshw, is your friend.
mark
on 10:37 Wed 09 Mar, Lamar Owen (lo...@pari.edu) wrote:
> On Wednesday, March 09, 2011 10:16:34 am Brunner, Brian T. wrote:
> > This would be far cheaper than the time spent troubleshooting the
> > running (sometimes hanging) system.
>
> Let me interject here, that from a budgeting standpoint 'che
on 07:06 Wed 09 Mar, Michael Eager (ea...@eagerm.com) wrote:
> Dr. Ed Morbius wrote:
> >on 09:24 Tue 08 Mar, Michael Eager (ea...@eagerm.com) wrote:
> >>Hi --
> >>
> >>I'm running a server which is usually stable, but every
> >>once in a while it hangs. The server is used as a file
> >>store using
on 10:05 Wed 09 Mar, Lamar Owen (lo...@pari.edu) wrote:
> On Tuesday, March 08, 2011 04:44:54 pm Dr. Ed Morbius wrote:
> > I'd very strongly recommend you configure netconsole.
>
> Ok, now this is useful indeed. Thanks for the information, even
> though I'm not the OP While I suspected the
> During the next server downtime, I'll re-seat RAM
If the ram is passing memtest86+, I think reseating only serves to introduce
dust and dirt into an area where a tight connection was previously keeping
it out.
Gently press them down to make sure they're seated, sure. But pulling them
out only
Les Mikesell wrote:
> Note that overheating can be localized or a bad heat sink mounting or
> fan on a CPU.
I'll re-seat the CPU, heatsink, and fan on the next downtime.
Heat related problems usually present as a system which fails
and will not reboot immediately, but will after they sit for a
Michael Eager wrote:
> m.r...@5-cent.us wrote:
>> Michael Eager wrote:
>>> John Hodrien wrote:
On Wed, 9 Mar 2011, Michael Eager wrote:
>>
>> Here's one more, off-the-wall thought: do the setterm --powersave off,
>> and find some way to make it work, so that you can see what's on the
screen
>
m.r...@5-cent.us wrote:
> Michael Eager wrote:
>> John Hodrien wrote:
>>> On Wed, 9 Mar 2011, Michael Eager wrote:
>>>
The problem with randomly replacing various components, other than
the downtime and nuisance, is that there's no way to know that the
change actually fixed any probl
On 3/9/2011 11:32 AM, Michael Eager wrote:
>
> I'm not particularly interested in a listing of the myriad of
> hypothetical causes absent observable evidence and some of
> which are contradicted by evidence (such as overheating).
Note that overheating can be localized or a bad heat sink mounting o
Michael Eager wrote:
> John Hodrien wrote:
>> On Wed, 9 Mar 2011, Michael Eager wrote:
>>
>>> The problem with randomly replacing various components, other than
>>> the downtime and nuisance, is that there's no way to know that the
>>> change actually fixed any problem. When the base rate is one
>
John Hodrien wrote:
> On Wed, 9 Mar 2011, Michael Eager wrote:
>
>> The problem with randomly replacing various components, other than
>> the downtime and nuisance, is that there's no way to know that the
>> change actually fixed any problem. When the base rate is one
>> unknown system hang every
>>sure, if your time is worthless. you can easily burn a couple hours
>>recapping a motherboard, which typically exceeds the boards worth.
>
> Amen. It's not enough to replace the bulging caps - you need to replace
> all
> the caps of the same brand as the damaged ones. Otherwise you'll just be
>
On Wednesday, March 09, 2011 11:45:06 am Les Mikesell wrote:
> And if you are running Centos the one thing you
> don't need is to pay for extra licenses to cover the backup/development
> instances.
And this is significant, and really highlights the reasoning of the CentOS team
in 'bug-for'bug'
On Wednesday, March 09, 2011 10:48:29 am m.r...@5-cent.us wrote:
> Lamar Owen wrote:
> > Heat and airflow are two others.
> Hmmm... has the a/c been changed lately? Or maybe stuff outside the rack
> been moved, and so obstructed the airflow?
To followup a little, I had a motherboard one time, wit
On 3/9/2011 9:55 AM, Brunner, Brian T. wrote:
>
> This is where mental ossification amongst bean-counters can kill a
> company.
> "Economic Opportunity Cost" should raise its head here: What would we do
> with the $capex if we paid $opex vs what would we do with the $opex if
> we paid $capex. "The
>sure, if your time is worthless. you can easily burn a couple hours
>recapping a motherboard, which typically exceeds the boards worth.
Amen. It's not enough to replace the bulging caps - you need to replace all
the caps of the same brand as the damaged ones. Otherwise you'll just be
doing it ag
centos-boun...@centos.org wrote:
> On Wednesday, March 09, 2011 10:16:34 am Brunner, Brian T. wrote:
>> This would be far cheaper than the time spent troubleshooting the
>> running (sometimes hanging) system.
>
> Let me interject here, that from a budgeting standpoint
> 'cheaper' has to be interpr
Lamar Owen wrote:
> On Wednesday, March 09, 2011 10:16:34 am Brunner, Brian T. wrote:
>> Starting with RAM and Power Supply is not random ... They're "The Usual
>> Suspects".
>
> This is a very true statement.
>
> Heat and airflow are two others.
Hmmm... has the a/c been changed lately? Or maybe
On Wednesday, March 09, 2011 10:16:34 am Brunner, Brian T. wrote:
> This would be far cheaper than the time spent troubleshooting the
> running (sometimes hanging) system.
Let me interject here, that from a budgeting standpoint 'cheaper' has to be
interpreted in the context of which budget the co
On Wednesday, March 09, 2011 03:24:48 am Leen de Braal wrote:
> While you open the case, check for the bulging capacitor problem.
> Will have the effect you describe, freezing up the system so that even
> bios routines don't work (your fans).
> If that's the case, replace mainboard.
I've seen capa
centos-boun...@centos.org wrote:
> On Wed, 9 Mar 2011, Michael Eager wrote:
>
>> The problem with randomly replacing various components, other than
>> the downtime and nuisance, is that there's no way to know that the
>> change actually fixed any problem. When the base rate is one
>> unknown syst
On Wed, 9 Mar 2011, Michael Eager wrote:
> The problem with randomly replacing various components, other than
> the downtime and nuisance, is that there's no way to know that the
> change actually fixed any problem. When the base rate is one
> unknown system hang every few weeks, how many wees sh
Dr. Ed Morbius wrote:
> on 09:24 Tue 08 Mar, Michael Eager (ea...@eagerm.com) wrote:
>> Hi --
>>
>> I'm running a server which is usually stable, but every
>> once in a while it hangs. The server is used as a file
>> store using NFS and to run VMware machines.
>>
>> I don't see anything in /var/lo
On Tuesday, March 08, 2011 04:44:54 pm Dr. Ed Morbius wrote:
> I'd very strongly recommend you configure netconsole.
Ok, now this is useful indeed. Thanks for the information, even though I'm not
the OP While I suspected the facility might be there, I hadn't really dug
for it, but if this
On 03/09/11 1:34 AM, Leen de Braal wrote:
> Very often resulting in a damaged board, because you damage the via's when
> pulling the caps. But it is worth a try.
>
sure, if your time is worthless. you can easily burn a couple hours
recapping a motherboard, which typically exceeds the boards wort
> On Wed, Mar 9, 2011 at 10:24 AM, Leen de Braal wrote:
>>> m.r...@5-cent.us wrote:
Michael Eager wrote:
>>>
> House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
Any chance the problem's with the video card?
>>>
>>> Video is on the MB. It doesn't seem likely that it's
>>> the
On Wed, Mar 9, 2011 at 10:24 AM, Leen de Braal wrote:
>> m.r...@5-cent.us wrote:
>>> Michael Eager wrote:
>>
House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
>>>
>>> Any chance the problem's with the video card?
>>
>> Video is on the MB. It doesn't seem likely that it's
>> the video, sin
> m.r...@5-cent.us wrote:
>> Michael Eager wrote:
>
>>> House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
>>
>> Any chance the problem's with the video card?
>
> Video is on the MB. It doesn't seem likely that it's
> the video, since the system doesn't respond to network
> when it crashes.
>
>
on 10:31 Tue 08 Mar, Michael Eager (ea...@eagerm.com) wrote:
> Les Mikesell wrote:
> > On 3/8/2011 11:24 AM, Michael Eager wrote:
> >> Hi --
> >>
> >> I'm running a server which is usually stable, but every
> >> once in a while it hangs. The server is used as a file
> >> store using NFS and to run
on 09:24 Tue 08 Mar, Michael Eager (ea...@eagerm.com) wrote:
> Hi --
>
> I'm running a server which is usually stable, but every
> once in a while it hangs. The server is used as a file
> store using NFS and to run VMware machines.
>
> I don't see anything in /var/log/messages or elsewhere
> to
John R Pierce wrote:
>
>> Video is on the MB. It doesn't seem likely that it's
>> the video, since the system doesn't respond to network
>> when it crashes.
>
> bad video hardware or drivers can easily crash the system
>
> If its running an X windows display of any sort, I'd suggest trying it
> in
> Video is on the MB. It doesn't seem likely that it's
> the video, since the system doesn't respond to network
> when it crashes.
bad video hardware or drivers can easily crash the system
If its running an X windows display of any sort, I'd suggest trying it
in text-only mode. in /etc/initt
m.r...@5-cent.us wrote:
> Michael Eager wrote:
>> House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM.
>
> Any chance the problem's with the video card?
Video is on the MB. It doesn't seem likely that it's
the video, since the system doesn't respond to network
when it crashes.
It could be anyt
Michael Eager wrote:
> m.r...@5-cent.us wrote:
>> Michael Eager wrote:
>>> Brian Mathis wrote:
On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager
wrote:
>
> I'm running a server which is usually stable, but every
> once in a while it hangs. The server is used as a file
> sto
Michael Eager wrote:
> m.r...@5-cent.us wrote:
>> Suggestion 1: ->from the console<-, run
>> setterm --powersave off
>> That way, even if you connect a monitor (in our, uh, "computer labs", we
>> have a monitor-on-a-stick), you'll still see what's on the screen at the
>> end, not the power save bl
Scott Silva wrote:
> Did you try the obvious stuff for older equipment? Remove and reseat ALL cards
> and memory, several times, to clean off any oxidation from contacts.
> Blow out any dust and collected lint.
> reseat drive cables.
Not yet, but that's always a good idea.
--
Michael Eagere
m.r...@5-cent.us wrote:
> Michael Eager wrote:
>> Brian Mathis wrote:
>>> On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager wrote:
Hi --
I'm running a server which is usually stable, but every
once in a while it hangs. The server is used as a file
store using NFS and to run
compdoc wrote:
>> The only indication that I had that there was a problem (other
>> that attached systems were not accessing files) was that the
>> fan(s) on the server were louder than normal.
>
> Are you saying the fans were running faster than normal while it was hung?
> Or are they louder than
On 3/8/2011 12:31 PM, Michael Eager wrote:
>
>>> Any suggestions where I might look for a clue?
>>
>> Probably something hardware related. Bad memory, overheating, power
>> supply, etc. I've even seen some rare cases where a bios update would
>> fix it although it didn't make much sense for a mac
on 3/8/2011 10:20 AM Michael Eager spake the following:
> Brian Mathis wrote:
>> On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager wrote:
>>> Hi --
>>>
>>> I'm running a server which is usually stable, but every
>>> once in a while it hangs. The server is used as a file
>>> store using NFS and to ru
Michael Eager wrote:
> Brian Mathis wrote:
>> On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager wrote:
>>> Hi --
>>>
>>> I'm running a server which is usually stable, but every
>>> once in a while it hangs. The server is used as a file
>>> store using NFS and to run VMware machines.
>>>
>>> I don't
>The only indication that I had that there was a problem (other
>that attached systems were not accessing files) was that the
>fan(s) on the server were louder than normal.
Are you saying the fans were running faster than normal while it was hung?
Or are they louder than usual even while its runni
Les Mikesell wrote:
> On 3/8/2011 11:24 AM, Michael Eager wrote:
>> Hi --
>>
>> I'm running a server which is usually stable, but every
>> once in a while it hangs. The server is used as a file
>> store using NFS and to run VMware machines.
>>
>> I don't see anything in /var/log/messages or elsewh
Brian Mathis wrote:
> On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager wrote:
>> Hi --
>>
>> I'm running a server which is usually stable, but every
>> once in a while it hangs. The server is used as a file
>> store using NFS and to run VMware machines.
>>
>> I don't see anything in /var/log/messag
compdoc wrote:
>> I'm running a server which is usually stable, but every
>> once in a while it hangs.
>
>
> There can be many reasons for that. One thing I'm curious about - try
> looking at the reallocated sector count, and current pending sector count
> for your drives with smartctl.
Thanks f
On Tue, Mar 8, 2011 at 12:24 PM, Michael Eager wrote:
> Hi --
>
> I'm running a server which is usually stable, but every
> once in a while it hangs. The server is used as a file
> store using NFS and to run VMware machines.
>
> I don't see anything in /var/log/messages or elsewhere
> to indicate
>I'm running a server which is usually stable, but every
>once in a while it hangs.
There can be many reasons for that. One thing I'm curious about - try
looking at the reallocated sector count, and current pending sector count
for your drives with smartctl.
__
On 3/8/2011 11:24 AM, Michael Eager wrote:
> Hi --
>
> I'm running a server which is usually stable, but every
> once in a while it hangs. The server is used as a file
> store using NFS and to run VMware machines.
>
> I don't see anything in /var/log/messages or elsewhere
> to indicate any problem
Hi --
I'm running a server which is usually stable, but every
once in a while it hangs. The server is used as a file
store using NFS and to run VMware machines.
I don't see anything in /var/log/messages or elsewhere
to indicate any problem or offer any clue why the system
was hung.
Any suggesti
95 matches
Mail list logo
