Re: Failure to boot after update to Fedora 32

2020-05-04 Thread George N. White III
On Mon, 4 May 2020 at 18:21, Samuel Sieb wrote: > On 5/4/20 2:18 PM, George N. White III wrote: > > On Mon, 4 May 2020 at 17:04, Samuel Sieb > > wrote: > > You're using LVM for your file system partitions, nothing to do with > > systemd. > > You just need to r

Re: Failure to boot after update to Fedora 32

2020-05-04 Thread Samuel Sieb
On 5/4/20 2:18 PM, George N. White III wrote: On Mon, 4 May 2020 at 17:04, Samuel Sieb > wrote: You're using LVM for your file system partitions, nothing to do with systemd. You just need to run "e2fsck /dev/mapper/fedora-root" to fix the file system. The

Re: Failure to boot after update to Fedora 32

2020-05-04 Thread George N. White III
On Mon, 4 May 2020 at 17:04, Samuel Sieb wrote: > On 5/4/20 12:15 PM, Andrew Wood wrote: > > I had Fedora 31 installed on my laptop and I decided to update it to > > Fedora 32. > > > > After the reboot then Fedora stops and brings up a terminal session. I'm > > invited to inspect the system log w

Re: Failure to boot after update to Fedora 32

2020-05-04 Thread Samuel Sieb
On 5/4/20 12:15 PM, Andrew Wood wrote: I had Fedora 31 installed on my laptop and I decided to update it to Fedora 32. After the reboot then Fedora stops and brings up a terminal session. I'm invited to inspect the system log with 'journalctrl'. Looking through the log then I have: May 04 1

Failure to boot after update to Fedora 32

2020-05-04 Thread Andrew Wood
Hello, I had Fedora 31 installed on my laptop and I decided to update it to Fedora 32. After the reboot then Fedora stops and brings up a terminal session.  I'm invited to inspect the system log with 'journalctrl'. Looking through the log then I have: May 04 17:03:09 localhost systemd[1]: