SuSe crashes with no error message .

[Brown-Brown]

Hi all,

Currently I am running the Enterprise Desktop 10 and recently the performance has not been the best . My computer has crashed at least 3 times with no error message popping up... the only thing is that everything freezes up on the screen. What I have noticed quite different while booting my machine up I get tons of lines like this:

Trans replayed: mountid 19, transid 133, desc 7983, len 2, commit
7986, next trans offset 7969
Trans replayed: mountid 19, transid 134, desc 7987, len 1, commit
7989, next trans offset 7972
Trans replayed: mountid 19, transid 135, desc 7990, len 17, commit
8008, next trans offset 7991

I consider myself a newbie in a learning stage !! please some help you could provide to avoid having my machine all frozen.

Thanks in advance,

Brown Brown

[Doog]

It sounds like your file system is corrupt. The link below kind of talks about your problem.
But that is all the more I know.

For all who use Reiser...

[gogalthorp]

The replay is because you turned the machine off without quiting. Think of it kind of like scandisk in windows but done for different reasons. These are transactions that were not yet committed to there final location or were corrupted. Think of it as a kind of cache. So when you restart, the journal is scanned (yes a journaling file system) and any corrupted, incomplete, etc transactions are replayed.

So this does not help at all in figuring out why the crash happened in the first place. There could be a bad sector on the hard drive. I use Spinright (not free) to scan the surface and correct hard disk error. Works with an OS.

You might try ctrl-alt-F1 to go to a virtual terminal and quit more gracefully. Of course if the keyboard is totally locked a hard reboot must be done.

[Brown-Brown]

Thanks Doog I have checked the link you gave me !.......gogalthorp, doog: if I follow the steps to solve the problem I am asked to install Suse in a different partition....... How is the best way to create a partition in my hard drive!!??? what would you recommend ???
Thank you for your help to both of you so far !

[gogalthorp]

please notice the date of the article referenced by Doog. It is 5 years old. The suggested action is already happening on your system.

I suggest that it is possible that you have a low level disk error. ie a corrupted sector(s) that may be causing your lockup. You need to scan the disk at a lower level then the file system. You need to get a low level scanner like Spinright. In my experience this is the best there is. But I'm sure that there may be some very good free ones available. You may be able to get something from your disk manufactures web site.