Created attachment 1165041 [details] kickstart file Description of problem: Enters dracut emergency shell after installation with autopart encrypted. Version-Release number of selected component (if applicable): rhev-hypervisor7-ng-4.0-20160527.0.x86_64 imgbased-0.7.0-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install NGN on a machine with kickstart file in attachment. key parameters: autopart --type=thinp --encrypted --passphrase=$1$wHbL1u1G$gqz7IPh.ctaUHFMpQnyKl/ 2. During rebooting , input the passphrase 3. Check system after rebooting process Actual results: Enters dracut emergency shell after rebooting. Expected results: System reboot successfully, and login screen prompt. Additional info:
Created attachment 1165042 [details] resosreport
Does this also happen with RHEL7?
Hi Fabian, I will give the feedback later since I need to debug some problems and future research.
Test Version RHEL-7.2-20151015.0-Server-x86_64-dvd1.iso Test Steps: 1. Get squashfs image from RHEL DVD iso 2. Get passphrase via command #openssl passwd -1 3. Install NGN on a machine with kickstart file key parameters: autopart --type=thinp --encrypted --passphrase=$1$wHbL1u1G$gqz7IPh.ctaUHFMpQnyKl/ 4. Check the process of installation Result: Install fail, since "Could not open X display" More info: Using rhev-hypervisor7-ng-4.0-20160608.0.x86_64 for retesting, and part /boot individually which is not encrypted, also install fail, the "Could not open X display" prompted.
LUKS does not the same crypt algorithm as the system password, and a pre-encrypted passphrase cannot be set in kickstart. The passphrase set for this install is literally "$1$wHbL1u1G$gqz7IPh.ctaUHFMpQnyKl/".
Hi, i am experiencing a similar issue. Description of problem: Was attempting to install CentOS v7.9 from the Bootable ISO onto my local machine to act as a branch webserver. During the EFI installation a warning displayed and the OS entered into Emergency Shell and instructed me to save some files from the install and lodge a bug report regarding the issue. I was then unable to finish the installation. Additionally I know that the machine likely needs to have its drivers updated, but I was intending on doing that once the OS was installed as its tricky without an OS to install the correct drivers (for me in any case), I was planning to install this OS, update the drivers then re-install the OS once the new drivers were in place. Version-Release number of selected component (if applicable): This was running on a Dell Optiplex 9020, i was installing from a DVD disk that I burnt from a web ISO of CentOS version 7.9 (it was the complete version) How reproducible: Havent attempted to reproduce this particular issue, however I can tell you that all my machines are fighting me every step of the way to making them more secure and it has been a nightmare even getting this far. It appears that someone somewhere is intent on making my life as difficult as humanly possible to setup a network. Steps to Reproduce: 1. Burn a DVD of the ISO directly over the ftp connection 2. Booted from the cd, auto install failed, loaded directly from grub by chainloading from the included key 3. Boot commenced and then stopped and entered an emergency shell and instructed the following two files be provided Actual results: System not bootable Expected results: Installed version of CentOS running in a safe and secure manner, free from any 3rd party or proprietary code, configured in a secure manner and suitable for production use for a small ecommerce comapny. Additional info:
Created attachment 1974975 [details] Log files system requested i include with this report Description of problem: Was attempting to install CentOS v7.9 from the Bootable ISO onto my local machine to act as a branch webserver. During the EFI installation a warning displayed and the OS entered into Emergency Shell and instructed me to save some files from the install and lodge a bug report regarding the issue. I was then unable to finish the installation. Additionally I know that the machine likely needs to have its drivers updated, but I was intending on doing that once the OS was installed as its tricky without an OS to install the correct drivers (for me in any case), I was planning to install this OS, update the drivers then re-install the OS once the new drivers were in place. Version-Release number of selected component (if applicable): This was running on a Dell Optiplex 9020, i was installing from a DVD disk that I burnt from a web ISO of CentOS version 7.9 (it was the complete version) How reproducible: Havent attempted to reproduce this particular issue, however I can tell you that all my machines are fighting me every step of the way to making them more secure and it has been a nightmare even getting this far. It appears that someone somewhere is intent on making my life as difficult as humanly possible to setup a network. Steps to Reproduce: 1. Burn a DVD of the ISO directly over the ftp connection 2. Booted from the cd, auto install failed, loaded directly from grub by chainloading from the included key 3. Boot commenced and then stopped and entered an emergency shell and instructed the following two files be provided Actual results: System not bootable Expected results: Installed version of CentOS running in a safe and secure manner, free from any 3rd party or proprietary code, configured in a secure manner and suitable for production use for a small ecommerce comapny. Additional info:
From journal.log: Jul 10 12:06:44 localhost dracut-initqueue[736]: mount: /dev/sr0 is write-protected, mounting read-only Jul 10 12:06:44 localhost kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Jul 10 12:06:44 localhost kernel: ISO 9660 Extensions: RRIP_1991A Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: loop: module loaded Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: Buffer I/O error on dev loop0, logical block 127328, async page read Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: Buffer I/O error on dev dm-0, logical block 127328, async page read Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: attempt to access beyond end of device Jul 10 12:06:44 localhost kernel: sr0: rw=0, want=19922100, limit=3145728 Jul 10 12:06:44 localhost kernel: Buffer I/O error on dev dm-1, logical block 127328, async page read It could be an incorrectly downloaded/burnt ISO.