this post was submitted on 24 Aug 2023
12 points (100.0% liked)

Bug Bounties

160 readers
1 users here now

Does your OSS project have an issue that needs fixing? Post a bounty here!

Rules:

  1. Title must state bounty amount in USD, EUR, or BTC. Crypto bounties are allowed, just list rough USD/EUR/BTC equivalent amount as well. Crypto bounties must be paid out in a Top 20 market cap coin.
  2. OSS projects only
  3. Limit one post per bounty per month
  4. Your bounty must state who it is open to. If open to all, it can be in the body, if restricted by country it must be in the title.
  5. Nothing illegal or morally questionable
  6. No links to bountysource due to their ongoing payment issues.

We do not vouch for any projects posting bounties here or their ability to pay, you are responsible for evaluating risks yourself.

Related sites:

boss.dev - Post and find bounties, only some countries and currencies eligible

algora.io - Post and find bounties, supports more countries than boss.dev, roughly 14% fee.

founded 1 year ago
MODERATORS
 

Note that once solved, the code from this bounty will be made publicly available for anybody who wants to use it on their ubuntu installer. Please see link for full details including results of previous attempts to fix the issue.

Bounty Amount and Terms:

This bounty is for $250 USD and will be paid out via PayPal. This bounty amount will increase at random amounts and intervals until it is claimed. The bounty is open to residents of all countries except those under embargo or sanction by the US govt. The bounty will be paid out to the first person to produce a working preseed recipe or steps to achieve the desired result. When the bounty is successfully claimed, this post will be updated. By submitting your fix and claiming your bounty, you agree to release any code, preseed files, etc delivered to us into the public domain and surrender all rights you hold to them.

Problem:

We want to create an Xubuntu 22.04 ISO using Cubic. Using the preseed, we want to automatically partition the drive with a standard encrypted LVM setup (same one that is achieved manually via the GUI installer). Unfortunately, all existing recipes, which supposedly worked in prior Ubuntu versions, fail with the error No modifications can be made to the device: Encrypted Volume (sda1p2_crypt) for the following reasons: In use by LVM module group crypt or whatever the volume is titled in the partman recipe.

Desired Solution:

  • A preseed file which enables automatic encrypted LVM partitioning identical to what is achieved by choosing it manually in the GUI installer
  • This solution must be compatible with Cubic and may involve making modifications to the underlying iso, for example, by issuing commands at the chroot terminal provided by Cubic. It should not require any modifications to the ISO outside of the abilities provided by Cubic.
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (4 children)

What, exactly, is the current LVM setup?

does sda1p2_crypt need to be mounted and/or preserved at that point in the script?

What is the full command being run that fails?

The easiest answer might just be to remove it from the group and then add it back

pvremove /dev/sda1p2_crypt

your code

vgextend crypt /dev/sda1p2_crypt

[โ€“] [email protected] 1 points 1 year ago

Check the linked post for the full info and background about the issue including results of previous attempts at fixes

load more comments (3 replies)