[Bug 277663] Component: /sbin/mount (No selection for sbin); mount -t msdosfs /dev/wrongusbdeviceID error output incorrect

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 13 Mar 2024 09:48:50 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277663

            Bug ID: 277663
           Summary: Component: /sbin/mount (No selection for sbin); mount
                    -t msdosfs /dev/wrongusbdeviceID error output
                    incorrect
           Product: Base System
           Version: 14.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: bkastning@protonmail.com

Component: /sbin/mount (No selection for sbin); mount -t msdosfs
/dev/wrongusbdeviceID error output incorrect

This is my first bug report. I'm sure I will make many mistakes submitting
these today and in the future. 

I have a fresh Installation of FreeBSD-14.0-RELEASE-amd64 and a Fresh formatted
Silicon Power 256GB USB FAT32 3.0/3.1 Flash Drive.

This is what I ran into and why I believe it's important to fix at a C base
level as it affects everyone in many situations; not restricted to only USB
Flash Drives but any device that is mountable with a FAT32 file system.

root@ShadowDragonR1:/mnt # mkdir NixDragonR1_256GB_SP
root@ShadowDragonR1:/mnt # mount -t msdosfs /dev/pa1 /mnt/NixDragonR1_256GB_SP
mount_msdosfs: /dev/pa1: Invalid fstype: Invalid argument

The device name was incorrect. While this may be "assumed" & acceptable output
by Professional C Programmers who are FreeBSD Committers it's not and i'll show
you why.

Next I performed the following:

root@ShadowDragonR1:/mnt # ls /dev/da*
/dev/da1 /dev/da1p1 (Only showing the two that was truly my correct USB Drive)

root@ShadowDragonR1:/mnt # mount -t msdosfs /dev/da1 /mnt/NixDragonR1_256GB_SP
mount_msdosfs: /dev/da1: Invalid argument

root@ShadowDragonR1:/mnt # mount -t msdosfs /dev/da1 /media (Reading "Absolute
FreeBSD" 2nd Edition "The Complete Guide to FreeBSD" by Michael W. Lucas which
I purchased while Studying American Constitutional Law at an Elementary College
several years back; Reading on page 230 under "Using Removable Media";
suggesting to mount with theFAT32 USB device to /media (which didn't suit my
intentions; however I gave it a go anyways and this is what happened). 

Example from Page 230: # mount -t msdosfs /dev/da0 /media 

This is what I ended up doing:

root@ShadowDragonR1:/mnt # mount -t msdosfs /dev/da1 /media
mount_msdosfs: /dev/da1: Invalid argument

So being a Linux x64 - Debian-12.5.0-amd64 User as My Primary Operating System
and preferred Desktop at this time in existence.

I ran the following to see the partition layout (Not familiar with fdisk in
FreeBSD as of yet). However it's relevant to my troubleshooting process.

root@ShadowDragonR1:/mnt # fdisk -l
fdisk: illegal option -- l
usage: fdisk [-BIaipqstu] [-b bootcode] [-1234] [disk]
       fdisk -f configfile [-itv] [disk]

So I went ahead and ran the next best thing:

root@ShadowDragonR1:/mnt # ls /dev/da*
/dev/da1 /dev/da1p1

root@ShadowDragonR1:/mnt # mount -t msdosfs /dev/da1p1
/mnt/NixDragonR1_256GB_SP/
/
root@ShadowDragonR1:/mnt #


My Conclusion:

When an invalid device is specified. The hardcoded C Base FreeBSD Operating
System for Component: /sbin/mount (Which isn't included in the Component list
for Selecting which Component on this Bug Fix Portal; I chose bin since I
couldn't find the appropriate "sbin" for FreeBSD Base Operating System.

This is the output Error Message that I would choose if I were on The Counsel
of FreeBSD C Base System Operating System Committers.

Current: mount_msdosfs: /dev/InvalidDeviceIDName (For Any Type of FAT32 Media)
= "Invalid argument"

Proposed: mount_msdosfs: /dev/InvalidDeviceIDName (For Any Type of FAT32 Media)
= "Invalid Device Specified"

Thank you for this Great Operating System.

Best Regards,

Brandon Kastning

106 East Burke Ave
Apartment Home #19
Arlington, WA 98223

American Constitutionally Bound, Guaranteed & Protected Disabled Housing

Email: bkastning@protonmail.com

Twitter/X: @BRKastning

Date: 03/13/2024
Time: 02:48AM

-- 
You are receiving this mail because:
You are the assignee for the bug.