Re: Unable to mount partitions on boot with latests F 21 Alpha updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well that did the trick, thanks.

-Erinn

On Fri, Sep 26, 2014 at 11:14 AM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:
On Fri, Sep 26, 2014 at 1:08 PM, Erinn Looney-Triggs
<erinn.looneytriggs@xxxxxxxxx> wrote:
> F 21 Alpha itself works just fine for booting and rebooting, unfortunately
> after updating all packages certain partitions fail to mount (usually home)
> which in turn drops me into single user mode.
>
> I am able to do a vgchange -ay and home will be detected and mount, but
> doing a ctl-d or systemctl default at that point results in a frozen system.
>
> There are a heap of updates since alpha so I can't say for sure which one
> causes the issue. Looking at the journal on a failed boot shows
> systemd-udevd core dumping multiple times. Unfortunately, given my workflow
> at this point I don't have a copy of the logs for you folks.
>
> A fresh install renders the same thing on update.
>
> Anyone else experiencing this? Looking through bugzilla I couldn't find a
> match.

Blacklist the microcode driver and downgrade the microcode_ctl package
if you have version -8.

josh
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux