Volume group names ignored in boot-repair

Bug #1633676 reported by Andrew Laughton on 2016-10-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Boot-Repair
Undecided
Unassigned

Bug Description

If a volume group is renamed, "sudo vgrename kubuntu-vg 2016-vg", grub2 will no longer boot.
If it is then renamed back again "sudo vgrename 2016-vg kububtu-vg", grub2 will boot again.

Boot-repair does not detect and fix this problem.

YannUbuntu (yannubuntu) wrote :

Thanks Andrew for your report.

Do you know a way to detect that a group has been renamed ?

Changed in boot-repair:
status: New → Incomplete

Hi YannUbuntu

Sorry, I very rarely use this software, and have not used it since.
Possibly you could refresh reading the group name before writing to it
again.
It would not matter then if it had been renamed or not.

Andrew.

On 23 December 2016 at 06:20, YannUbuntu <email address hidden> wrote:

> Thanks Andrew for your report.
>
> Do you know a way to detect that a group has been renamed ?
>
> ** Changed in: boot-repair
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633676
>
> Title:
> Volume group names ignored in boot-repair
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/boot-repair/+bug/1633676/+subscriptions
>

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers