This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( 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 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 "", 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 1929105 - [Regression] Cannot install the system when hard disk is pre-hosting a CDROM image
Summary: [Regression] Cannot install the system when hard disk is pre-hosting a CDROM ...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Sagar Dubewar
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-16 08:37 UTC by Renaud Métrich
Modified: 2024-03-25 18:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Hard drive partitioned installations with iso9660 filesystem fails You cannot install RHEL on systems where the hard drive is partitioned with the `iso9660` filesystem. This is due to the updated installation code that is set to ignore any hard disk containing a `iso9660` file system partition. This happens even when RHEL is installed without using a DVD. To workaround this problem, add the following script in the kickstart file to format the disc before the installation starts. Note: Before performing the workaround, backup the data available on the disk. The `wipefs` command formats all the existing data from the disk. [literal,subs="quotes"] ---- %pre wipefs -a __/dev/sda__ %end ---- As a result, installations work as expected without any errors.
Clone Of:
Last Closed: 2023-09-18 15:02:50 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
Anaconda logs with kickstart in run/install (102.68 KB, application/gzip)
2021-02-16 08:37 UTC, Renaud Métrich
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4711 0 None Migrated None 2023-09-18 15:02:48 UTC

Description Renaud Métrich 2021-02-16 08:37:33 UTC
Created attachment 1757202 [details]
Anaconda logs with kickstart in run/install

Created attachment 1757202 [details]
Anaconda logs with kickstart in run/install

Description of problem:

When the hard drive contains a preloaded CDROM image, the system cannot be installed, due to python-blivet excluding any hard disk containing a iso9660 file system partition.
This happens even when the installation is performed without using a DVD at all.

The reason for this seems new detection code introduced with 8.3

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


How reproducible:


Steps to Reproduce:
1. Attach a disk to a VM and copy a DVD on it

  # dd if=/dev/sr0 of=/dev/sdb bs=10M
2. Detach the disk and attach it to a new VM to install

  The VM was configured with a DVD drive (unused), but this doesn't change anything.

3. Install the system using a kickstart (/run/install/ks.cfg in anaconda.tar.gz)

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
clearpart --all --initlabel
autopart --type=lvm
bootloader --location=mbr
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Actual results:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Saving storage configuration...
Failed to save storage configuration
No usable disks.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- device sr0 as protected. device sda as protected.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Expected results:

/dev/sda gets repartitioned and system installs

Additional info:

This is a critical issue for customers deploying system booting on a pre-initialized hard disk hosting a pre-boot environment.

Comment 1 Vojtech Trefny 2021-02-16 09:50:31 UTC
Moving this to Anaconda, it is marking all iso9660 devices as protected to be able to use them as installation sources. I believe the change was introduced because of

Related upstream PRs:

Comment 2 Jan Stodola 2021-02-16 09:54:03 UTC
The disk is also not visible in UI during manual installation.

A workaround for kickstart installation is to clean the disk in %pre script, for example:

wipefs -a /dev/sda

Comment 18 RHEL Program Management 2023-09-18 15:00:49 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 19 RHEL Program Management 2023-09-18 15:02:50 UTC
This BZ has been automatically migrated to the Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit for general account information.

Note You need to log in before you can comment on or make changes to this bug.