The installation of Fedora 18 on my new desktop system hanged in the grub install. It turns out that the os-prober part of grub2-mkconfig hangs for some reason. During the install the prober had worked for 20+ minutes, and nothing had happened
Can you attach Anaconda log files (in /tmp/ during installation) or run os-prober from command line and attach its output in syslog?
It appears that the call to blkid in the line: blkid | grep btrfs | cut -d ':' -f 1 "Never" returns. This is in the partitions function.
Looks like "never" was a little pessimistic: [root@abuse grub.d]# time blkid /dev/sda1: UUID="694780e7-e13e-4424-af4e-ed452b7e6fff" TYPE="ext4" /dev/sda2: UUID="4q3Nxi-2VtO-qd0o-JIMV-8q59-Rbsg-Ted7QR" TYPE="LVM2_member" /dev/mapper/fedora-swap: UUID="d0f9ce4c-5215-4ccb-b0c3-460a04e151d6" TYPE="swap" /dev/mapper/fedora-root: UUID="0473bb89-b294-4d94-ba5b-8d60f9a74b66" TYPE="ext4" /dev/mapper/fedora-home: UUID="fe7c7e14-f622-46d5-bcef-ab83aaa0ed44" TYPE="ext4" real 11m34.600s user 0m0.002s sys 0m0.009s Still odd that it takes 11:34.6 wall clock time.
Had to reboot the box for other reasons and the problem went away: [root@abuse ~]# time blkid /dev/sda1: UUID="694780e7-e13e-4424-af4e-ed452b7e6fff" TYPE="ext4" /dev/sda2: UUID="4q3Nxi-2VtO-qd0o-JIMV-8q59-Rbsg-Ted7QR" TYPE="LVM2_member" /dev/mapper/fedora-swap: UUID="d0f9ce4c-5215-4ccb-b0c3-460a04e151d6" TYPE="swap" /dev/mapper/fedora-root: UUID="0473bb89-b294-4d94-ba5b-8d60f9a74b66" TYPE="ext4" /dev/mapper/fedora-home: UUID="fe7c7e14-f622-46d5-bcef-ab83aaa0ed44" TYPE="ext4" real 0m0.008s user 0m0.002s sys 0m0.003s Can the OP try rebooting and see if the problem goes away for him too?
I'm not sure, but looks like a hard disk issue. blkid can take a long time if hard disk is problematic. Have you seen any ATA errors in your dmesg or /var/log/messages/ ? does your blkid wait when trying to print data about a specific partition?
Only saw the delay on that particular update and the problem went away after the reboot. Since I can't recreate the problem, I can't tell you if it tracks to a specific partition, sorry. Also, I just grabbed and installed the latest FC 18 update which includes a kernel update and, again, no problem with grub2-mkconig or blkid. Seems to be specific to what got changed in the particular update we (me and the OP) installed.
OK, since blkid is not expected to take long, it doesn't seem to be an os-prober bug. Anyway, it seems to be fixed already. so closing this bug.