Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
beta still means beta though, and as masonm correctly pointed out, using a beta version of anything in a production environment is IMHO irresponsible if not foolhardy. Of course, that statement applies a lot more to a corporate environment than a home PC, but even so, presumably if there is a need or desire to mount the NTFS partition, the data on the NTFS partition must have some value, and therefore should not be subjected to unnecessary risk of damage or loss.
The OP didn't furnish details about where/how this would be used, and given that even the ntfs-3g maintainers state that the software is in beta status, the ability to write to NTFS in Linux should continue to be considered as experimental. Granted, ntfs-3g may be quite reliable, but until it loses the beta label I would only consider it for use in a non-essential, test environment. Just my 2 cents
Ntfs-3g is quite widely used already and there isn't anything wrong with its reliability. In fact, most distributions already replaced the "stable" captive-ntfs with the "beta" ntfs-3g because it's miles ahead both in reliability and speed.
This has turned out to be a great learing experience for me and for those users who are trying to switch over to Linux.
Regarding the importance of data in my Windows partition, I have taken a backup and if something at all happens, I do not risk much. I have decided long ago that I am going to use Linux. So I have to take chances (if any).
As suggested here I am mentioning the steps taken by me to activate ntfs-3g in my system. As I have already installed ntfs-3g earlier, I am starting from the next step.
SUBSYSTEM=="block", GROUP="disk", MODE="0640"
SUBSYSTEM=="block", GROUP="disk", MODE="0660"
b) Added my username by
$ usermod -a -G disk,fuse username
c) Changed permissions of the mounted NTFS directory :
$ chmod 777 /mnt/windows
d) As mentioned in SELINUX bug workaround :
Set SELINUX to "permissive" in /etc/selinux/config
e) Added this line to /etc/fstab:
/dev/hda1 /mnt/windows ntfs-3g dmask=022,fmask=133,noauto,locale=hu_HU.UTF-8,user 0 0
And then System reboot.
No error message in booting. But -
$ ls /mnt/windows
Tried in SU mode
$ ntfs-3g /dev/hda1 /mnt/windows
NOW IT IS WORKING. I have tried writing and that also worked.
So everything is ok except I have to give the ntfs-3g command everytime I boot? I will wait for your's suggestion.
I understand that ntfs-3g is in beta state and as because it is still having the beta tag the user runs the risk of using a beta software. But as correctly pointed out by J.W., it is the question of how much important data is there in my windows partition is the important factor. As I have taken a backup so I took the chance.
Thank you all for your help. Please help me to clear the last hurdle.
Remove the 'noauto' option from the /etc/fstab line. It means don't mount during boot.
Thanks, now it is working correctly.
I would like to point it out here that while shutting down Fedora I am getting an unmount (audit) error. I can't read it properly because by then it is switching off. But from the language of the error message it seems if I unmount the windows partition before switching off then it would be better. Do I have to unmount the partition everytime before switching off? Please advise.
Can you find anything in /var/log/messages? It seems you still have some SELinux bug. It's a very serious problem if you can't unmount filesystems during shutdown because you can easily lose data. This is true for any filesystem.
You should have opened a new thread to ask your question, as it is not related to read/write mounting of a ntfs partition.
But I will try to answer nevertheless.
1) look for the Windows partition on your disk :
in a root console do fdisk -l <device>
from 'man fdisk'
The device is usually one of the following:
(/dev/hd[a-h] for IDE disks, /dev/sd[a-p] for SCSI disks, /dev/ed[a-d] for ESDI disks, /dev/xd[ab] for XT disks).
A device name refers to the entire disk.
eg, on my machine 'fdisk -l /dev/hda' gives : Périphérique Amorce Début Fin Blocs Id Système
/dev/hda1 * 1 3698 29704153+ 7 HPFS/NTFS
so the Windows partition is /dev/hda1 for me
2) create a directory where you want to mount that partition :
eg, mkdir /mnt/windows
3) try to mount it manually under root, running : mount -t ntfs /dev/hda1 /mnt/windows
change the partition and the directory accordingly.
1) To use fuse (which ntfs-3g does), you should be a member of the fuse group.
2) selinux can not parse a filesystem name containing a dash. Thus:
..2a) You can not use ntfs-3g unless you set selinux to "permissive" mode.
..2b) While you should review the selinux audit logs for intrusion attempts, etc, when you're running in "permissive" mode, the messages re "fuse" and "ntfs-3g" are expected, and can be ignored.
Thanks for the quick answer man...I succeeded in mounting my ntfs partitions, but....after I restart, they aren't mounted anymore, and when the system checks whether all it's components are OK( just after the boot loader ), it says right there that he couldn't mount the partitions because smthing with FUSE...(I didn't memorize the entire error). The thing is that I added in the file /etc/fstab the lines( sda1 & sda5 being my windows partitions ) :
[HTML]/dev/sda1 /media/c_drive ntfs-3g ro,defaults,umask=0222 0 0
/dev/sda5 /media/d_drive ntfs-3g ro,defaults,umask=0222 0 0 [/HTML]
But it seems not working, so every time I start the system, I hae to manually remount my ntfs partitions :|
See if you can find the error message in /var/log/messages. I suspect that the message is that your fuse kernel module is an older version, and that ntfs-3g requires version 2.6.3 to work (more) reliably. On my Fedora system, I had to compile that version from source since the Fedora project hasn't yet updated their distributed version.
For what it's worth, my fstab entry looks like this:
I notice that you're mounting the filesystem "ro." If you don't need write access, the drivers from the ntfs-project are (slightly) easier to install and use. (Just search for "ntfs" in your repository.