| Summary: | Asus t101mt not boot after kernel update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | vde <vde> |
| Component: | dracut | Assignee: | dracut-maint |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dracut-maint, gansalmon, harald, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-16 11:18:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
vde
2011-12-24 00:04:34 UTC
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 :) |