boot-info blocks when trying to read LUKS partition

Bug #1785812 reported by Bougron on 2018-08-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Boot-Info
Medium
YannUbuntu
Boot-Repair
Medium
YannUbuntu

Bug Description

hello

My computer is in ubuntu version 18.04.1.
I decided to make ext4 encrypted partitions using a crypto-luks envelope

sudo blkid | grep LUKS
/dev/sda28: UUID="9aaa5da4-ddc2-4243-be35-f3dd0c05407a" TYPE="crypto_LUKS" PARTUUID="2c98f23a-d74f-4ddb-8332-b1be866d0c8c"
/dev/sda37: UUID="223d40d7-6718-4d2e-8add-757a5b90312b" TYPE="crypto_LUKS" PARTUUID="6ec87159-355e-417a-839d-87b665256d94"

boot-info wants to look at its fill rate but it forgets to ask me for the security phrase to allow editing.

He then completely blocks himself. I must kill him then.
If I manually climb this partition. he asks me if the computer has disks in RAIDS technology.
My answer is no. He then uses the LVM software. Which seems to me much worseT

thank you for doing something.
I think you should not try to read the contents of this type of partition. security requires!

Bougron (francis-bougron) wrote :

log with raids option

Bougron (francis-bougron) wrote :

boot-info.log

YannUbuntu (yannubuntu) on 2018-08-25
summary: - boot-info loop in the partition mount sequence
+ boot-info blocks when trying to read LUKS partition
Changed in boot-info:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → YannUbuntu (yannubuntu)
Changed in boot-repair:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → YannUbuntu (yannubuntu)
YannUbuntu (yannubuntu) wrote :

Thx Bougon for the report about LUKS.
Concerning the fact that boot-info should not use LVM in certain conditions, please can you open a new ticket ?

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

Other bug subscribers