HOWTO Automount in Hardy

[kylirh]

Thank you very much for this! It was uber annoying having to manually mount my partitions at every startup.

[biebel]

Alternatively you could use the "NTFS configuration" tool to achieve all this with just a few clicks.

[brokenLockpick]

Nice guide worked for me.

[rich-dvd]

this is the easiest way i found to automount:

http://onlyubuntu.blogspot.com/2008/05/auto-mounting-internal-drives-in-ubuntu.html[/URL]

but make sure you change all the false values to true instead of just the one he mentions, otherwise i found it didnt work.

[rich-dvd]

Sorry let me repost that link:

http://onlyubuntu.blogspot.com/2008/...in-ubuntu.html

[biebel]

Ok ntfs-config was a very bad suggestion. As it turns out that only works untill you actually turn off your computer. It seems that after every cold boot the sd* values change so that doesn't work.

The fastest way to do this if you have loads of sata/scsi ntfs drives is to:
1. Install and run ntfs-config (without any of the target drives mounted). You can do this from the add/remove or

sudo apt-get install ntfs-config

2. Make an fstab backup

sudo cp /etc/fstab /etc/fstab.bak

and uninstall ntfs-config.
Unmount the drives (you might need root privileges to do that, if so it can be done by running nautilus as root as described in the next step or from terminal if you know how to).

3. I was quite happy with the folders as they were created by ntfs-config (they are created as root) so i kept them as they were. If you want to change/rename them you can do that as root in nautilus

gksu nautilus

or from the terminal using

sudo rmdir /media/mountfolder

and create new ones

sudo mkdir /media/mountfolder

I'm sure you can rename folders from terminal, but I don't know how.

4. Open a terminal and enter

sudo blkid

This will list your drives with all the info you'll need.

5. Open another terminal window and edit the fstab ntfs-config created by ntfs-config

gksu gedit /etc/fstab

Once opened replace all the sd* values in the fstab file with the uid values from blkid (for newer users: just select it with the mouse, rightclick and choose copy and paste it over the sd values) and remove the "" from the uuid. Don't touch the settings for linux filesystems or optical drives.

6. Save fstab and everything should be ok.

In my instance these were the fstab entries created by ntfs-config

/dev/sde3 /media/Moviez ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdd2 /media/Epz ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdc1 /media/Download ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdb1 /media/Stuff ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sda2 /media/DVDS ntfs-3g defaults,locale=en_US.UTF-8 0 0

And this what I made of it:

UUID=6E286A1C2869E415 /media/Moviez ntfs-3g defaults,locale=en_US.UTF-8 0 0
UUID=02E09007E08FFF5B /media/Epz ntfs-3g defaults,locale=en_US.UTF-8 0 0
UUID=3C406343406302CE /media/Download ntfs-3g defaults,locale=en_US.UTF-8 0 0
UUID=A078885D78883456 /media/Stuff ntfs-3g defaults,locale=en_US.UTF-8 0 0
UUID=10F0F34141BBBDF9 /media/DVDS ntfs-3g defaults,locale=en_US.UTF-8 0 0

This is the output from blkid i get now (notice how the sd* has changed from cold booting) :

/dev/sda1: UUID="6C383ED8383EA0CE" LABEL="GAMES" TYPE="ntfs" 
/dev/sda2: UUID="02E09007E08FFF5B" LABEL="Epz" TYPE="ntfs" 
/dev/sdc1: UUID="2dfb4ef1-dcde-490a-9e21-40ee47a0c5e2" TYPE="ext3" 
/dev/sdd1: UUID="A078885D78883456" LABEL="Stuff" TYPE="ntfs" 
/dev/sda3: TYPE="swap" UUID="6dd3d793-8049-4335-8bbe-14992a4681c7" 
/dev/sdb2: UUID="689074C590749AF0" LABEL="******* XP x64" TYPE="ntfs" 
/dev/sdb3: UUID="6E286A1C2869E415" LABEL="Moviez" TYPE="ntfs" 
/dev/sdb5: UUID="e2e49a1a-77d7-4691-a5d8-11be2eae6ecb" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sdc2: UUID="10F0F34141BBBDF9" LABEL="DVDS" TYPE="ntfs" 
/dev/sde1: UUID="3C406343406302CE" LABEL="Download" TYPE="ntfs"

This way my samba shares and all other permissions stayed intact.

I have no idea which events could change the uuid from a disk, but i'm sure I'll find out in time

If I opened a securityhole like this please delete this post.

If creative and ati would be so kind to either make decent binary drivers or provide the necessary information to the linux community I'd no longer have use for ntfs drives

This is meant to be a guide for noobs by a noob (obviously). This way I actually had some notion of what I was doing and could always go back a step.

[CaptMorgan]

Sorry let me repost that link:

http://onlyubuntu.blogspot.com/2008/...in-ubuntu.html

Thank you very much, that worked like a charm

[jaygo]

hrmm, umask, gid, & uid all break it -- error:

mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

no biggie, I can manually change permissions on each partition but I'm really trying to find a way to automount hotswap (SATA) drives.

[jaygo]

nosuid,nodev,uhelper=hal,utf8,shortname=winnt,uid= 1000 0 0

uhelper=hal let's me mount fine but trying to unmount gives me the following error, in console and dolphin:

Device to unmount is not in /media/.hal-mtab so it is not mounted by HAL

...

the uhelper option seems to disable the user option (?) because I can only unmount as root. Line in fstab reads:

LABEL=backup1    /media/backup    ext3    uhelper=hal,auto,rw,sync,user        0    2

[xen-uno]

First off, I fixed the automount problem using the link prov'd by rich-dvd ... thanks. The negative is that it's mounting the XP system partition ( C: ) as well.

I was having trouble with all my NTFS partitions labeled (as an example) ntfs-part-X becoming ntfs-part-X_ (notice the tail underscore), with the original becoming deactivated. This would happen every other boot up. Clearing out all folders in Places>Computer>Filesystem>media> except for the cdromX's and folders that matched NTFS partition names seems to have fixed that problem. I also cleared out all ntfs entries from fstab which may have been unnecessary since correcting via the media folder. System>Administration>StorageDeviceManager device tree still doesn't match results from Terminal's ls -l /dev/disk/by-uuid. There is a device entry of sda5 which does not show up in SDM's tree (shows sda1 only) ... appears to be non-fatal though.