I don’t know when this happened. There was a system update a few days ago which went fine. Two days ago I wanted to download something onto one of my HDDs and got an I/O error. After investigating I found out that I no longer am the owner of any of my drives and can’t create/delete any files. Chmod/chown didn’t help. Editing the fstab file didn’t help since it had the exact same contens as when everything worked. Shuffeling exec,rw around has no effect. Mounting/unmounting didn’t do anything. Phisically removing the drives also didn’t work. Adding a completely new drive automatically set it to restricted. How the hell does soemthing like this happen? I don’t want to do a system wipe.
Edit: Windows is to blame
It appears Windows did something to the drives the last time I used it which messed up the partitin tables and prevented Linux from mounting them correctly. After poking around in the journalctl like suggested I found an entry with the error message. Googling brought me to an arch forum post with the same problem. All that had to be done was to go back into Windows and run shutdown /s /f /t 0 in cmd/powershell.
Link to the post: https://bbs.archlinux.org/viewtopic.php?id=231375
Tnx everyone for the assistance!
Can you read/write to the disks as root? If so, then something has likely gone sideways with your fstab entry. For example, the device name, order, or UID/GID may have changed, depending on how you’ve configured the entry.
It’s difficult to assist much more without seeing the contents of
/etc/fstab.I checked fstab and it’s the same from day one. I tired adding stuff to it and shuffeling parameters around (like phtting rw,exec last), but it did nothing.
Your fstab file can remain unchanged and still fail, if the drive or user identifiers have changed unexpectedly. It depends on how you’ve configured your fstab entries, which is why it’s helpful to share them. In future, no one will be able to offer much assistance without seeing the entry details. Either way, glad you were able to get it sorted!