All my drives unmount and can't be remounted

[Kyium]

Hi all.
I’m having a very strange issue where all my mounted drives (apart from the boot drive) become unmounted and cant be remounted with the following error:

An error occurred while accessing ‘drive name here’, the system responded: The requested operation has failed: Error mounting /dev/sdb5 at /run/media/username/drive: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.

This error repeats for all 4 of my mounted drives (1 SATA SSD, 1 NVMe SSD and 2 SATA HDDs). I dual boot and have confirmed all the drives are operational on windows 11. This is the 2nd time this has happened after my whole system lagged for about 5 seconds and my desktop appears to reload. it previously randomly fixed itself after rebooting but not this time.

My external drive that is NTFS won’t mount but my fat32 USB drives will without issue.

Things I have tried:
Restarting numerous times
Booting into windows and back into manjaro
Updating all packages (pacman, yay and flatpack)
Disabling fast boot in UEFI and shutting down windows fully

I was able to find another person having a similar issue:
https://www.reddit.com/r/linux4noobs/comments/1dpk1x1/can_no_longer_mountread_an_ntfs_partition_in/

I ran the following commands from one of the comments:

mkdir ~/ntfs_test
sudo ntfs-3g /dev/sdb1 ~/ntfs_test
ls ~/ntfs_test

The result I got:

Windows is hibernated, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Could not mount read-write, trying read-only

I got the same output as them leading me the believe I have the same issue with windows messing with the drives. I don’t want to remove my dual boot as I need windows as a fallback for some applications. I don’t use hibernation and i didn’t put the system to sleep when I exited it.

inxi output:

CPU: 12-core AMD Ryzen 9 3900X (-MT MCP-) speed/min/max: 2159/2200/4672 MHz
Kernel: 6.6.54-2-MANJARO x86_64 Up: 16m Mem: 6.96/31.26 GiB (22.2%)
Storage: 6.37 TiB (6.5% used) Procs: 479 Shell: Zsh inxi: 3.3.36

[cscs]

Are these NTFS drives/partitions?
And you are dual-booting?

Have you always made sure to fully shut down?

By default windoze does not shut down and only hibernates.
You must disable ‘fast startup’ to disable this ‘feature’.

To ‘recover’ your drives/partitions in this case you need to use chkdsk on windoze.
( Proprietary filesystem go brrrr )

See any related thread or search engine.

@Kyium

The result I got:

Windows is hibernated, refused to mount.

Eh, yup. As above.

@Kyium

I don’t use hibernation and i didn’t put the system to sleep when I exited it.

Unless you have disabled the windorful feature as stated above… you did hibernate. You have been hibernating. I guess you just didnt know it.
( Proprietary operating system go brrrr )

[Kyium]

I just booted into windows and disabled the fast boot setting i think?

From here: https://support.lenovo.com/gb/en/solutions/ht513773-how-to-enable-or-disable-fast-startup-on-windows-11

For method 1 the option was missing for me.
I ran the command from method 2 and got no output but it did run.

I shutdown windows and booted into manjaro and the issue persists.

[cscs]

@Kyium

I shutdown windows and booted into manjaro and the issue persists.

The drives/partitions are already ‘broken’.

You must run chkdsk in windoze.

(No, there is no linux tool.)

@cscs

To ‘recover’ your drives/partitions in this case you need to use chkdsk on windoze.
( Proprietary filesystem go brrrr )

Some examples;

windows 11 chkdsk at DuckDuckGo

[Kyium]

After repairing the drives with chkdsk or by using the file explorer repair tool on each of the drives, they appear normally in manjaro again, thank you.

[cscs]

Glad it worked out.

I’ll just leave a follow-up note in case anyone else comes looking…

While some linux tools claim to be able to ‘fix’ NTFS partitions … this is mostly false.
At the very best they can remove the ‘dirty bit’ set on these partitions that denotes their spoiled state. Doing so and then continuing to use a partition while damaged can result in damaged or lost data. Do not use any such tools.

NTFS is a proprietary filesystem produced by microsoft. You must use their tools to properly manage that filesystem. chkdsk (or some frontend) as launched by a windows operating system (or PE such as Hirens) is the only acceptable approach.