I may have messed up my Debian 13.1 system while trying to get Armored Core 6 to work. When I attempted to run it, Steam threw an error saying it couldn't write to my secondary drive, which has been a troublesome drive before. Despite setting it up for write access in my /etc/fstab file, I still encountered issues needing manual unmounting and remounting with a password.
After some research, I read that mounting issues might stem from it being in /media due to special permissions associated with that folder. I decided to remount my drive to my home directory instead. However, instead of simply creating a new folder in my home directory, it appears to have overridden it completely. Now, many files are inaccessible, I see "file does not exist" errors when trying to open folders on my desktop, and several UI elements have reverted to default settings. I tried unmounting the drive using Dolphin, but it was greyed out, and the partition manager failed to unmount it.
I rebooted to find even more errors popping up, all while my desktop environment looks like it reverted to factory settings. Recovery mode hasn't helped; when I unplugged the secondary drive, the system just hangs at a screen with network info. My desktop settings may be lost, but some things like my mouse lights and username are still intact. I'm bewildered and urgently need advice on what to do next. Thanks in advance for any help!
3 Answers
It sounds like your filesystem might have gone read-only due to a detected issue or corruption on your secondary drive. Try checking the logs with the `dmesg` command; it will show if there were any problems that led to that behavior. Also, to access other consoles, use the Alt-Ctrl-F1 through F7 combos to check if you can log in or access the GUI elsewhere. That might help you regain control of your system without the need to reboot again.
It sounds rough! Since you've unplugged the secondary SSD, try booting up in recovery mode again after a full shutdown. Make sure you let the system start completely before logging in again. Also, keep an eye on the logs in the recovery console for clues about what's been happening. You can try to run `fsck /dev/sda1` (or the appropriate drive) to attempt to fix any filesystem errors there.
When you say you couldn't unmount the drive, it usually means the system is still trying to access it. It's a good sign that you're able to use Alt-Ctrl-F2 to bring up a login prompt. Once logged in, run `dmesg` again to see what errors are being thrown. If it still indicates read-only issues, it might hint at some corruption that needs fixing. You might have to perform a filesystem check on your drives from a live USB or recovery mode.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures