Control: reassign -1 lvm2
On Wed, 16 Mar 2016 17:51:32 +0100 Gilles Sadowski
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 theVolum
Processing control commands:
> reassign -1 lvm2
Bug #818280 [systemd] upgrade-reports: System is unusable after "aptitute
safe-upgrade"
Bug reassigned from package 'systemd' to 'lvm2'.
Ignoring request to alter found versions of bug #818280 to the same values
previously set
Ignoring request to a
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 no
Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
I first ran
# aptitude safe-upgrade
which completed successfully.
["aptitude" automatically selected packages related to "console".]
I then installed the linu
4 matches
Mail list logo