I'm trying to install F17 using PXE on a Dell M6600 laptop. We've been doing PXE installs on other Dell machines for quite a while, using F13 and F14 successfully. And the F17 installation on the M6600 seems to work. No errors are reported during the installation and no errors appear in the installation logs.
However, when we attempt to boot the newly installed system, the process gets almost all the way done, then utterly fails. Booting with the default options nearly fills the graphic balloon, then suddenly drops to these messages.
Cannot open font file True
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode
Neither choice actually works. No prompt is presented and no keyboard entry is accepted. (Keyboard interrupts are working as the NumLock light can be toggled properly.) The only exit is a power cycle.
Booting using grub to delete the rhgb and quiet options gets a number of errors.
Failed to start Software RAID Monitor Takeover.
Failed to start Configure read-only root support.
Failed to start Load legacy module configuration.
Failed to activate swap /dev/mapper/vg_laptop-lv_swap.
Failed to start Initialize storage subsystems (RAID, LVM, etc.).
Failed to start Initialize storage subsystems
Failed to start Monitoring of LVM2 mirrors, snapshots, etc. using dmeventd or progress polling.
Timed out waiting for device dev-mapper-vg_laptop\x2dlv_home.device
Followed by a huge number of "Job xxx failed with result 'dependency'.
" and "Dependency failed for xxx
". Then it drops to the unresponsive emergency mode.
Booting in recovery mode gets most of the same errors, then also drops to the unresponsive emergency mode.
Booting the machine from the F17 netinst/recovery image on a USB stick is successful. Examination of the files shows an empty /var/log/messages and no hint of an error in any other log file. I have saved copies of the files in /var/log/anaconda.
After chroot, "rpm -V" shows a huge number (4591!) of missing files. Among the missing files are most of the /lib/modules and /lib/firmware directories, many of the /etc/systemd/system files, and many binaries in /usr/bin. (A complete list is available if needed.) It is surprising to me that booting gets as far as it does.
The problem is absolutely repeatable and identical on several different machines. If it is a hardware issue, then it must be a general characteristic of the M6600.
I'm stuck on what to do next and suggestions are appreciated.