Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1817150

Summary: LVMs across disks require the same disk logical block size
Product: Red Hat Enterprise Linux 8 Reporter: Arthur Benoit <abenoit>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.1CC: jstodola
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-26 07:11:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Arthur Benoit 2020-03-25 17:05:24 UTC
Description of problem:
During install anaconda tries to create a stripe across drives with 2 different disk logical block sizes. This then causes the following error:

Setting up the installation environment      
      
.      
       


      
Configuring storage      
      
..      
       


      
Creating disklabel on /dev/nvme0n1      
      
      
Creating lvmpv on /dev/nvme0n1p1      
    
        
Creating disklabel on /dev/sda      
      
      
Creating xfs on /dev/sda2      
      
       
Creating lvmpv on /dev/sda3      

      
An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for more details      

  
    self._task(*self._task_args, **self._task_kwargs) 
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 472, in start 
    self.run_task() 
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start 
    item.start() 
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start 
    item.start() 
  File "/usr/lib64/python3.6/site-packages/pyanaconda/installation.py", line 388, in doInstall 
    installation_queue.start() 
  File "/usr/lib64/python3.6/threading.py", line 864, in run 
    self._target(*self._args, **self._kwargs) 
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 286, in run 
    threading.Thread.run(self) 
gi.overrides.BlockDev.LVMError: Process reported exit code 5:   Devices have inconsistent logical block sizes (4096 and 512).      
      
      
What do you want to do now? 
1) Report Bug 
2) Debug 
3) Run shell 
4) Quit      

This is seen on intel-purley-04.khw1.lab.eng.bos.redhat.com      
       
https://beaker.engineering.redhat.com/jobs/4154267


Version-Release number of selected component (if applicable):

RHEL-8.1.0


How reproducible:

Always

Steps to Reproduce:
1. Clone Beker Job
2. Run job
3 Watch console

Actual results:

2 OS should install either not using LVM or using multiple volumes based on the like block sizes of the drives. 

Expected results:

OS should not fail to install.

Additional info:

Comment 1 Jan Stodola 2020-03-26 07:11:52 UTC
This issue is already tracked in bug 1804282, so I'm closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1804282 ***