LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-21-2007, 06:12 PM   #1
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Rep: Reputation: Disabled
Attempted to kill init


Heres scenario,


I installed 2.6.18, then upgraded slackware, with slackware-current , however i made slight mistake in steps
i didnt take before /sbin/lilo before *.new are taking place but after, is that a problem?


then i wanted to source kernel customized install to 2.6.21.1 and after i created initrd.gz entered in lilo.conf initrd=/boot/initrd.gz ln -sf /etc/rc.d/rc.modules-2.6.21.1(chmod for that file is 755) rc.modules

/sbin/lilo
it wont boot, says no kernel modules found for linux 2.6.21.1
mount> mounting /dev/sda1 on /mnt failed
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
Kernel panic - not syncing: Attempted to kill init!

however i can boot back to 2.6.18.

Where could be the problem?

Thanks!


p.s. normally from slack 11, 2.6.18 i can go to 2.6.21.1 customized kernel no problem. but its my first time upgrading slack, so i dont know where could be the problem
 
Old 05-21-2007, 06:17 PM   #2
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Is there /lib/modules/kernel-version?
 
Old 05-21-2007, 06:30 PM   #3
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
yes there is!
 
Old 05-21-2007, 07:56 PM   #4
slimm609
Member
 
Registered: May 2007
Location: Chas, SC
Distribution: slackware, gentoo, fedora, LFS, sidewinder G2, solaris, FreeBSD, RHEL, SUSE, Backtrack
Posts: 428

Rep: Reputation: 65
how many partition do u have for slackware?
 
Old 05-21-2007, 08:25 PM   #5
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 70
It looks like a problem with the initrd. Did you create a new initrd with your new kernel?
 
Old 05-22-2007, 03:22 AM   #6
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
i got /, /usr, /opt /home partitions ext3, just wondering also how its possible to create lvm from the start and install it? I tried to do that on the beginning but it had to be ext3 at least in order to install slack 11, from my expirience.

Wheres the catch on that one?

yes i thought about initrd, so i tried to delete initrd.gz from /boot and run again

mkinitrd -c -k vmlinuz-2.6.21.1. and same thing happens!
 
Old 05-22-2007, 04:05 AM   #7
slimm609
Member
 
Registered: May 2007
Location: Chas, SC
Distribution: slackware, gentoo, fedora, LFS, sidewinder G2, solaris, FreeBSD, RHEL, SUSE, Backtrack
Posts: 428

Rep: Reputation: 65
take a look at the man page for mkinitrd

try

mkinitrd -c -k 2.6.21.1 -m jbd:ext3 -f ext3 -r /dev/(rootdev_here)
 
Old 05-22-2007, 04:08 AM   #8
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
from bootable dvd ive recreated initrd

and now gives error

cannot open root device "801" or unknown-block (8,1)
Please append a correct "root=" boot option
Kernel panic - not syncing : VFS: Unable to mount root fs on unknown-block(8,1)
 
Old 05-22-2007, 04:10 AM   #9
slimm609
Member
 
Registered: May 2007
Location: Chas, SC
Distribution: slackware, gentoo, fedora, LFS, sidewinder G2, solaris, FreeBSD, RHEL, SUSE, Backtrack
Posts: 428

Rep: Reputation: 65
did u make sure to include whatever format you used for the fs (ext3, reiserfs, etc) into the new kernel?

also verify your lilo.conf post it if you can
 
Old 05-22-2007, 05:44 AM   #10
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
to notify: if i create mkinitrd for 2.6.21.1 when booting from 2.6.18 kernel

i get kill init error, as i posted 1st , if i make mkinitrd from bootable dvd then second error occurs, now note

before when i havent tried to makeinitrd from bootable dvd i didnt need to enter root = /dev/sda1 in lilo.conf

now when i done so, to go back to kernel 2.6.18 root= /dev/sda1 has to be included otherwise also kernel 2.6.18 wont boot

note also that i have to include lb32 in lilo.conf otherwise warning was issued.

When upgrading kernel 2.6.18, to 2.6.21 from slack11 without upgrading with slackware-current i successfully installed 2.6.21.1 without a problem and lba32 warning wasnt issued.
but now since i upgraded with slackware-current (and didnt do correctly /sbin/lilo - check my post from the beggining) those problems occurs!

heres lilo.conf, when booting from 2.6.18, and note theres no initrd = /boot/initrd.gz since i had to remove it in order 2.6.18 to work

lilo.conf


# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
lba32
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
label = Linux
read-only
root = /dev/sda1
# Linux bootable partition config ends


NOTE: when switching to 2.6.21.1. from /boot
i always do ln -sf vmlinuz-2.6.21.1 vmlinuz
ditto for config, and System.map and /etc/rc.d/rc.modules-2.6.21.1 rc.modules (i need it for customized kernel)


Thanks!
 
Old 05-22-2007, 07:00 AM   #11
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Do you have 2.6.21 modules installed? If you want additional filesystems support, you need either build it into the kernel or create it as module nad then make initrd. Run lilo after you create all symlinks (just before reboot).

Firstly fix your 2.6.18 kernel. Post what happens when you comment lba32, remove reference to 2.6.21 (check lilo) and do not load initrd.

EDIT: Read this for lvm: http://wiki.linuxquestions.org/wiki/...LVM-partitions

Last edited by Alien_Hominid; 05-22-2007 at 07:13 AM.
 
Old 05-22-2007, 07:19 AM   #12
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
Im currently running 2.6.18

When commenting lba32 it says:
Warning: LBA32 addressing assumed
Added Linux *
One warning was issued.

If i remove comment theres no warning. As i mentioned in previous post when upgrading slack11 2.6.18 to 2.6.21.1 without upgrading slack-current lb32 directive isnt needed and no warning, nothing so i think maybe i messed something up while using UPGRADING.TXT but, all packages are updated and working...

let me tell quick how i done upgrading:
10. Remove all of the packages listed below in the "Removed Packages" section.
----------------------------------------------------------

In this step i entered /var/log/packages and removed packages wich are listed in removed section. Is this wrong? Or i had to remove it from slackware-current/ dir?


11. Make sure the paths in /etc/lilo.conf point to a valid kernel and run
"/sbin/lilo" to reinstall LILO. Note that by default, /boot/vmlinuz will
be a symlink to one of the installed kernels. If you plan to use one of
the generic kernels (this is recommended), you will need to make an initrd.
---------------------------------------------------------------

I reversed it with step 12, i ran /sbin/lilo after step 12. is this wrong ?

12. Be sure to move your *.new config files into place and merge any custom
changes you had made to the originals. To find them, run:
find /etc -name "*.new"
You will need to leave passwd, shadow, group, and gshadow alone for the
most part (do not copy the *.new versions over the existing ones), but
you will need to add any new user/group accounts in passwd.new and
group.new to the existing files. There have also been some changes to
the network scripts, so pay close attention to those as well.
----------------------------------------------------------

as i said this was my step 11.

and what ive done in this step is from what i understood, i renamed all *new using mv to its original in slack11 installation,

EXAMPLE: mv /etc/rc.d/rc.4.new /etc/rc.d/rc.4

except passwd.new, group.new shadow.new i didnt touch it remained with .new extension, note that gshadow.new i found so i didnt do anything about gshadow.new.

is that wrong?
and then its step 13 reboot... thats how i finished upgrading with slack-current

Last edited by matters; 05-22-2007 at 07:41 AM.
 
Old 05-22-2007, 08:14 AM   #13
Hern_28
Member
 
Registered: Mar 2007
Location: North Carolina
Distribution: Slackware 12.0, Gentoo, LFS, Debian, Kubuntu.
Posts: 906

Rep: Reputation: 38
Could you post the lilo you are trying to use?

The one with the calls to boot 2.6.21 kernel as well.
 
Old 05-22-2007, 09:22 AM   #14
matters
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 281

Original Poster
Rep: Reputation: Disabled
I didnt quite understood ur meaning, the one with the calls to boot 2.6.21.1 , if i understood u correctly, im doing symlinks and not including kernels so i can choose wich one to boot, if thats not what you menat, please explain a bit more on what you meant.

Thanks!
 
Old 05-22-2007, 11:00 AM   #15
Hern_28
Member
 
Registered: Mar 2007
Location: North Carolina
Distribution: Slackware 12.0, Gentoo, LFS, Debian, Kubuntu.
Posts: 906

Rep: Reputation: 38
append options

To get the 2.6.21 kernel to work on my system i have to add *append="root=/dev/sda1 initrd=initrd.img"* to get it to boot, but instead of using symlinks I had multiple lilo entries calling the kernels specifically.

Something to try, but i don't think it would work, since 2.6.18 is working sounds like something went awry with the 2.6.21.1 install or the mkinitrd.

Edit:
Since I have switched to grub so i can't test using symlinks as you outlined to check if thats the problem

Last edited by Hern_28; 05-22-2007 at 11:08 AM.
 
  


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
Kernel panic : Attempted to kill init! kwng Linux - General 14 01-10-2006 10:36 PM
kernel panic:Attempted to kill init! mjsadiq Linux - Newbie 1 10-24-2005 07:40 AM
kernel panic: attempted to kill init fanche Linux - Newbie 4 02-13-2004 05:20 AM
Kernel (and me) panic. Attempted to kill init! LinuxBlackBox Linux - General 2 10-29-2003 04:24 PM
Kernel panicked: Attempted to kill init! edok Linux From Scratch 2 06-13-2003 06:26 PM


All times are GMT -5. The time now is 03:16 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration