regarding my installation dual boot Ganymede/windows 10 I have such error whan I try to access to windows os partition : “Une erreur est survenue en accédant à « OS ». Message reçu : L’opération demandée a échoué: Error mounting /dev/nvme0n1p3 at /run/media/maco/OS: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error”
ntfs3-g is installed , my windows work also correctly , I do not see a solution ; here partition detaillsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM D6C9-927B 214M 16% /boot/efi
├─nvme0n1p2
├─nvme0n1p3 ntfs OS 8616CB4D16CB3CC5
├─nvme0n1p4 ntfs RECOVERY AC628185628154CC
├─nvme0n1p5 vfat FAT32 MYASUS D282-4AB6
├─nvme0n1p6 swap 1 b39bda89-742e-45b5-b3b2-87616ffde66a [SWAP]
├─nvme0n1p7 ext4 1.0 linux-root 88bc54da-2519-4783-b26a-18d09d788a98 34,8G 22% /
└─nvme0n1p8 ext4 1.0 home 0c72b0be-1435-4141-a401-26369bdd4629 127G 1% /home
This generally happens when the NTFS drive is not cleanly unmounted. You can login to you windows and check the disks in question make sure to use the F flag to force it to check and clean the volume. Once done it should be accessible again.
And disable fast boot/fast startup or whatever it’s called, so that it does a proper shutdown.
I will add the obligatory, ‘it’s best to keep them separated because they’re like feral cats (Windows and Linux) and will fight and cause each other damage.’ Just saying….NTFS is not well supported outside MS platforms.
news from this morning ; partition is mounted in the terminal without difficulties but still not by dolphin ; I installed also fuse but error is the same; I used several linux since more than 10 years and I never had a such matter to connect ntfs partitions ; it’s not thrue that Linux have difficulties on that subject , it’s only this version of EOS , and it’s not at all positive ! probably EOS is not designed for dual boot ?some app other than ntfs3-g , fuse or others shall be added manually?
I have been dual-booting in the past, and i still have 2/3 of my drives formatted in ntfs without any problems, this is likely a problem with your setup.
Can you show us the content of your fstab ?
You might also want to check in System Settings > Disks & Camera > Device Auto-mount that the On login box is ticked (Should not be necessary but sometimes Dolphin get capricious without it).
In fact the problem is not the mounting by fstab -don’t need permanent access-but by dolphin;I have the error msg after password entering.I saw on the forum others have also this mater,but non solution it seems.
What would be the settings in kde ?
Note : the mounting works perfectly through the console
Interesting, I usually do mounting (permanently) vis fstab or terminal vs GUI.
However, I have occasionally (and successfully) browsed to a NTFS partition via dolphin?
EOS is a rolling release distro, therefore there are no “versions” of endeavouros.
The versions you find are the ISOs (mercury, ganymede) but once you update, it’s not considered mercury or ganymede anymore, as it’s completely different now. Very hard to explain, but “this version of EOS” is basically different for everyone, depending on what hour / minute they updated and what mirrors are used.
Then I would argue the problem isn’t EOS but dolphin, and as someone else has also said, dirty bits can also cause issues like this, if the drive isn’t unmounted correctly before shutdown you can get in trouble the next time you want to mount it. From my experience, dolphin doesn’t always handle unmounting drives well.
I agree with you , it’s probably dolphin the matter - not EOS I hope - but anyway for me no chnage , still a problem ; for your information it’s the first time I install this version of EOS kde/dolphin ; I have another EOS with xfce in dual boot and I will check if there is an issue
Yeah, I dont know why dolphin makes these issues as I have similar issues since pretty much I use Linux, therefore I am always super careful when using USB-Sticks or external drives with it. Not shure if the KDE devs are aware of it, but I would assume that they know since many have this issue.
In your case, either be super careful like me, or use xfce or install a different file explorer if you want. some use the gnome one (think nautilus?) or you can use nemo or whatever, plenty to choose from. whatever works for you
regarding the quantity of same matter on the web through others distro succh as mandriva , arch…., I fail to understand how kde/dolphin can still have the problem non cleared.
I could of course install xfce but anyway , I installed this version of EOS to test specailly kde ; then I will mount when necessary my ntfs pattion with the terminal.Plenty of data on the indicate to configure specific files such as blacklist.conf , options_mount.conf ….. I prefer to keep the distro as it is ; I will delete kde if necessary later on ,and in that case I will indicate the reasons of my decision in distrowatch ( and I will be not at all gentle)
I know it’s a couple months old by now but I wanted to add that disabling Fast Startup and checking/repairing disk from Windows actually solved this issue for me!! I hope someone else can find this in the future so that it can be of help; I had to read a lot of stuff for it to work [also that and having ntfs-3g of course]
I have just run into this issue on EOS with XFCE after an update, although my install complained about fsconfig (sorry, I didn’t write down the exact error). I have been able to access my Windows partition for years on EOS.
Anyway, rolling back via Timeshift fixes the problem, so there’s an issue/incompatibility somewhere within the update.
When it’s discovered, could someone please let me know?
