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
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...