-1

I was about to spend the next 3 hours playing CSGO, but the Steam client wouldn’t launch. I tried launching it from the command line interface, but there was an error saying that ~/.steam/error.log was read-only. I then performed chmod 666 on the file to yet again encounter the same error. Frustrated, I tried to open up Discord and I got a similar read-only file error bug. Then, I realized almost all my files were read-only, so I decided to restart my computer. Upon restarting, I found this 1st error.

First error

I therefore decided to go into my BIOS and turn TMP state to disabled. I then booted my computer up once again and found this 2nd error, which is where we are at now.

enter image description here

I am totally stumped as it looks like it seems to be a bad drive superblock and I don't know how to fix it.

karel
  • 122,292
  • 133
  • 301
  • 332
RandomName
  • 1

1 Answers1

0

Okay, so I figured it out. First, I re-enabled TPM. Then, All I had to do was type in fsck -f /dev/{corrupted device}. This would fix everything by reorganizing the file system and dealing with the blocks.

RandomName
  • 1