Kernel Panic

General support questions including new installations

Kernel Panic

Postby abevec1 » 2013/01/25 18:44:15

Hello,

I am having problems with booting Centos, i.e., I get a Kernel Panic. I have no idea what to do. Googled everywhere no clue as to what is wrong. Any help or ideas are appreciated. I'm a newbie. Would attach photo screen shot to this post, but no obvious option to do that on this forum, so I typed out as much of the error message as may be needed. Can boot using rescue disk and get the prompt.

Error message appearing with Kernel Panic screen:

Red Hat nash version 5.1.19.6 starting
Reading all physical volumes..
Couldn't find device with uuid 5c36oc-K3xc-lYrt-lcJj-yEQF-eE28-Ejc1pi.
Couldnt' find device..
Found volume group "VolGroup00" using metadata type lvm2.
Couldn't find device..
Coudnt' find device ..
Refusing activiation of partial LV LogVo100. Use --partial to overide.
1 logical volume(s) in volume group "VolGropu00" now active
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: no such file or directory
setuproot: error mountindg /proc: No such file or directory
setuproot: error mounting /sys: No such file or driectory
switchroot: mount failed: No such file or directory
witch root: mount failed: no such file or directory
Kernel panic - not syncing: Atempted to kill init!
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Kernel Panic

Postby TrevorH » 2013/01/25 20:56:14

Couldn't find device with uuid 5c36oc-K3xc-lYrt-lcJj-yEQF-eE28-Ejc1pi.
Couldnt' find device..
Found volume group "VolGroup00" using metadata type lvm2.
Couldn't find device..
Coudnt' find device ..
Refusing activiation of partial LV LogVo100. Use --partial to overide.
1 logical volume(s) in volume group "VolGropu00" now active


This looks to me like you have more than one physical disk and you've used LVM to combine them into a single Volume Group - is that correct? If so then it looks like one of your physical disks has gone AWOL - it used to have a UUID of the one listed above. I'd check that all your physical disks are present and working correctly from your rescue boot - perhaps checking cabling and/or power connections to make sure it's actually working. If the disk is present then does `blkid` show it using the right UUID? How about the output of the commands `lvm pvs`, `lvm vgs` and `lvm lvs` run from the rescue disk? Do they check out OK?
User avatar
TrevorH
Forum Moderator
 
Posts: 9164
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel Panic

Postby abevec1 » 2013/01/26 01:45:25

Hello and thanks for your reply. Yes I have four disks @ 500G each. I think they are all OK, but have not taken the server apart to check the hard disks.

Anyway trying your commands, this is what I got:

entering "blkid"

/dev/mapper/VolGroup00-LogVol01: TYPE="swap"
/dev/mapper/VolGroup00-LogVol00: UUID="8ec27966-c6f3-4eda-b312-68f23a6c3eb3" TYPE="ext3"
/dev/sda1: LABEL="/boot" UUID="8ace36ad-2ba6-487b-a5e3-df1cbb607d62" TYPE="ext3" SEC_TYPE="ext2"
/dev/VolGroup00/LogVol00: UUID="8ec27966-c6f3-4eda-b312-68f23a6c3eb3" TYPE="ext3"
/dev/VolGroup00/LogVol01: TYPE="swap"


entering "lvm pvs"

PV VG Fmt Attr PSize PFree
/dev/sda2 VolGroup00 lvm2 a-- 465.66G 0
/dev/sdb1 VolGroup00 lvm2 a-- 465.66G 0
/dev/sdc1 VolGroup00 lvm2 a-- 465.66G 0
/dev/sdd1 VolGroup00 lvm2 a-- 465.66G 0

entering "lvm vgs"

VG #PV #LV #SN Attr VSize VFree
VolGroup00 4 2 0 wz--n- 1.82T 0



entering "lvm lvs"

LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 1.81T
LogVol01 VolGroup00 -wi-ao 5.81G
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Re: Kernel Panic

Postby abevec1 » 2013/01/26 12:39:55

Additional info before Kernel Panic message:

In the boot up it could not find:
Couldn't find device with uuid 5c360C-K3xc-IYrt-IcJj-yEqf-eE28-Ejc1pi
Couldn't find device with uuid PYW30n-uJkN-UKo1-fvaJ-n36v-oySE-H4IjDR

So maybe its looking for the wrong uuid??
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Re: Kernel Panic

Postby TrevorH » 2013/01/26 12:42:13

All looking fairly hopeful so far. Can you post the output of `lvm pvdisplay` this time? Likely to be a fair bit bigger than the last lot since you have 4 disks.
User avatar
TrevorH
Forum Moderator
 
Posts: 9164
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel Panic

Postby abevec1 » 2013/01/26 20:57:23

typing in lvm pvdislplay:

---Physical Volume---------
PV Name /dev/sda2
VG Name VolGroup00
PV Size 465.66GB / not usable 3.56 MB
Allocatable yes (but full)
PE Size (Kbye) 32768
Total PE 14901
Free PE 0
Allocated PE 14901
PV UUID yLADpb-iJoE-STKV-PFfk-SUK6-CxfI-D97iBF

---Physical Volume---------
PV Name /dev/sdb1
VG Name VolGroup00
PV Size 465.66GB / not usable 9.50 MB
Allocatable yes (but full)
PE Size (Kbye) 32768
Total PE 14904
Free PE 0
Allocated PE 14904
PV UUID 1dMvN1-TWSW-Yunr-k2VB-relJ-CVHR-ybxg59

---Physical Volume---------
PV Name /dev/sdc1
VG Name VolGroup00
PV Size 465.66GB / not usable 9.50 MB
Allocatable yes (but full)
PE Size (Kbye) 32768
Total PE 14904
Free PE 0
Allocated PE 14904
PV UUID 5c36oC-K3xc-IYrt-1cJj-yEQf-eE28-Ejc1pi

---Physical Volume---------
PV Name /dev/sdd1
VG Name VolGroup00
PV Size 465.66GB / not usable 9.50 MB
Allocatable yes (but full)
PE Size (Kbye) 32768
Total PE 14904
Free PE 0
Allocated PE 14904
PV UUID PYW30n-uJkN-Uko1-fvaJ-n36v-oySE-H4IjDR
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Re: Kernel Panic

Postby abevec1 » 2013/02/07 03:53:03

Does anyone else have any ideas what is wrong?
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Re: Kernel Panic

Postby TrevorH » 2013/02/07 09:22:31

I just realised that in your first post there are actually 4 different messages about being unable to find the device but that you only put in the UUID on the first of them. Is that true - do you see 4 messages, one for each of the UUIDs in your LVM set up? Did you just do a kernel upgrade and is this the first time you've booted the upgraded kernel? If so, did you try one of the older kernels listed in the grub menu that you can see by pressing ESC when you see the initial grub boot screen?
User avatar
TrevorH
Forum Moderator
 
Posts: 9164
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel Panic

Postby abevec1 » 2013/02/08 04:14:45

When the computer boots now there is only one kernel to choose. I generally did yum updates on a monthly basis. At one time it had a few older kernels, which i tried to no avail, but took those out after running into this problem. Yes there are four uuid here is the complete message:

Red Hat nash version 5.1.19.6 starting
Reading all physical volumes..
Couldn't find device with uuid 5c36oc-K3xc-lYrt-lcJj-yEQF-eE28-Ejc1pi.
Couldnt' find device with uuid PYW30n-uJkN-UKo1-fvaJ-n36v-oySE-H4IjDR
Found volume group "VolGroup00" using metadata type lvm2.
Couldn't find device with uuid 5c360C-K3xc-IYrt-IcJj-yEqf-eE28-Ejc1pi
Coudnt' find device with uuid PYW30n-uJkN-UKo1-fvaJ-n36v-oySE-H4IjDR
Refusing activiation of partial LV LogVo100. Use --partial to overide.
1 logical volume(s) in volume group "VolGropu00" now active
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: no such file or directory
setuproot: error mountindg /proc: No such file or directory
setuproot: error mounting /sys: No such file or driectory
switchroot: mount failed: No such file or directory
witch root: mount failed: no such file or directory
Kernel panic - not syncing: Atempted to kill init!
abevec1
 
Posts: 7
Joined: 2013/01/25 18:16:16

Re: Kernel Panic

Postby TrevorH » 2013/02/08 11:04:54

There are 4 messages but only 2 UUIDs. I'm going to guess that you have two hard disks attached to an add-in SATA controller or something else that requires a special driver that's missing from the initramfs. Or perhaps there's a BIOS setting for the hard disk controller that switches it from one mode to another. Either way, it looks like both /dev/sdc and /dev/sdd are not being detected by your initramfs so your LVM volume group is broken. Did you make any changes recently to your hardware or BIOS settings and can they be reversed? Perhaps booting the install media in rescue mode and following the wiki article on how to rebuild your initrd might help? If you do this I would make sure you do not replace the existing initrd but create a new file and amend the grub menu to point a duplicate entry to it
User avatar
TrevorH
Forum Moderator
 
Posts: 9164
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Next

Return to CentOS 5 - General Support

Who is online

Users browsing this forum: No registered users and 1 guest