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.
=Comment: #0=================================================
Reinhard Buendgen <buendgen.com> -
Description of problem:
First installation phase, request for DASD range:
input: "DASD=none" as described in manual results in "Incorrect format for lower bound ..." message
-> documentation error, input should be "none" for interactive input.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- Please create the following tar archive and contact your bug assistant:
tar --exclude=/tmp/install.img -cvzf /logs.tgz /tmp /etc
=Comment: #1=================================================
Thorsten Diehl <thorsten.diehl.com> -
Red Hat Enterprise Linux Installation Guide says at the end of chapter 19.6:
Note
The installer requires the definition of a DASD. If a SCSI-only installation is desired, enter a
DASD=none parameter interactively in installation phase 1 or written into the parameter or CMS
configuration file. This will satisfy the requirement for a defined DASD parameter, while resulting
in a SCSI-only environment.
=Comment: #7=================================================
HEMALI G. TENGSHE <htengshe.com> -
1. Server architecture(s) (please list all effected) (x86/POWER6/Z/etc.):
Z series (Z/VM Guest)
2. Server type (9117-MMA/HS20/s390/etc.):
s390, Z10 machine
Type: 2097
Model: 724 E26
3. Other components involved (ixgbe/java/emulex/etc.): NA
4. Does the server have the latest GA firmware?
Yes.
5. Has the problem been shown to occur on more than one system?
Yes
6. Collect "sosreport" from machine problem was found on, and attach to bug.
7. What is the latest official distro build on which this bug has been seen ?
RHEL6.0 Snap7
8. Steps to reproduce.
During First installation phase, when requested for DASD range:
input: "DASD=none"
9. Business justification. This is needed as we approach the end of the release
for RHEL6.
This is documentation error, input should be "none" for interactive input.
I re-iterate from previous comments and confirm:
The mistake is in Red Hat Enterprise Linux Installation Guide at the end of chapter 19.6 in the text :
......
The installer requires the definition of a DASD.
If a SCSI-only installation is desired, enter a DASD=none parameter interactively in installation phase 1 or written into the parameter or CMS configuration file. This will satisfy the requirement for a defined DASD parameter, while resulting in a SCSI-only environment.
.....
Please correct the second sentence from wrong:
.., enter a DASD=none parameter ....
to correct:
.., enter a "none" parameter ...
Note: the user need to enter the parameter "none"
The second sentence in that text when corrected is
If a SCSI-only installation is desired, enter a "none" parameter interactively in installation phase 1 or written into the parameter or CMS configuration file.
Comment 4Ruediger Landmann
2011-02-07 03:51:32 UTC
(In reply to comment #0)
Thank you IBM
Joseph, this is indeed the correct component. Can you please confirm the version of the Installation Guide in which you see this error? You can find this information in the Revision History at the back of the guide.
The current version (1.0-4) is available at http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Installation_Guide/index.html
In this version, the text you identified is now towards the end of section 23.6, in the subsection "23.6.1.2.2. FCP Devices" and now reads:
Important — you must define a DASD
The installer requires the definition of a DASD. For a SCSI-only installation, enter none as the parameter interactively during phase 1 of an interactive installation, or add DASD=none in the parameter or CMS configuration file. This satisfies the requirement for a defined DASD parameter, while resulting in a SCSI-only environment.
I believe that the problem reported in this bug has been fixed some time ago.
Can you please review the text in the current version of the guide and confirm?
Regards
Ruediger Landmann
Engineering Content Services