Creating RAID Troubleshooting Guide

When dealing with issues related to the inability to create RAID, it is recommended to follow these troubleshooting steps:

  1. Check the Number of Hard Drives

Ensure that there are at least two hard drives available to meet the basic requirements for RAID setup.

  1. Check Disk Health Status

  1. Check whether the individual disk formatting is successful

Format each hard drive individually to ensure that the formatting process completes successfully without any errors.

  1. Check Mount Point

Verify that the RAID mount point does not already contain files. The mount point must be empty to ensure the smooth configuration of RAID. If files are present, back them up and clear the mount point.

  1. System Reboot

After completing the above checks, restart the system and try creating RAID again.

If further assistance is needed, please contact the technical support team for additional help. support@icewhale.org

This guide is not helpful at all. I have three 10TB drives loaded, Formatted each several times now. Rebooted several times now. I NEVER get any prompt to discover “new” drives or set up RAID again. There are zero places to do so. Basically I get to step 4 and then nothing.

Hi, scoobarama,

We are sorry to bring you a bad experience. We have located this issue in certain scenarios and fixed it in the upcoming version. You can proceed further in one of the following ways:

  1. If you can connect a monitor and keyboard to ZimaCube, you can refer to this document to reinstall ZimaOS v1.2.1, and recreate RAID after installation
  2. If you do not have the above equipment or conditions, you may need to wait for the new version to be released in the next few days.

Looking forward to your further reply. :slight_smile:

I have the same problem. Have ZimaOS 1.2.1. The HDDs cannot be created as RAID. There is always an error message. Error 1, I have already installed CasaOS several times.

Hi, Daniel,

This is the first time we have been reported this type of problem, and it seems to be related to the disk or disk partition. If you can use shell/ssh, please provide us with the log if possible to help us further locate the information.

Execute the following command:
tail /var/log/casaos/local-storage.log

Your disk has been individually enabled. Please click Disable first, see the “New hard drive found” notification, and then create RAID @scoobarama
image

This does NOTHING. I have disabled, reformatted, swapped drive slots and NOTHING works. Drives always come up as separate and I have NEVER seen an option to create RAID. I freaking hate this OS.

Would you mind to send an email to support@icewhale.org? We want to build the direct communication with you. Follow up your disk issues and the potential compatibility issue.

Hi, Michael,

Thanks for your feedback! We’ve just released ZimaOS v1.2.2, which includes a fix for the issue of disabling single disks. You can update by checking for the red dot in the upper left corner of the web UI settings.

We’re also enhancing RAID features for v1.2.3, currently in testing.

If you have any questions or need assistance, feel free to reach out to our support team.

BTW, if you would like to get an early experience of ZimaOS and don’t mind using the beta version, you can refer to the ttyd usage instructions here to switch to our beta channel.

I just updated to 1.2.2.
Same problem again:

image

image

Here is the excerpt from the log:

2024-07-09T13:04:34.062Z info trying to mount… {“path”: “/dev/s da”, “mountPoint”: “/media/Files”, “func”: “service.(*diskService).MountDisk”, " file": “/home/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/service/disk.g o”, “line”: 470}
2024-07-09T13:04:34.062Z error error when checking if mount point alrea dy exists, or when creating the mount point if it does not exists {“error” : “mkdir /media/Files: read-only file system”, “mount point”: “/media/Files”, “f unc”: “service.(*diskService).MountDisk”, “file”: “/home/runner/work/ZimaOS-Loca lStorage/ZimaOS-LocalStorage/service/disk.go”, “line”: 486}
2024-07-09T13:04:34.062Z error err {“error”: “mkdir /media/Files: r ead-only file system”, “mountPoint”: “/media/Files”, “output”: “”, “func”: “v2.( *LocalStorage).CreateStorage”, “file”: “/home/runner/work/ZimaOS-LocalStorage/Zi maOS-LocalStorage/route/v2/storage.go”, “line”: 236}
2024-07-09T13:04:41.420Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:04:41.453Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:04:41.516Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:04:41.599Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:04:43.436Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:05:44.559Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}
2024-07-09T13:05:47.560Z error error when getting nvme slot {“error” : “not found nvme slot name”, “func”: “v2.(*LocalStorage).GetDisks”, “file”: “/h ome/runner/work/ZimaOS-LocalStorage/ZimaOS-LocalStorage/route/v2/disk.go”, "line ": 121}

Greets Daniel

Hi Daniel,

Thank you for providing the log details. It looks like the issue stems from the /media directory being mounted as a read-only file system, which is preventing the creation of the /media/Files directory that the newly created disk is mounted on.

Possible Causes:

  1. / or /media Not Mounted Successfully: The / or /media directory might not have mounted correctly, leading to it being read-only.
  2. File System Errors: The file system may have errors that caused it to switch to read-only mode to prevent further damage. This is less common but still possible.
  3. Other Reasons: There could be other configuration issues or permissions problems causing the read-only status.

Next Step:

Check the Mount Point: Please run the following commands in shell / ssh to check the mount options for /media:

mount -l | grep "/ "
mount -l | grep /media
lsblk

These commands will list all mount points related to /media and their attributes.

Review the Output: Look for ro (read-only) or rw (read-write) in the output. If you see ro, it confirms that /media is read-only.

Please let me know the results of the mount command, and we can determine the next steps based on that information.

For further assistance and to ensure quicker progress, you can also reach out to our support team directly at support@icewhale.org.

Best regards,
Orca