Bug 1471453 - kernel /boot/initramfs-4.13.0-0.rc0.git6.1.fc27.x86_64 fails to boot
Summary: kernel /boot/initramfs-4.13.0-0.rc0.git6.1.fc27.x86_64 fails to boot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-16 02:17 UTC by George R. Goffe
Modified: 2017-08-07 12:54 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-07 12:54:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Console from VirtualBox VM that shows the problem (33.52 KB, text/plain)
2017-07-19 15:39 UTC, George R. Goffe
no flags Details
gziped flat file of boot log and other debug files... (145.10 KB, application/x-gzip)
2017-07-20 00:48 UTC, George R. Goffe
no flags Details

Description George R. Goffe 2017-07-16 02:17:34 UTC
Description of problem:

I have updated this system to 4.13.0-0.rc0.git6.1.fc27.x86_64 but that fails to boot and seems to leave me in the grub shell. Is that right? Limited commands available? I'd like to post a system.journal file but I can't seem to figure out how to mount a USB drive. The jounal shows, I think, a problem with /sysroot/sysroot/mount.usr. Something in the system thinks is wrong with my /usr partition maybe?

I have tried and succeeded running dracut and replacing the initramfs without any luck. The filesystem did have a minor problem but that was fixed. Rerunning dracut and reboot still didn't solve the problem. The system will boot from an earlier kernel so maybe this bug report isn't "urgent". The rest of the system is up to date with respect to the Fedora 27 x86_64 (rawhide) repo. 

uname -a
Linux fc27 4.13.0-0.rc0.git5.1.fc27.x86_64 #1 SMP Tue Jul 11 15:31:13 UTC 2017 x86_64 GNU/Linux

Version-Release number of selected component (if applicable):
see above

How reproducible:
all to readily

Steps to Reproduce:
1.see above
2.
3.

Actual results:
grub shell(?)

Expected results:
"normal" boot

Additional info:

Comment 1 George R. Goffe 2017-07-19 15:39:17 UTC
Created attachment 1301185 [details]
Console from VirtualBox VM that shows the problem

I had a VM that mirrored the "real" system that has the problem. I updated the VM with "dnf -y upgrade" and then tried a reboot. Alas, same problem on the newer kernel. Perhaps this console log can help the debugging process?

Here is what fdisk says about the system drive:

fdisk -l /dev/sda
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xf02bc8e0

Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda1  *         2048    4196351    4194304     2G 83 Linux
/dev/sda2         4196352    8390655    4194304     2G 83 Linux
/dev/sda3         8390656   25167871   16777216     8G 82 Linux swap / Solaris
/dev/sda4        25167872 1953525167 1928357296 919.5G  5 Extended
/dev/sda5        25169920   81793023   56623104    27G 83 Linux
/dev/sda6        81795072  201332735  119537664    57G 83 Linux
/dev/sda7       201334784  320872447  119537664    57G 83 Linux
/dev/sda8       320874496 1953525167 1632650672 778.5G 83 Linux

Comment 2 Laura Abbott 2017-07-19 18:06:37 UTC
Can you follow the instructions at https://fedoraproject.org/wiki/How_to_debug_Dracut_problems?rd=Dracut/Debugging#Identifying_your_problem_area to get more debugging output?

The serial console output is truncated slightly so it's hard to see what actually failed.

Comment 3 George R. Goffe 2017-07-20 00:48:16 UTC
Created attachment 1301475 [details]
gziped flat file of boot log and other debug files...

This file is the output of the script command, unedited. As such, it contains all special characters generated by the keyboard.

Comment 4 George R. Goffe 2017-07-26 12:59:33 UTC
Hi,

Is anything happening with this bug?

Thanks,

George...

Comment 5 Harald Hoyer 2017-08-07 12:51:04 UTC
(In reply to George R. Goffe from comment #0)
> Description of problem:
> 
> I have updated this system to 4.13.0-0.rc0.git6.1.fc27.x86_64 but that fails
> to boot and seems to leave me in the grub shell. Is that right? Limited
> commands available? I'd like to post a system.journal file but I can't seem
> to figure out how to mount a USB drive. The jounal shows, I think, a problem
> with /sysroot/sysroot/mount.usr. Something in the system thinks is wrong
> with my /usr partition maybe?

the /sysroot/sysroot issue is fixed with:

https://github.com/systemd/systemd/pull/6411

Comment 6 Harald Hoyer 2017-08-07 12:54:37 UTC
should be fixed with systemd-234-5


Note You need to log in before you can comment on or make changes to this bug.