From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I was playing a game, alt-tabbing froze my system so I waited a bit and then rebooted by using the button on the case, since I couldn't do differently.
It now throws an error when mounting a drive: error mounting /dev/sdb1 at /media/user/local disk 1: unknown error when mounting (udisks-error-quark, 0)
This drive doesn't have anything I was using on it, since it's a media storage drive. I booted up Windows on my second drive and it can see and access this one without problems. How to fix?
Firstly, check the logs directly to get a more concise error that we can analyse.
journalctlis the standard systemd logging client you can use in the terminal. By specifying the unit (units can be socket files, timers, services) you can get logs specifically for said unit.You can also specify binary, if said binary logs to journalctl, like so (if the binary path exists):
You can also check kernel messages (dmesg) by using the -k flag, like so:
You can utelize flags such as
-eto scroll to the end of a journal,-fto follow a journal in realtime and utelize the-pflag to set priorities like error, crit, warning (-o error) and others to filter away common journal entries so you don't have to scroll through every line in the log.Secondly, and this is gonna sound weird, but reboot into windows twice. The first time you boot windows run diskchk on the partition(s) in terminal/powershell/command as administrator. If it tells you it needs to do an offline scan, reboot and you'll see an offline diskchk screen on boot before login. If not, reboot again into windows anyways, and then reboot into Linux.
The reason is that NTFS has a weird failsafe flag that NTFS on Linux considers a no-go, and it's usually set if the system crashes more than twice, but not always. If Linux NTFS drivers see the flag, it won't mount as a precaution. The only way to reset the flag is to reboot in windows twice. Not once, not three times, but twice.
This might be outdated info, but that was the fact some years ago. There might be a way to fix it with modern day Linux, but I don't know, especially when I have no direct and informative errors to go by.
journalctlis your friend :)