Can you capture (or reproduce here) the text of grub's complaint? There may also be something in /var/log/messages or /var/log/boot.log which would be interesting. Also, assuming that you have used the boot parameters selinux=1 enforcing=0 to get your system up and running, there may be some 'audit .. denied' messages recorded or on your console during boot which might indicate what security feature is being ignored by setting 'enforcing=0' BobG >Hello, > >After I have create a kernel image on a SELinux enabled system, >grub complaint a access to a invalid block when the compiled >kernel should be booted. > >But when I turn off SELinux via a boot parameter this issue >didn't occured. > >It will nice, if anyone give me a hint. > >Best Regards: > >Jochen Schmitt >
