Just a heads up on the following
ID-2: /dev/sdb type: USB model: General USB Flash Disk size: 28.91 GiB type: SSD serial: <filter> rev: 1100 scheme: MBR
That is a standard representation of a normal FAT32 USB stick, nothing unusual or lacking.
I'll show you with just the relevant portion of the same inxi command in my environment.
Drives:
Local Storage: total: 5.75 TiB used: 1.30 TiB (22.6%)
ID-1: /dev/sda vendor: Seagate model: ST2000LM007-1R8174 size: 1.82 TiB
speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: SDM2 temp: 38 C
scheme: GPT
ID-2: /dev/sdb vendor: Micron model: 1100 SATA 256GB size: 238.47 GiB
speed: 6.0 Gb/s serial: <filter> rev: L022 temp: 42 C scheme: GPT
ID-3: /dev/sdc type: USB vendor: Western Digital model: WD My Book 25EE
size: 3.64 TiB serial: <filter> rev: 4004 scheme: GPT
ID-4: /dev/sdd type: USB vendor: Kingston model: DataTraveler 3.0
size: 57.73 GiB serial: <filter> rev: 0000 scheme:
MBR
The last part I have bolded and italicised is simply my 64 GB Kingston Data Traveller I use with Ventoy on it to house a dozen or so Linux Distro isos.
There is seldom a reason to format a USB stick to, say, EXT4 and GPT (unless, for the GPT you want to be able to create up to 128 partitions, rather extreme and time-consuming).
So for the inxi output on drives for Linux, under UEFI, you can often see
EXT 4 ==> GPT and
FAT32 ===> MBR
@MrBob22 - could you please give us the output from the following command
That -l is with an l for list, not a numeric 1
I'll be back on my tomorrow with more.
Cheers
Wiz