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

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

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).

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.

Fsck output said clean.

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.

How do I check these?

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.

Just a quick update!
I tried this:

Good news is, the system booted, but my NIS is broken now

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

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:

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

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.

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

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.