Ask Your Question
0

Unable to boot after creating disk partition

asked 2018-12-08 15:32:00 -0600

kevingal gravatar image

On my computer, Fedora and Windows are installed on an SSD (sdb). I've been using them for months without issues.

Yesterday, I added a partition to my HDD (sda) for the first time and was able to use it. But now, when I try to boot, the boot hangs indefinitely after this message is printed:

IPv6: ADDRCONF (NETDEV_CHANGE): w1p31s0: link becomes ready

When I go to boot settings (UEFI), the boot drive priority is correct, i.e. the SSD comes before the HDD. Also, the grub script / config for my Fedora boot contains the line set root=(hd1,gpt5), which I believe corresponds to the drive & partition that Fedora is installed on. I can still boot into Windows just fine.

Any ideas? This is the most similar question I have been able to find, but I don't know whether it's the same problem or why running grub2-mkconfig -o /boot/grub2/grub.cfg in a live boot would fix it.

Thanks in advance for the help!

edit retag flag offensive close merge delete

Comments

I figured out that you can access a pseudo-shell during boot using ctrl+alt+f2, I’ve used this to further debug the situation.

The boot order is correct, according to efibootmgr output.

$ efibootmgr ... BootOrder: 0005, 0000, 0001 Boot0000* Windows Boot Manager Boot0001 Hard Drive Boot0005* Fedora

I don’t think it’s a networking issue because I was able to update grub's efi-related packages through dnf.

I tried removing the rhgb “graphical boot” option, no luck there.

kevingal gravatar imagekevingal ( 2018-12-09 06:33:28 -0600 )edit

I regenerated the grub config file, as was suggested in the question I linked above, but that had no effect.

kevingal gravatar imagekevingal ( 2018-12-09 06:36:24 -0600 )edit

Huh, it boots with an older kernel version. Maybe it’s more related to the updates I installed in the same session where I created the partition.

kevingal gravatar imagekevingal ( 2018-12-09 06:53:17 -0600 )edit

Digging further, using ‘journal-ctl’ I see that Light Display Manager is crashing on start-up. Ah, damn, my NVIDIA driver is failing to initialize.

kevingal gravatar imagekevingal ( 2018-12-09 07:03:03 -0600 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2018-12-09 08:06:31 -0600

kevingal gravatar image

Kernel version 4.19 required an update to the NVIDIA drivers. I followed this guide: https://www.if-not-true-then-false.co...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2018-12-08 15:21:46 -0600

Seen: 49 times

Last updated: Dec 08 '18