Author Topic: [SOLVED] Kernel panic - not syncing  (Read 3261 times)

Offline JerryP

  • Sr. Member
  • ****
  • Posts: 451
  • "Let's GO Yankees"
Re: Kernel panic - not syncing
« Reply #15 on: November 05, 2010, 12:09:29 PM »
Ok, My problem is solved but I feel I might have done it the hard way.  My OS is completely reinstalled and all my preferences are how I like them (took hours and really exercised the gray matter to remember how to do this and that.  I couldn't set up my P.A.S.S. right (it's still really FUBAR) but discovered that by running Repository Speed Test I could at least update from a "free" Repository. Thanks to all who helped and to even those who took the time to read my post since that opens the matter to being resolved. 
Even the calendar asks _ _ _! after SMT

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2110
  • Rubenus Parvus MCMXCI
Re: [SOLVED] Kernel panic - not syncing
« Reply #16 on: November 05, 2010, 01:13:06 PM »
Maybe you can make a remaster now.....  ;)
(there are posts enough on the forum on how to accomplish that)
=> if then some disaster occurs, you can just reinstall your remaster which has all your preferences, configurations, applications, etc....)
And maybe do it every month, or even every week: then it's just something of minutes to have your 'good' install back (park the ISO e.g. on a extern hard drive, or on a USB stick via UnetBootin)

Offline JerryP

  • Sr. Member
  • ****
  • Posts: 451
  • "Let's GO Yankees"
Re: [SOLVED] Kernel panic - not syncing
« Reply #17 on: November 05, 2010, 03:06:01 PM »
Remastering sounds like a great idea but the last time (some years ago) I tried to make a live USB drive I hosed my system. I only have bad memories of it. I also don't seem to have the programs loaded to do it.  I am terrible when it comes to backups and usually all I do is buy new hard drives and the old one is the backup.
Even the calendar asks _ _ _! after SMT

Offline IrishGuy

  • Full Member
  • ***
  • Posts: 67
Re: [SOLVED] Kernel panic - not syncing
« Reply #18 on: November 05, 2010, 07:26:39 PM »
Hi guys,

I'm having the exact same problem as in the OP (kernel panic after failing to find sdaX). I installed a new motherboard and now I can't boot the system. Below is my fdisk and menu.lst outputs. Can anyone see where I'm going wrong or give me any advice on how to repair the associations between the GRUB and my hard drive?

Code: [Select]
[root@localhost guest]# fdisk -l

Disk /dev/sda: 74.4 GB, 74355769344 bytes
255 heads, 63 sectors/track, 9039 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1019     8185086   83  Linux
/dev/sda2            1020        9039    64420650    5  Extended
/dev/sda5            1020        1528     4088511   82  Linux swap / Solaris
/dev/sda6            1529        9039    60332076   83  Linux

Code: [Select]
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 failsafe
initrd (hd0,0)/boot/initrd.img

title 2.6.32.11-pclos2.bfs
kernel (hd0,0)/boot/vmlinuz-2.6.32.11-pclos2.bfs BOOT_IMAGE=2.6.32.11-pclos2.bfs root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.11-pclos2.bfs.img

title 2.6.32.24-pclos1.a64
kernel (hd0,0)/boot/vmlinuz-2.6.32.24-pclos1.a64 BOOT_IMAGE=2.6.32.24-pclos1.a64 root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.24-pclos1.a64.img

"There are no kernel hackers in Ireland. They spend all their time in the pub." - Alan Cox

KDE4 on 22" widescreen = woohoo!

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3981
Re: [SOLVED] Kernel panic - not syncing
« Reply #19 on: November 06, 2010, 08:57:59 AM »
Post the output of blkid.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline melodie

  • Hero Member
  • *****
  • Posts: 5942
  • XMMP=Jabber, free instant messaging protocol !
    • PCLinuxOS Fr
Re: [SOLVED] Kernel panic - not syncing
« Reply #20 on: November 06, 2010, 09:00:54 AM »
Post the output of blkid.



.... that you will invoke in a console *as root*. :)

(Hi kjpetrie!)

melodie at swissjabber dot ch - IRC #pclinuxos-fr sur freenode

Offline IrishGuy

  • Full Member
  • ***
  • Posts: 67
Re: [SOLVED] Kernel panic - not syncing
« Reply #21 on: November 06, 2010, 10:10:29 AM »
Here it is :)

Code: [Select]
[root@localhost guest]# blkid
/dev/sda1: UUID="d361e038-dbb4-48db-9e65-09342edf7c36" TYPE="ext4"
/dev/sda5: UUID="cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380" TYPE="swap"
/dev/sda6: UUID="447b3452-8e8f-40cb-8b05-8753f3bb2d3f" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
"There are no kernel hackers in Ireland. They spend all their time in the pub." - Alan Cox

KDE4 on 22" widescreen = woohoo!

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3981
Re: [SOLVED] Kernel panic - not syncing
« Reply #22 on: November 06, 2010, 01:11:45 PM »
OK, well it's not the obvious. It could be a BIOS/driver issue. GRUB can access the disc but your Linux install can't. As the livecd can also access it, I suspect a re-install might be the quickest way. You should be able to keep your /home partition.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline melodie

  • Hero Member
  • *****
  • Posts: 5942
  • XMMP=Jabber, free instant messaging protocol !
    • PCLinuxOS Fr
Re: [SOLVED] Kernel panic - not syncing
« Reply #23 on: November 06, 2010, 01:37:32 PM »
I suspect a re-install might be the quickest way.

Hi, because of the informations written in initrd, it is probably necessary to redo the initrd. Would you explain to IrishGuy how to start a Live CD, chroot the / partition, connect to the web (dhclient eth0), and install another kernel version to force the initrd to be redone, then reinstall grub to make it reconfigure the whole stuff ?

melodie at swissjabber dot ch - IRC #pclinuxos-fr sur freenode

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3981
Re: [SOLVED] Kernel panic - not syncing
« Reply #24 on: November 06, 2010, 03:51:31 PM »
Melodie,

If you think that would be a better way, why not explain it yourself? Why ask me to explain your idea?
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline melodie

  • Hero Member
  • *****
  • Posts: 5942
  • XMMP=Jabber, free instant messaging protocol !
    • PCLinuxOS Fr
Re: [SOLVED] Kernel panic - not syncing
« Reply #25 on: November 06, 2010, 05:55:21 PM »
Melodie,

If you think that would be a better way, why not explain it yourself? Why ask me to explain your idea?


Let's do it ! In case I don't give enough details you will complete : do you agree ?

Start for explanation:
When our beloved distro is in trouble, we have at least 3 means to access to it for repair.

1) from init1
2) from a livecd
3) from another distribution which is installed in the same machine, same hard driver or next hard drive

The most important in theses 3 methods is the ability to access to the root partition (the / )

Let's show how to do it from a Live CD:
* Boot a Live CD;
* Once you are logued in a X session as user, open a console;
* Become root in the console;
* Mount the partition where you have the sick / partition, in order to cure it (mount it to /mnt directory for instance);
* Move to the /mnt partition where the / from hard drive is mounted;
* Now check you have all of the / directories there, with a "ls -l" command, if you see all the directories : /bin, /sbin, /home, and so on, it's all ok.

* Now you need to mount a few stuff to make the / from hard drive feel well (no technical language here, just do... I don't have the right tech explanation in english for that):

From within the /mnt directory where the partition of hard drive that need to be repaired, as with root priviledge:
Code: [Select]
# mount -o bind /dev dev/
this is to have same as /dev, but in the partition which is mounted. Then:
Code: [Select]
mount -t proc none proc/
about same for "none". For both commands beware of the place of the slashes ! /dev is not the same as dev/ !!!

Then you will do this, which is where all begins:
Code: [Select]
# chroot .
Beware of the dot after the chroot command !!! There is "chroot", then _a space_, then a dot ! If you do not do the same it won't work. This command has the following effect : it makes the shell think that it is in the real / directory of the system. In other words, it raises the mounted partition to the same level as the / directory : but only in that one shell.

Once done, connect the chrooted partition to internet:
# dhclient eth0 // if eth0 is the cable network interface... usually this works, and sometimes it's not even necessary

Then:
# apt-get update && apt-get dist-upgrade

Then:
# apt-get install kernel-<here choose a version>

If you don't know what version, look in the Synaptic which you probably have in the PCLinuxOS Live CD of your's, to find one that is not yet installed in the hard drive install.


Hope this will help you. Some details for a complete howto might be missing, if necessary : ask. :)

melodie at swissjabber dot ch - IRC #pclinuxos-fr sur freenode

Offline IrishGuy

  • Full Member
  • ***
  • Posts: 67
Re: [SOLVED] Kernel panic - not syncing
« Reply #26 on: November 07, 2010, 11:38:06 AM »
Hi Melodie,

I was able to mount "/" in my "/media" directory. It wouldn't mount in "/mnt". Otherwise everything went exactly as you described without any problems.

However, do I need to redo the MBR in order for the new kernel to appear in the GRUB? I rebooted after I finished the instructions and the kernel I downloaded was not visible in the GRUB menu...

You know, at first I was kind of annoyed at how such a simple thing as replacing a motherboard would cause so many issues. But then I realised that the vast majority of people don't even bother replacing the motherboard, they just get a new computer!

Even if this doesn't work, at least I know how that a quick and painless re-installation awaits  8)
"There are no kernel hackers in Ireland. They spend all their time in the pub." - Alan Cox

KDE4 on 22" widescreen = woohoo!

Offline melodie

  • Hero Member
  • *****
  • Posts: 5942
  • XMMP=Jabber, free instant messaging protocol !
    • PCLinuxOS Fr
Re: [SOLVED] Kernel panic - not syncing
« Reply #27 on: November 07, 2010, 12:43:32 PM »
Hi,

I'll try to explain you how to re-install grub from the command line with a method starting on the same base. But this time you will not need to chroot, and not need to mount the partition either.

Just be sure to know in which device name you have the boot directory, do again a "blkid" in root console (if you don't remember where the / is... as you probably have the /boot under / )

In root console type "grub".
You will get this:
Code: [Select]
    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub>

Then type:

root (hdX,Y) // where X is number of the hard drive (0 if there is only one, can be 1 if there are 2 hard drives) and Y is the number partition starting from 0, so if you have "/dev/sda5" on first hard drive master,  it will be "root (hd0,4)"

Then once you get this:
Code: [Select]
Filesystem type is ext2fs, partition type 0x83
(here it's a ext4, but it sees it as ext2 : never mind... it's not a problem)

Then you will type:

setup (hd0) // to install grub to mbr

This should be then ok.

If not, you will post the content of menu.lst next, and we can help you arrange it by hand.




melodie at swissjabber dot ch - IRC #pclinuxos-fr sur freenode

Offline IrishGuy

  • Full Member
  • ***
  • Posts: 67
Re: [SOLVED] Kernel panic - not syncing
« Reply #28 on: November 07, 2010, 02:45:38 PM »
I gave that a go but still got the same problem. I have a feeling that although the GRUB and MBR may be functioning correctly, there may be some hardware-related conflicts that are stopping my install from being recognized. During startup (after GRUB) I brought up the verbose mode and there were a whole bunch of errors listed that I can't even begin to list.

If upgrading all the packages and redoing GRUB didn't work, then there may well be something deeper that we can't see that is causing the problems. In that case, a fresh install may be the simplest (if not the ideal) solution.

Having said that, if you can think of anything else that might be at fault, I'd like to try and fix that before I re-install.  :)
"There are no kernel hackers in Ireland. They spend all their time in the pub." - Alan Cox

KDE4 on 22" widescreen = woohoo!

Offline melodie

  • Hero Member
  • *****
  • Posts: 5942
  • XMMP=Jabber, free instant messaging protocol !
    • PCLinuxOS Fr
Re: [SOLVED] Kernel panic - not syncing
« Reply #29 on: November 07, 2010, 02:50:35 PM »
Having said that, if you can think of anything else that might be at fault, I'd like to try and fix that before I re-install.  :)

Yes, that mobo may need an option... I would like you to boot it in verbose mode and try to copy on a paper to bring back here the 3 or 4 last lines before the boot hangs. Can you do that ?

And also give us the full copy of your /boot/grub/menu.lst file : between code tags.

One other thing I just think of : have you done/checked any setups in the BIOS ? Is the type of hard drive you have activated there ? (ide or sata... ). If no, what about checking there first ?

melodie at swissjabber dot ch - IRC #pclinuxos-fr sur freenode