Description of problem: Kernels 5.5.9 and 5.5.13 fail to mount the portable ssd drive. Kernel 5.5.8 allows potable ssd drive to mount and work correctly. Version-Release number of selected component (if applicable): SanDisk Extreme Portable SSD 500 GB Up to 550 MB/s Read (SDSSDE60-500G-G25) - USB Type-C to Type-C cable and a Type-C to Type-A adapter. How reproducible: When the drive is plugged into the usb 2 an 3 ports and can not open drive with any application as the file manager Dolphin states: (An error occurred while accessing 'Extreme SSD', the system responded: The requested operation has failed: Error mounting system-managed device /dev/sdb1: unknown filesystem type 'exfat') Steps to Reproduce: 1.Connect drive at boot time 2.Connect drive after OS initialisd 3.Check OS in kernel 5.5.8, 5.5.9 and 5.5.13 for steps 1 and 2
Assignee: bugsquad => kernel
From the software center I installed fuse-exfat. Unfortunately the 5.5.13 Kernel had to be uninstalled for this to install, so the 5.5.9 Kernel was reverted back to for this to take place. I rebooted the O/S and from the Device Notifier selected the Dolphin file manager in the system tray. The SSD device then started to mount and the Dolphin icon flashed for about six seconds then stopped and nothing else happened. I directly went into the Dolphin file manager and selected the ssd device where it then mounted and showed all the files that were in it. I selected some files within the file manager and was able to access them successfully. It appears after installing fuse-exfat the device was able to mount but was unable to access the Dolphin file manager from the Device Notifier in the system tray. I could however access the SSD device only when I went directly into the file manager.It would appear the Device Notifier in the system stray is not linking directly to the Dolphin file manager now.
CC: (none) => egc
Can not mount with kernel 5.5.14
From the software center I also installed exfat-utils 1.3.0 2 mga7 but still the Device Notifer will not open the the SSd device in the Dolphin file manager. I received an update from Mageia today to upgrade to the 5.5.14.1 Kernel. When I updated the Kernel and rebooted the new kernel had not been loaded so I had to maually install it in the software center and when rebooted the fuse-exfat 1.3.0 package had to be re-installed. Unfortunately just like the 5.5.13 Kernel the 5.5.14.1 kernel had to be removed as well for the package to be installed for the SSD portable device to function. I also have another Linux distro on my system and that uses the 5.5.10 Kernel and the sdd device works perfectly even when initialised from the Device Notifier in the system tray for the Dolphin file manager display the contents. This O/S also uses the exfat-utils and fuse-exfat packages. I have now come to the conclusion there is a problem with the fuse-exfat package to allow full functionality within the Mageia O/S and that includes when the kernels have been upgraded past 5.5.9 as they say there is a conflict and the upgraded Kernels will have to be removed if the package needs to be installed. Please Advise. Thank you.
Same problem with XFCE Related : https://bugs.mageia.org/show_bug.cgi?id=26344 With 5.5.9, without fuse-exfat, mount via the desktop didn't work, but it was still possible to mount "manually". With 5.5.14, without fuse-exfat, manual mounting doesn't work anymore
CC: (none) => choucroot
I pushed a 5.5.15-1 to updates_testing that drops the conflict on fuse-exfat for now so you cann still use latest kernel and fixes.... I'll try to setup a system with exfat here and see if I can find a better fix for auto-mounting...
CC: (none) => tmb
Hello, Seems that the new exfat module doesn't know the parameter "namecase" I had to load manually the exfat module, without this the exfat filesystem is unknown. under the 5.5.14-1 ( not tested the 5.5.15) [root@mageia7-test x]# udisksctl mount -t exfat -b /dev/sda3 Error mounting /dev/sda3: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sda3 at /run/media/root/1A38-2763: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt -o namecase=0 mount: /mnt: mauvais type de système de fichiers, option erronée, superbloc erroné sur /dev/sda3, page de code ou programme auxiliaire manquant, ou autre erreur. [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt [root@mageia7-test x]# ls /mnt tests/ [root@mageia7-test x]# uname -a Linux mageia7-test 5.5.14-desktop-1.mga7 #1 SMP Wed Apr 1 15:12:13 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux under the 5.5.6 [root@mageia7-test x]# uname -a Linux mageia7-test 5.5.6-desktop-2.mga7 #1 SMP Tue Feb 25 11:54:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt -o "namecase=0" [root@mageia7-test x]# ls /mnt tests/ [root@mageia7-test x]# mount | grep /mnt /dev/sda3 on /mnt type exfat (rw,relatime,fmask=0022,dmask=0022,iocharset=utf8,namecase=0,errors=remount-ro) It seems that udisk has an harcoded option in it to use the option "namecase=0" the file https://github.com/storaged-project/udisks/blob/master/src/udiskslinuxmountoptions.c contains static const gchar *exfat_defaults[] = { "uid=", "gid=", "iocharset=utf8", "namecase=0", "errors=remount-ro", NULL }; static const gchar *exfat_allow[] = { "dmask", "errors", "fmask", "iocharset", "namecase", "umask", NULL }; hope this helps.
CC: (none) => joe_c_moi
CC: joe_c_moi => (none)
Hello, Some extra tests... leading me to conclude it is the exfat module that might have a problem (in fact either we patch udisks or we patch the kernel module to add a non existent namecase parameter ;-) ). Sorry for the french in the tests, i didn't remove locales. [root@mageia7-test x]# uname -a Linux mageia7-test 5.5.15-desktop-2.mga7 #1 SMP Sat Apr 4 00:09:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt mount: /mnt: type de système de fichiers « exfat » inconnu. [root@mageia7-test x]# modprobe exfat [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt [root@mageia7-test x]# ls /mnt tests/ [root@mageia7-test x]# urpmi fuse-exfat Afin de poursuivre la mise à jour, les paquetages suivants doivent être désinstallés : kernel-desktop-5.5.14-1.mga7-1-1.mga7.x86_64 (en raison de conflit avec fuse-exfat[< 1.3.0-3]) kernel-desktop-latest-5.5.14-1.mga7.x86_64 (en raison du manque de kernel-desktop-5.5.14-1.mga7) (o/N) o $MIRRORLIST: media/tainted/release/fuse-exfat-1.3.0-1.mga7.tainted.x86_64.rpm installation de fuse-exfat-1.3.0-1.mga7.tainted.x86_64.rpm depuis /var/cache/urpmi/rpms Préparation... ######################################################################################################################### 1/1: fuse-exfat ######################################################################################################################### désinstallation du paquetage kernel-desktop-5.5.14-1.mga7-1-1.mga7.x86_64 1/2: désinstallation de kernel-desktop-5.5.14-1.mga7-1-1.mga7.x86_64 ######################################################################################################################### Utilisation : grub2-set-default [OPTION] ENTRÉE_MENU Configurer l'entrée de menu par défaut pour GRUB. Cela nécessite de configurer GRUB_DEFAULT=saved dans /etc/default/grub. -h, --help afficher ce message et quitter -V, --version afficher la version du logiciel et quitter --boot-directory=RÉP chercher les images GRUB dans le répertoire RÉP//grub2 au lieu du répertoire /boot/grub2 ENTRÉE_MENU est un numéro, un titre d'entrée de menu ou un identifiant d'entrée de menu. Signaler les bogues à <bug-grub@gnu.org>. désinstallation du paquetage kernel-desktop-latest-5.5.14-1.mga7.x86_64 2/2: désinstallation de kernel-desktop-latest-5.5.14-1.mga7.x86_64 ######################################################################################################################### [root@mageia7-test x]# umount /mnt [root@mageia7-test x]# mount -t fuse-exfat /dev/sda3 /mnt mount: /mnt: type de système de fichiers « fuse-exfat » inconnu. [root@mageia7-test x]# mount -t exfat-fuse /dev/sda3 /mnt FUSE exfat 1.3.0 fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option [root@mageia7-test x]# ls /mnt test_smb/ test-wine/ [root@mageia7-test x]# mkdir /mnt/fuse-exfat [root@mageia7-test x]# mount -t exfat-fuse /dev/sda3 /mnt/fuse-exfat FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. [root@mageia7-test x]# ls /mnt/fuse-exfat/ tests/ [root@mageia7-test x]# mount | grep /mnt/fuse-exfat /dev/sda3 on /mnt/fuse-exfat type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [root@mageia7-test x]# umount /mnt/fuse-exfat [root@mageia7-test x]# udisksctl mount -t exfat -b /dev/sda3 Mounted /dev/sda3 at /run/media/root/1A38-2763. [root@mageia7-test x]# mount | grep /run/media/root/1A38-2763 /dev/sda3 on /run/media/root/1A38-2763 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) [root@mageia7-test x]# umount /run/media/root/1A38-2763 [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt -o "namecase=0" FUSE exfat 1.3.0 fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt/fuse-exfat -o "namecase=0" FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. [root@mageia7-test x]# ls /mnt/fuse-exfat tests/ [root@mageia7-test x]# umount /mnt/fuse-exfat [root@mageia7-test x]# urpme fuse-exfat désinstallation de fuse-exfat-1.3.0-1.mga7.tainted.x86_64 désinstallation du paquetage fuse-exfat-1.3.0-1.mga7.tainted.x86_64 1/1: désinstallation de fuse-exfat-1.3.0-1.mga7.tainted.x86_64 ######################################################################################################################### [root@mageia7-test x]# mount -t exfat /dev/sda3 /mnt -o "namecase=0" mount: /mnt: mauvais type de système de fichiers, option erronée, superbloc erroné sur /dev/sda3, page de code ou programme auxiliaire manquant, ou autre erreur. [root@mageia7-test x]# udisksctl mount -t exfat -b /dev/sda3 Error mounting /dev/sda3: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sda3 at /run/media/root/1A38-2763: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error [root@mageia7-test x]#
Awesome, thanks for debugging this. I've patched udisks2 to remove the non-existent option, and submitted: udisks2-2.8.2-1.1.mga7 to Core Updatea Testing Please try that when it's available and see if it works.
full rpms list: SRPM: udisks2-2.8.2-1.1.mga7.src.rpm i586: libudisks2_0-2.8.2-1.1.mga7.i586.rpm libudisks2-devel-2.8.2-1.1.mga7.i586.rpm libudisks-gir2.0-2.8.2-1.1.mga7.i586.rpm udisks2-2.8.2-1.1.mga7.i586.rpm udisks2-btrfs-2.8.2-1.1.mga7.i586.rpm udisks2-iscsi-2.8.2-1.1.mga7.i586.rpm udisks2-lvm2-2.8.2-1.1.mga7.i586.rpm udisks2-zram-2.8.2-1.1.mga7.i586.rpm x86_64: lib64udisks2_0-2.8.2-1.1.mga7.x86_64.rpm lib64udisks2-devel-2.8.2-1.1.mga7.x86_64.rpm lib64udisks-gir2.0-2.8.2-1.1.mga7.x86_64.rpm udisks2-2.8.2-1.1.mga7.x86_64.rpm udisks2-btrfs-2.8.2-1.1.mga7.x86_64.rpm udisks2-iscsi-2.8.2-1.1.mga7.x86_64.rpm udisks2-lvm2-2.8.2-1.1.mga7.x86_64.rpm udisks2-zram-2.8.2-1.1.mga7.x86_64.rpm
If allows fuse-exfat to mount the device, but fails without that package. When it fails, strace shows ... # grep exfat strace.txt 24767 stat("/sbin/mount.exfat", 0x7ffdfd7615e8) = -1 ENOENT (No such file or directory) 24767 stat("/sbin/fs.d/mount.exfat", 0x7ffdfd7615e8) = -1 ENOENT (No such file or directory) 24767 stat("/sbin/fs/mount.exfat", 0x7ffdfd7615e8) = -1 ENOENT (No such file or directory) 24767 mount("/dev/sde1", "/media", "exfat", 0, NULL) = -1 ENODEV (No such device) 24767 write(2, "/media: unknown filesystem type 'exfat'.", 40) = 40 Could the udisks2 update also suggest fuse-exfat in order to get it back into users systems?
CC: (none) => davidwhodgins
Meant to add, without fuse-exfat installed, mounting requires first manually running modprobe exfat, otherwise the mount fails.
(In reply to Dave Hodgins from comment #10) > > Could the udisks2 update also suggest fuse-exfat in order to get it back into > users systems? no, we are trying to get rid of fuse-exfat.
Ah, the new kernel exfat is missing an alias... will fix
CC: (none) => rolfpedersen
Hello, I confirm that the new udisks2 package ( not tested to install the libs or subpackages (don't have brts or lvm volumes to test), but as the change is only to remove the namecase=0 option only for exfat, should not matter). But as it only works if the exfat module is loaded manually. [root@mageia7-test x]# rmmod exfat rmmod: ERROR: Module exfat is not currently loaded [root@mageia7-test x]# udisksctl mount -t exfat -b /dev/sda3 Error mounting /dev/sda3: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sda3 at /run/media/root/1A38-2763: unknown filesystem type 'exfat' [root@mageia7-test x]# modprobe exfat libkmod: kmod_config_parse: /etc/modprobe.d/rtbth.conf line 2: ignoring bad line starting with 'rtbt' [root@mageia7-test x]# udisksctl mount -t exfat -b /dev/sda3 Mounted /dev/sda3 at /run/media/root/1A38-2763. [root@mageia7-test x]# rpm -q --info udisks2 Name : udisks2 Version : 2.8.2 Release : 1.1.mga7 Architecture: x86_64 Install Date: sam. 04 avril 2020 20:37:40 CEST Group : System/Libraries Size : 2322655 License : GPLv2+ Signature : RSA/SHA256, sam. 04 avril 2020 18:05:09 CEST, Key ID b742fa8b80420f66 Source RPM : udisks2-2.8.2-1.1.mga7.src.rpm Build Date : sam. 04 avril 2020 17:38:51 CEST Build Host : localhost Relocations : (not relocatable) Packager : tmb <tmb> Vendor : Mageia.Org URL : https://github.com/storaged-project/udisks Summary : Disk Manager Description : udisks provides a daemon, D-Bus API and command line tools for managing disks and storage devices. This package is for the udisks 2.x series. [root@mageia7-test x]# uname -a Linux mageia7-test 5.5.15-desktop-2.mga7 #1 SMP Sat Apr 4 00:09:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@mageia7-test x]#
Yes, the exfat module autoloading is fixed in kernel-5.5.15-3 that is currently building.
Confirmed fixed in kernel-desktop-5.5.15-3.mga7-1-1.mga7 I expect it will be pushed to updates as part of bug 26434, so closing this bug as resolved. After opening an exfat filesystem on an inserted usb stick using the device manager in Mageia 7 kde, x86_64, mount shows ... /dev/sde1 on /run/media/dave/red type exfat (rw,nosuid,nodev,relatime,uid=500,gid=500,fmask=0022,dmask=0022,iocharset=utf8,bps=512,errors=remount-ro,uhelper=udisks2)
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
*** Bug 26344 has been marked as a duplicate of this bug. ***
Hello, @Dave: on the repository i checked, i have kernel-desktop-latest-5.5.15-3.mga7.x86_64.rpm but only kernel-desktop-5.5.15-3.mga7-1-1.mga7.x86_64.rpm So installation fail due to the missing of kernel-desktop-5.5.15-3.mga7.x86_64.rpm Is it normal ? Should it not have a kernel-desktop-latest-5.5.15-3.mga7-1-1.mga7.x86_64.rpm Thanks
(In reply to Nicolas Nicolas from comment #18) > Hello, > @Dave: on the repository i checked, i have > kernel-desktop-latest-5.5.15-3.mga7.x86_64.rpm > but only > kernel-desktop-5.5.15-3.mga7-1-1.mga7.x86_64.rpm > So installation fail due to the missing of > kernel-desktop-5.5.15-3.mga7.x86_64.rpm > Is it normal ? > Should it not have a kernel-desktop-latest-5.5.15-3.mga7-1-1.mga7.x86_64.rpm Give it a few hours. The kernel packages are large, and with the mirrors also syncing cauldron, with it's large number of builds, it can take quite a while for some mirrors to fully sync. I'd also try switching to a fast mirror. For example https://mirror.math.princeton.edu/pub/mageia/distrib/7.1/x86_64/media/core/updates_testing/ had the actual kernel about 10 minutes before I tested the update. Even though it may be geographically far from you, it may actually be faster at getting and distributing updates then a physically closer mirror. The internet generally doesn't care about distance.
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2020-0162.html