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.
Created attachment 559106[details]
anaconda xml output
I would like to kickstartize my servers installation, but I can't, because anaconda is crashing all the time at disk partitioning.
I use this layout:
---------------------------
[root@ph04r01 ~]# cat /proc/mdstat
Personalities : [raid1] [raid10]
md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1]
975719424 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
bitmap: 1/8 pages [4KB], 65536KB chunk
md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
524276 blocks super 1.0 [4/4] [UUUU]
unused devices: <none>
[root@ph04r01 ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/md1 vg_ephan lvm2 a- 930.52g 0
[root@ph04r01 ~]# vgs
VG #PV #LV #SN Attr VSize VFree
vg_ephan 1 3 0 wz--n- 930.52g 0
[root@ph04r01 ~]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
root vg_ephan -wi-ao 20.00g
storage vg_ephan -wi-ao 906.52g
swap vg_ephan -wi-ao 4.00g
---------------------------
... and I just can't find any way how to kickstart it.
If I try to use the anaconda-generated kickstart which appears at /root/anaconda-ks.cfg after the installation, I need to change order of the lines (because it tries to use a PV before it is actually defined, etc. which is probably bug as well), anaconda crashes.
I tried to modify it a bit, even add %pre to overwrite first 32 MB of all hard drives, doesn't help.
The same problem occurs with:
- RHEL 6.1
- RHEL 6.2
- Scientific Linux 6.1
- CentOS 6.1
- CentOS 6.2
Attached is the latest kickstart and what it produces on SL 6.1 (because that's the last one I've tried so I collected the logs from it) - anaconda xml output + screenshot. Also you can have a look at lshw output.
Comment 7RHEL Program Management
2012-05-03 05:42:50 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.
Created attachment 559106 [details] anaconda xml output I would like to kickstartize my servers installation, but I can't, because anaconda is crashing all the time at disk partitioning. I use this layout: --------------------------- [root@ph04r01 ~]# cat /proc/mdstat Personalities : [raid1] [raid10] md1 : active raid10 sda2[0] sdd2[3] sdc2[2] sdb2[1] 975719424 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU] bitmap: 1/8 pages [4KB], 65536KB chunk md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1] 524276 blocks super 1.0 [4/4] [UUUU] unused devices: <none> [root@ph04r01 ~]# pvs PV VG Fmt Attr PSize PFree /dev/md1 vg_ephan lvm2 a- 930.52g 0 [root@ph04r01 ~]# vgs VG #PV #LV #SN Attr VSize VFree vg_ephan 1 3 0 wz--n- 930.52g 0 [root@ph04r01 ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert root vg_ephan -wi-ao 20.00g storage vg_ephan -wi-ao 906.52g swap vg_ephan -wi-ao 4.00g --------------------------- ... and I just can't find any way how to kickstart it. If I try to use the anaconda-generated kickstart which appears at /root/anaconda-ks.cfg after the installation, I need to change order of the lines (because it tries to use a PV before it is actually defined, etc. which is probably bug as well), anaconda crashes. I tried to modify it a bit, even add %pre to overwrite first 32 MB of all hard drives, doesn't help. The same problem occurs with: - RHEL 6.1 - RHEL 6.2 - Scientific Linux 6.1 - CentOS 6.1 - CentOS 6.2 Attached is the latest kickstart and what it produces on SL 6.1 (because that's the last one I've tried so I collected the logs from it) - anaconda xml output + screenshot. Also you can have a look at lshw output.