You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
USB Stick Formatter 1.6.6 creates invalid exFAT filesystems on multiple drives #153
After formatting with mintstick, this read-only check:
sudo fsck.exfat -n /dev/sdb1
reported:
Bad fs_name in boot sector, which does not describe a valid exfat filesystem
In both cases, lsblk showed the partition but did not detect a filesystem type.
Expected result
The formatter should create a valid exFAT filesystem, verify that formatting succeeded, and only then report completion.
Working command-line workaround
Reformatting each same partition directly with exfatprogs worked:
sudo mkfs.exfat -n LABEL /dev/sdb1
Afterward, Linux detected exFAT 1.0 and fsck.exfat -n reported the filesystem as clean.
Suspected cause
This is an inference from the observed behavior and installed mintstick source.
/usr/lib/mintstick/raw_format.py recreates the partition table and immediately runs wipefs and mkfs.exfat on the new partition path. Its execute() function calls commands with subprocess.call() but does not inspect or propagate nonzero return codes. There is also no visible partprobe, udevadm settle, or equivalent wait after recreating the partition table.
This may allow formatting against stale partition geometry, or allow a failed command to be ignored while the UI still reports success.
Please consider:
checking and propagating every subprocess return code;
waiting for the kernel and udev to recognize the new partition geometry;
verifying the result with blkid or fsck.exfat -n before reporting success.
Activity