Non-fatal boot automount errors generated after adding NTFS partition to fstab

Question

I had a problem mounting an NTFS partition using pysdm that's discussed here -

can't mount ntfs partition without root access

I resolved it by the fstab edits suggested. However, I now get an "error mount 0 - skip or fix now?" (paraphrased from memory) message on startup. "Skip" boots normally and everything mounts correctly. I have found these messages in the kernel log -

26/07/13 11:27:25   EXT4-fs (sda6)  warning: maximal mount count reached, running e2fsck is recommended
26/07/13 11:27:25   EXT4-fs (sda6)  mounted filesystem with ordered data mode. Opts: (null)

This is my current /etc/fstab -

# /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>
proc                                       /proc             proc  nodev,noexec,nosuid                                                           0  0  
# / was on /dev/sda8 during installation
UUID=[id###]  /                 ext4  errors=remount-ro                                                             0  1  
# swap was on /dev/sda7 during installation
UUID=[id###]  none              swap  sw                                                                            0  0  
/dev/sda5                                  /media/data       ntfs   
nls=iso8859-1,rw,umask=000,user  0  0
/dev/sda6                                  /media/ext4-data  ext4  defaults                                                                      0  0

This is the only part I manually edited -

nls=iso8859-1,rw,umask=000,user 0 0

This line is residue from pysdm -

/dev/sda5                                  /media/data       ntfs

Did I cause this error or is there some configurable mount setting I am unaware of?

EDIT: This is screencap of fstab showing the split line for sda5 -

http://oi42.tinypic.com/6nywcx.jpg

score 0 · Answer 1 · answered Jul 26 '13 at 04:52

I cannot recommend using pysdm as it has not been maintained for ages. It still uses devices not UUID and does not have good parameters.

Your fstab does not look at all correct. Is it as posted? Did you edit out UUID and parameters at ends of every line?

The nls.. line is not a separate line but part of the sda5 ntfs mount line.

For ntfs UUID shown is example only see below to find yours:

UUID=DA9056C19056A3B3 /media/data ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0

Window_names prevents the use of invalid windows characters: (which are the nine characters ” * / : < > ? \ | and those whose code is less than 0×20) uid=1000 should fix the trash problems as well:

for ext4

UUID=076426af-cbc5-4966-8cd4-af0f5c879646 /media/ext4-data ext4 defaults,noatime 0 2

find UUIDs

sudo blkid -c /dev/null -o list

And when you are done editing fstab and saving it run the following command to test for errors and mount the partitions without requiring a reboot. You will know before you reboot if something is amiss. Make sure you have partition unmounted if previously mounted: