Hide Forgot
Description of problem: Asus t101mt not boot after kernel update from 3.1.0-7.fc16.i686 to 3.1.5-6.fc16.i686 How reproducible: yum update. then reboot Actual results: "Dracut: Signal caught, dropping to debug shell" Expected results: boot to GUI Additional info: this takes place on ASUS eee transformer T101MT
need more information: http://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#id570784
>Remove ''rhgb'' and ''quiet'' from the kernel command line it done by default >Add ''rd.shell'' to the kernel command line. This will present a shell should dracut be unable to locate your root device boot process ALREADY drops to shell! >Add ''rd.shell rd.debug'' to the kernel command line so that dracut shell commands are printed as they are executed commands before stop: wmi: mapper loaded EXT4-fs: mounted filesystem... dracut: checking Ext4... dracut: issuing e2fsck -a ... dracut: _Fedora-16-i686-: clean... dracut: Remounting... with -o noatime,ro Ext4-fs: Mounted filesystem in ordered data mode dracut: mounted root filesystem dracut: Warning: Signal caught! [lot of shell commands] echo Dropping to debug shell >With dracut >= 002-11, you can inspect the rd.debug output with: but how I can upload this file when boot not successfull? last lines are: + udevadm control --exit + udevadm info --cleanup-db + export RD_TIMESTAMP + set +x dracut Warning: Signal caught!
try: "rd.break=pre-pivot rd.shell" or if that does not work: "rd.break=mount rd.shell"
>try: "rd.break=pre-pivot rd.shell" "dracut Warning: Break pre-pivot" after Ctrl-D: "dracut Warning: Break before switch_root" again Ctrl-D: "dracut Warning: Signal caught!" again Ctrl-D: "kernel panic - not syncing: Attempt to kill init! >or if that does not work: "rd.break=mount rd.shell" "dracut Warning: Break mount" after Ctrl-D: "dracut Warning: Break before switch_root" again Ctrl-D: "dracut Warning: Signal caught!" again Ctrl-D: "kernel panic - not syncing: Attempt to kill init! Question is: what sould I to see after dropping to shell - by "signal" or else?
remove "quiet" and add "rd.debug" to see what dracut is doing...
Ops... but about WHAT was two letters above? ----cite---- >Remove ''rhgb'' and ''quiet'' from the kernel command line it done by default >Add ''rd.shell'' to the kernel command line. This will present a shell should dracut be unable to locate your root device boot process ALREADY drops to shell! >Add ''rd.shell rd.debug'' to the kernel command line so that dracut shell commands are printed as they are executed commands before stop: wmi: mapper loaded EXT4-fs: mounted filesystem... dracut: checking Ext4... dracut: issuing e2fsck -a ... dracut: _Fedora-16-i686-: clean... dracut: Remounting... with -o noatime,ro Ext4-fs: Mounted filesystem in ordered data mode dracut: mounted root filesystem dracut: Warning: Signal caught! [lot of shell commands] echo Dropping to debug shell >With dracut >= 002-11, you can inspect the rd.debug output with: but how I can upload this file when boot not successfull? last lines are: + udevadm control --exit + udevadm info --cleanup-db + export RD_TIMESTAMP + set +x dracut Warning: Signal caught! ------/cite--------- This is not "what dracut doing"? If no (why?) then what I should to see when dropped to debug shell?
Kernel 3.1.8 resolves this bug
cool :)