Home | Contact
whichnas.com

Configuring your NAS to send email alerts for disk failures

A network-attached storage (NAS) server can report a failed drive, a degraded RAID array or a read-only volume, but those warnings are easy to miss when nobody is looking at the screen. Email disk failure alerts send a storage-health warning to an administrator at home, in a Sydney office or while travelling. This gives you an early warning while the NAS remains online and any redundancy is still available.

The basic setup is straightforward: create an authenticated SMTP connection, enable the relevant storage-event notifications in QNAP or Synology, and test delivery from the NAS to a real mailbox. Australian broadband providers can block outbound SMTP, and common mailbox services often require two-factor authentication, so provider-specific settings matter. Keep the alert channel separate from ordinary personal email and confirm that backups will still work if the NAS itself becomes unreachable.

Define the failures that matter

Distinguish the event from the symptom. A removed drive, a disk reporting bad sectors, a storage pool leaving RAID redundancy and a filesystem that has switched to read-only mode can require different responses. An alert should identify the NAS, affected volume or pool and drive bay when possible, without exposing customer file names in the subject line.

Choose recipients by responsibility rather than convenience. Send storage warnings to a role-based address such as storage-admin@yourcompany.com.au, then copy a second administrator or a managed-service provider. A shared mailbox remains useful when one person is on leave. If alerts describe personal or customer data, keep the body generic and review the handling rules before enabling detailed event content.

A useful storage monitoring rule set includes the following conditions, although the exact event names vary between QTS and DSM releases:

Configure email delivery in QNAP

In QNAP QTS, sign in as an administrator and open Control Panel > Notification System > Email. Button names can vary by QTS release, but the page accepts an SMTP server, port, account, password, sender address and encryption settings. Prefer the mail provider’s authenticated SMTP service, commonly on port 587 with STARTTLS, and follow its instructions because SSL and STARTTLS are not interchangeable. Save a sender identity that the remote service will authenticate.

Send a test message before creating any disk event rule. Check delivery from the NAS interface and confirm that the recipient sees a readable subject, timestamp and NAS name. A successful test proves only the SMTP path; it does not prove that QTS is monitoring the right storage events or that the account can send beyond its own domain.

Then open Control Panel > Notification System > Event Notification and create a rule for the storage, disk, RAID or volume events offered by that QTS version. Add the shared address, choose an appropriate severity and test a non-destructive event. If a particular SMART threshold is absent from the event list, check Storage Manager and the system health screens; some deployments use a scheduled health check or external monitor to cover that gap.

Configure email delivery in Synology

In Synology DSM, open Control Panel > Log Center > Log Settings and select the email notification panel. Enter the SMTP host, port, username, password, sender name and sender address, choose the encryption required by the mail provider, and enable email notifications. Use Send Test Email to verify the account before changing event categories. DSM wording and placement can change between releases, but the core settings remain the same.

Use the custom notification controls to include storage and volume events such as disk errors, RAID or pool degradation, failed rebuilds and filesystem trouble. For drive-level health, review Storage Manager > HDD/SSD and the Health information for each bay. Some DSM versions do not offer every SMART counter as a direct notification, so a scheduled Task Scheduler health check may be needed for earlier warning.

Keep DSM and the Synology DiskStation Manager client updated, and give the SMTP account only the permissions it needs. A dedicated sender is easier to suspend or rotate than a reused personal password. If staff receive the alerts, agree that someone checks the shared mailbox even when no primary administrator is available.

Test the full notification path

Test the path from more than one place. Send a test while connected through the home or office network, then confirm receipt on a mobile connection outside the building. Do not pull a healthy drive from an active array merely to generate an alert; use the platform’s test button or a harmless volume event. Email cannot report a NAS that has lost power or networking, so pair it with a remote uptime or NAS-health monitor.

Deliverability depends on the sender domain as well as the NAS settings. Configure SPF, DKIM and DMARC through the SMTP provider or domain administrator, and use an address from a domain the organisation controls. Consumer mailboxes can apply daily sending limits, while a supported business relay is usually better for unattended infrastructure. Some providers issue an app password, while newer NAS releases may support a provider-approved automated sign-in method.

Set the NAS clock through NTP and choose the correct Australian time zone. Sydney and Melbourne move between standard and daylight-saving time, Brisbane and Perth do not, and Adelaide uses a half-hour offset during daylight saving. Correct timestamps help distinguish a new storage warning from an old notification and reveal a mail server that has stopped delivering.

A short monthly verification routine covers the weak points:

Prepare for the failure behind the alert

When a disk failure email arrives, first check the pool status, RAID level, drive bay and SMART report before replacing anything. A member-disk error in a healthy RAID 1, RAID 5, RAID 6 or SHR array may leave the volume available, but a second failure can destroy the array. Do not initialise, format or repeatedly restart a degraded system; preserve the event logs and confirm whether a rebuild is progressing.

RAID redundancy is not a backup. Keep versioned or immutable copies on another system or storage platform, and test a restore rather than assuming a successful backup job proves recovery. Protect the NAS and router with a suitable UPS and safe shutdown after mains outages. A geographically separate copy also limits the effect of flooding, fire and prolonged site outages.

Keep a compatible spare drive and record the replacement procedure before a failure becomes urgent. QNAP and Synology systems sold through Australian retailers come with seller and manufacturer warranty terms that can differ, and NAS drives may have separate RMA arrangements. Check the approved compatibility list and retain purchase records. Before ordering a larger replacement, use NAS buying guidance to compare expansion options and model support with an Australian reseller.

Make the alert path ready now

An email alert becomes useful only when ownership is clear. Record who monitors the mailbox, the response time for a degraded pool, the person authorised to replace a drive, and where the current backup report and restore test are stored. A short runbook prevents a critical warning from sitting unread during holidays, staff turnover or an internet outage.

Create the SMTP profile, enable the storage-event rules, send a test from QNAP or Synology, and confirm receipt on an external mobile connection today. Then give the monitoring task a named owner and put the next verification date in the calendar. Do not wait for the first drive error to discover that the alert was blocked, misrouted or never monitored.