How to Rename an exFAT Volume on the Comet Pro (and Make It Stick)
If you’re using a Comet Pro and want to rename a storage volume (like an exFAT partition), the good
news is: It does work. The bad news is: the change doesn’t survive a reboot — unless you use a small
workaround.
Step 1: Find the Volume
First, SSH or CLI into the Comet Pro and list all storage devices:
blkid
You’ll see output similar to:
/dev/mmcblk0p10: LABEL=”GLKVM” UUID=”0026-D81A” TYPE=”exfat”
This tells you: – The device path: /dev/mmcblk0p10 – The current label: GLKVM – The filesystem: exfat
Step 2: Rename the Volume
To change the label, use:
exfatlabel /dev/mmcblk0p10 NEWLABEL
Verify the change:
blkid /dev/mmcblk0p10
At this point, the label is changed on the device.
Step 3: Refresh File Sharing
If the volume is shared to a remote client (KVM, VM, network share, etc.): 1. Stop file sharing 2. Start
file sharing again
This forces the remote system to re-detect the new volume label.
Why the Change Doesn’t Survive a Reboot
The Comet Pro uses an OverlayFS system. That means: – The base system is read-only – Changes are
written to a temporary overlay layer – On reboot, the system resets to its original template
So while exfatlabel does change the volume label, the system reverts it on every reboot.
The Safe Fix: Auto-Rename on Boot
Instead of modifying the system image (which risks stability), the simplest solution is to run the rename
command automatically at startup.
Create a Startup Script
nano /etc/init.d/S99label-fix.sh
Paste this inside:
#!/bin/sh exfatlabel /dev/mmcblk0p10 NEWLABEL
Then make it executable:
chmod +x /etc/init.d/S99label-fix.sh
Now, every time the Comet Pro boots, it will automatically rename the drive to your preferred label.
Important Notes
– This does not modify the core OS – It does not affect system stability – It only re-applies the label on
boot – Firmware updates may remove the script, so you may need to re-add it after updates
Final Thoughts
This method keeps the system safe, stable, and predictable while still giving you control over your
storage labels. No risky firmware changes. No filesystem hacks. Just a simple, clean startup script. If
you’re working with embedded Linux devices like the Comet Pro, this is the smart way to handle
persistent customization.