Anyone else have a kernel-panic with initramfs created by: dracut-018-74.git20120522.fc18
Am 23.05.2012 11:17, schrieb Frank Murphy:
Anyone else have a kernel-panic with initramfs created by: dracut-018-74.git20120522.fc18
How exactly does the kernel panic look like? Normally, you are dropped to a shell.
you can get more debug info, if you add "rd.debug rd.shell loglevel=77" to the kernel command line.
On 23/05/12 11:10, Harald Hoyer wrote:
Am 23.05.2012 11:17, schrieb Frank Murphy:
Anyone else have a kernel-panic with initramfs created by: dracut-018-74.git20120522.fc18
How exactly does the kernel panic look like? Normally, you are dropped to a shell.
you can get more debug info, if you add "rd.debug rd.shell loglevel=77" to the kernel command line.
This is a snip from serial console, will get to box later this evening.
[ 2.474250] Refined TSC clocksource calibration: 2402.495 MHz. [ 2.480737] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2 [ 2.486190] md: Waiting for all devices to be available before autodetect [ 2.489062] md: If you don't use raid, use raid=noautodetect [ 2.496160] md: Autodetecting RAID arrays. [ 2.498194] md: Scanned 0 and added 0 devices. [ 2.500101] md: autorun ... [ 2.501416] md: ... autorun DONE. [ 2.503585] VFS: Cannot open root device "mapper/luks-c19c397b-248d-4e6b-9a54-2a5d592f9d0d" or unknown-block(0,0): error -6 [ 2.508111] Please append a correct "root=" boot option; here are the available partitions: [ 2.511797] 0b00 1048575 sr0 driver: sr [ 2.513906] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.521261] Pid: 1, comm: swapper/0 Not tainted 3.4.0-2.fc18.x86_64 #1 [ 2.521437] usb 1-1: New USB device found, idVendor=0627, idProduct=0001 [ 2.521440] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5 [ 2.521443] usb 1-1: Product: QEMU USB Tablet [ 2.521445] usb 1-1: Manufacturer: QEMU 1.0 [ 2.521447] usb 1-1: SerialNumber: 42 [ 2.536688] Call Trace: [ 2.537934] [<ffffffff816ab086>] panic+0xba/0x1cb [ 2.541185] [<ffffffff81f010e2>] mount_block_root+0x1d9/0x28a [ 2.543489] [<ffffffff81f011ea>] mount_root+0x57/0x5b [ 2.545699] [<ffffffff81f0132b>] prepare_namespace+0x13d/0x176 [ 2.548045] [<ffffffff81f00e45>] kernel_init+0x1d2/0x1d7 [ 2.550463] [<ffffffff81f00604>] ? do_early_param+0x8c/0x8c [ 2.554616] [<ffffffff816c2b34>] kernel_thread_helper+0x4/0x10 [ 2.556917] [<ffffffff816b8d30>] ? retint_restore_args+0x13/0x13 [ 2.559452] [<ffffffff81f00c73>] ? start_kernel+0x410/0x410 [ 2.561622] [<ffffffff816c2b30>] ? gs_change+0x13/0x13
On 23/05/12 11:10, Harald Hoyer wrote:
you can get more debug info, if you add "rd.debug rd.shell loglevel=77" to the kernel command line.
managed to get on to Vm machine. panics before getting to above debug switches.
Will boot if dracut downgraded to previous: dracut-018-53.git20120509.fc18 and --force initramfs
F17 boxes with dracut-018-40.git20120522.fc17 boot fine.
Full serial console capture with debug switch's included: http://frankly3d.eu/kernel-panic
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
this means there was no initramfs even loaded
check your bootloader config and the existence of the initramfs image Am 23.05.2012 13:09 schrieb "Frank Murphy" frankly3d@gmail.com:
On 23/05/12 11:10, Harald Hoyer wrote:
you can get more debug info, if you add "rd.debug rd.shell loglevel=77"
to the kernel command line.
managed to get on to Vm machine. panics before getting to above debug switches.
Will boot if dracut downgraded to previous: dracut-018-53.git20120509.fc18 and --force initramfs
F17 boxes with dracut-018-40.git20120522.fc17 boot fine.
Full serial console capture with debug switch's included: http://frankly3d.eu/kernel-**panic http://frankly3d.eu/kernel-panic
-- Regards, Frank "Jack of all, fubars" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.**org/mailman/listinfo/testhttps://admin.fedoraproject.org/mailman/listinfo/test
On 23/05/12 16:27, Harald Hoyer wrote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
this means there was no initramfs even loaded
check your bootloader config
/boot/grub2/grub.cfg has all the entries most recent shown.
--snipped--- ### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora (3.5.0-0.rc0.git3.1.fc18.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-34748375-c797-4d5c-9990-3e46f3f74b6f' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='hd0,gpt2' 7475273f-7176-4568-92d7-03d91659ca39 else search --no-floppy --fs-uuid --set=root 7475273f-7176-4568-92d7-03d91659ca39 fi echo 'Loading Fedora (3.5.0-0.rc0.git3.1.fc18.x86_64)' linux /vmlinuz-3.5.0-0.rc0.git3.1.fc18.x86_64 root=/dev/mapper/luks-c19c397b-248d-4e6b-9a54-2a5d592f9d0d rd.debug rd.shell loglevel=77 ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks.uuid=luks-c19c397b-248d-4e6b-9a54-2a5d592f9d0d SYSFONT=latarcyrheb-sun16 KEYTABLE=uk LANG=en_IE.UTF-8 console=tty0 console=ttyS0,115200 echo 'Loading initial ramdisk ...' } --snipped-----
and the existence of the initramfs image
You are correct here,
dir /boot | grep initramfs initramfs-3.4.0-0.rc6.git1.1.fc18.x86_64.img initramfs-3.4.0-0.rc6.git2.2.fc18.x86_64.img initramfs-3.4.0-0.rc6.git3.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git0.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git1.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git2.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git3.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git4.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git5.1.fc18.x86_64.img initramfs-3.4.0-0.rc7.git6.1.fc18.x86_64.img
The 3 kernels installed with the new dracut are not created initramfs.
On 23/05/12 16:27, Harald Hoyer wrote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
this means there was no initramfs even loaded
check your bootloader config and the existence of the initramfs image
This is what happens when manually trying to create initramfs:
dracut initramfs-3.5.0-0.rc0.git3.1.fc18.i686.img kernel-3.5.0-0.rc0.git3.1.fc18.i686 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory F: installkernel failed in module kernel-modules
I even installed kernel-modules-extra in case of something there.
There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/*
On Thu, May 24, 2012 at 7:10 AM, Frank Murphy frankly3d@gmail.com wrote:
On 23/05/12 16:27, Harald Hoyer wrote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
this means there was no initramfs even loaded
check your bootloader config and the existence of the initramfs image
This is what happens when manually trying to create initramfs:
dracut initramfs-3.5.0-0.rc0.git3.1.fc18.i686.img kernel-3.5.0-0.rc0.git3.1.fc18.i686 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/': No such file or directory F: installkernel failed in module kernel-modules
I even installed kernel-modules-extra in case of something there.
There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/*
Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64?
josh
On 24/05/12 12:53, Josh Boyer wrote:
There are mant *ko files in /lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.i686/*
Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64?
josh
Apologies, it happens on both 32 and 64.
On 24/05/12 12:53, Josh Boyer wrote:
Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64?
josh
Put up some more info: http://frankly3d.eu/kernel-error
On Thu, May 24, 2012 at 9:08 AM, Frank Murphy frankly3d@gmail.com wrote:
On 24/05/12 12:53, Josh Boyer wrote:
Erm... your grub2 config file you sent previously showed you were using and x86_64 kernel. Do you even have the i686 kernel installed? There are clearly modules in the RPM in koji, so I suspect maybe you want to try with x86_64?
josh
Put up some more info: http://frankly3d.eu/kernel-error
dracut initramfs-3.5.0-0.rc0.git3.1.fc18.x86_64 kernel-3.5.0-0.rc0.git3.1.fc18.x86_64 find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory find: `/lib/modules/kernel-3.5.0-0.rc0.git3.1.fc18.x86_64/': No such file or directory F: installkernel failed in module kernel-modules
ls -R frank@test08 ~$ su - Password: [root@test08 ~]# ls -R /usr/lib/modules/3.5.0-0.rc0.git3.1.fc18.x86_64
Look closely. You're telling dracut the kernel version is 'kernel-3.5.0....' and it takes that very literally. Remove the 'kernel-' prefix and just use '3.5.0-0.rc0.git3.1.fc18.x86_64'.
None of that explains why there is no initramfs being created from the kernel update itself though. If you yum update to today's rawhide kernel, is one created?
josh
On 24/05/12 14:27, Josh Boyer wrote:
On Thu, May 24, 2012 at 9:08 AM, Frank Murphyfrankly3d@gmail.com wrote:
<snipped>
Look closely. You're telling dracut the kernel version is 'kernel-3.5.0....' and it takes that very literally. Remove the 'kernel-' prefix and just use '3.5.0-0.rc0.git3.1.fc18.x86_64'.
After removing prefix:
]# dracut initramfs-3.5.0-0.rc0.git3.1.fc18.x86_64 3.5.0-0.rc0.git3.1.fc18.x86_64 F: installkernel failed in module multipat
# rpm -qa | grep multipath device-mapper-multipath-libs-0.4.9-22.fc18.x86_64 device-mapper-multipath-0.4.9-22.fc18.x86_64
None of that explains why there is no initramfs being created from the kernel update itself though. If you yum update to today's rawhide kernel, is one created?
Today's kernel-3.5.0-0.rc0.git5.1.fc18 no auto initramfs, also same manual fail "multipath"
On 23/05/12 10:17, Frank Murphy wrote:
Anyone else have a kernel-panic with initramfs created by: dracut-018-74.git20120522.fc18
Can't get anywhere myself so: https://bugzilla.redhat.com/show_bug.cgi?id=824981