Fail to boot due to not OS NTFS disk

Today I’ve got a new problem.
Neon fail to boot due to a problem with mounting a disk (that I use just for games) using fstab.
If I comment the line on fstab related to that disk, Neon starts correctly, otherwise it goes in maintenance mode.
I can’t understand what’s going wrong considering that if I run Dolphin I can see the unmounted disk and, if I try to manually mount it, Neon mounts with, apparently, no problem.

What do you suggest me to check trying to understand where is the problem?

I’ll add some more info about this.
Yesterday I had to solve an issue with the Rockstar Games Launcher that wasn’t running anymore (I’ve installed some months ago using Lutris and everything was fine). After fixed it, I had to redownload all the GTA5 files caused by mine error and, the download was ok until it reaches 100GB of data and after that it starts to have problem and everytime I pressed “retry” in the downloader, it started to download 2GB more…increasing by about 2Gb the final total…but as I was suspecting some issue…I decided to go back to Win11 and use the RockstarGamesLauncher on Win and complete there the download.
I’ve run Win11 and I’ve noted that on boot it asked me if I’d like to analyze that disk (where I store the games files), I’ve skipped and I’ve booted Win and run Rockstar Launcher to complete the download.
Actually, it lacks to download 60GB. After completed, I’ve checked if game runs and everything was OK.
Today, I’ve booted Neon and I had this problem with that disk.
If you have any suggestion, please give me. :slight_smile:

Thanks in advance for everything

Do you have Windows Fast Startup disabled?

This is known to lock NTFS drives

https://www.makeuseof.com/windows-11-turn-on-or-off-fast-startup/

1 Like

Thank you for your input.
Actually I really don’t know which one of these are the solution…anyway I’ve tried:

  • make a checkdisk on Windows forcing to try solve the integrity (actually checkdisk hadn’t found any issue… anyway…I’ve done it)
  • removed the cache on that disk on Windows
  • disabled the Fast Startup as suggested

Now seem working correctly.
Thank you.

1 Like