Error mounting / dev / sda9 at / media / qwertiy / Data E: Command-line `mount -t" ntfs "-o" uhelper = udisks2, nodev, nosuid, uid = 1000, gid = 1000, dmask = 0077, fmask = 0177 "" / dev / sda9 "" / media / qwertiy / Data E "'exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/ dev / sda9': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.

As far as I understand, this warning is intended to prevent problems with writing to disk when the cache is not reset, for example, in the case of Windows hibernation.

  1. Does it really make sense to boot to Windows if the reboot was done with a reset? If not, how to ignore the error?

  2. How to mount a disk in readony-mode?

1 answer 1

1) Yes, sometimes rebooting into Windows and shutting down help :-)

2) mount ntfs in ridonly in ~/user/temp/ntfsro

 sudo mount -t "ntfs" -o "ro,uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdb5" "/home/user/temp/ntfsro"

change the parameters and ways as you like

/dev/sdb5 - you know, the Windows partition

uid / guid 1000 - default user id under ubuntoy (and, probably, debian and mints)

About hibernation:

very good answer / article, In short - if your memory is flushed to disk, and then you make any changes to the file system, it is possible that Vin may collapse on reboot.

If you touch something important, you can, in principle, lose data (since the system is restored to memory, assuming that everything is in place).

Those. Windows leads FS, memory, running programs in a consistent state after a restart from hibernation

About rezet:

When you cut, you will still have a dirty bit set for the file system, since when cutting it may be damaged, and in this case the Windows will run its analog fsck and remove the dirty bit during a normal reboot.

If you start writing in broken NTFS in Linux in RW mode, there is no guarantee that you won’t break everything (I don’t know personally what checks the ntfs driver does in Linux), I would be reinsured.

You can probably mount the force, but why? This is only in some extreme cases required. Better to reboot.

  • 1. Yes, they help. But if there is no hibernation, but pressing reset, does the reboot have any meaning at all? - Qwertiy ♦
  • Yes exactly. Therefore, the question is whether the Windows does something useful, or just cleans the flag? And what words to look for an article? Can you bring the link? - Qwertiy ♦
  • moved comments in response - strangeqargo
  • one
    By the way, Windows itself decides whether to run chkdsk. And she rarely wants to run it for all drives. In most cases, it does not start at all, sometimes it starts for one or two. Fishing for everyone is a very rare exception. Although a dozen or so saw a couple of times recently. - Qwertiy ♦
  • Well, it all depends on the state of the magazine, I think. there is almost a transaction) apparently for this and determines - to run or not - strangeqargo