- 1 ia64-rawhide known issues and workarounds
- 1.1 General failure to install rawhide trees
- 1.2 Installing using VNC fails
- 1.3 /boot/efi must be "efi" type not "vfat"
- 1.4 HP Smart Array boot failures
- 1.5 Anaconda crash on HP Smart Array with no disks
- 1.6 yum update complains: initscripts needs /sbin/pidof, this is not available."
- 1.7 kernel boot hangs or cannot mount /dev/root
ia64-rawhide known issues and workarounds
General failure to install rawhide trees
It is not unusual during the development cycle to have problems in anaconda that prevent installing. Often the best way to get a rawhide tree installed is to do a yum update from a previous installable version. This can be done by:
1. make sure all repos in /etc/yum.repos.d/ are disabled by setting "enabled=0" in each one.
2. create the file /etc/yum.repos.d/rawhide.repo
[rawhide] name=latest nightly for $basearch baseurl=http://ia64.koji.fedoraproject.org/fedora-ia64/rawhide-latest/development/ia64/os/ enabled=1 gpgcheck=0
Installing using VNC fails
There is no known workaround for this at this time. You must use either the text or the normal GUI install under X.
/boot/efi must be "efi" type not "vfat"
Manually partitioning fails if /boot/efi is selected as "vfat" filesystem type. The workaround is to select "efi" from the list of filesystem types. This issue is also seen when trying to reuse an existing /boot/efi partition. Due to this it is currently not possible to install onto an existing /boot/efi partition.
HP Smart Array boot failures
Occational boot failures on HP Smart Array (aka "cciss") devices. This is still under investigation and it is unclear what the root cause is. Users who have seen this report good results by booting with selinux disabled (selinux=0).
Anaconda crash on HP Smart Array with no disks
When installing on a system that has an HP Smart Array card that has no disks configured anaconda will crash. The only known workaround at this time is to be sure all Smart Array cards have disks configured on them or to remove the card. This is still under investigation.
yum update complains: initscripts needs /sbin/pidof, this is not available."
There were some oddities on the transition from the old sysvinit to the new upstart model (if anybody has documentation on what changed please let me know). Depending on when you did yum updates you may not be able to update cleanly. If so try the following steps:
rpm -e sysvinit --nodeps yum install sysvinit-tools yum install event-compat-sysv
kernel boot hangs or cannot mount /dev/root
We have seen a couple of problems resulting in the system not being able to mount the root filesystem on bootup.
booting with selinux=0 often helps, note, for this specific issue it is not enough to just have selinux disabled in /etc/selinux/conf.