Description of problem:
I've tried installing Fedora 14 Alpha from hard disk. After selecting the hard disk partition and entering the path of the image, I press next. Then, the selection window disappears and nothing appears again. The blue screen remains on the screen and nothing happens. The last messages in other virtual screens say that the partition is successfully mounted and there is no error messages after wards. I've tried both with normal mode and using "nomodeset" options, the same thing happens. If I go to the second virtual screen (Alt+F2 or F3) and press Ctrl+Alt+Delete, the installer starts rebooting but then I see a dialoge in the blue screen (The first terminal) saying that the installer is unable to find appropriate installation image. But the DVD iso image and the images/install.img files are available in the path I enter.
Steps to Reproduce:
1. Boot Fedora 14 Alpha installer with a custom installation method
2. Select HardDisk installation mode
3. select the appropriate partition and enter the path containing Fedora 14 Alpha iso file and images directory containing install.img
4. press next
The dialoge disappears and nothing happens
It should either show an error dialog (which was shown if I reboot the system from another virtual terminal) or continue with the installation. In my case, I was sure that the selected partition and the entered path are OK, so it should continue with the installation. (I always install Fedora from hard disk on my system since it doesn't have any CD/DVD drive).
What, exactly, are the kernel commands you are booting with?
What is the path on your install partition and what does the directory look like? eg. ls -lR /path/to/install
Take a look at tty3 and tty5 for any errors.
Does tty2 have a shell? If so, could you go to /tmp/ and copy *log to another machine and attach them to this bug?
I've booted kernel and initrd without any special arguments:
This is the output of the ls command (The same problem with Fedora 14 Beta TC1):
[hedayat@localhost]AppInstall/Fedora% ls -lR .
-rwxrwxrwx. 1 hedayat hedayat 3277086720 2010-05-26 06:17 Fedora-13-i386-DVD.iso
-rwxrwxrwx. 1 hedayat hedayat 3630045184 2010-05-25 22:33 Fedora-13-x86_64-DVD.iso
-rwxrwxrwx. 1 hedayat hedayat 3539900416 2010-09-13 04:06 Fedora-14-Beta-x86_64-DVD.iso
drwx------. 1 hedayat hedayat 0 2010-05-26 10:16 images
-rwxrwxrwx. 1 hedayat hedayat 27283 2010-05-25 21:37 jigdo-lite
-rwxrwxrwx. 1 hedayat hedayat 157409280 2010-09-13 04:20 install.img
There is no errors in tty3 and tty5. The only error I see is when I reboot from tty3, which I see an error dialog in tty1 saying that it cannot find appropriate install image.
No, tty2 doesn't provide a shell yet.
Apparently there is something wrong with handling NTFS file systems. If I select an ext3/4 partition and write a wrong path, an error dialog appears and says that it cannot find correct installation images. But when I select my NTFS partition, it doesn't show any dialogs before rebooting, and the entered path doesn't make any difference (same thing happens with the correct path and any arbitrary paths).
Can you try with the images on an ext4 partition?
Also, can you try with only the F14 iso in the directory.
Using the same files in an ext4 partition works fine. There is certainly a problem with NTFS partitions. Whatever NTFS partition I select, regardless of the entered path, the installer just stops right after printing this message in tty3:
mounting device /dev/sdxx for hard disk installation
(And the message: "Path to stage2 images is ... " doesn't appear)
Having only F14 iso didn't help either (apparently, the installer does not reach that far at all. it simply stops when mounting or right after mounting an NTFS partition, without any error messages. (The tested partitions are clean and can be mounted and used under Linux without any problems)
NTFS isn't a supported as an install source. See http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/ch04s07.html
We should probably show an error though.
BTW, it worked fine in F13 (and I think F12 too), so it is a regression in F14 anaconda and should be (hopefully) easy to fix.
And I think the document is outdated, since before recent times in which I could install from NTFS successfully, anaconda showed an error when selecting NTFS partitions because it was unable to mount them at all in those times (apparently there were no NTFS support in the installer at all).
Apparently (I heard from someone), the installer's problem with NTFS does not end here. It seems that if you have an NTFS partition in your current Fedora's /etc/fstab and you try to upgrade your Fedora to F14, it'll stop working too. I'm not sure but that might be the same problem.
Installing from NTFS is not a supported feature.
OK, so maybe I should report a new bug as Feature Request, since on a modern hard drive (well, a Fedora featured harddrive!) it is not easy to find a FAT or a non-LVM ext partition (except the 500mb /boot partition); so hard disk install is very outdated and unusable in many modern hard disks!
Has an RFE been filed for this issue?
I intended to do so, but IIRC I didn't and I forgot to do it.
In searching for existing bugs, I found bug 651534. In particular, https://bugzilla.redhat.com/show_bug.cgi?id=651534#c9 sounds like it wouldn't be possible anymore.
No, it doesn't say that it is not possible to install from an NTFS partition anymore; it just says that there is no stage2 anymore where in Fedora 14 installer, anaconda hang when trying to mount stage2 from an NTFS partition. This is right, there is no stage2 so we don't have any problem here. However, we do want to mount Fedora iso from an NTFS partition, and now the installer hangs in this place (stage2 is now included in the initrd which is already completely loaded when installer reaches this step).
Therefore, we can open a new RFE and request for NTFS support. Apparently, the problem is still what stated there: the different behavior of mount for NTFS partitions. From what I read from that bug, it should be fairly easy to add the support back: either by putting a timeout when waiting for mount to terminate, or changing the mount.ntfs behavior (which seems to be harder or impossible). So, the timeout solution seems to be a good one. It can be used only when an NTFS partition is being mounted.
RFE filled: bug #748780