LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-10-2017, 08:40 PM   #1
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Rep: Reputation: Disabled
Call Trace error on Slackware 14.02


Good evening, first time poster go easy

This error is on Slackware 14.2
I have this Call Trace error I would like to get more information about. Tell me if I'm wrong, but I believe the init process is failing to boot? According to what I know, after GRUB boots the kernel loads, executes the /sbin/init process then after init loads, the kernel executes runlevel programs. So according to that I believe init is the problem here, and from the error that says "Kernel panic - not syncing: No init found" . But what do the Call Trace Errors mean? And ideas?

Picture: http://imgur.com/a/vFoZC

EDIT: additions

Last edited by rocko11; 03-13-2017 at 09:00 AM.
 
Old 03-10-2017, 10:01 PM   #2
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,956

Rep: Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952
Quote:
Originally Posted by rocko11 View Post
Good evening, first time poster go easy

This error is on Slackware 14.02
Maybe you should use the correct version number

I'm joking, but FYI, it is 14.2, not 14.02. Not a huge deal and since it is your first time, I'll let it slide

Quote:
Originally Posted by rocko11 View Post
I have this Call Trace error I would like to get more information about. Tell me if I'm wrong, but I believe the init process is failing to boot? According to what I know, after GRUB boots the kernel loads, executes the /sbin/init process then after init loads, the kernel executes runlevel programs. So according to that I believe init is the problem here, and from the error that says "Kernel panic - not syncing: No init found" . But what do the Call Trace Errors mean? And ideas?

Picture: http://imgur.com/a/vFoZC

EDIT: additions
So, can you give us a bit of background? Is this after a fresh install or did you make some changes and then this occurred? Or did it just happen randomly after a reboot?

Reading online for "init not found" errors, the majority of them seem to imply it is a harddrive issue and that running fsck on your root partition may fix this. To do that, you can boot off your installation media and once you get to the prompt, you can run fsck -y /dev/sda1 (replacing sda1 with your correct root partition -- and the -y option will try to automatically fix any errors it finds).
 
Old 03-10-2017, 10:27 PM   #3
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
This happened after a reboot of the machine. I will look into running fsck when I have access to the machine and I will keep you updated.
 
Old 03-13-2017, 08:21 AM   #4
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
Fsck output said clean.
 
Old 03-13-2017, 08:43 AM   #5
GazL
Senior Member
 
Registered: May 2008
Posts: 4,315
Blog Entries: 7

Rep: Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766
Quote:
Originally Posted by bassmadrigal View Post
it is 14.2, not 14.02.
I noticed a "3.10.17 #2" tucked away on that screen-shot, so it looks more like an unpatched 14.1. Either that or the bootloader is misconfigured and picking up an old kernel image for some reason.


I suspect this is a misconfigured bootloader/initrd rather than hardware or fs corruption.
 
Old 03-13-2017, 11:18 AM   #6
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
I suspect this is a misconfigured bootloader/initrd rather than hardware or fs corruption.
How do I check these?
 
Old 03-13-2017, 11:21 AM   #7
GazL
Senior Member
 
Registered: May 2008
Posts: 4,315
Blog Entries: 7

Rep: Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766Reputation: 1766
As you're using grub I'm not really best placed to advise on that as I've always avoided it (favouring lilo) but first thing would be to ensure you're specifying the right root device. I'm sure someone with more grub knowledge than I will be along shortly to provide a little more insight than I can.

Last edited by GazL; 03-13-2017 at 11:23 AM.
 
Old 03-13-2017, 02:52 PM   #8
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
Just a quick update!
I tried this:

Code:
grub> set root=(hd0,1)
grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1
grub> initrd /boot/initrd.img-3.13.0-29-generic
grub> boot
Good news is, the system booted, but my NIS is broken now

EDIT: After a reboot I get the same Call Trace error

Last edited by rocko11; 03-13-2017 at 03:24 PM. Reason: Additions
 
Old 03-13-2017, 04:01 PM   #9
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,956

Rep: Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952Reputation: 1952
Like GazL, I'm not familiar at all with grub as I've always preferred lilo, but that command might temporarily set the kernel, but maybe not permanently (honestly, no clue... just a guess). I know many users on here will run a command to update their grub... I think it is the following:

Code:
grub-mkconfig -o /boot/grub/grub.cfg
 
Old 03-13-2017, 05:35 PM   #10
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 756

Rep: Reputation: 53
Hi rocko11

My impression from the screenshot is that that the kernel starts to load, but fails to find the root partition, so can't launch init.
If you were successfully booting before this error, then I suspect you have somehow changed the drive assignments from what grub is expecting. This happened to me recently on my desktop when I disconnected a hard drive with another OS on it.
End result is that /etc/fstab created when you installed slackware has an incorrect / (root) assignment.


If this were to be the case (and we haven't got much to go on), then what I would do is:
1. Boot from slackware install medium (dvd)
2. At the root prompt, run fdisk -l to find the / linux partition - I presume this is /dev/sda1
3. mount your filesystem - #mount -t auto /dev/sda1 /mnt
4. Now check your fstab - nano /mnt/etc/fstab

if there is an inconsistency between the / partition here and what you found in the the fdisk -l command, edit fstab to match. (ctrl-x to save)

exit everything, eject disk and reboot.

If that doesn't work, then we have to chmod into the filesystem to run the command that bassmadrigal gave earlier, but one thing at a time...

tobyl
 
Old 03-13-2017, 05:45 PM   #11
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
My Slackware partition is on /dev/sda3. I have Ubuntu installed on /dev/sda1. I would post the output of fdisk -l and such but I can't remote into the machine . I won't be back in the office until Wed, so I can give you more information then.
 
Old 03-13-2017, 06:10 PM   #12
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 756

Rep: Reputation: 53
Ok, well if you can boot into Ubuntu ok, we can skip the install disk part and start from step 2.

I'm puzzled that you didn't use /dev/sda3 in your grub prompt commands that you issued in your earlier post though.

tobyl
 
Old 03-13-2017, 06:21 PM   #13
rocko11
LQ Newbie
 
Registered: Mar 2017
Posts: 7

Original Poster
Rep: Reputation: Disabled
I did use /dev/sda3 in my commands. I found that online and just copied and pasted it, substituting my own partitions. I have to use the disk because ubuntu default boots into a guest session and it's very limited.

Last edited by rocko11; 03-13-2017 at 06:31 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
insllation of gives trace/cmu-trace.cc:1531:9: error: stray \342 in program error rakeshpanchiwala Linux - Newbie 17 04-26-2013 01:28 AM
Sir, While installing ns2.34 on fedora 16 got the error : trace/cmu-trace.cc 1327:22 jeevanpinto Linux - Newbie 2 06-28-2012 03:35 AM
kernel error and call trace archdave Slackware 0 02-17-2009 01:45 AM
FC5 machine frozen w/ Call Trace error thetawaverider Fedora 1 02-11-2007 11:20 AM
Call Trace: azpaul Linux - Security 2 10-25-2006 12:20 AM


All times are GMT -5. The time now is 11:08 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration