How to fix readonly-NTFS from Linux Mint without formatting drives and risk losing data on them?

Question

linux

Linux Mint does not allow you to overwrite/delete/create files on NTFS drives ("the file system is read-only").

There is no place to back up information that is stored on NTFS.
Nothing critical, but I would not want to lose.

What are the options to solve the problem without formatting NTFS and the risk of losing data on them?

Answer 1

On dual-boot machines, this happens when Windows doesn't shut down correctly. For example, if instead of turning it off, it went into hibernation.
If this is your case, then just load Windows, and then turn it off with the appropriate item in the start menu. After that, the disk will be mounted in Linux as it should.

Answer 2

The most reliable option is to check this disk with Windows chkdsk (by booting from any liveCD). Most likely, the dirty flag is set on the partition, so Linux is being careful.
You can also try from Linux: https://askubuntu.com/questions/112150/how-to-corr...

Answer 3

I agree with kisaa - NTFS is such a thing that it is best to fix it by native means, that is, any repair for Windows is taken, it is downloaded and checked with Windows chkdsk, which will fix bugs and remove the "emergency unmount" flag. At least I prefer not to go into NTFS with unwashed flippers :)

Answer 4

First you need to determine the path to the block device of the partition.
It is convenient to do this with such tools:
lsblk
If the disk is connected via SCSI (IDE, SATA, USB), then the name of the physical disk will be indicated by the letter of the alphabet following sd , for example, sda , sdb , sdc , and the partitions will be numbered after the disk name: sda1 , sda2 , sda3 (numbering of partitions on the disk starts from one).
If the disk is solid-state and soldered on the board, or connected via a card reader, then the required disk can be called, for example, mmcblk0 , mmcblk1 , mmcblk2(Please note that the numbering of disks starts from zero). The corresponding partitions will be named mmcblk0p1 , mmcblk0p2 , mmcblk0p3 (numbering of partitions on the disk starts from one).
If the SSD is connected via pci-e, the name of the disk will be e.g. nvme0n1 , nvme0n2 , nvme0n3 (please note that the disk numbering starts from one and the first zero after nvme is the controller number), their corresponding partitions will be e.g. nvme0n1p1 , nvme0n1p2 , nvme0n1p3 (numbering of partitions on the disk also starts from one).
Sometimes it helps
blkid
But blkid doesn't show partition sizes, which can lead to partition confusion.
After you have decided on the path to the partition, you need to make sure that the disk is unmounted.
The command
mount | grep sda1 | cut -d' ' -f3
, where sda1 is the name of your NTFS partition,
determines where the disk is mounted. If nothing is returned, then the disk is not mounted. And if something issued - then this something will be the path to mount your partition.
Then you need to execute the command:
umount -R /mnt/winSystem
where /mnt/winSystem is the path to which the partition is mounted.
After making sure that the partition is not mounted, you must execute:
ntfsfix -vbd /dev/sda1
where /dev/sda1 is the path to the desired partition with NTFS.
After that, you can reboot with the command
reboot