Hide Forgot
Description of problem: Booting system with kernel 2.6.40.6-0.fc15 stopped without any messages except of one final: "Dropping to debug shell sh: can't access tty; job control turned off" The same error with kernel-2.6.40.4-5.fc15. Working kernel: 2.6.38.6-26.rc1.fc15 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can you remove the 'rhgb quiet' parts from the grub command line and see if you can get other boot output. Also, adding rdinitdebug might provide additional information.
There are last lines of output you have asked: drm: registered panic notifier No ACPI video bus found [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 dracut: Starting plymouth deamon dracut: rd.dm=0 removing MD RAID activaton dracut: Autoassembling MD RAID md: md0 stopped md: bind <sda> md: bind <sdb> dracut: mdadm: Container /dev/md0 has been assembled with 2 drives md: md127 stopped md: bind<sdb> md: bind<sda> md: raid1 personality registered for level 1 bio: create slab <bio-1> at 1 dracut: mdadm: array /dev/md127 now has 2 devices dracut Warning: No root device "block:/dev/mapper/VolGroup-lv_root" found dracut Warning: LVM VolGroup/lv_root not found dracut Warning: LVM VolGroup/lv_swap not found + rm -f /run/initramfs/initlog.pipe /run/initramfs/init.log.end + [ -e /.die ] + getargboot 1 rd.shell -y rdshell + local _b + unset _b + local _default + _default=1 + shift + getarg rd.shell -y rdshell + set +x + return 1 + _b= + [ 1 -ne 0 -a -z ] + _b=1 + [ -n 1 ] + [ 1=0 ] + [ 1=no ] + return 0 + echo Dropping to debug shell Dropping to debug shell + echo + export PS1 :dracut: ${PWD}# + [ -e /.profile] + echo exec 0 <>/dev/console1<>/dev/console2<>/dev/console + sh -i -l sh: can't access tty; job control turned off
This looks somewhat like the final messages I am getting from one system after 2.6.40.6-0 kernel update. In this case, the update failed to install initramfs-2.6.40.6-0.fc15.x86_64.img, or to add the corresponding initrd line to grub.conf. (Actually, I have another system also giving similar diagnostics, but as it's in a different location, I haven't had a chance to confirm yet that it's the same problem.) I'm not sure why the update failed - there are no obvious failure messages in yum.log. A dozen other systems updated perfectly OK, and I haven't been able to figure whether the two failed systems have anything in common. Vadim, please can you check whether initramfs-2.6.40.6-0.fc15.x86_64.img - or the equivalent for 32-bit - exists in your /boot? If so, it's a different problem, and I will file a separate bug report once I have more details; if not, it possibly explains why your boot is failing.
Hi, Bob. I have the initramfs-2.6.40.6-0.fc15.x86_64.img in /boot.
I've Just installed a new kernel kernel-2.6.41.1-1.fc15.x86_64. Works fine.
Thanks for letting us know.