Closed dseeley closed 2 years ago
Seems like the special volume label file is actually required in some cases (and you just discovered one of them :tada:). I was under the impression that the special file is optional - at least with FAT16/32 I cannot remember that fsck ever complained about it. file
and fatcat
seem to work just fine without it, but lsblk/Linux is a bit more picky. :slightly_smiling_face:
As a workaround you can add a new FATDirectoryEntry to the root directory with the FATDirectoryEntry.ATTR_VOLUME_ID
set as an attribute. I'll need to investigate under which circumstances the special file is actually required first.
Attempting to create a volume using the new mkfs() function:
It appears that on mounting, the volume label is not set:
I get the same results with FAT16/32
A similarly created file using mkfs yields a label: