Stopping boot messages on SuSE Linux

S

Slipstream

New Member
Hi,

I'm having fdisk failures at boot, but I can't see where the problem starts because the boot messages scroll by too fast. Is there a way to scroll back upward---or even to stop the boot process---so the messages can be read?

Thanks for any replies!
 
look into your log files under /var/log typically (may be slightly different) and then copy/paste any messages that could help us figure it out.

if you need help, go to terminal and type this
Code: 
ls -al /var

that will list all directories under /var. I can't remember off the top of my head what exact directory they are in, but if you copy/paste the results of the ls I can navigate you through.
 
Ok, I finally got some of this stuff figured out---in particular, how to read the files!

The only one I could open is /var/log/boot.msg. Nothing seems out of place, until it stops at lines:

Skipped services in runlevel 3: nfs nfsboot
<notice>killproc: kill(4274,3)

Seems like all the /dev/md still exist. But the file systems don't get mounted. I guess that happens after runlevel 3. Could this be mechanical failure?
 
I finally figured out how to read /var/log/boot.msg. Nothing seems out of place, until it stops at lines:

Skipped services in runlevel 3: nfs nfsboot
<notice>killproc: kill(4274,3)

Seems like all the /dev/md still exist. But the file systems don't get mounted. I guess that happens after runlevel 3.

What could this be?
 
Yes, I did that. There's nothing obviously wrong. It stops at runlevel 3, like I stated. Nothing more to report.

Just wish I could scroll upward through the actual boot messages to see where it all begins. I don't think it's all being logged.
 
Slipstream said:
Yes, I did that. There's nothing obviously wrong. It stops at runlevel 3, like I stated. Nothing more to report.

Just wish I could scroll upward through the actual boot messages to see where it all begins. I don't think it's all being logged.
Click to expand...

try

cat /var/log/boot.menu head -100

That will print the first 100 lines of the log file, but I doubt its that big...


can you boot into run level 1? and run a fsck?
 
cat /var/log/boot.menu head -100
Click to expand...

The file doesn't exist.



can you boot into run level 1?
Click to expand...

No, there's a problem with some module. I can't even login as root user.


I'm about to order a copy of Windows, but I'm still hopeful that this is hardware related...if that's something one can be hopeful about :-/
 
Formatted and reinstalled? Only about once every month or two, for the past year. Until recently, I've been running x86_64 SuSE; this is my first attempt at 32-bit.

The x86_64 caused lots of problems due to needing 32-bit libraries for certain apps. So now I decided to forgo that mess, and just run 32-bit. I guess it doesn't work either.

by the way, I ran memtest overnight; so far no errors. I also did a surface scan of all disks, which included a write test; no errors.
 
what OSes have you tried? Perhaps you have a rare configuration that is not supported?

Or, perhaps you do have hardware failure somewhere. Very strange issue you have.
 
You must log in or register to reply here.
Back
Top