Why HDD in read-mode only??

[Linares]

Hello.

I have an internal hard drive with which, until today, I normally worked editing and creating files. Today, suddenly, I can't create files, nor delete them, nor copy.
It is as if the hard drive has been put into "read only" mode.
What fault could it be?

[sturmvogel]

You should check your /etc/fstab
If your partition has the 'ro' setting, then it is read only.

[filip]

Failing drives can show such symptoms. So I would also test it with GSmartControl. I test all my drives regularly. No serious loss for now.

[doktor5000]

What happens more regularly is if this an NTFS partition, then those will sometimes be marked as readonly if windows has not been shutdown properly or if fastboot is not disabled.

Although without more details it's hard to say what the cause is.

[jiml8]

The OS will commonly kick a drive into read-only mode when there is a serious problem with the filesystem on the drive. This could be software corruption, or it could be a hard drive failure underway.

If the "hard drive" is actually an SSD, then becoming a read-only device is a common failure mode. You'll have to replace it.

With NTFS, if you kill the computer (or it crashes) without proper shutdown, the filesystem remains "open", the pending journal is unwritten, and the overall state of the system is not consistent. When this happens in a Windows system, on next startup Windows fixes things up. In the case, for instance, of a dual-boot, if Linux is the next boot, Linux does not fix it up so the NTFS driver marks it read only to avoid corrupting it.

You will also see this kind of behavior from UFS on BSD, and I believe iOS will do the same thing.

So what you do next depends on your exact problem. If it is a linux filesystem on a hard drive, run fsck on the filesystem first. Then run hardware diagnostics (smartctl) on the drive itself.

If it is NTFS, boot into windows to clean it up.

If it is an SSD, run some diagnostics (start with smartctl) on the SSD and be prepared to replace it.