Repository navigation
Title: Existing USB-connected RAID5 is missing from ZimaOS Storage UI after updating to v1.8.0 #625
Description
Hello ZimaOS team,
After updating to ZimaOS v1.8.0 and rebooting, my existing USB-connected RAID5 array is no longer detected correctly in the ZimaOS Storage interface.
The RAID array itself is working correctly in Linux, and my data is still accessible. However, ZimaOS does not list the array in its Storage interface or API.
System information
ZimaOS version: v1.8.0
Local storage service version: v0.4.4
RAID type: RAID5
Connection: Four drives connected via USB
RAID device: /dev/md0
Filesystem: ext4
Mount point: /DATA/RAID5
RAID state: clean
Active members: 4/4, no failed drives
Capacity: approximately 17 TB
Used space: approximately 3.3 TB
Observed behavior
The RAID5 array is assembled and active in Linux.
All four RAID members are active and synchronized.
The filesystem is mounted and accessible at /DATA/RAID5.
Linux correctly reports the filesystem capacity and usage.
The ZimaOS local storage database has an empty raids table.
The API endpoint /v2/local_storage/raid?all=true returns an empty list.
The file /var/lib/casaos/db/local-storage.json recognizes the four USB-connected RAID member drives and /dev/md0, but the RAID filesystem information is incomplete: the mount point is empty and filesystem size and usage are reported as zero.
The issue appears to have started after the update to ZimaOS v1.8.0 and the subsequent reboot.
Expected behavior
ZimaOS should detect and register the existing USB-connected RAID5 array, display its correct filesystem capacity and usage, and preserve its existing mount point and data. The array should remain available after future reboots.
Request
Could you please advise how to safely restore the RAID metadata or storage database entry so that ZimaOS recognizes the existing array again, without recreating, formatting, or rebuilding it?
The data is important, so I have not attempted to create a new RAID array, format any drives, modify RAID superblocks, or manually insert records into the database.
Thank you for your help.
Activity
ruttko commentedon Oct 18, 2026
ruttko@ZimaOS:~ ➜ $ cat /proc/mdstat
Personalities : [raid4] [raid5] [raid6]
md0 : active raid5 sdc[0] sdd[4] sde[2] sdb[1]
17581171200 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/44 pages [0KB], 65536KB chunk
unused devices:
ruttko@ZimaOS:~ ➜ $ sudo mdadm --detail /dev/md0
Password:
/dev/md0:
Version : 1.2
Creation Time : Thu Oct 1 15:52:54 2026
Raid Level : raid5
Array Size : 17581171200 (16.37 TiB 18.00 TB)
Used Dev Size : 5860390400 (5.46 TiB 6.00 TB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Consistency Policy : bitmap
ruttko@ZimaOS:~ ➜ $ df -hT /DATA/RAID5
Filesystem Type Size Used Avail Use% Mounted on
/dev/md0 ext4 17T 3.3T 13T 22% /DATA/RAID5