Linux MintThis forum is for the discussion of Linux Mint.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I browse my Windows partition in Mint, I have come to realise that the first time I do it after starting up, Mint must be doing something like “initialising” it, in order to read it?
I’m asking this because I have a Mint torrent client that I have set to save the d/l files on my Windows partition, enabling me to access it in both OSes.
However, as the torrent client starts up in when I login to Mint, it throws up a read error, until I access the Windows partition manually then restart the torrent client.
Is there some straightforward way to get Mint to access/initialise the Windows partition automatically before the torrent client starts?
This link might get you started in the right direction.
Thanks very much for the info. My fstab file looks like this:
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=fc8ebdee-1c9b-4c3f-979d-6c83f11d534d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda7 during installation
UUID=1e6c4cf2-5e03-49b0-9d23-ffe3b8ea8681 none swap sw 0 0
I used “sudo blkid” which told me the Data partition I want to access is:
Assuming that you want to mount it in /media/ntfs (as a suggestion, but it's your choice), create that folder (as root) and add the following entry to your fstab (you can place it at the end with a comment, just to indicate that you added the entry, but the placement isn't important):
Assuming that you want to mount it in /media/ntfs (as a suggestion, but it's your choice), create that folder (as root) and add the following entry to your fstab (you can place it at the end with a comment, just to indicate that you added the entry, but the placement isn't important):
To test the fstab once you've saved it, use sudo mount -a (it's better to know of any problems now rather than on reboot).
You've got me worried now. Does that mean there's a possibility nothing will work?
I assumed it would add an additional partition to initialise. but maybe it might ignore the normal one?
You've got me worried now. Does it there's a possibility nothing will work?
I assumed it would add an additional partition to initialise. but maybe it might ignore the normal one?
No need to be worried. All you are doing is auto mounting an existing ntfs partition (which you do manually anyway). It won't affect the auto mounting of any other partitions listed in fstab.
It is always good practice to run sudo mount -a after you've changed /etc/fstab to check that any changes work - if there are any errors, you can always revert to how it was before by re-editing the file or restoring a backup of the file that you made before you edited it.
Be brave, try stuff. (But make good backups!) You will learn more by reading and doing than by copy/paste. The link I gave included this simple statement for /etc/fstab:
Code:
/dev/sda3 /media/windows ntfs defaults 0 0
I just pasted that myself into my fstab (you need to change to sdb5, since that's what blkid reported to you). After a reboot, I found that /media/windows was indeed automatically mounted to my Windows partition. You don't have to name it "windows"... it can be anything you want. Sure, paste it at the end of fstab, but it may not matter. You'll probably have to be root or use sudo to open and save changes to fstab.
I don't use Windows 8/10, so I don't know about the hyberfile issue described in the link.
It is always good practice to run sudo mount -a after you've changed /etc/fstab to check that any changes work - if there are any errors, you can always revert to how it was before by re-editing the file or restoring a backup of the file that you made before you edited it.
there are a lot of good tips here, here is an additional advice:
booting with an incorrect fstab is not really possible, so be care about that. In that case you would need to boot into recovery mode or use a live cd to fix your fstab.
No need to be worried. All you are doing is auto mounting an existing ntfs partition (which you do manually anyway). It won't affect the auto mounting of any other partitions listed in fstab.
It is always good practice to run sudo mount -a after you've changed /etc/fstab to check that any changes work - if there are any errors, you can always revert to how it was before by re-editing the file or restoring a backup of the file that you made before you edited it.
I'm really reluctant to do anything now. Although users have given helpful advice on how to do this, I see there's the possibility my system might not even start up again if I've made an error?
If I did edit the file, then run the command "sudo mount -a" immediately afterwards, how would I know if there's something wrong? Will it tell me in plain English what's wrong/what to do?
The last post #9 says there's chance it won't boot if an error, and I'd have to use recovery mode, (which is quite worrying to me) or use a CD (my CD doesn't work anyway) to try to fix it.
I'm really reluctant to do anything now. Although users have given helpful advice on how to do this, I see there's the possibility my system might not even start up again if I've made an error?
Relax, paxolin. You are not planning any changes to the existing fstab that mounts your root partition. You are only adding a new mount instruction. If, for some reason, that new mount instruction does not work, your system will still boot. Your boot process might stop and tell you something is wrong, and ask if you want to proceed (skip mounting that partition). Simply answer SKIP, and the boot will continue successfully.
Therefore, the previous statement "booting with an incorrect fstab is not really possible," is nonsense... in this case.
Quote:
Originally Posted by paxolin
If I did edit the file, then run the command "sudo mount -a" immediately afterwards, how would I know if there's something wrong? Will it tell me in plain English what's wrong/what to do?
It will provide very helpful information about the error - in plain English.
Last edited by TxLonghorn; 02-13-2017 at 07:16 AM.
Relax, paxolin. You are not planning any changes to the existing fstab that mounts your root partition. You are only adding a new mount instruction. If, for some reason, that new mount instruction does not work, your system will still boot. Your boot process might stop and tell you something is wrong, and ask if you want to proceed (skip mounting that partition). Simply answer SKIP, and the boot will continue successfully.
Therefore, the previous statement "booting with an incorrect fstab is not really possible," is nonsense... in this case.
It will provide very helpful information about the error - in plain English.
I finally had a go at editing the fstab file.
First, I thought I would make a copy (using text editor) and save it it the etc folder as fstab-old, but I seem unable to do that? I don't understand why?
See the attached image.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
