Bugzilla – Bug 306029
installation try to mount ntfs partition and exit install on error
Last modified: 2007-08-30 10:20:14 UTC
I have tried to install 10.3beta2 on a Acer TM 3000 with a windows NTFS partition. I have finished partitioning and package selection ans started the installation. After format my existing partition, yast try to mount the windows NTFS partition which fail with -3003. See attached logs and screenshot. 1) Why try yast to mount the windows partition which I didn't change and which is not needed while installation? 2) Why try yast to mount it writable via fuse/ntfs-3g, this is not needed and potential problematic if e.g. something go wrong while install (e.g. yast eat the memory and OOM-Killer kill the fuse process as only one screnario). If the mount is really needed (the only case I see atm is if the user try to install to a NTFS partiton, wich wasn't the case here) mount via kernel ntfs filesystem as RO 3) The partition is not needed for the installation. Why exit yast the installation process in this case? If yast exit also the complete error message for the user is _useless_ (see screenshot) there is no way for the user to change the fstab, there is only a 'OK' button which end the install process. There should be a 'Ignore' button which would allow the user to force the installation (with a text like this: "I know, what I do and I don't need the partition while installation.")
Created attachment 160772 [details] Yast logs
Created attachment 160774 [details] screenshot of the error message
It is just the known problem that ntfs-3g sometimes refuses to mount the fs. *** This bug has been marked as a duplicate of bug 300694 ***
NTFS-3G supports this case since version 1.826: http://ntfs-3g.org/releases.html
Do we really need to mount it during installation?
No, would there have been a feature request that NTFS filesystems should not be mounted during installation, this could certainly have been implemented. To my knowledge there was none. Me was told ntfs-3g is just a drop-in replacement for ntfs and it was integrated under this assumption.