Missing RAID storage after reboo

Operating System ZimaOS
1

My Zima setup was working great… until a reboot today. My 10TB RAID1 array (2 x 10TB) is missing from Files. The drives are detected by Linux, but don’t seem to be mounted. I’ve seen similar issues reported, linked to capitalisation of “BTRS” in the Zima database. Checking the storage logs, the issue does seem to be with the RAID file type.

mount raid with fsType failed, trying with unknown fsType

Is there any way to fix this?

Thanks!

=================

2026-01-28T19:35:21.231Z info run raid {“info”: “”, “func”: “service.(*raidStruct).CheckRaidMount.func1”, “file”: “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/raid.go”, “line”: 1053}
2026-01-28T19:35:21.232Z info mount raid {“path”: “/dev/md0”, “mountPath”: “/media/Safe-Storage”, “flags”: 0, “func”: “service.(*raidStruct).MountRaid”, “file”: “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/raid.go”, “line”: 356}
2026-01-28T19:35:21.235Z info mount attempt failed {“path”: “/dev/md0”, “fsType”: “BTRFS”, “error”: “no such device”, “func”: “service.(*raidStruct).tryMountWithType”, “file”: “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/raid.go”, “line”: 383}
2026-01-28T19:35:21.235Z info mount raid with fsType failed, trying with unknown fsType {“path”: “/dev/md0”, “func”: “service.(*raidStruct).MountRaid”, “file”: “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/raid.go”, “line”: 358}
2026-01-28T19:35:21.239Z info mount attempt failed {“path”: “/dev/md0”, “fsType”: “”, “error”: “no such device”, “func”: “service.(*raidStruct).tryMountWithType”, “file”: “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/raid.go”, “line”: 383}
2026-01-28T19:35:21.239Z error mount raid error

2

Hi
i am dealing with the same problem and cant fix it but there seems to be a way around it.

Maybe this can help:

4

This does not appear to be data loss.

What’s happening

  • Your RAID still exists and the disks are healthy (they are visible at the Linux level).
  • The issue occurs at the ZimaOS RAID mount layer, not within mdadm or BTRFS itself.
  • The log points to this clearly:
mount attempt failed … fsType: "BTRFS" → no such device

ZimaOS is attempting to mount /dev/md0 using a filesystem type stored in its internal metadata.
When this does not match what the system expects, the mount attempt fails and is retried without a filesystem type, which also fails.

This results in:

  • The RAID not appearing in Files
  • The disks still being visible to Linux
  • Reboots not resolving the issue

What not to do

  • Do not recreate the RAID
  • Do not format the disks
  • Avoid ad-hoc mount commands unless advised

Your data remains intact — this is a mount management issue, not filesystem damage.

Current situation

  • There is currently no supported user-side resolution for this behavior in ZimaOS
  • RAID state and filesystem details are managed internally by ZimaOS rather than /etc/fstab
  • Manual mounts may work temporarily but are not persistent

Recommended next steps

lsblk
cat /proc/mdstat
  • Reference:

“RAID mount fails due to filesystem type handling in ZimaOS LocalStorage service”

Why this helps
This provides IceWhale with the information needed to investigate and advise on the correct resolution.
Until further guidance is provided, the safest option is to leave the RAID unchanged.

You did the right thing by stopping and asking.

1 Like
5

Thank you! This is very helpful. I’m new to Zima but already very impressed by the community here. Thank you once again. I will raise a bug report as suggested.