Description of problem: At beginning instalation of FC5 from DVD-ROM anaconda crash if in /etc/fstab exists line with ntfs filesystem. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. put to /etc/fstab file line like this: /dev/hdaXX /windows auto umask=0022,rw 1 1 where /dev/hdaXX is ntfs filesystem 2. Try install FC5 3. Actual results: anaconda crash Expected results: ignore ntfs or unknow filesystems from /etc/fstab? Additional info:
What message are you seeing from anaconda?
I don't precisely remember, message was in debug options, it was some error about mounting /dev/hda4 /windows auto umask=0022,rw 1 1 from /etc/fstab. It was of course during upgrade from FC4 to FC5, not install new system.
Unfortunately, if you use auto, there is no way to determine what filesystem type you _really_ want. We do ignore filesystems that are explicitly listed as 'ntfs', thus if you want it ignored on upgrade, use that instead of 'auto'
*** Bug 187281 has been marked as a duplicate of this bug. ***
*** Bug 187321 has been marked as a duplicate of this bug. ***
I initiated a bug report marked as duplicate. My fstab did not contain references to ntfs partitions (per se or auto) I eliminated step by step other file systems, vfat, smbfs, nfs etc. to no avail. Finally I removed fd0 the floppy and got past the crash. It is quite possible that the problem lies in ntfs but it appears that upgrades involving a number of file systems are a problem. I can provide the original fstab and the minimal file needed to upgrade or the diff file.
Charles - on closer inspection, you're getting the exact same problem but in a different way. Your /dev/fd0 mount is an auto fstype as well, so that exploded. We need to be handling these better in general.
*** Bug 187626 has been marked as a duplicate of this bug. ***
*** Bug 188500 has been marked as a duplicate of this bug. ***
*** Bug 189848 has been marked as a duplicate of this bug. ***
*** Bug 190051 has been marked as a duplicate of this bug. ***
*** Bug 191067 has been marked as a duplicate of this bug. ***
*** Bug 191256 has been marked as a duplicate of this bug. ***
*** Bug 206408 has been marked as a duplicate of this bug. ***