RAID 1 recovery on ZimaOS - how to do it?

[hlnk]

Hi,

I have a ZimaBoard with ZimaOS installed. I initially made a setup based on RAID 1 with two 750GB disks. One of them failed, so it entered recovery mode.

I bought another 750GB HDD to do RAID recovery and connected it to the machine, it is correctly detected as a separate drive, but ZimaOS won’t give me an option to start recovery and add it to the existing RAID.

MAIN_STORAGE is the RAID disk and HDD-storage is the newly added drive.
I have already formatted the new disk, and I see a recovery start option on other threads related to this issue but I don’t see any of that here.

My ZimaOS version is 1.4.1

Thank you

[Zima-Giorgio]

Is this helpful?

How to recover RAID5 array when a hard drive fails

I have two RAID arrays: a RAID5 array of four 12 TB disks and a RAID0 array of two 4 TB disks Disk 2 of the RAID5 array has been marked as “Damaged”. All other disks are marked as “Protecting”. Both arrays have been placed in read only mode by ZimaOS even though only the RAID5 array has the damaged disk. I have a replacement drive ordered and it will be here tomorrow. What is the protocol for replacing the drive marked as damaged and recovering the RAID5 array as well as restoring read/wr…

If not helpful, please copy/migrate all your files/data to a safe location.

And, to prevent issues/data loss. Our engineer will help you to repaire the RAID 1. I will PM you to tell you how we will help you.

[donafinador]

I have an identical issue. It seems the only difference is that my array is of two 2 TB disks. I too have replaced the bad drive with a new one. I have updated to v 1.4.2 b1. I appreciate the new Create Storage tool, but the Combine section doesn’t include joining with the existing disk in the array. I would be nice to have a documented procedure for repairing an array.

[Zima-Giorgio]

We will add the automation flow to recover RAID1. For now, either copy data to extra drives or try to locate the issue using CLI.

If you are familiar with CLI, you can run lsblk and mdadm -D /dev/md0 and forward the output/result here.

Useful steps for the CLI:

1. Enter CLI(Settings-> General-> Developer mode view-> SSH Access enable → Web-based terminal)

2. Log in

3. Run these commands after logging in:

# In some cases, you need to switch to root
# You may need to type the password again
sudo -i

lsblk
# lsblk output...

mdadm -D /dev/md0
# mdadm output...

[Squalo]

so, after all this time you found a way to recover a raid 1, otherwise I will be forced to say goodbye to zimaos,
it seems like a joke that something so important at the base of a server is not implemented,
I urge everyone to change their server’s operating system as soon as possible!

[Zima-Giorgio]

Sorry for the inconvenience, but like you, we believe data loss is unacceptable.

Therefore, we will spare no effort in both feature development and engineering support. And I’m happy to report that version 1.4.4 will provide a more comprehensive RAID 1 repair process. Please continue to provide us with timely feedback so we can improve your product experience!

[fwarring]

I have the same issue. New installed v1.4.4-1 on a zimablade 3760.

Could you please help how I can re-create my RAID1?

[fwarring]

Sorry for not reaching out earlier. I messed around with var/lib/casaos until I couldn´t get it fixed. I am happy to get through CLI commands to repair the Raid1.

[Zima-Giorgio]

Could you tell us how you repaired your RAID1 through CLI? (In 1.4.4, you can do it by the WebUI.)

Thanks for sharing. Look forward to your feedback.

[fwarring]

No, I was asking you to please help me to find a day to repair raid1. I was saying that if needed and you know a way i am trying to follow your instructions, even if technically difficult. Let me know what you need. Thanks.

[Zima-Giorgio]

I have made a PM for you. Please check your message box.

[Zima-Giorgio]

We’re pleased to hear that our engineers have successfully repaired your RAID 1 array via private message.

It is a risk that you do operations via CLI under root privilege if you do not have sufficient knowledge of the OS.

Please note that under no circumstances should you attempt to access the CLI and perform operations as root (unless instructed by our engineers).

[fwarring]

Thanks. I have learned a lot and will be less experimental going forward. Have a great day