ZimaOS Says Disk Format Unsupported: Fix the New SSD

Bottom Line: “Unsupported” Can Mean the Disk Has No Valid Filesystem Yet, Not That the SSD Is Incompatible

The July 2026 case looked confusing because the user had wiped partitions and tried several formats, yet ZimaOS still showed Format: Unsupported. The solved detail was simple: the disk needed a real partition and filesystem. The correct sequence is identify the device → create a GPT table → create a partition → format the partition as a supported filesystem → reboot/rescan → enable it in Storage.

First Identify the Correct Disk

lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINTS
sudo lshw -C disk

Do not assume the new SSD is /dev/sdb. Verify model and capacity before running any destructive command. A typo at this stage can erase the wrong drive.

Use wipefs Only When You Intend to Remove Old Signatures

sudo wipefs -n /dev/sdX

-n inspects signatures without changing them. If the drive is definitely the new/empty target and old signatures are confusing ZimaOS, then wipefs -a can remove them. The wipefs signatures explains the difference.

Create a GPT Partition Table and One Partition

sudo parted /dev/sdX
mklabel gpt
mkpart primary 0% 100%
quit

Then verify:

lsblk /dev/sdX

You should now have a partition such as /dev/sdX1. Format the partition, not the entire disk device, unless you deliberately know why you are using a filesystem directly on a whole block device.

Format the Partition as EXT4

sudo mkfs.ext4 /dev/sdX1

The source thread contained a later shorthand typo around mkfs -t ext; do not copy that. EXT4 is the supported filesystem name. Current ZimaOS format material lists EXT4, NTFS, exFAT and BTRFS as readable/writable, while XFS remains unsupported in that compatibility table.

The ZimaOS disk formats provides the current support matrix.

Why BTRFS Can Be Supported Yet Still Fail to Add

“Filesystem supported” and “disk accepted into the Storage workflow” are different checks. Stale signatures, no partition, an incomplete format, a mounted device or old RAID metadata can block management even when BTRFS itself is supported. That is why the clean partition/filesystem sequence matters.

Reboot or Rescan, Then Add the Disk Through Storage

After creating the filesystem, restart ZimaOS or trigger a rescan if available, then open Settings → Storage and use the normal enable/add flow. Avoid continuing with manual mounts if your goal is a ZimaOS-managed storage space.

The ZimaCube 2 storage provides a current multi-drive reference.

Do Not Run Destructive Commands on a Disk With Data

wipefs -a, mklabel gpt and mkfs.ext4 can make existing data inaccessible. If the SSD contains files you might need, stop and make a verified copy before proceeding. The ZimaOS backup covers that safety boundary.

If ZimaOS Still Says Unsupported

Collect lsblk -f, blkid, wipefs -n, disk model and ZimaOS version. If EXT4 on a normal GPT partition is visible to Linux but still rejected by current Storage, you now have evidence of a ZimaOS management problem rather than an incomplete disk format.

The util-linux blkid filesystem probe helps confirm that distinction.

Verify the Partition Table and Filesystem After Reboot

After ZimaOS restarts, run lsblk -f again and confirm the partition still shows the expected UUID and EXT4 filesystem. If the partition disappears or the filesystem type returns blank, the problem is below the ZimaOS UI and should be investigated at the device/controller level before repeating destructive formatting steps.

FAQ

Why does ZimaOS say Format Unsupported on a blank SSD?

A wiped disk may have no partition or filesystem yet. Create a GPT partition and format the partition with a supported filesystem such as EXT4.

Is BTRFS supported by ZimaOS?

Current compatibility material lists BTRFS as readable/writable, but stale metadata or an incomplete storage layout can still prevent a disk from being managed.

Is XFS supported?

The current ZimaOS disk-format compatibility table still lists XFS as unsupported.

Should I run mkfs on /dev/sdX or /dev/sdX1?

For a normal GPT layout, create a partition and format /dev/sdX1.

Will wipefs erase my data?

Removing signatures can make filesystems or RAID metadata inaccessible. Use inspection mode first and back up anything important.