Created attachment 730523 [details] dracut shell Description of problem: Installed fedora 18 and boot is ok. After running update it is not able to boot correctly with updated kernels. Always driven to an emergency shell Version-Release number of selected component (if applicable): 3.8.4-202.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. update system after installing fedora 18 2. boot with new kernel --> emergency shell 3. bot with 3.6.10-4.fc18.x86_64 Actual results: emergency shell Expected results: normal boot Additional info: tried with 3.7.9-205.fc18.x86_64 and 3.8.4-202.fc18.x86_64 on two different blades. Same result. I suspect scsi controller cause, due to attached screenshot when booting. lshw gives: ... *-scsi description: SCSI storage controller product: SAS1064ET PCI-Express Fusion-MPT SAS vendor: LSI Logic / Symbios Logic physical id: 0 bus info: pci@0000:04:00.0 logical name: scsi1 version: 08 width: 64 bits clock: 33MHz capabilities: scsi pm pciexpress msi msix bus_master cap_list rom scsi-host configuration: driver=mptsas latency=0 resources: irq:30 ioport:1000(size=256) memory:b1910000-b1913fff memory:b1900000-b190ffff memory:b1c00000-b1dfffff *-disk description: SCSI Disk product: Multi-Flex vendor: Intel physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sda version: 0308 serial: 4C202020000000000000000078164A5806D0806B size: 20GiB (21GB) capacity: 20GiB (21GB) capabilities: 15000rpm partitioned partitioned:dos configuration: ansiversion=5 sectorsize=512 signature=00020619 ...
Is there a way for you to get the full contents of dmesg off the machine? The error messages in the picture are truncated and don't really give us much to work with. Also, could you attach the dmesg output from a boot with the working kernel?
what can do when I'm put into a dracut shell to collect output and then send to you? Do I have to mount sort of floppy and copy there? Can I use any command when in a dracut shell? Could it help if I start with a serial console? Have you any indication about fedora 18 settings for it in case? Gianluca
Hello, the best I was able to do in the mean time is install kernel-3.8.6-203.fc18.x86_64 and record a boot session where I ran journalctl command at the dracut emergency shell. See here the webm file generated https://docs.google.com/file/d/0BwoPbcrMv8mvMllXNE5udlcyZFE/edit?usp=sharing Gianluca
Hello, any further info I can provide?
Are you still having issues with 3.9.8? I can't really see much from the webm video. The messages are truncated on the right side. It would be better if you could bring up networking manually and copy off the output of dmesg to some other machine.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days