Bug 743948

Summary: Fail to Auto Mount NTFS partitions with fstab
Product: [Fedora] Fedora Reporter: simonds.rick
Component: grubAssignee: Peter Jones <pjones>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jonathan, lkundrak, madhu.chinakonda, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-07 17:26:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description simonds.rick 2011-10-06 14:48:33 UTC 
I have been running Fedora on this laptop for 9 months.  Last week an update caused the system to halt at boot up. The system failed to mount the file system.  After troubleshooting I can get the system to boot if I edit fstab and comment out auto mounting additional NTFS partitions.  I can recreate this error every time by un-commenting the mount points (see copy of fstab below).  I was able to auto-mount these until last week. Once i boot into gnome i can dynamically mount the partitions. However, this does not let me run any virtually machines with VBox located on the ntfs partitions.  Thank you in Advance.

# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0c49a2fe-e3e4-42a5-8a43-783318e202f5 /                       ext4    defaults        1 1
UUID=89b286b3-28b0-4308-9f9d-a8ca5f7c2b31 swap                    swap    defaults        0 0
# UUID=74A28BF5A28BB9DE /data	ntfs	defaults 1 1
# UUID=582C80B22C808CA6 /recover	ntfs	defaults 1 1
# UUID=146E25306E250BD4 /windows	ntfs	defaults 1 1
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
Comment 1 simonds.rick 2011-10-07 17:26:57 UTC 
This issue was fixed by disabling fsck on the ntfs volumes

UUID=74A28BF5A28BB9DE /data ntfs defaults 0 0
UUID=582C80B22C808CA6 /recover ntfs defaults 0 0
UUID=146E25306E250BD4 /windows ntfs defaults 0 0