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!

  • Telorand@reddthat.com
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    23 days ago

    I am not familiar with I/O stuff, but I didn’t see you mention if you tried doing an rpm-ostree rollback.

    Since you said it happened after an update, did you already try that to see if it fixes your issue? Another thing to look at is topgrade. It’s the underlying tool for Bazzite upgrades, so perhaps that can give you some clues as to what went wrong.

    ETA: Have you tried asking in their discord? The community and devs are really nice and generally pretty helpful.

    • some_random_nick@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      23 days ago

      Tnx for the suggestions. I have asked on the discord server, but no response as of now. I will take a look at those commands and see if anything fixes it.