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.
Description of problem:
After configuring a test run which specifies 2 data partitions to be ext3 (/usr/local and /mnt/testarea)
- \ | / - \ | / - \ | / - \ | /
Elapsed time since release of system processors: 668275 mins 4 secs
System has 128 Mbytes in RMA
/vdevice/v-scsi@30000002/disk@8100000000000000:-1,/etc/yaboot.conf: Unknown or corrupt filesystem
Can't open config file
Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-35.el6_0.1)
Enter "help" to get some basic usage information
Version-Release number of selected component (if applicable):
0923.3 tree
How reproducible:
very frequent if not always, have seen on power6 and power 7 hardware
Steps to Reproduce:
1.Install a ppc from Beaker using ext3 for /mnt/testarea and /usr/local (doubt that actual mount points matter that much, I'm leaving /boot and other system partitions alone.
2. Installation seems to complete normally, then boot fails
3.
Actual results:
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/09/1364/136469/282652//console.log
Expected results:
installation boots
Additional info:
the kickstart and other job info:
https://beaker.engineering.redhat.com/jobs/136958http://lab.rhts.englab.brq.redhat.com/beaker/logs/recipes/283434//ks.cfg