I had various problems related with smartd - but I don’t think that it is your case. First examine if that was problem only with X server (/var/log/Xorg.0.log.old, ~/.xsession-errors.old). You may also look at /var/log/warn.
About smartd: I think if you don’t use it (I mean : if you don’t look at logs) simply disable it.
> About smartd: I think if you don’t use it (I mean : if you don’t look
> at logs) simply disable it.
DON’T DO THAT!
Gosh!
So you prefer not to know there is no oil in your car engine, instead of
having a “nasty” yellow light for a second when you “boot” the car?
You MUST have smartd enabled, so that you know when your disk really warns
about impending disaster, if it knows. It may destroy itself without
advance notice, but sometimes it does warn you. When it does, smartd can
save your year.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 2010-11-22 08:06, glistwan wrote:
>
> Hi,
>
> My system just crashed and I had to reboot. The only interesting
> message I have found in the logs before the crash was :
All those you have are irrelevant.
> My system is 32 bit openSUSE running latest KDE from the sable repo.
Insufficient data to compute.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
No, I don’t mean that - I also have smartd always working, but I also check the logs via scripts everyday or configure smart to warn me about any problem in some way. I really doubt if there is some desktop user, who watch the logs everyday.
Maybe there some application/program/applet which can notify user with problems detected by smart - if yes, then I’m sorry for my stupidy. If no - what is the purpose of this yellow light if you don’t see it?
I think most likely it was frozen KDE or X although I can’t tell for sure cause my brother turned off the computer by pushing and holding the power on button.
As he said trying to turn it of by shortly pushing the button didn’t work (it normally does although not sure if that works with frozen KDE).
I’ve already checked /var/log/messages before the supposed crash and as far as I could tell nothing more relevant than what I pasted in the initial post was there.
I can tell provide more info once I get home and that won’t be before 18.00 CET as I’m at work at the moment
> No, I don’t mean that - I also have smartd always working, but I also
> check the logs via scripts everyday or configure smart to warn me about
> any problem in some way. I really doubt if there is some desktop user,
> who watch the logs everyday.
I do.
> Maybe there some application/program/applet which can notify user with
> problems detected by smart - if yes, then I’m sorry for my stupidy. If
> no - what is the purpose of this yellow light if you don’t see it?
In linux, the yellow light is the /var/log/warn log, and as admin you have
to look at it everyday, even if it is your bedroom computer >:-P
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Yes. On the other side it can be computer for your younger brother who doesn’t know what smartd is. Or for anyone else, who doesn’t suppose to be able work with logs file.
But to end this - I’m sure that glistwan now knows most pros and cons for smartd
Nov 22 06:13:58 linux-lx7s kernel: [199858.957799] martian source 199.1.1.34 from 199.1.1.34, on dev wlan0
Nov 22 06:13:58 linux-lx7s kernel: [199858.957806] ll header: 00:25:d3:cc:fe:bf:1c:af:f7:2b:e1:4e:08:00
However I’m seeing it now and it doesn’t cause a system crash. Is it in any way more relevant than the smartd logs ?
I had various problems related with smartd - but I don’t think that it is your case. First examine if that was problem only with X server (/var/log/Xorg.0.log.old, ~/.xsession-errors.old).
I don’t have ~/.xsession-errors.old file and ~./xsession-errors is a bit useless as no time and date is specified inside, however it looks quite healthy.
No - those warnings about martian source are irrelevant to your problem. There warn about packages which appears where they shouldn’t. You can disable it using command:
I don’t have ~/.xsession-errors.old file and ~./xsession-errors is a bit useless as no time and date is specified inside, however it looks quite healthy.
Mostly the last messages in xsession-errors is important - after a crash nothing more will appended. And you can always look at /var/log/Xorg.0.log.old.
But if now your system is working properly you should just wait for next crash - to find out if you can reproduce it or it was some various bug.
GSmartControl is a graphical user interface for smartctl, which is a tool for
querying and controlling SMART (Self-Monitoring, Analysis, and
[more]
GSmartControl is a graphical user interface for smartctl, which is a tool for
querying and controlling SMART (Self-Monitoring, Analysis, and Reporting
Technology) data in hard disk drives. It allows you to inspect the drive’s
SMART data to determine its health, as well as run various tests on it.