[RESOLVED] Read only file system

[rikitiki]

Hello! I use Kubuntu system with several SSD-devices. Most of them use NTFS because I have to use Windows as well.

$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 3.0M 3.2G 1% /run
/dev/sdc2 55G 45G 7.6G 86% /
tmpfs 16G 235M 16G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
efivarfs 128K 48K 76K 39% /sys/firmware/efi/efivars
/dev/sdc4 164G 105G 51G 68% /home
/dev/sdc3 94M 9.9M 84M 11% /boot/efi
tmpfs 3.2G 7.8M 3.2G 1% /run/user/1000
/dev/sda3 107G 63G 44G 60% /media/username/projects
/dev/sde4 117G 3.9G 114G 4% /media/username/Kubuntu 24.
/dev/sda2 116G 63G 54G 54% /media/username/windows
/dev/sdb2 932G 761G 171G 82% /media/username/games
/dev/nvme0n1p1 1.9T 1.6T 281G 86% /media/username/storage
/dev/sdd1 466G 440G 26G 95% /media/username/hdd

Now one of mounted disk is read only and I don't understand why and how to fix it.
I'm talking about /dev/sda3

I checked it on Windows side and it works correctly there. I tried to execute "chkdsk" in Windows and it returns no errors.

But when I try to update any files and create one more on Kubuntu side I faced with error:

$ touch test
touch: cannot touch 'test': Read-only file system
​

When I try to use ntfsfix command:

$ sudo ntfsfix /dev/sda3
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking file system overflow... FAILED
Error: Failed to fix the alternate boot sector
​

Why? Could someone give some an advice?

[GreyGeek]

https://askubuntu.com/questions/7124...tem-read-write

[Snowhog]

GreyGeek Besides being over eight years old, there is no solution given (that I saw) in the link you provided.

[GreyGeek]

GreyGeek Besides being over eight years old, there is no solution given (that I saw) in the link you provided.

How to remount an RO drive as RW is shown in that link:

sudo mount -o remount,rw /partition/identifier /mount/point

[rikitiki]

Sorry, I didn't understand what I need to do.
One more time: I have a problem only with /media/username/projects all other mounted devices are not read-only.

And one more question: why I didn't see configuration of mounted device in cat /etc/fstab ? Only main partitions there, not ntfs

[oshunluvr]

Sorry, I didn't understand what I need to do.
One more time: I have a problem only with /media/username/projects all other mounted devices are not read-only.

And one more question: why I didn't see configuration of mounted device in cat /etc/fstab ? Only main partitions there, not ntfs

Unless YOU put the other partitions in fstab, they won't be there. The installer only mounts the required file systems for the installation. Additionally, NTFS not being a Linux file system, requires additional software to use which may not be installed by default.

As to your original post:

If you're accessing file systems on fixed drives (hard drives or SSDs) using udev to mount them (just clicking on them with Dolphin for example) is not the best method to access them. You should create entries in fstab for each of them with proper options to best access them. The "/media/user" mounting location is intended for removable devices.

"MFT" means Master File Table. IMO, the first thing to do before anything else is make a backup of everything on the file system - from the windows side if necessary - because anything else you might try to do to fix this may result in an unreadable file system.

Once you have a backup safely tucked away, then install and run "testdisk" from Linux and see if it offers to repairs the tables on the drive. There should be a backup table that testdisk can see and use to repair the primary table. I have done this in the past mostly with success, including rebuilding a totally lost table. However, as always, mucking about with disk headers and tables can be fatal.

Alternately, back up the files, wipe a reformat the disk, and reload the files.

[rikitiki]

Thank you. I backed up files, format the disk and restore files. Now it works