LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
LinkBack Search this Thread
Old 06-07-2010, 06:44 PM   #1
redbuttelinux
LQ Newbie
 
Registered: Jun 2010
Posts: 4

Rep: Reputation: 0
Unhappy PClinuxOS hangs on boot: "Kernal panic- not syncing: Attempted to kill init!


I recently installed new hard drive and cloned old hard drive software onto it. The bootloader installs either linux or other operating system. Ever since the cloning, boot hangs. Words in the thread title are the last to appear before everything grinds to a halt. Just before the kernal panic message appears, "Initrd finished" is last line. Will have to try booting again to find more info before this.

Last edited by redbuttelinux; 06-07-2010 at 06:59 PM.
 
Old 06-07-2010, 07:05 PM   #2
AlucardZero
Senior Member
 
Registered: May 2006
Location: USA
Distribution: Debian
Posts: 4,570

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
You'll need to post the lines before the last one. "Attempted to kill init" is a catchall, the real reason is before it.
 
Old 06-07-2010, 07:12 PM   #3
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
The boot loader's /boot/grub/menu.lst file or /etc/fstab may use the hardware id to reference the partitions. You will need to fix these entries.
These are entries that look like ata-TOSHIBA_MK2049GSY_48CYT01OT-part1. The kernel creates the /dev/disk/by-id entries dynamically when you boot and they will be different with a new drive.
 
Old 06-07-2010, 07:14 PM   #4
redbuttelinux
LQ Newbie
 
Registered: Jun 2010
Posts: 4

Original Poster
Rep: Reputation: 0
Smile Thanks AlucardZero

Will do it now.
 
Old 06-07-2010, 07:21 PM   #5
redbuttelinux
LQ Newbie
 
Registered: Jun 2010
Posts: 4

Original Poster
Rep: Reputation: 0
Jschiwal, how do I correct the entry in the boot process? And can I find the info I need on the side of the hard drive?
 
Old 06-08-2010, 05:08 PM   #6
redbuttelinux
LQ Newbie
 
Registered: Jun 2010
Posts: 4

Original Poster
Rep: Reputation: 0
Alucard Zero, here is the last page before it hangs

Creating Root Device
Trying to resume from /dev/hda6
Unable to access resume device (/dev/hda6)
echo: cannot open /proc/suspend2/do_resume for write: 2
Mounting root filesystem /dev/root
Mount: error 6 mounting ext flags defaults
well, retrying without the option flags
input AT Translated Set 2 keyboard as/class/input/input@
mount: error 6 mounting ext 3
well, retrying read-only without any flag
mount: error 6 mounting ext3
Switching to new root
ERROR opening /dev/console!!!!:2
unmounting old /proc
unmounting old /sys
switchroot: mount failed: 22
Initrd finished
Kernel panic-not syncing: Attempted to kill init!
 
Old 06-08-2010, 05:54 PM   #7
AlucardZero
Senior Member
 
Registered: May 2006
Location: USA
Distribution: Debian
Posts: 4,570

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Ok, error 6 mounting ext3 is the relevant error here. The kernel can't mount your root filesystem. This could be for a number of reasons.

Boot from a live CD, collect the output of "fdisk -l". fsck your Linux partitions and make sure this comes back clean. Mount them and collect your etc/fstab (from the disk, not the live CD's) and boot/grub/grub.conf and post them there. Also collect the UUIDs of your Linux partitions with "blkid /dev/sdaX" replacing sdaX with the partition names appropriate for your setup. If jschiwal is right, you have mismatched UUIDs in your fstab and on the new disk.
 
Old 06-09-2010, 05:32 AM   #8
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
The kernel running on a live distro (or rescue mode in install disk) will create symbolic links in /dev/disk/by-id/. List them with "ls -l /dev/disk/by-id/". They will point to the regular devices such as /dev/sda1, etc. Write down what they are. There are also /dev/disk/by-uuid/ links as will which point to the same devices. The UUID numbers are for the filesystems on the partitions. The UUID numbers may be used in /etc/fstab. /boot/grub/menu.lst will most likely use IDs instead.

Posting your current menu.lst file and the current fstab file may help as well.
 
  


Reply

Tags
boot loader, harddrive


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Explained: "kernel panic - not syncing - attempted to kill init" sundialsvcs Linux - Software 36 04-24-2010 08:58 AM
/sbin/init: Kernel panic - not syncing: Attempted to kill init! jalejo08 Linux - Kernel 7 07-02-2009 01:16 PM
PXE Boot Error: "Kernel panic - not syncing: Attempted to kill init!" veeruk101 Linux - Networking 1 07-18-2007 03:30 PM
"Kernel panic - not syncing: Attempted to kill init!" after Yum update, CentOS 4.4 TestedDoughnut Linux - General 7 02-15-2007 04:22 PM


All times are GMT -5. The time now is 04:38 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