Kernel panic with kernel 3.4.3-1

[akiross]

Hello
just upgraded to kernel 3.4.3-1.fc17.x86_64 and it went panic after 2 minutes.

Now I get a kernel panic message when booting the machine:

Kernel panic - not syncing: VFS: Unable to mount root fs n unknown-block(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.4.3-1.fc17.x84_64 #1

and the call trace which I'm not reporting.
Using old kernels gives me a filesystem error, requiring to execute e2fsck manually.

I'm not doing it just to be sure to not doing anything harmful...

Should I execute it and upgrade to any new kernel (if any) or change any boot parameter?

Grub has this booting line (not sure if it's the right one, I never used grub2):

linux /vmlinux-3.4.3-1.fc17.x86_64 root=/dev/mapper/vg_myhostname-lv_root ro rd.md-0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_myhostname/lv_swap KEYTABLE=us rd.lvm.lv=vg_myhostname/lv_root rd.luks=0 LANG=en_US.UTF-8 rhbg quiet acpi_backl

Any help is appreciated

Thanks!

EDIT: fsck actually doesn't repair anything, the fs is clean. I'm running with the old kernel now.
I read somewhere that this may be related with UUID and kernel root parameter, but, well, it seems that UUID is not used when booting...

[Keldorn]

Can you show your /etc/fstab and /boot/grub2/grub.cfg

[akiross]

Sure Here they are:

http://nopaste.voric.com/paste.php?f=empoki

Thanks

[Keldorn]

Hmm, try to reconfigure grub with
grub2-mkconfig
"linux" line in grub2 should contain UUID, if it won't help you can disable UUID for grub2 in
"/etc/default/grub" by adding
GRUB_DISABLE_LINUX_UUID=true

[akiross]

Non of them worked, still kernel panic when loading 3.4.3 and fsck error in 3.4.2 :S

[Keldorn]

Forgot to mention, that after adding option to "/etc/default/grub" grub2-mkconfig should be run.
No ideas anymore

[akiross]

Yes ofc

Anyway, the problem is still not solved :S