Description of problem: (Note: not sure if anaconda, firstboot or selinux) On firstboot after network install of rawhide from download.fedora.redhat.com on 3/7/06, received errors as follows-- (hand copied, only pertinent) setting up Logical Volume Management: /dev/VolGroup1/FedoraHomes mkdir failed permission denied /dev/VolGroup1/FedoraHomes mkdir failed permission denied (msg repeated 9 more times) 11 logical volumes in volume group "VolGroup1" now added 10 logical volumes in volume group "VolGroup0" now added fsck.ext3: No such file or directory while tryping to open /dev/VolGroup1/FedoraHomes. /dev/VolGroup1/FedoraHomes The superblock could not be read or does not descirbe a correct ext2 filesystem. *** An error occured during the filesystem check *** Dropping you to a shell: the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery *** Run "setenforce 1" to enable give root password for maintenance (or type Control-D to continue) Version-Release number of selected component (if applicable): Network install of rawhide on 3/7/06 How reproducible: Every time. Tried two mirrors. Steps to Reproduce: 1. Create boot.iso cd from working system 2. Boot CD and select HTTP install 3. Select custom partitioning and select /dev/hda17 as /boot, format ext3; select /VolGroup0/Rawhide as /, format ext3; select /VolGroup1/FedoraHomes as /home, NOFORMAT 4. Select packages, custom and added KDE Destop 5. Install 6. boot new system firstboot Actual results: can't mount /dev/VolGroup1/FedoraHomes Expected results: normal first boot and continue on thereafter Additional info: When dropped to a shell, mounted /dev/hda17 on /boot and modified kernel parms in grub.conf by adding selinux=0. Firstboot then proceeded normally and rest of install proceeded normally. Disabled selinux when prompted.
Had you previously been running SELinux? This works fine for me when not using a pre-existing /home at least, so that's the only thing I can see maybe being different.
I had NOT been running selinux. Yes, /home was a pre-existing LV and had been used routinely and never with selinux on.
I have similiar problems after updating yesterday. Things were working fine on Friday and on Monday the problems started. At boot, udev can make /dev/vg{0,1} fine but can't create /dev/vg{2,3,4}: Mar 7 09:10:22 zero kernel: audit(1141740346.618:2): avc: denied { create } for pid=2118 comm="lvm.static" namella.="vg3" scontext=system_u:system_r:lvm_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=dir Mar 7 09:10:22 zero kernel: audit(1141740346.642:3): avc: denied { create } for pid=2118 comm="lvm.static" name="vg2" scontext=system_u:system_r:lvm_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=dir Mar 7 09:10:22 zero kernel: audit(1141740346.682:4): avc: denied { create } for pid=2118 comm="lvm.static" name="vg4" scontext=system_u:system_r:lvm_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=dir I had been running selinux all along and yum update to rawhide daily. New policy and new udev came on Monday. Relabeling didn't help.
Original problem still present in rawhide of 3/8/06.
Fixed in selinux-policy-2.2.23-7
I can confirm fixed with rawhide of 3/9/06. Nice looking install. Very smooth on LVs over software raid5 PVs.