Bug 1007914
Summary: | Do not place /boot on iSCSI if it is not possible to boot from it | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Stodola <jstodola> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | medium | Docs Contact: | Clayton Spicer <cspicer> |
Priority: | medium | ||
Version: | 6.5 | CC: | anaconda-maint-list, cspicer, sbueno, tlavigne |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | s390x | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
The /boot Partition May Be Created on Network Storage on IBM System z
A known issue in Anaconda on IBM System z causes the /boot partition to be placed on an iSCSI disk if you do not explicitly configure this partition to be placed on a local drive (DASD). As a result, the system is unable to boot after the installation.
To work around this issue, specify a local drive for your /boot partition. When configuring storage using Kickstart, use the 'part /boot --ondisk=<local drive>' command to create /boot. If you are performing a manual installation, select only local drives in the Allowable Drives section of the Add Partition dialog. Do not use automatic partitioning.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-06 11:23:55 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: | |||
Bug Depends On: | |||
Bug Blocks: | 972747 |
Description
Jan Stodola
2013-09-13 14:44:16 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Engineering and Product Management along with CCS have determined that this bug should be described in the RHEL 6.7 Release Notes. Please update the Doc Text field with a description following the Cause Consequence Workaround Result model by April 22. Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |