USB 64GB stick works on Linux TW laptop but not on Vero 4K, could it be a allocation unit issue?

Before I start posting details here is there a app I can use to look into the details of an USB memory stick?

My reason is the 64GB stick formatted as exfat does not work but a 256GB stick formatted as exfat does work. Both are Samsung devices but I cannot remember if and when I reformatted them. I wonder if I might have set an allocation unit which is indigestible format for Vero 4K. What is best tool to look into details of USB?

Budge.

I doubt this has anything to do with the fact that this mass-storage is connected through USB. Unless proven otherwise, I would check about partitioning and the file system(s) on the device or it’s partitions.

As usual (with the device connected and as root):

fdisk -l
lsblk -f

And to speculate on the next step:
When you mean with “is the 64GB stick formatted as exfat” (we hope to see what it is using the commands above), that you have created an exfat file system on the device or on a partition of 64GB size, are you sure an exfat file ssytem supports such a size. Because it is non-Linux, I do not know anything about it, but some fs types do have their limitations.

Probably I am also confused because you compare “TW laptop” (very vague, but a type of computer with a well known operating system) with “Vero 4k” (probably somelhinng computer like with unspecified operating system?).

Also in fact you only say “it does not work” without any indication of what happens (firework out of the USB connector, system down, …?).

Hi Henk,
Thanks for the suggestions. Here is what I have from the 64GB stick which works fine on my Lenovo T530 but not on my Vero4K which uses and Arm processor and has a Debian like OS.

alastair@localhost:~> sudo fdisk -l 
[sudo] password for root:  
**Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors**
Disk model: CT1000MX500SSD1  
Units: sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 4096 bytes 
I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
Disklabel type: gpt 
Disk identifier: 235BA8AC-05E4-4233-AA37-D1DAEFDBED28 

**Device    ****    Start****       End****   Sectors****  Size****Type**
/dev/sda1       2048    3074046    3071999   1.5G EFI System 
/dev/sda2    3074048  514862302  511788255   244G Microsoft basic data 
/dev/sda3  514863104  516216831    1353728   661M Windows recovery environment 
/dev/sda4  516218880  517961727    1742848   851M Microsoft basic data 
/dev/sda5  517961728  546633727   28672000  13.7G Microsoft basic data 
/dev/sda6  546633728  630519807   83886080    40G Linux filesystem 
/dev/sda7  630519808  634714111    4194304     2G Linux swap 
/dev/sda8  634714112 1953525134 1318811023 628.9G Linux filesystem 


**Disk /dev/loop0: 30.27 MiB, 31735808 bytes, 61984 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 


**Disk /dev/loop2: 95.73 MiB, 100376576 bytes, 196048 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 


**Disk /dev/loop3: 55.36 MiB, 58052608 bytes, 113384 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 


**Disk /dev/loop4: 55.32 MiB, 58007552 bytes, 113296 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 


**Disk /dev/loop1: 30.94 MiB, 32440320 bytes, 63360 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 


**Disk /dev/sdb: 59.75 GiB, 64160400896 bytes, 125313283 sectors**
Disk model: Flash Drive      
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: 0x0b2a01bb 

**Device    ****Boot****Start****      End****  Sectors**** Size****Id****Type**
/dev/sdb1        2048 125313023 125310976 59.8G  7 HPFS/NTFS/exFAT 
alastair@localhost:~> 


alastair@localhost:~> lsblk -f 
NAME FSTYPE FSVER LABEL   UUID                                 FSAVAIL FSUSE% MOUNTPOINTS 
loop0 
     squash 4.0                                                      0   100% /snap/snapd/9279 
loop1 
     squash 4.0                                                      0   100% /snap/snapd/9721 
loop2 
     squash 4.0                                                      0   100% /snap/get-iplayer/250 
loop3 
     squash 4.0                                                      0   100% /snap/core18/1932 
loop4 
     squash 4.0                                                      0   100% /snap/core18/1885 
sda                                                                            
├─sda1 
│    vfat   FAT32         0F08-0688                               1.4G     2% /boot/efi 
├─sda2 
│    ntfs         Windows7_OS 
│                         B8168B4B168B0A18                                     
├─sda3 
│    ntfs                 94B0612AB06113D0                                     
├─sda4 
│    ntfs                 76BAC38DBAC34877                                     
├─sda5 
│    ntfs         Lenovo_Recovery 
│                         D42C841B2C83F6B0                                     
├─sda6 
│    btrfs                e603e5d0-7019-4f80-a3db-0042732f33f4   27.5G    31% /var 
│                                                                             /usr/local 
│                                                                             /tmp 
│                                                                             /srv 
│                                                                             /root 
│                                                                             /opt 
│                                                                             /boot/grub2/x86_64-efi 
│                                                                             /boot/grub2/i386-pc 
│                                                                             / 
├─sda7 
│    swap   1             c8c36e04-835d-4151-8ac2-aa8aea7e4fb1                [SWAP] 
└─sda8 
     ext4   1.0           adaaa3ba-2329-4210-85e6-3246af0b6fc5  525.3G    10% /home 
sdb                                                                            
└─sdb1 
     exfat  1.0   16_USB_64G 
                          902C-190C                              59.1G     1% /run/media/alastair/16
_USB_64G 
sr0                    

For comparison, here are the same details from the 256GB stick:-

alastair@localhost:~> sudo fdisk -l 
[sudo] password for root:  
**Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors**
Disk model: CT1000MX500SSD1  
Units: sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 4096 bytes 
I/O size (minimum/optimal): 4096 bytes / 4096 bytes 
Disklabel type: gpt 
Disk identifier: 235BA8AC-05E4-4233-AA37-D1DAEFDBED28 

**Device    ****    Start****       End****   Sectors****  Size****Type**
/dev/sda1       2048    3074046    3071999   1.5G EFI System 
/dev/sda2    3074048  514862302  511788255   244G Microsoft basic data 
/dev/sda3  514863104  516216831    1353728   661M Windows recovery environment 
/dev/sda4  516218880  517961727    1742848   851M Microsoft basic data 
/dev/sda5  517961728  546633727   28672000  13.7G Microsoft basic data 
/dev/sda6  546633728  630519807   83886080    40G Linux filesystem 
/dev/sda7  630519808  634714111    4194304     2G Linux swap 
/dev/sda8  634714112 1953525134 1318811023 628.9G Linux filesystem 


**Disk /dev/loop0: 30.27 MiB, 31735808 bytes, 61984 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 


**Disk /dev/loop2: 95.73 MiB, 100376576 bytes, 196048 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 


**Disk /dev/loop3: 55.36 MiB, 58052608 bytes, 113384 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 


**Disk /dev/loop4: 55.32 MiB, 58007552 bytes, 113296 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 


**Disk /dev/loop1: 30.94 MiB, 32440320 bytes, 63360 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 


**Disk /dev/sdb: 239.02 GiB, 256641603584 bytes, 501253132 sectors**
Disk model: Flash Drive      
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/sdb1         256 501253099 501252844  239G  7 HPFS/NTFS/exFAT 
alastair@localhost:~> 


alastair@localhost:~> lsblk -f      
NAME FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS 
loop0 
     squash 4.0                                                     0   100% /snap/snapd/9279 
loop1 
     squash 4.0                                                     0   100% /snap/snapd/9721 
loop2 
     squash 4.0                                                     0   100% /snap/get-iplayer/250 
loop3 
     squash 4.0                                                     0   100% /snap/core18/1932 
loop4 
     squash 4.0                                                     0   100% /snap/core18/1885 
sda                                                                           
├─sda1 
│    vfat   FAT32        0F08-0688                               1.4G     2% /boot/efi 
├─sda2 
│    ntfs         Windows7_OS 
│                        B8168B4B168B0A18                                     
├─sda3 
│    ntfs                94B0612AB06113D0                                     
├─sda4 
│    ntfs                76BAC38DBAC34877                                     
├─sda5 
│    ntfs         Lenovo_Recovery 
│                        D42C841B2C83F6B0                                     
├─sda6 
│    btrfs               e603e5d0-7019-4f80-a3db-0042732f33f4   27.5G    31% /var 
│                                                                            /usr/local 
│                                                                            /tmp 
│                                                                            /srv 
│                                                                            /root 
│                                                                            /opt 
│                                                                            /boot/grub2/x86_64-efi 
│                                                                            /boot/grub2/i386-pc 
│                                                                            / 
├─sda7 
│    swap   1            c8c36e04-835d-4151-8ac2-aa8aea7e4fb1                [SWAP] 
└─sda8 
     ext4   1.0          adaaa3ba-2329-4210-85e6-3246af0b6fc5  525.3G    10% /home 
sdb                                                                           
└─sdb1 
     exfat  1.0   13_USB_256G 
                         64A5-F009                               116G    51% /run/media/alastair/13_
USB_256G 
sr0                                                                           
alastair@localhost:~> 


The Vero 4K device is working with HDMI display and no keyboard but a wand so for now all I can see on the screen is the absence of any files.
I shall remove the device so I can connect with full keyboard & monitor but had hoped to see some difference. I may have missed something but do you see any obvious issues from the comparisons above? How may I see the allocation unit size?

Budge.

I do not see strange things in your output. Both devices are partitioned into one partition (sounds strange, I always wonder why people partition when they do not need parts???). Both with an exfat file system. In the meantime I checked Wikipedia, but it looks as if exfat can grow far beyond what you have. Both sector size, etc. all 512 bytes.

I understand that the problem is on a Linux system, but not on an openSUSE one. And that you can not even check if it is mounted at all? And who is assumed to mount it? When there is no Desktop Environment to do that for an end-user, the mount must be done otherwise (normally that is by a mount command).

Hi Henk,
Sorry if I was not clear but the USB devices are auto mounted and both USB sticks mount and may be seen on the system but the problem one is showing empty, ie no files whereas the working stick is full.

In case you ask, the problem stick is now empty as I have moved the files to a safe place in anticipation of having to re-format.

I shall just check again by coping good files from one stick to the other just to be sure it is not the files which are the problem. I create partitions out of habit and believe it is good practice. Tell me if I am wrong.
Thanks again,
Budge

I have only a few remarks.

  • “Automount” is not a good description. I know of at least three different mechanisms that are called colloquially “automounting”, mostly by people that are unaware of the other “automounting ways”. (And remember that many people use “auto” when they do not understand how something happens. a sort of replacement for “magically”.)
  • Saying that a file system (the stick
    is NOT mounted, the file system is, again colloquially impreciseness) is mounted is often not enough for people here. One does not believe story telling, but only computer facts shown. - Yes, partitioning is a habit. And it seems not many people ever ask themselves why they partition when they do not need several parts. The problem is not that it does not “work”, but that the knowledge level of people stays at the same level because of lack of curiosity.

Some appliances have unpartitioned drives. This comes with a lack of flexibility. Overhead of unneeded partitioning is very small.


i3-4130:~ # fdisk -l /dev/sdb 
Disk /dev/sdb: 10.08 MiB, 10570752 bytes, 20646 sectors 
Disk model: FR735XT Flash    
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 
i3-4130:~ # 

i3-4130:~ # journalctl -b 0 _KERNEL_SUBSYSTEM=scsi 
-- Journal begins at Tue 2021-11-30 07:39:48 CET, ends at Sat 2021-12-11 08:38:46 CET. -- 
...
Dec 11 08:21:21 i3-4130 kernel: scsi 4:0:0:0: Direct-Access     ATA      CT250MX500SSD1   023  PQ: 0 ANSI: 5
...
Dec 11 08:21:24 i3-4130 kernel: scsi 6:0:0:0: Direct-Access     Brother  MFC-255CW        1.00 PQ: 0 ANSI: 2
...
# connect
Dec 11 08:21:24 i3-4130 kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Dec 11 08:21:24 i3-4130 kernel: sd 6:0:0:0: [sdb] Media removed, stopped polling
Dec 11 08:21:24 i3-4130 kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Dec 11 08:36:55 i3-4130 kernel: scsi host6: usb-storage 2-10:1.0 
Dec 11 08:36:56 i3-4130 kernel: scsi 6:0:0:0: Direct-Access     Garmin   FR735XT Flash    1.00 PQ: 0 ANSI: 5
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: [sdb] 20646 512-byte logical blocks: (10.6 MB/10.1 MiB)
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: [sdb] Write Protect is off
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 11 08:36:56 i3-4130 kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
# disconnct
Dec 11 08:38:46 i3-4130 kernel: sd 6:0:0:0: [sdb] Synchronizing SCSI cache
Dec 11 08:38:46 i3-4130 kernel: sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK 
i3-4130:~ #