External HD Partition mounting error

I have an external HD with several partitions ,used for backup ; unfortunately since this morning - after export on this HD of a virtual machine recently installed - the partition can’t be read with such error :"impossible to mount sda3 : wrong fs type, bad option, bad superblock ,missing codepage or helper ,or other error "
This partition can be read with my other Linux ( Mx ) and also with Windows10 ( installed in VM )
Also through Gparted it can’t be mounted but no indication error ( all indication format , name , size … are correct )
Note : it’s a ntfs partition 135G , others partitions - ntfs or ext4 -can be mounted and read with no pb.
here a fdisk of the said partition( sda3 )

Blockquote
Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 2048 230842367 230840320 110,1G b W95 FAT32
/dev/sda2 230842368 435640319 204797952 97,7G 7 HPFS/NTFS/exFAT
/dev/sda3 435640320 720773119 285132800 136G 7 HPFS/NTFS/exFAT
/dev/sda4 720773120 976771071 255997952 122,1G f Étendue W95 (LBA)
/dev/sda5 720775168 976771071 255995904 122,1G 7 HPFS/NTFS/exFAT

Blockquote

@endko
Check if exfat-utils or exfatprogs is installed:

yay -Ss exfat-utils

Edit 1: I don’t really know what is crucial.
With me :

extra/exfatprogs 1.2.2-1 (62.3 KiB 181.6 KiB) (Installed)
    exFAT filesystem userspace utilities for the Linux Kernel exfat driver

I confirm exfat-utils 1.4.0-2 is installed now ( and in conflict with exfatprogs then I deinstall it)
But the problem isn’t cleared

I can have access if I mount the partition by commend : sudo mount /dev/sda3 /mnt !!!
but if I try to mount it through the system the error appear " impossible to mount /dev/sad3 /run/media/ecr/P2-VMexport-135G " ( P2-VMexport-135G is the label of the partition

Mount the partition by the UUID instead of the label and see if that gives you better results

1 Like

@endko
With gparted I created an exfat partition (no matter if it’s in msdos or GPT) and the label
is limited to 11 in length. Is it a caprice of gparted?

@thefrog
the partition is connected normally if I use the command “mount” , the error is due to the EOS /Xfce4 system when I try to connect through Thunar : no choice to use the label or the UUID in that case ( I don’t known the command used? )
The partition is fully working also with others systems : Mx linux and Windows10 , then no defects in the partition ( even if Thunar indicates errors : fs type, superblock…)

@eso
my Gparted - rev 1.5.0 - limits not the label to 11 characters it seems ; the partition we are speaking is labelled "P2-VMexport-135G " i.e 16 characters ; hope there is no prohibited characters in Thunar ?

Here the detail of the partitions ( P2 & P3 in error through Thunar)

This looks like an extra space at the end or is that the way your formatted it here?

Maybe the issue is the space if its part of the name.

@thefrog
it’s an extra space ,not part of the label
Do you known if Thunar require e specific configuration ? because I am quite sure the origin of the matter is Thunar

I don’t have problems with thunar. However I don’t use NTFS or FAT files systems either

as I have a dual boot linux/windows I have to use ntfs or fat format for access with windows ; both partitions with error are ntfs type , but one ntfs ( p2b ) is workinf , then I do not understand…

My problem nis still not cleared , it’s a big issue , can’t read my HD external