How to check RAID status

A practical Online Audience guide covering how to check raid status.

Overview

This Online Audience guide explains how to check raid status for customers using dedicated server. It is written for beginners and focuses on safe, practical steps you can follow before opening a support ticket.

Before you start

Make sure you have the correct login details and know which service you are working on. Use the Client Area, cPanel, EU cPanel, SonicPanel and AzuraCast links in the main menu when you need to access your service.

Steps

• Identify the server name, IP address and service affected.
• Check monitoring, control panel or console access if available.
• Avoid rebooting production systems without understanding the impact.
• Record error messages and timestamps.
• Open a support ticket with the details if needed.

Good practice

Take a screenshot before changing settings, copy any existing values, and test the service after each change. Avoid deleting files, DNS records, email accounts or databases unless you are sure they are no longer needed.

When to contact support

Contact Online Audience support if you see an error message, cannot access the panel, are unsure which server you are on, or the change could affect a live website, email service or radio stream.

Common mistakes to avoid

• Do not change several settings at once without taking notes.
• Do not share passwords or private keys in screenshots.
• Do not delete files, mailboxes, playlists, databases or users unless you have a backup and understand the result.

Recommended image

Add a screenshot that shows the exact page used for this task. For Online Audience articles, use your own screenshots where possible and blur customer information before uploading. Suggested image file: online-audience-how-to-check-raid-status.jpg.

When to contact Online Audience

Open a support ticket from the Client Area menu link if you are unsure, if the service is down, if email has stopped working, if a radio stream is offline, or if WordPress may be hacked. Include the domain or service name, the exact error message, and what changed before the issue started.