So Bullseye can't use exfat?

If none of the more specific forums is the right place to ask

So Bullseye can't use exfat?

Postby ab1jx » 2021-02-21 23:21

I wouldn't choose it, my camera formatted this 64GB SD card with it. FAT32 is only used for 32 GB and smaller. My Raspberry Pis running Buster have no problem with it, this Pinebook Pro had no problem with it running Stretch. I have exfat-fuse and now exfat-utils installed. Doesn't work with exfatprogs either.

I get "unknown file system 'exfat'" when as far as I can see it should work. I seem to have fuse, I see fuse3, gvfs-fuse, libfuse2, libfuse3. On a quick check by ssh to a Buster Raspberry Pi I see no mention of fuse3, only fuse2. So I installed fuse2 under Bullseye, still doesn't work. I have both libfuse2 and libfuse3.

Code: Select all
ii  exfat-fuse                            1.3.0-2                         arm64        read and write exFAT driver for FUSE
ii  exfat-utils                           1.3.0-2                         arm64        utilities to create, check, label and dump exFAT filesystem

Code: Select all
ii  exfat-fuse                            1.3.0-2                         arm64        read and write exFAT driver for FUSE
ii  fuse2fs                               1.46.1-1                        arm64        ext2 / ext3 / ext4 file system driver for FUSE
ii  fuse3                                 3.10.2-1                        arm64        Filesystem in Userspace (3.x version)
ii  gvfs-fuse                             1.46.2-1                        arm64        userspace virtual filesystem - fuse server
ii  libfuse2:arm64                        2.9.9-3                         arm64        Filesystem in Userspace (library)
ii  libfuse3-3:arm64                      3.10.2-1                        arm64        Filesystem in Userspace (library) (3.x version)


dmesg | grep fuse says:
Code: Select all
[    1.260664] fuse: init (API version 7.31)
[    6.451723] systemd[1]: Starting Load Kernel Module fuse...
[    6.520286] systemd[1]: modprobe@fuse.service: Succeeded.
[    6.521131] systemd[1]: Finished Load Kernel Module fuse.
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby reinob » 2021-02-22 13:15

Where/how do you get
I get "unknown file system 'exfat'"

Could you show which command you're using (mount ), and the exact output?
Something like:
Code: Select all
mount.exfat-fuse /dev/sdb1 /mnt/
reinob
 
Posts: 910
Joined: 2014-06-30 11:42

Re: So Bullseye can't use exfat?

Postby Bloom » 2021-02-22 16:32

Install the proper utilities first:
Code: Select all
sudo apt install exfat-fuse exfat-utils
User avatar
Bloom
 
Posts: 331
Joined: 2017-11-11 12:23

Re: So Bullseye can't use exfat?

Postby reinob » 2021-02-22 19:18

Bloom wrote:Install the proper utilities first:
Code: Select all
sudo apt install exfat-fuse exfat-utils


ab1jx wrote: I have exfat-fuse and now exfat-utils installed.


It must be something else..
reinob
 
Posts: 910
Joined: 2014-06-30 11:42

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-22 21:11

it's the mount.exfat-fuse /dev/sdb1 /mnt/ where just mount used to work before and it would figure out the type. I've only had to use mount -t for ufs.

But something's still weird which I haven't explored fully. Either the SD card has suddenly (within the last few hours) gone bad or it's not working right. I moved my real files off onto a Pi normally. Then I tried again here and got weird stuff so I let the camera reformat the sd card.

fsck -fy /dev/sda1 doesn't work, it wants fsck.exfat and the "-f" is now invalid. It just checked a 64 GB card in about 1/2 second and told me there were no errors. Which is probably correct but how does it know that fast?
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby Bloom » 2021-02-23 06:33

fsck only checks it the file system root structure is valid. It does not do a surface check for bad blocks. There's a program called badblocks you can use for that.
-f and -y are both invalid for fsck.

Fsck.exfat should have been installed with the exfat-utils package. For fsck to find it, you have to execute it as root (or via sudo). You can call fsck.exfat directly, though.
User avatar
Bloom
 
Posts: 331
Joined: 2017-11-11 12:23

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-23 09:35

What seems to be suddenly gone is whatever turned mount into mount.exfat (/sbin/mount.exfat-fuse) and fsck into fsck.exfat (/sbin/fsck.exfat). I don't know whether those were aliases or symlinks or whether mount and exfat looked at the file system type and decided to call the exfat versions. Yes, I'm doing this all as root.

My eMMC on this Pinebook Pro is the Stretch it came with, Bullseye is in the internal sd card slot, which I'm booted from. There are differences here which partly explain the problem. mount itself is in /bin so it doesn't show here.

Code: Select all
Stretch
cd /sbin
ls -la mount*
lrwxrwxrwx 1 root root    16 Jan 20  2017 mount.exfat -> mount.exfat-fuse
-rwxr-xr-x 1 root root 38564 Jan 20  2017 mount.exfat-fuse
-rwxr-xr-x 1 root root  9712 Aug 21  2018 mount.fuse

Bullseye
cd /sbin
ls -la mount*
-rwxr-xr-x 1 root root 51544 Jun 29  2020 mount.exfat-fuse
lrwxrwxrwx 1 root root    11 Feb  8 15:21 mount.fuse -> mount.fuse3
-rwxr-xr-x 1 root root 14488 Feb  8 15:21 mount.fuse3
lrwxrwxrwx 1 root root    15 Mar 21  2019 mount.lowntfs-3g -> /bin/lowntfs-3g
lrwxrwxrwx 1 root root    13 Mar 21  2019 mount.ntfs -> mount.ntfs-3g
lrwxrwxrwx 1 root root    12 Mar 21  2019 mount.ntfs-3g -> /bin/ntfs-3g

Stretch
cd /sbin
ls -la fsck*
-rwxr-xr-x 1 root root 30780 Mar  7  2018 fsck
-rwxr-xr-x 1 root root 26524 Mar  7  2018 fsck.cramfs
lrwxrwxrwx 1 root root     6 Jul 25  2020 fsck.ext2 -> e2fsck
lrwxrwxrwx 1 root root     6 Jul 25  2020 fsck.ext3 -> e2fsck
lrwxrwxrwx 1 root root     6 Jul 25  2020 fsck.ext4 -> e2fsck
-rwxr-xr-x 1 root root 42508 Jan 24  2017 fsck.fat
-rwxr-xr-x 1 root root 59416 Mar  7  2018 fsck.minix
lrwxrwxrwx 1 root root     8 Jan 24  2017 fsck.msdos -> fsck.fat
lrwxrwxrwx 1 root root     8 Jan 24  2017 fsck.vfat -> fsck.fat

Bullseye
cd /sbin
ls -la fsck*
-rwxr-xr-x 1 root root  47304 Feb  7 09:38 fsck
-rwxr-xr-x 1 root root  39112 Feb  7 09:38 fsck.cramfs
lrwxrwxrwx 1 root root      9 Jul  4  2020 fsck.exfat -> exfatfsck
lrwxrwxrwx 1 root root      6 Feb  9 17:36 fsck.ext2 -> e2fsck
lrwxrwxrwx 1 root root      6 Feb  9 17:36 fsck.ext3 -> e2fsck
lrwxrwxrwx 1 root root      6 Feb  9 17:36 fsck.ext4 -> e2fsck
-rwxr-xr-x 1 root root  80040 Feb  7 20:13 fsck.fat
-rwxr-xr-x 1 root root 125120 Feb  7 09:38 fsck.minix
lrwxrwxrwx 1 root root      8 Feb  7 20:13 fsck.msdos -> fsck.fat
lrwxrwxrwx 1 root root      8 Feb  7 20:13 fsck.vfat -> fsck.fat
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-24 13:43

I do fsck -fy all the time. From an ssh session to a Raspberry Pi (Raspbian)
Code: Select all
root@upstairs:/home/pi# fsck -fy /dev/sda3
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes


This machine with Bullseye has util-linux 2.36.1-7. Most of my SD cards are ext4 but I run several Raspberry Pis and do fsck -fy after power failures or if an SD card is starting to go bad. Strange crashes can sometimes be fixed by doing it.

From the fsck man page:
Code: Select all
In actuality, fsck is simply a front-end  for  the  various  filesystem
checkers  (fsck.fstype) available under Linux.  The filesystem-specific
checker is searched for in the PATH environment variable. If  the  PATH
is undefined then fallback to "/sbin".

So by that fsck should automatically call fsck.exfat, which it does under Stretch and Buster, not Bullseye. There are a few rough edges still. Is it set up in an rc or conf file for fsck?
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby p.H » 2021-02-27 08:30

A change in bullseye is the current kernel (5.10) includes exFAT support, not requiring exfat-fuse anymore. So the mount.exfat link to mount.exfat-fuse has been removed from exfat-fuse package. However this should not affect fsck, as exfat-utils and exfatprogs packages still provide fsck.exfat.
p.H
 
Posts: 1739
Joined: 2017-09-17 07:12

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-27 18:37

OK, this is Linux pbp 5.7.0-2-pinebookpro-arm64 #1 SMP PREEMPT Thu Jan 14 03:12:22 UTC 2021 aarch64 GNU/Linux but it's a temporary situation installed with debootstrap on an SD card. I have a 1 TB nvme drive in here I want to migrate to. As I understand it that will require a serial console cable which I've temporarily misplaced. I probably won't fiddle with changing kernels until then, but I'm surprised apt-get update and upgrade didn't just do it. Maybe it's a notch too experimental so far.

exfat-utils and exfatprogs seem to be mutually exclusive, if I install one the other gets removed. Which should I be using?
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby Head_on_a_Stick » 2021-02-27 18:50

ab1jx wrote:this is Linux pbp 5.7.0-2-pinebookpro-arm64 #1 SMP PREEMPT Thu Jan 14 03:12:22 UTC 2021 aarch64 GNU/Linux but it's a temporary situation installed with debootstrap on an SD card.

How exactly did you install that system and where did you get that kernel from?

An arm64 system should use the linux-image-arm64 kernel metapackage, which is on v5.10.13-1 at the moment.

ab1jx wrote:exfat-utils and exfatprogs seem to be mutually exclusive, if I install one the other gets removed. Which should I be using?

The exfatprogs package should be preferred because it uses the native kernel driver but that isn't available with your current kernel version.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 13450
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-27 19:32

I'm pretty sure it was
debootstrap --arch=arm64 bullseye /deboot
because I still have a little script (for reproducibility) dated January 26
Then there was stage 2:
debootstrap --second-stage

So I didn't specify a kernel but I got one, I don't remember adding one manually. Maybe it copied from the host?
Last edited by ab1jx on 2021-02-27 19:57, edited 1 time in total.
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby Head_on_a_Stick » 2021-02-27 19:42

The debootstrap command doesn't install a kernel.

Can we see
Code: Select all
aptitude search '?narrow(?installed, linux-image)'
aptitude search '?narrow(?installed, !?origin(Debian))!?obsolete'
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 13450
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: So Bullseye can't use exfat?

Postby ab1jx » 2021-02-27 20:08

I see:
Code: Select all
i A linux-image-5.7.0-2-pinebookpro-arm64 - Linux kernel, version 5.7.0-2-pinebookpro-arm64
i  linux-image-pinebookpro-arm64 - Linux kernel (meta-package)

and
Code: Select all
i  cubicsdr - Software Defined Radio receiver
i  ffmpeg - Tools for transcoding, streaming and playing of multimedia files
i A gstreamer1.0-plugins-bad - GStreamer plugins from the "bad" set
i  iproute2 - networking and traffic control tools
i A libavcodec58 - FFmpeg library with de/encoders for audio/video codecs - runtime files
i A libavdevice58 - FFmpeg library for handling input and output devices - runtime files
i A libavfilter7 - FFmpeg library containing media filters - runtime files
i A libavformat58 - FFmpeg library with (de)muxers for multimedia containers - runtime files
i A libavresample4 - FFmpeg compatibility library for resampling - runtime files
i A libavutil56 - FFmpeg library with functions for simplifying programming - runtime files
i  libbsd0 - utility functions from BSD systems - shared library
i A libc-dev-bin - GNU C Library: Development binaries
i  libc6 - GNU C Library: Shared libraries
i A libc6-dbg - GNU C Library: detached debugging symbols
i A libc6-dev - GNU C Library: Development Libraries and Header Files
i A libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
i A libgbm1 - generic buffer management API -- runtime
i A libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
i A libglapi-mesa - free implementation of the GL API -- shared library
i A libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library
i A libgstreamer-plugins-bad1.0-0 - GStreamer libraries from the "bad" set
i A libpostproc55 - FFmpeg library for post processing - runtime files
i A libpython3.9 - Shared Python runtime library (version 3.9)
i A libpython3.9-minimal - Minimal subset of the Python language (version 3.9)
i A libpython3.9-stdlib - Interactive high-level object-oriented language (standard library, version 3.9)
i A libswresample3 - FFmpeg library for audio resampling, rematrixing etc. - runtime files
i A libswscale5 - FFmpeg library for image scaling and various conversions - runtime files
i A python3.9 - Interactive high-level object-oriented language (version 3.9)
i A python3.9-minimal - Minimal subset of the Python language (version 3.9)
i A soapysdr0.7-module-audio - Audio device support for SoapySDR
i A soapysdr0.7-module-lms7 - Lime Microsystems LMS7 device support for SoapySDR


There might not be a mainstream kernel for this, it's only about a year old and not produced in large quantities. The wiki is here: https://wiki.pine64.org/wiki/Pinebook_Pro More about software is here: https://wiki.pine64.org/wiki/Pinebook_P ... ity_Images but when that was written the Debian installer had no support for the video.

Maybe this is the Daniel Thompson version, I've lost track. I used debootstrap on my nvme drive but haven't gotten it to boot yet. The Thompson setup uses a Gentoo kernel I think and debootstrap to get everything else. I didn't like the inflexibility: I didn't want to use GPT and I wanted to install to a certain partition or two and leave the rest of the drive alone. So on the SD card is probably a debootstrap but using the Thompson script. Yes, it has a signature 7 partitions, I wouldn't do that by choice. It's from https://github.com/daniel-thompson/pine ... installer/
Last edited by ab1jx on 2021-02-28 02:07, edited 3 times in total.
ab1jx
 
Posts: 61
Joined: 2016-01-23 21:28
Location: Heath, MA, USA

Re: So Bullseye can't use exfat?

Postby p.H » 2021-02-27 22:06

Head_on_a_Stick wrote:The exfatprogs package should be preferred because it uses the native kernel driver

Can you elaborate ? I fail to see why mkfs or fsck of any sort would use filesystem drivers.
p.H
 
Posts: 1739
Joined: 2017-09-17 07:12

Next

Return to General Questions

Who is online

Users browsing this forum: No registered users and 21 guests

fashionable