Windows-related partitions mounted as read-only

[whole latch]

Yeah, so i have a Windows SSD, an Arch drive and a shared drive to store random stuff. Usually i use either Windows SSD or an Arch drive in primary drive slot and the shared drive in secondary slot.

So I have just rebooted from Windows, with a full proper shutdown, into Arch, swapping the primary slot drive, and GRAVITOS-INTERNAL, located on the shared drive, is mounting read-only. Are there any ways to clean the "unclean file system (0,0)" from Arch directly? I feel like this is going to be a pretty common problem for me...

Oh, yeah, completely forgot, all three partitions on the shared drive are NTFS.

[smoky grove]

I assume this is using ntfs-3g to mount?

[whole latch]

i would assume yes, i do not specify explicitly because i forgor how to

[whole latch]

also, this

[smoky grove]

wait, why aren't you running these as root?

[bronze crater]

https://wiki.archlinux.org/title/NTFS#Explicit_file_system_type_required_to_mount
@whole latch have you tried this?

[vocal slate]

ntfs and windows

that's your answer

this is because either
you hibernated, did a fast shut down, powerloss or did a hybrid sleep in windows (it hidden as shutdown but you can turn it off in settings)

if you want to fix this @whole latch reboot into windows and either restart and choose arch to boot next
or do an actual shutdown

[pearl vale]

Windoz moment

You must disable fast startup on windoz

@gravitos#1405

@whole latch

[uncut brook]

you need to specify -t ntfs3 when mounting

and have the required packages

[violet vector]

nah theres an ntfs driver in the kernel

[uncut brook]

oh yeah my bad

old news

[violet vector]

all they need to do is go back into windows and hit restart

instead of shutdown

[uncut brook]

well you can make a udev rule to always use the flag when mounting ntfs

/etc/udev/rules.d/ntfs3_by_default.rules ```
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs3"

[inner spoke]

if you know for a fact you shut it down right, try sudo ntfsfix -d device to clear the dirty bit

[vocal slate]

no
there is no required packages
the ntfs3 driver is in the kernel

if you dont want to use ntfs3 then
you can use ntfs-3g which is the one that actually needs to be installed if youre using it

ntfs-3g is a fuse based driver

[vocal slate]

that's what they're evoking with the -t ntfs3

the kernel module

[worthy folio]

Just turn off fast startup on windows

[inner spoke]

its almost like someone said that

[low edge]

Hold shift while pressing shutdown windows, boot linux, should work.

If that doesnt work try getting ntfs-3g (works for me with gnome disks)

[bronze crater]

its almost like i linked to an article saying that.

by "article" i mean archwiki page

[violet vector]

idk i don’t remember having to specify a type it jus kinda figured it out

[vocal slate]

it's almost like i didnt reply
to the same message

[vocal slate]

perhaps you added

[vocal slate]

this to your udev rules

which makes not need the -t ntfs3

or
you could be using ntfs-3g when you were mounting it

[violet vector]

nope, just checked

this is the command i used

[vocal slate]

cat /etc/mtab | grep /dev/sdc1

[vocal slate]

yep ntfs-3g

[violet vector]

i do have ntfs3g installed yeah

[violet vector]

this is the result of an fstab mount tho

didnt know nfts3g worked that early in userspace

[vocal slate]

oh huh

[violet vector]

yeah idk

the only things ive had to specify type for is samba mounts

[vocal slate]

lsmod | grep ntfs3

[violet vector]

not loaded

[vocal slate]

weird

hidden driver pausechamp

[violet vector]

true

i guess nfts3g does some early userspace magic to get systemd to use it for fstab mounts

[uncut brook]

you don't have the udev rule?

I guess not if fstab can mount it as ntfs, must be some nfts-3g sorcery