[Solved] Changing kernel with LVM2 system partition

[GigaGaga]

Hello,
I had issues by using the .bfs kernel on two machines here. One did not shutdown in appropriate time nor was the machine able to copy files on an external USB-drive. Changing the kernel to the non-bfs version solved the problem. Shutdown is quick and the computer can do multiple tasks at once again.
The other machine did hang up several times while using FUSE. After a warm reboot, which took ages, I was forced to a fsck.ext4, which I did not gave the attention I should have. Answering the deletion of some faulty entries with a blank YES, several directories were missing, akonadi showed up errors and some other funny things happened too. Changing the kernel to its non-bfs-derivative solved this problem and the system never froze again.

Because I got a new hard drive on my notebook, I decided to install PCLOS again, but this time I wanted to use the freedom in partitioning by using LVM2. Thus I created a separate /boot partition in ext3 and formatted the free space in LVM2, where I put the /, /swap and /home. After installation of PCLOS I did an update with synaptic and rebooted. After this I wanted to change the kernel from .bfs to its non-bfs-version. The booting process hung up while trying to mount the system.
Thus GRUB showed properly the new kernel on the separate /boot-partition in ext3, the booting process starts and the device-mapper finds the LVM and the partitions in there. But then it stops and can not mount properly /.

Using dmesg on the running .bfs-system, the next entry should have been:

EXT4-fs (dm-0): mounted filesystem with ordered datamode

Instead it appears:
mount: error mounting /dev/root on /sysroot as ext4: Invalid argument. Attempted to kill init!

The last relevant messages during boot with the non-bfs are as follows:

Scanning logical volumes
   Reading all physical volumes. This may take a while ...
   Found volume group “vg-0“ using metadata type lvm2
Activating logical volumes
   5 logical volume(s) in volume group “vg-0“ now active.
Creating root device.
Mounting root filesystem.
mount: error mounting /dev/root on /sysroot as ext4: Invalid argument.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1,comm: init Not tainted 2.6.33.7-pclos6 #1
Call Trace:
   (...).... (funny, very arbitrarily looking numbers and letters.)
   (...).... I do not have rectangular brackets right now,
   (...).... got to switch to a German system after solving this problem.
   (...)....
   (...)....
   (...)....
   (...)....
(drm.drm_fb_helper_panic)  *ERROR* panic occurred, switching back to text console

And here the booting process stops.
Is there something which I can add during the booting process into GRUB to force loading missing modules like drm or so?
The Kernel is loaded, the error occurs when mounting the actual system partition in ext4-format, which is laying within the lvm-container.
I am capable of loading my dishwasher, but when it comes to putting the correct booting parameters into GRUB, I am lost. I think adding a correct parameter there would solve the problem and I would be very pleased if somebody out there could help me with this. Or is there another way to solve this problem?
I know LVM2 is not actually supported by PCLOS, but it would be great if a friendly soul out there could help me with my self-inflicted problem.
Regards,
Giga.

[GigaGaga]

Sorry guys,
I solved it.
Always the same, describing a problem within a forum sharpens my mind by excluding other things.
I had to change the Kernel-parameters in GRUB and the new kernel was booting.
The entry was root=UUID=xxx and I changed it to root=/dev/vgo/1, the system partition within the LVM container.
Now I got to change this permanently in the GRUB configuration.
I can delete this thread here, but maybe it is helpful for others.
Sorry for the fuzz,
Giga