Hello, i am dual booting windows 10 and debian 12 kde plasma 5.27.5, but when i try to mount a hard drive that windows uses (its not where windows is installed but i used the drive with windows) it gives an error:
"An error occurred while accessing '[disk name]', the system responded: The requested operation has failed: Error mounting /dev/sda2 at /media/progcan/[disk name]: Filesystem type ntfs3,ntfs not configured in kernel"
i have ntfs-3g, libfsntfs-utils, and libfsntfs1 packages installed and it still gives this error. It used to be able to easily mount the hard drive but recently idk what happened but it started giving that error. Any help would be appreciated!

UPDATE: OH GOD NO. I remembered that i used kde partition manager to shrink the drive a bit. NOW IT SAYS THE DRIVE IS RAW, EVEN IN WINDOWS. I have stuff i cant lose there, HOW CAN I FIX IT PLEASE? btw windows 10 asks me to format it (what is wrong with you windows lol) at least it isnt the drive i have windows installed on. but its the drive i have linux on. what am i gonna doooo?? PLEASE HELP ME
also i shrinked a partition but it still had like 50 gb left to it, so i am sure i didnt somehow overshrink it.
EDIT: linux works well tough, i think the problem is eiher with windows or the partition it uses (which i have important stuff on)

The Usual Tool...

If necessary you can use TestDisk to find and restore your partition table. TestDisk is on many help compilations you may download.

Best practice is to make a clone copy of the problem hdd and work with the copy

In passing, is this an occasion to emphasize the usefulness of backup?

hello everyone, i researched my problem a bit and some people say i should do a disk check. is it safe on a drive that windows 10 recognizes RAW, and will it format the drive with or without asking to check it?

NO NO NO

Make an image copy of the disk, perform the actions suggested above on that copy.

Anything that writes to the disk may cause further problems and without a copy you would then be totally lost.

oh ok, good thing i didnt chkdsk already. i'll update when i do what i can

As far as I know ntfs3 is not enabled in the debian 12 kernel by default. I have not paid much attention if it is enabled in testing or unstable. What kernel are you running?

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=998627

I believe all the tools still use ntfs-3g so KDE's partition manager should be able to resize NTFS successfully. I don't use KDE. Technically it is a two stage process, the first is to shrink the filesystem and then shrink the partition. There is also the possibility that you resized the partition while the filesystem was hibernated and not fully shutdown. I don't know if that could corrupt the filesystem but it isn't a good idea. Is the drive internal or external?

I agree with creating an image of the filesystem and then see what happens if you try mounting using ntfs-3g i.e.
mount -t ntfs-3g /dev/sdxy

"External or Foreign" filesystem support is usually provided by a loadable kernel module – which is part of an optional "package" that you can install for your distro. When this is done, Linux will know how to recognize the filesystem and automagically load the necessary module.

As of kernel 5.15 there is a real kernel NTFS module. Can you claim that NTFS is still a foreign filesystem?

I don't know why the system would be trying to use ntfs3 versus ntfs-3g.

So shrinking the drive a bit using kde partition manager caused it?

That's speculative but first 'a bit' would need to be defined and more details about what exactly was done. What the OP reports from windows asking him to format is usually seen when a non-windows filesystem is detected. The OP might have inadvertently formatted it or as suggested above, left it in a hibernated state while modifying the partition. Other possibilities come to mind and this is one reason why when using a windows fs, you should modify it from windows and it is generally suggested running chkdsk immediately on reboot when making changes to partitions. Of course, one would have a backup of important data before doing any of this.

2 members found this post helpful.