Zima OS 1.5.4
I have an issue when trying to delete the existing RAID5 pool, I get an error “maybe RAID is using by kernel, please try again later”
I have try to migrate all data, then stoped all apps, reboot, but the massage is the same.
1 Like
For the last question, I found the solution Files app no longer loads files after last ZimaOS update - #11 by vskom
Had the same issue.
After some googling and poking around found solution.
*************** YOUR DATA WILL BE GONE AFTER THAT ***************
*************** BE WARNED ***************
In my case Raid5 was md0 vitual device:
root@ZimaOS:/var/lib/casaos_data/.casaos ➜ # mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Fri Dec 26 18:37:57 2025
Raid Level : raid5
Array Size : 5860268032 (5.46 TiB 6.00 TB)
Used Dev Size : 2930134016 (2.73 TiB 3.00 TB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Mon Mar 2 18:51:32 2026
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : zimaos:25def48510bd63ab
UUID : d0d43fed:80a6f077:e5284dee:8980ccad
Events : 5645
Number Major Minor RaidDevice State
0 8 64 0 active sync /dev/sde
1 8 32 1 active sync /dev/sdc
3 8 48 2 active sync /dev/sdd
Steps taken:
systemctl stop icewhale-files ← stopping files subsystem(without it next command will not work)
mdadm -S /dev/md0 ← stop md0 raid
mdadm --zero-superblock /dev/sdc
mdadm --zero-superblock /dev/sdd
mdadm --zero-superblock /dev/sde ← zeroing disks
systemctl start icewhale-files ← restart files subsystem
Then in storage GUI I had info that all disks in Raid5 failed and I was able to delete it:
And create new Raid.
Regards
Tom
*************** YOUR DATA WILL BE GONE AFTER THAT ***************
*************** BE WARNED ***************
This helped me.
Thanks a lot!