[Bug 2126780] Re: cryptsetup - OPAL range 1 does not match device length

[Ravi Kant Sharma]

** Tags added: rls-nn-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/2126780

Title:
  cryptsetup - OPAL range 1 does not match device length

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Hello,

  We are running into an issue using LUKS to manage OPAL drives that are
  30TB in size.

  # cryptsetup luksFormat --hw-opal-only /dev/nvme0n1

  WARNING!
  ========
  This will overwrite data on /dev/nvme0n1 irrevocably.

  Are you sure? (Type 'yes' in capital letters): YES
  Enter passphrase for /dev/nvme0n1:
  Verify passphrase:
  Enter OPAL Admin password:
  Verify passphrase:
  Compensating device size by 48 sectors to align it with OPAL alignment granularity.
  root at basis-loader01:~# cryptsetup open /dev/nvme0n1 nvme_PHAC2431012530PGGN
  Enter passphrase for /dev/nvme0n1:
  OPAL range 1 length 60011631232 does not match device length 60011631280.

  # lsb_release -rd
  No LSB modules are available.
  Description:	Ubuntu 24.04.3 LTS
  Release:	24.04

  Based on some research and testing, I opened an issue up on the cryptsetup project located here.
  https://gitlab.com/cryptsetup/cryptsetup/-/issues?sort=created_date&state=closed&first_page_size=20&show=eyJpaWQiOiI5NjEiLCJmdWxsX3BhdGgiOiJjcnlwdHNldHVwL2NyeXB0c2V0dXAiLCJpZCI6MTc0Mjc1MDYyfQ%3D%3D

  It looks like this issue is fixed in 2.7.2, which is mentioned at the
  bottom of the thread. I also did verify that 2.8.0 was functional too.

  Is it possible to backport 2.7.2 into 24.04? If this isn't the correct
  form for such things, please let me know. Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2126780/+subscriptions