Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

Michael Biebl biebl at debian.org
Mon Oct 31 23:14:00 GMT 2016


Control: reassign -1 lvm2

On Wed, 16 Mar 2016 17:51:32 +0100 Gilles Sadowski
<gilles.sadowski at ulb.ac.be> wrote:
> Hi.
> 
> It turned out that the problem was related to LVM partitions not being
> "available" while "systemd" was trying to run "fsck" on them.
> 
> In maintenance mode, I just ran
> 
>  # vgchange -a y theVolumeGroupName
> 
> and they were automatically detected, and mounted.
> Then the boot sequence could proceed normally.
> 
> Why couldn't "systemd" figure out the problem?

Problem seems to happen under "sysinit" as well.

> Upon rebooting, I chose the option "sysinit" (rather than the default grub entry).
> This led to a flood of "Failed" during the boot sequence, seemingly caused by a read-only root filesystem.


So might be a LVM problem. Unfortunately the bug report is very light of
details. Might be just a misconfigured system


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161101/8bf18041/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list