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.

Bug 731314

Summary: Installation without swap partition fail
Product: Red Hat Enterprise Linux 6 Reporter: Michal Kovarik <mkovarik>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2   
Target Milestone: rc   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-18 05:35:25 UTC Type: ---
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: 691780    
Attachments:
Description Flags
dracut log
none
anaconda.log
none
first booting log
none
next booting log none

Description Michal Kovarik 2011-08-17 10:40:31 UTC 
Description of problem:
After reboot from success installation system without swap, booting fails.

How reproducible:
always

Steps to Reproduce:
1. start graphical installation via vnc
2. make two partition - /boot and rootfs  or request to auto partition the disk and remove swap partition
3. complete the installation and reboot
  
Actual results:
after first start - dracut Warning: dracut: FATAL: Initial SELinux policy load failed. Machine in en
forcing mode. To disable selinux, add selinux=0 to the kernel command line.
dracut Warning: dracut: Refusing to continue


next starts - dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel

Expected results:
boot to installed system
Comment 1 Michal Kovarik 2011-08-17 10:41:28 UTC 
Created attachment 518646 [details]
dracut log
Comment 2 Michal Kovarik 2011-08-17 10:41:53 UTC 
Created attachment 518648 [details]
anaconda.log
Comment 3 Michal Kovarik 2011-08-17 10:43:41 UTC 
Created attachment 518649 [details]
first booting log
Comment 4 Michal Kovarik 2011-08-17 10:44:10 UTC 
Created attachment 518650 [details]
next booting log
Comment 5 Harald Hoyer 2011-08-17 11:55:28 UTC 
(In reply to comment #3)
> Created attachment 518649 [details]
> first booting log
Kernel command line: root=/dev/disk/by-path/ccw-0.0.3724-part1 rd_NO_LUKS crashkernel=auto LANG=en_US.UTF-8 rd_DASD=0.0.3724  KEYTABLE=us rd_NO_LVM rd_NO_MD cio_ignore=all,!0.0.0009 rd_NO_DM SYSFONT=latarcyrheb-sun16 BOOT_IMAGE=0 

dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/poli
cy.24: No such file or directory /sbin/load_policy: Can't load policy and enforcing mode requested: No such file or directory 
dracut Warning: Initial SELinux policy load failed. 
dracut: FATAL: Initial SELinux policy load failed. Machine in enforcing mode. To
 disable selinux, add selinux=0 to the kernel command line. 
dracut: Refusing to continue 


well, what can dracut do about that one?
Comment 6 Harald Hoyer 2011-08-17 12:00:47 UTC 
(In reply to comment #4)
> Created attachment 518650 [details]
> next booting log

Kernel command line: root=/dev/mapper/vg_rtt4-lv_root rd_DASD=0.0.3124 rd_NO_LUK
S LANG=en_US.UTF-8 rd_DASD=0.0.3724 rd_DASD=0.0.3524 rd_NO_MD cio_ignore=all,!0.
0.0009 rd_LVM_LV=vg_rtt4/lv_root  KEYTABLE=us crashkernel=auto SYSFONT=latarcyrh
eb-sun16 rd_DASD=0.0.3424 rd_DASD=0.0.3324 rd_DASD=0.0.3624 rd_DASD=0.0.3024 rd_
NO_DM rd_DASD=0.0.3224 BOOT_IMAGE=0 

dracut: Partial mode. Incomplete logical volumes will be processed. 
dracut: Couldn't find device with uuid dk7q7S-8bD8-3dHU-J3zO-LQOf-E1et-pzqmJx. 
dracut: Couldn't find device with uuid wxuFbB-6Pnc-Q31x-VHrt-Pm3s-zjBD-231P9f. 


so, your root device is distributed on all these dasds?
rd_DASD=0.0.3124
rd_DASD=0.0.3724
rd_DASD=0.0.3524
rd_DASD=0.0.3424
rd_DASD=0.0.3324
rd_DASD=0.0.3624
rd_DASD=0.0.3024
rd_DASD=0.0.3224
Comment 7 Michal Kovarik 2011-08-18 05:40:31 UTC 
Sorry, my mistake "next booting log" booted from bad partition.