Hey guys,
I have a 64GB Memory Card from my Camera, I just plugged it into my laptop and it told me it cannot mount it because it dosen’t recognize exFAT, I get
exited with non-zero exit status 32: mount: unknown filesystem type 'exfat'
Any ideas what I can do?
Thanks
Hi, try installing ex-fat related utilities using yast or this command as root:
zypper install fuse-exfat exfat-utils
You may need to reboot after, to be safe.
On 2015-03-16, jurgen73 <jurgen73@no-mx.forums.opensuse.org> wrote:
> Any ideas what I can do?
http://software.opensuse.org/package/fuse-exfat
or
I’d like to jump in on this thread as I’m experiencing the same…
I have the same issue w/ openSuSE 13.2 - I have Samsung EVO 64 GB microSDHD cards formatted as exFAT that won’t mount.
I added the exfat packages through yast (exfat-utils & fuse-exfat), restarted, but still can’t mount.
The packages that I added were:
and
linux-29m7:/ # fdisk /dev/sdc
Welcome to fdisk (util-linux 2.25.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdc: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1 32768 122814463 122781696 58.6G 7 HPFS/NTFS/exFAT
Command (m for help): q
linux-29m7:/ # mount /dev/sdc1 /sdxc
mount: special device /dev/sdc1 does not exist
linux-29m7:/ # ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 May 6 13:42 /dev/sda
brw-rw---- 1 root disk 8, 1 May 6 13:42 /dev/sda1
brw-rw---- 1 root disk 8, 2 May 6 13:42 /dev/sda2
brw-rw---- 1 root disk 8, 3 May 6 13:42 /dev/sda3
brw-rw---- 1 root disk 8, 16 May 6 13:42 /dev/sdb
brw-rw---- 1 root disk 8, 17 May 6 13:42 /dev/sdb1
brw-rw---- 1 root disk 8, 18 May 6 13:42 /dev/sdb2
brw-rw---- 1 root disk 8, 19 May 6 13:42 /dev/sdb3
brw-rw---- 1 root disk 8, 32 May 6 14:20 /dev/sdc
linux-29m7:/ # mount -t exfat /dev/sdc1 /sdxc
FUSE exfat 1.1.0
ERROR: failed to open '/dev/sdc1': No such file or directory.
linux-29m7:/ # ls -l /sbin/mount*
-rwxr-xr-x 1 root root 39736 Sep 25 2014 /sbin/mount.cifs
lrwxrwxrwx 1 root root 16 May 6 13:39 /sbin/mount.exfat -> mount.exfat-fuse
-rwxr-xr-x 1 root root 48112 Jan 20 03:41 /sbin/mount.exfat-fuse
lrwxrwxrwx 1 root root 20 Apr 27 12:41 /sbin/mount.fuse -> /usr/sbin/mount.fuse
lrwxrwxrwx 1 root root 19 Oct 26 2014 /sbin/mount.lowntfs-3g -> /usr/bin/lowntfs-3g
-rwsr-xr-x 1 root root 114912 Sep 29 2014 /sbin/mount.nfs
lrwxrwxrwx 1 root root 9 Oct 26 2014 /sbin/mount.nfs4 -> mount.nfs
lrwxrwxrwx 1 root root 28 Oct 26 2014 /sbin/mount.ntfs -> /etc/alternatives/mount.ntfs
lrwxrwxrwx 1 root root 16 Oct 26 2014 /sbin/mount.ntfs-3g -> /usr/bin/ntfs-3g
fdisk sees the partition and type, /dev/ only sees the device, but not the partition, and manually trying to mount to an existing mount point by explicitly invoking type fails.
Am I missing something else here?
openSuSE 13.2
Linux linux-29m7 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64 x86_64 x86_64 GNU/Linux
KDE 4.14.6
GIGABYTE GA-990FXA-UD3
AMD FX-8350
32 GB Crucial Ballistix DDR3 - 1866
2 x WD 1 TB HDD
2 x PNY GeForce GT730 2 GB DDR3
4 x ASUS VN247HP
Hi
From which repository did you get the packages?
I used (to me a known home user and education repo maintainer) the version from lrupp;
https://build.opensuse.org/package/show?project=home%3Alrupp&package=fuse-exfat
Both for openSUSE 13.2 and also have a SLE 12 package and both work with a 64GB exfat formatted device.
Malcolm,
Thanks for the quick reply. I pulled them from http://packman.links2linux.de. Are you suggesting that I remove & replace with the open build package?
-Jim
Hi
I would remove the ones you have installed and try it, there are some differences in build flags, so would be interesting to confirm if that’s the issue.
On 2015-05-06 22:46, ejboshinski wrote:
> Code:
> --------------------
> linux-29m7:/ # fdisk /dev/sdc
…
> Device Boot Start End Sectors Size Id Type
> /dev/sdc1 32768 122814463 122781696 58.6G 7 HPFS/NTFS/exFAT
…
> linux-29m7:/ # mount /dev/sdc1 /sdxc
> mount: special device /dev/sdc1 does not exist
>
> linux-29m7:/ # ls -l /dev/sd*
> brw-rw---- 1 root disk 8, 0 May 6 13:42 /dev/sda
> brw-rw---- 1 root disk 8, 1 May 6 13:42 /dev/sda1
> brw-rw---- 1 root disk 8, 2 May 6 13:42 /dev/sda2
> brw-rw---- 1 root disk 8, 3 May 6 13:42 /dev/sda3
> brw-rw---- 1 root disk 8, 16 May 6 13:42 /dev/sdb
> brw-rw---- 1 root disk 8, 17 May 6 13:42 /dev/sdb1
> brw-rw---- 1 root disk 8, 18 May 6 13:42 /dev/sdb2
> brw-rw---- 1 root disk 8, 19 May 6 13:42 /dev/sdb3
> brw-rw---- 1 root disk 8, 32 May 6 14:20 /dev/sdc
> --------------------
>
>
> fdisk sees the partition and type, /dev/ only sees the device, but not
> the partition, and manually trying to mount to an existing mount point
> by explicitly invoking type fails.
If the partition doesn’t appear in the /dev tree, there is nothing at
all you can do to mount it. I don’t think that replacing the exfat
packages with those of another repo will change that.
Years ago we created device nodes manually, now they appear
automatically. I don’t know if it is possible to still create it
manually, and I don’t remember the command name to check if it exists…
Ah! “mknod”. I found it. You could try…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
On Wed 06 May 2015 11:34:06 PM CDT, Carlos E. R. wrote:
On 2015-05-06 22:46, ejboshinski wrote:
> Code:
> --------------------
> linux-29m7:/ # fdisk /dev/sdc
…
> Device Boot Start End Sectors Size Id Type
> /dev/sdc1 32768 122814463 122781696 58.6G 7 HPFS/NTFS/exFAT
…
> linux-29m7:/ # mount /dev/sdc1 /sdxc
> mount: special device /dev/sdc1 does not exist
>
> linux-29m7:/ # ls -l /dev/sd*
> brw-rw---- 1 root disk 8, 0 May 6 13:42 /dev/sda
> brw-rw---- 1 root disk 8, 1 May 6 13:42 /dev/sda1
> brw-rw---- 1 root disk 8, 2 May 6 13:42 /dev/sda2
> brw-rw---- 1 root disk 8, 3 May 6 13:42 /dev/sda3
> brw-rw---- 1 root disk 8, 16 May 6 13:42 /dev/sdb
> brw-rw---- 1 root disk 8, 17 May 6 13:42 /dev/sdb1
> brw-rw---- 1 root disk 8, 18 May 6 13:42 /dev/sdb2
> brw-rw---- 1 root disk 8, 19 May 6 13:42 /dev/sdb3
> brw-rw---- 1 root disk 8, 32 May 6 14:20 /dev/sdc
> --------------------
>
>
> fdisk sees the partition and type, /dev/ only sees the device, but not
> the partition, and manually trying to mount to an existing mount point
> by explicitly invoking type fails.
If the partition doesn’t appear in the /dev tree, there is nothing at
all you can do to mount it. I don’t think that replacing the exfat
packages with those of another repo will change that.
Years ago we created device nodes manually, now they appear
automatically. I don’t know if it is possible to still create it
manually, and I don’t remember the command name to check if it exists…
Ah! “mknod”. I found it. You could try…
Hi
This is fuse controlled nothing to do with mknod AFAIK…
If I only have fuse-exfat installed ( no utils package etc) it mounts,
if I remove fuse-exfat then I see the device appear in lsblk, but no
mount.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2015-05-07 02:49, malcolmlewis wrote:
> Hi
> This is fuse controlled nothing to do with mknod AFAIK…
>
> If I only have fuse-exfat installed ( no utils package etc) it mounts,
> if I remove fuse-exfat then I see the device appear in lsblk, but no
> mount.
The device appearing or not should be independent of the filesystem
inside, or being able to mount or not.
If that is not the case, I’m baffled.
I’d rather think that the stick has a faulty partition table. There was
a recent thread in which the solution was to blank, partition, format
the stick.
But that’s not something he can do, I think.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Before I go down the trail of installing different builds (of which I will do), it is worth noting that I have 4 of these Samsung microSDHC cards - all of which perform the same way.
As additional food for thought, this microSDHC card, along with the “SD Adapter for microSD” (provided by Samsung) will not mount on one Win 7 Home box, while it will on another. Also, I am able to mount successfully a 32 GB microSDHC from SanDisk, using the same Samsung “adapter” - the only difference being that the 32 GB card is formatted as FAT32 (vfat); ergo there should be no problem regarding the adapter, USB port or ability to read microSDHC (as I have seen in other 'net posts as causes for failure). Of course, this is my thought on this matter - can’t prove/disprove this point…
linux-29m7:/ # fdisk /dev/sdc
Welcome to fdisk (util-linux 2.25.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdc: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
Command (m for help): q
linux-29m7:/ # ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 May 6 13:42 /dev/sda
brw-rw---- 1 root disk 8, 1 May 6 13:42 /dev/sda1
brw-rw---- 1 root disk 8, 2 May 6 13:42 /dev/sda2
brw-rw---- 1 root disk 8, 3 May 6 13:42 /dev/sda3
brw-rw---- 1 root disk 8, 16 May 6 13:42 /dev/sdb
brw-rw---- 1 root disk 8, 17 May 6 13:42 /dev/sdb1
brw-rw---- 1 root disk 8, 18 May 6 13:42 /dev/sdb2
brw-rw---- 1 root disk 8, 19 May 6 13:42 /dev/sdb3
brw-rw---- 1 root disk 8, 32 May 6 23:12 /dev/sdc
brw-rw---- 1 root disk 8, 33 May 6 23:12 /dev/sdc1
linux-29m7:/ # mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
.....
/dev/sdc1 on /run/media/root/6238-3063 type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
linux-29m7:/ #
As an aside, I would think that this would be a rather common occurrence - either positive or negative; I can’t believe that I’m the only one encountering this challenge…
-Jim
On Thu 07 May 2015 01:48:06 AM CDT, Carlos E. R. wrote:
On 2015-05-07 02:49, malcolmlewis wrote:
> Hi
> This is fuse controlled nothing to do with mknod AFAIK…
>
> If I only have fuse-exfat installed ( no utils package etc) it mounts,
> if I remove fuse-exfat then I see the device appear in lsblk, but no
> mount.
The device appearing or not should be independent of the filesystem
inside, or being able to mount or not.
If that is not the case, I’m baffled.
I’d rather think that the stick has a faulty partition table. There was
a recent thread in which the solution was to blank, partition, format
the stick.
But that’s not something he can do, I think.
Hi
So tried both a USB and SD card without exfat present, just using
udevadm monitor I get udev events showing the devices created etc, then
if fuse-exfat installed fuse running with udisk2 mounting the devices.
So like you say, could be an actual partition issue.
Interesting the usb device (sdc) shows as type 7 HPFS/NTFS/exFAT yet
the sd card (mmcblk0) just shows as Microsoft Basic data from fdisk -l
command.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi
Is the sd card reader a USB device or (as in my case) part of the system? Yes some external sd card readers can’t read sd cards > 4GB.
Can you format the 32GB one as exfat?
On the windows 7 system it may need a driver…
Malcolm,
It is a USB reader. As noted above, it will read microSDHC cards. The successful instance has a partition formatted as FAT32. At this point I am reluctant to reformat as it (32 GB card) is readable across all HW platforms; also, I have data on the card that I would like to preserve for now. The same situation exists with the 64 GB cards; I have data on them that needs to be retained (until I can mount them - thus, the thread we’re discussing). No re-format option here until I can mount & transfer the data.
So for the 32 GB - NO ISSUE - I only included it as an example that in fact the HW worked for microSCHC hardware.
To refocus, we’re trying to read the 64 GB EVO card with a formatted partition as exFAT (as per Samsung literature, they were formatted prior to shipment) …
-Jim
All,
I have tried w/o the exfat-utils loaded (both 1.1.1 from Packman & 1.1.0-3.1 from LRupp) - no joy.
I have tried the full install from LRupp (http://download.opensuse.org/repositories/home:/lrupp/openSUSE_13.2/x86_64/) exfat-utils-1.1.0-3.1 & fuse-exfat-1.1.0-2.1) - no joy.
I have the exact same results as posted above in the code boxes: fdisk sees the partition (in this case dev/sdc1), ls of /dev/sd* shows /dev/sdc, and of course a manual mount fails…
linux-29m7:/ # date
Thu May 7 16:27:08 EDT 2015
linux-29m7:/ # mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=16480736k,nr_inodes=4120184,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
/dev/md127 on / type ext4 (rw,relatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sdb1 on /boot-bu type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /boot type ext4 (rw,relatime,data=ordered)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
192.168.100.130:/mnt/HD/HD_a2/X2 on /x4/130 type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.100.130,mountvers=3,mountport=59369,mountproto=udp,local_lock=none,addr=192.168.100.130)
gvfsd-fuse on /run/user/0/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
linux-29m7:/ # fdisk /dev/sdc
Welcome to fdisk (util-linux 2.25.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdc: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1 32768 122814463 122781696 58.6G 7 HPFS/NTFS/exFAT
Command (m for help): q
linux-29m7:/ # ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 May 7 16:25 /dev/sda
brw-rw---- 1 root disk 8, 1 May 7 16:25 /dev/sda1
brw-rw---- 1 root disk 8, 2 May 7 16:25 /dev/sda2
brw-rw---- 1 root disk 8, 3 May 7 16:25 /dev/sda3
brw-rw---- 1 root disk 8, 16 May 7 16:25 /dev/sdb
brw-rw---- 1 root disk 8, 17 May 7 16:25 /dev/sdb1
brw-rw---- 1 root disk 8, 18 May 7 16:25 /dev/sdb2
brw-rw---- 1 root disk 8, 19 May 7 16:25 /dev/sdb3
brw-rw---- 1 root disk 8, 32 May 7 16:29 /dev/sdc
linux-29m7:/ # mount -t exfat /dev/sdc1 /sdxc
FUSE exfat 1.1.0
ERROR: failed to open '/dev/sdc1': No such file or directory.
Any other ideas?
-Jim
On Thu 07 May 2015 09:16:02 PM CDT, ejboshinski wrote:
All,
I have tried w/o the exfat-utils loaded (both 1.1.1 from Packman &
1.1.0-3.1 from LRupp) - no joy.
I have tried the full install from LRupp (http://tinyurl.com/mv2cfp3)
exfat-utils-1.1.0-3.1 & fuse-exfat-1.1.0-2.1) - no joy.
I have the exact same results as posted above in the code boxes: fdisk
sees the partition (in this case dev/sdc1), ls of /dev/sd* shows
/dev/sdc, and of course a manual mount fails…
Code:
linux-29m7:/ # date
Thu May 7 16:27:08 EDT 2015
linux-29m7:/ # mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs
(rw,nosuid,size=16480736k,nr_inodes=4120184,mode=755) securityfs
on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs
(rw,nosuid,nodev) devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run
type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type
tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup
on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset) cgroup
on /sys/fs/cgroup/cpu,cpuacct type cgroup
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup
on /sys/fs/cgroup/memory type cgroup
(rw,nosuid,nodev,noexec,relatime,memory) cgroup
on /sys/fs/cgroup/devices type cgroup
(rw,nosuid,nodev,noexec,relatime,devices) cgroup
on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer) cgroup
on /sys/fs/cgroup/net_cls,net_prio type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup
on /sys/fs/cgroup/blkio type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio) cgroup
on /sys/fs/cgroup/perf_event type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event) cgroup
on /sys/fs/cgroup/hugetlb type cgroup
(rw,nosuid,nodev,noexec,relatime,hugetlb) /dev/md127 on / type ext4
(rw,relatime,data=ordered) systemd-1 on /proc/sys/fs/binfmt_misc type
autofs
(rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs
on /dev/hugepages type hugetlbfs (rw,relatime) debugfs
on /sys/kernel/debug type debugfs (rw,relatime) /dev/sdb1 on /boot-bu
type ext4 (rw,relatime,data=ordered) /dev/sda1 on /boot type ext4
(rw,relatime,data=ordered) rpc_pipefs on /var/lib/nfs/rpc_pipefs type
rpc_pipefs (rw,relatime) 192.168.100.130:/mnt/HD/HD_a2/X2 on /x4/130
type nfs
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.100.130,mountvers=3,mountport=59369,mountproto=udp,local_lock=none,addr=192.168.100.130)
gvfsd-fuse on /run/user/0/gvfs type fuse.gvfsd-fuse
(rw,nosuid,nodev,relatime,user_id=0,group_id=0) fusectl
on /sys/fs/fuse/connections type fusectl (rw,relatime) linux-29m7:/ #
fdisk /dev/sdc Welcome to fdisk (util-linux 2.25.1). Changes will
remain in memory only, until you decide to write them. Be careful
before using the write command. Command (m for help): p Disk /dev/sdc:
1 MiB, 1048576 bytes, 2048 sectors Units: sectors of 1 * 512 = 512
bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size
(minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk
identifier: 0x00000000 Device Boot Start End Sectors Size
Id Type /dev/sdc1 32768 122814463 122781696 58.6G 7
HPFS/NTFS/exFAT Command (m for help): q
linux-29m7:/ # ls -l /dev/sd*
brw-rw---- 1 root disk 8, 0 May 7 16:25 /dev/sda
brw-rw---- 1 root disk 8, 1 May 7 16:25 /dev/sda1
brw-rw---- 1 root disk 8, 2 May 7 16:25 /dev/sda2
brw-rw---- 1 root disk 8, 3 May 7 16:25 /dev/sda3
brw-rw---- 1 root disk 8, 16 May 7 16:25 /dev/sdb
brw-rw---- 1 root disk 8, 17 May 7 16:25 /dev/sdb1
brw-rw---- 1 root disk 8, 18 May 7 16:25 /dev/sdb2
brw-rw---- 1 root disk 8, 19 May 7 16:25 /dev/sdb3
brw-rw---- 1 root disk 8, 32 May 7 16:29 /dev/sdc
linux-29m7:/ # mount -t exfat /dev/sdc1 /sdxc
FUSE exfat 1.1.0
ERROR: failed to open ‘/dev/sdc1’: No such file or directory.
Any other ideas?
-Jim
Hi
I would guess it’s the USB card reader and a limitation of the device
or in windows it has/requires a driver, can you check the specs… Not
plugging in to a USB 3.0 port?
So it works on one windows 7 machine, but not another, same USB device
and 64GB sd card? Both windows versions the same etc?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2015-05-07 23:16, ejboshinski wrote:
> Any other ideas?
Me, I would play a bit.
I would read the cards in a Windows machine (ok, that’s cheating), and
make a backup of the files.
Then, back in Linux I would do a full image backup of the card, with dd.
Then I would fill with zeroes the start of the card (one card only), say
a hundred megs with dd. I would then create a partition table and one
partition.
Then, back to Windows, I would format that partition with exfat —
assuming that Windows can create exFAT volumes, which I do not know. And
restore the files.
Then, back to Linux, I would try and see if the partition is visible in
/dev.
If at some point the procedure fails, you can restore the card to the
original state using the image previously done with dd. So there should
be no danger of damage (should not, but might).
If the procedure works, do it with all of them.
That’s what I would do. O:-)
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Ok, so I have finally found some progress on this, and as a preface, I feel quite ashamed of myself…
However, for the benefit of others that might be struggling with this, hopefully it will provide some clarity.
In a nut shell, I introduced too many variables into the equation.
Yes, the card would read with the micro adapter on one Windows box; the point that I forgot was that I was using a built-in card reader on that machine; hence USB adapter was not in the picture.
On my Linux box, I was using the USB adapter, and on the other Windows box I’m also using a built-in card reader.
So when I happened to find another USB card reader, I plugged the adapter with micro card into & attached it to the USB 2.0 port - and the files appeared!! I was able to read them directly, however a lot of them would only be read partially (jpegs).
So the culprit all along was the USB adapter!!
I still want to test different implementations of exFAT to if there is better performance of reading the jpegs, but I haven’t had time to go down that route. Currently I am using the exfat-utils 1.1.0-3.1 & fuse-exfat 1.1.0-2.1 from obs://build.opensuse.org/home:lrupp .
When I get around to testing other builds, I’ll report back on what I found.
Thank you all for your assistance in helping me troubleshoot this issue!
Cheers!
On 2015-05-14 05:56, ejboshinski wrote:
> So when I happened to find another USB card reader, I plugged the
> adapter with micro card into & attached it to the USB 2.0 port - and the
> files appeared!! I was able to read them directly, however a lot of them
> would only be read partially (jpegs).
>
> So the culprit all along was the USB adapter!!
Curious! :-o
> When I get around to testing other builds, I’ll report back on what I
> found.
>
> Thank you all for your assistance in helping me troubleshoot this issue!
Welcome! 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Worked for me, Thank you very much