[Bug 1008117] Re: Nautilus suggests option for mounting hibernated ntfs partitions that could lead to data loss

Jean-Pierre 1008117 at bugs.launchpad.net
Fri Sep 21 07:10:04 UTC 2012

The mounting denial is not a bug. It is a feature preventing you from
losing data.

Also please see http://jp-andre.pagesperso-orange.fr/advanced-ntfs-

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ntfs-3g in Ubuntu.

  Nautilus suggests option for mounting hibernated ntfs partitions that
  could lead to data loss

Status in NTFS-3G:
Status in “ntfs-3g” package in Ubuntu:

Bug description:
  --- What happens: ---
  If a user tries to open an ntfs partition that has been hibernated while using Nautilus they will be presented with this dialog:
  Unable to mount XP

  Error mounting: mount exited with exit code 14: Windows is hibernated, refused to mount.
  Failed to mount '/dev/sda3': Operation not permitted
  The NTFS partition is hibernated. Please resume and shutdown Windows
  properly, or mount the volume read-only with the 'ro' mount option, or
  mount the volume read-write with the 'remove_hiberfile' mount option.
  For example type on the command line:

              mount -t ntfs-3g -o remove_hiberfile /dev/sda3 /media/XP_

  The last suggestion, "mount the volume read-write with the
  'remove_hiberfile' mount option," is problematic because doing this
  would delete the 'hiberfile.sys' file and cause the user to lose all
  information on the saved session--potentially including unsaved work.
  Here is a selection from the ntfs-3g manpage explaining this option:

                Unlike in case of  read-only  mount,  the  read-write  mount  is
                denied  if  the  NTFS  volume is hibernated. One needs either to
                resume Windows and shutdown it  properly,  or  use  this  option
                which  will  remove  the  Windows hibernation file. Please note,
                this means that the saved Windows  session  will  be  completely
                lost. Use this option under your own responsibility.

  The fact that the exact command to do this is prominently displayed
  (and is the only command displayed) without any warning that this will
  delete the saved Windows session only aggravates the risk of data

  --- What should happen: ---

  1. If a command is to be prominently displayed it should be the
  command to mount the partition in read-only mode (see command
  below)--this is the only completely safe way to mount a hibernated
  ntfs-partition without risking data loss.

                mount -t ntfs-3g -o ro /dev/sda3 /media/XP_

  2. A warning should be included in the Nautilus dialog which explains
  that using the 'remove_hiberfile' option to mount the drive in read-
  write mode will require deleting the saved Windows session and losing
  any unsaved files.

  --- Steps to reproduce: ---

  1. Hibernate a Windows installation
  2. Boot Ubuntu
  3.  Attempt to open the Windows partition using Nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Sun Jun  3 22:08:06 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1192x655+56+24'
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-04-29 (34 days ago)
   (gnome-settings-daemon:1917): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
   (gnome-settings-daemon:1917): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output
   (gnome-settings-daemon:1917): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero
   (compiz:1933): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list