• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Centos kernel 2.6.9-42.0.2 is borked!

M

mediashaker

Guest
Just a little note that there seems to be problems with the latest centos kernel version 2.6.9-42.0.2.

EG:
Found volume group "VolGroup00" using metadata type lvm2
Acivated logical volumes
2 logical volume(s) found in volume group "VolGroup00" now active
Creating root devic
Mounting root filesystem
mount: error 19 mounting ext3,usrquota
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernal panic - not syncing: Attempting to kill init!


Look here:
http://www.centos.org/modules/newbb/viewtopic.php?form=1&topic_id=5087&forum=27&order=ASC&start=0

Don't upgrade to this kernel or your plesk 8.01 system will kernel panic on reboot (Mine did on our test system and I had to edit /etc/grub.conf to use a previous kernel)!
 
Same as 2.6.9-42.0.3

I tried to upgrade only kernel and went to huge problems. Server couldn't reboot - Kernel panic

Anyone has an answer how to upgrade kernel properly?
 
seems to be some problem with either the init scripts (initramfs) or missing device drivers / support not included in the kernel at compile time, most likely SATA, RAID or LVM2 support.

the error suggests that the boot process is mounting the LVM but then switching to a drive that is no longer available. seems to boot on machines without a RAID or SATA controller

similar problems with all kernels after 2.6.17 too. No definitive answer that works with all hardware.

Does not appear to affect Fedora, perhaps they've fixed mkinitrd? then again they don't use LVM by default...
 
no solution for this? got the same error after updating to the last kernel usimg yum.. was on a testserver, but would be nice to figure out what causes this..
 
I've noticed this as well.

We operate an SOE with several hundred Dell PowerEdge 1950 servers.

The CentOS 4.4 servers with either a "vanilla" or cPanel install update fine. The servers running Plesk panic.

I've noticed that the Plesk servers are generating initrd images of ~380977 bytes. The others are generating ~466385 bytes.

Copying one of the larger initrd files over to the Plesk servers allows it to boot up fine.

We're still investigating - it's quite strange.
 
we had this issue several times on new servers and this may be because of a PLESK bug

using sw raid 1 , centos4.4

the solution for us was was "dont upgrade your kernel" after installing plesk because only this condition replicated the problem in our case.

please try this

go to /etc/fstab

and check where userquota is placed

it should be defaults,usrquota however plesk inserts it into the wrong coloumn like ext3,userquota

if it is like this correct it and try to reboot

please also let me know if this fixed the issue

knocx
 
this should fix the issue look at your error log

mount: error 19 mounting ext3,usrquota

this is the case i am mentioning

sw-soft programmers are really fun
 
OK :) keep it posting since i had reported this bug to sw-soft but the dont show any response if i get confident i will post it again
 
The testserver I used was reinstalled, so I didn't get a chance to test it.. but I'll try to test it as soon as I get a chance..
 
OK my current /etc/fstab looks like this

Code:
LABEL=/ /       ext3,usrquota   defaults        1
LABEL=/boot             /boot                   ext2    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=SWAP-hda2         swap                    swap    defaults        0 0

What exactly I need to change?
 
I think it should be:

Code:
LABEL=/ /       ext3	usrquota,defaults        1
LABEL=/boot             /boot                   ext2    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=SWAP-hda2         swap                    swap    defaults        0 0
 
hmm.. I just tried this.. but didn't work. I still get the same kernel panic.. ideas?

knocx: could you post your fstab file? You have upgraded to the last kernel and got it working?
 
Finally I've figured what caused the problem on my servers.

It seems that it is VERY important how the /etc/fstab file looks like BEFORE you upgrade the kernel. If it looks like this before you upgrade the kernel it won't work:

Code:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00        /       ext3,usrquota   defaults        1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=/tmp              /tmp                    ext3    defaults        1 2
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0


BUT, if it looks like this BEFORE you upgrade the kernel, it will work (atleast on my two testservers):

Code:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00        /       ext3    defaults,usrquota       1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=/tmp              /tmp                    ext3    defaults        1 2
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0

I will send this to plesk, and hopefully they will fix it.

After each update of the kernel I checked the size of the /boot/initrd-2.6.9-42.0.3.ELsmp.img. If it was not working, the size was like 0,1MB lower than it should be. In my case:

working size:
-rw-r--r-- 1 root root 1111385 Nov 11 09:59 initrd-2.6.9-42.0.3.ELsmp.img

not working size:
-rw-r--r-- 1 root root 1022841 Nov 10 20:49 initrd-2.6.9-42.0.3.ELsmp.img
 
what is your kernel complaining about;

if it is still get

Mounting root filesystem
mount: error 19 mounting ext3,usrquota
mount: error 2 mounting none

then it is still ext3,usrquota problem which plesk messes up

you have to fix your fstab that plesk screwed before upgrading the kernel

hope this helps
 
It is working with what I wrote above.. not sure if the last post was ment for me? :)
 
sorry :) i did not realized that post , great to hear that it is working
 
Back
Top