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 810892 - Can't install RHEL6.2 in 3TB RAID HDD.
Summary: Can't install RHEL6.2 in 3TB RAID HDD.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: beta
: 6.2
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-09 14:56 UTC by chenyh6
Modified: 2012-07-05 15:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-05 15:26:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Warning message (1.34 MB, image/pjpeg)
2012-04-09 15:08 UTC, chenyh6 		no flags Details
View All

Description chenyh6 2012-04-09 14:56:55 UTC 
Description of problem:
Can't install RHEL6.2 in 3TB RAID HDD.

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


How reproducible:
Always reproduced

Steps to Reproduce:
=======================  STEP-BY-STEP PROBLEM RECREATION   =======================
    1: Connect Seagete 3TBx3 HDD in SATA1, SATA2 and SATA3.
    2: Power on the system and press "F1" to boot to BIOS.
    3: Setting SATA to RAID mode.
       Devices -> ATA Drive Setup -> Configure SATA as [RAID]
    4: Save and Exit BIOS.
    5: Press "Ctrl+i" to boot to RAID setup menu.
    6: Choose "Create RAID Volume" to set HDD to RAID5 then "Exit".
    7: System auto boot from DVD ROM with installation DVD.
    8: Install OS under UEFI mode.
    9: Follow install steps.
       You can observe that an error occurs during installing.
       Warning "Disks sda, sdb, sdc contain BIOS RAID metadata,....sda, sdb, sdc."
   10: Choose "OK" to do the next step.
   11: Still follow installation steps.
       You can observe that another error occurs then can't continue to install OS.
       "An unhandled......bug report."
  
Actual results:
Can't install RHEL6.2 in 3TB RAID HDD.

Expected results:
Can install RHEL6.2 in 3TB RAID HDD.

Additional info:
    1: This symptom is also observed with 3TB*2 under RAID0 or RAID1.
    2: This symptom isn't observed with 3TB HDD w/o RAID.
    3: This symptom isn't observed with seagate 2TB HDD under RAID0,1 and 5.
Comment 1 chenyh6 2012-04-09 15:08:56 UTC 
Created attachment 576236 [details]
Warning message
Comment 2 Jiri Olsa 2012-04-09 19:57:52 UTC 
This does not look like DUP issue, moreover it's not mentioned anywhere.
moving to anaconda
Comment 4 David Lehman 2012-04-09 21:46:48 UTC 
Please collect the following files from the shell on tty2 after the error has occurred and attach them to this bug report one at a time:

 /tmp/anaconda.log
 /tmp/storage.log
 /tmp/program.log
 /tmp/syslog

You can get to tty2 by pressing ctrl+alt+f2. Thanks.
Comment 5 David Lehman 2012-04-09 21:57:07 UTC 
(In reply to comment #0)
> Additional info:
>     1: This symptom is also observed with 3TB*2 under RAID0 or RAID1.
>     2: This symptom isn't observed with 3TB HDD w/o RAID.
>     3: This symptom isn't observed with seagate 2TB HDD under RAID0,1 and 5.

Are you certain the only difference between the reported case and item 3 above is the size of the drives? Is it possible that the firmware is a different revision?
Comment 6 chenyh6 2012-04-13 01:42:46 UTC 
The log files not able to got because the installation not yet finished and the installation stopped at very early beginning.
Thanks.
Comment 7 David Lehman 2012-04-13 12:57:37 UTC 
(In reply to comment #6)
> The log files not able to got because the installation not yet finished and the
> installation stopped at very early beginning.
> Thanks.

During install, there is a shell on tty2. You can get there by pressing ctrl+alt+f2. From there you can use scp or other means to copy the logs off to another system.
Comment 8 chenyh6 2012-04-17 02:41:54 UTC 
I can see the logs from tty2.But how can I copy the data from there?
I try to mount usb, but does not seem to able to mount it.Any suggestion?
Thanks a lot.
Comment 9 RHEL Program Management 2012-05-03 05:42:17 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 10 Chris Lumens 2012-05-03 18:29:45 UTC 
You can create a new directory under /, mount your USB device (partition and make filesystems if necessary) at that point, and then copy things over there.  Just like you'd do with a regular system.
Comment 11 David Cantrell 2012-07-05 15:26:24 UTC 
Closing bug due to lack of requested information.
Note You need to log in before you can comment on or make changes to this bug.