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 ...
Status: NEW
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: 2023-03-24 08:27 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:
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

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< --------
DEBUG:anaconda.storage:Marking device sr0 as protected.
DEBUG:anaconda.storage:Marking 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 https://bugzilla.redhat.com/show_bug.cgi?id=1856264.

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

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