I installed pysdm through this article to auto-mount my ntfs
partitions.
My drive structure looks like this:
jatin@jatin-ubuntu:/media$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda8 18G 12G 5.5G 68% /
none 1.5G 344K 1.5G 1% /dev
none 1.5G 216K 1.5G 1% /dev/shm
none 1.5G 92K 1.5G 1% /var/run
none 1.5G 0 1.5G 0% /var/lock
none 1.5G 0 1.5G 0% /lib/init/rw
/dev/sda2 50G 50G 277M 100% /media/Jatin
/dev/sda3 49G 46G 2.9G 95% /media/Study
/dev/sda5 88G 83G 5.4G 94% /media/Fun
/dev/sda7 32G 32G 177M 100% /media/Masti
/home/jatin/.Private 18G 12G 5.5G 68% /home/jatin
/dev/sda1 59G 57G 2.4G 96% /media/Windows7
My pysdm
settings as mentioned in the above article are as follows:
The assistant options for the ntfs
drives are as follows:
The file system is mounted at boot time.
Mount file-system in only read-only mode.
I have two files: /etc/fstab
and /etc/fstab.BAK
with their contents as follows:
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda8 / ext4 errors=remount-ro 0 1
/dev/sda6 none swap sw 0 0
/dev/sda2 /media/Jatin ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sda3 /media/Study ntfs nls=iso8859-1,umask=000 0 0
/dev/sda5 /media/Fun ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sda7 /media/Masti ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sdc1 /media/sdc1 ntfs nls=iso8859-1,ro,noauto,umask=000 0 0
and fstab.BAK
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda8 / ext4 errors=remount-ro 0 1
/dev/sda6 none swap sw 0 0
/dev/sda2 /media/Jatin ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sda3 /media/Study ntfs nls=iso8859-1,umask=000 0 0
/dev/sda5 /media/Fun ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sda7 /media/Masti ntfs nls=iso8859-1,ro,umask=000 0 0
/dev/sdc1 /media/sdc1 ntfs nls=iso8859-1,ro,noauto,umask=000 0 0
Initially, I had mistakenly created Silver Spoon
as the mount location for /dev/sda2
and it was not booting Ubuntu. Then I fixed the problems by changing the fstab
file contents by booting from a LiveCD and mounting the drive on /mnt/*
.
PROBLEMS NOW
-
When I look at the contents under
/media
, they are:jatin@jatin-ubuntu:~$ cd /media/
jatin@jatin-ubuntu:/media$ ls
Fun Jatin Masti sda2 sda3 sda5 sda7 sdc1 Silver Silver Spoon
Study Windows7
With issues in all the directories in bold. When I open Silver or Silver Spoon, nothing shows up.
-
Some of my
ntfs
drives get auto-mounted in READ-ONLY Mode, while others get auto-mounted in correct(READ-WRITE) mode. -
When I try to open my external hard drive, it says only root can mount it and a user can't. I know this can be fixed by simply removing the line for
/dev/sdc1
from thefstab
file.
QUESTIONS
-
Are both these
fstab
andfstab.BAK
files important? Shouldn't just one be there? -
How can I get my system in it's previous state, before I installed
pysdm
? -
When should I uninstall
pysdm
, before editing thefstab
file or after?
Best Answer
fstab.BAK
is a backup of your fstab file.ntfs
entries from yourfstab
file. The backupfstab
will also mountntfs
partitions, so we can't use it.pysdm
before you edit thefstab
file.I suggest you follow this guide to edit your
fstab
file.