6.9.3 Viewing the Storage Summary

February 6th, 2026

RBAC required: bear: Physical storage configuration

In addition to monitoring for storage utilisation via Logs & Monitoring,it is important to understand and periodically review the current physical storage configuration and status. To view the current storage summary, do the following:

1. From the Admin Tools menu, select Physical Storage and activate the Health tab if not already active.

The storage summary will automatically load.

6.9.3.1 Understanding the Storage Summary

The summary provides insight into all the configuration aspects of the BEAR host's storage. This may include devices and filesystems which are not directly manageable from BEAR but manually configured by the ACHE system administrator.

Filesystems

This shows all the mounted filesystems on the host. Information provided includes:

• Type: The type of storage device the filesystem is created on, This could be any of the following:

1. Single physical disk
2. RAID0 striped array
3. RAID1 mirrored array
4. RAID10 striped array of mirrors

• Status: The health of the filesystem. This is effectively showing green for good, or red for faults and errors.
• Path: The path that the filesystem is mounted on.
• Device: The SCSI name of the device as found in /dev/.
• Filesystem: The filesystem type. While there are many supported by ACHE, anything managed by BEAR will be XFS.
• Used %: The utilisation of the storage space for the filesystem as a percentage.

Remember, BEAR creates a simpler association of one filesystem on one device and does not use multiple partitions per device for multiple filesystems. This is by intentional design.

A filesystem in a faulted state has events recorded against it. Not all events are actually failures. It could have problem with just the filesystem, the underlying RAID array (if used) or an underlying disk. You can usually tell exactly what level the fault is at by looking at the status of the other sections below. Benign events can be cleared.

Filesystems backed by a hardware RAID devices will appear as a single non RAID disk. Hardware RAID is transparent to ACHE.

RAID Devices.

Any RAID devices configured on the system (whether in use by a filesystem or not) will appear here. Information provided includes:

• Type: The type of RAID device. This could be any of the following:

1. RAID0 striped array
2. RAID1 mirrored array
3. RAID10 striped array of mirrors

• In Use: Indicates whether the device is in use by a filesystem. Devices not in use can have new filesystems created on them.
• Status: The health of the array. This is effectively showing green for good, or red for faults and errors.
• Sync Status: Whether a sync on a RAID1/10 array is run manually from BEAR or automatically by ACHE, this provides the current progress (if running).
• Logical Name: A friendly name or label associated with the RAID device. While this is arbitrary, it may indicate the indented usage in some way.
• Devices: A list of devices (disks) that make up the array.
• Size: The total storage size of the array. This is the absolute size, not the remaining free space. As such the value does not change depending on utilisation.

Hardware RAID devices will appear as a single non RAID disk. Hardware RAID is transparent to ACHE.

A faulted RAID array will often be due to a failed disk. In this situation, locating the failed array disk can be done by looking for failed Disk Devices described further down.

XFS Log Devices

In most use cases, no log devices will exist. However, for performance systems, one or more log devices may exist here. Information provided includes:

• Status: The health of the log device. This effectively shows green for good or red for bad. A completely faulted log device will effectively block all IO on the filesystems that are registered to it.
• Device: The name of the device as found in /dev/.
• Total Partitions: The total number of available partitions. In general, a single log device can be used for multiple filesystems.
• Used Partitions: The total number of partitions in use by filesystems. Considering how small a log partition generally is, the number of used partitions, even on the smallest drive, will probably never be exhausted.

Disk Devices

At the lowest level is the physical disks attached to the system. While all the storage layers described above describe aspects configuration, this section describes what you would physically see when looking at the server. This information includes:

• Type: This will always be a single physical disk.
• In Use: Whether the disk is actually used in a filesystem, XFS log device, or RAID devices or not. Disks shown as not in use are available for assignment.
• Status: The health of the disk device. This effectively shows green for good or red for bad. A completely faulted disk device will effectively block all IO on the filesystems that are registered to it, either directly or via RAID or XFS log devices.
• Model: The hardware vendor's model number and serial number for the device.
• Technology: The actual type of disk as Hard Disk Drive (HDD), Solid State Drive (SSD) or Non Volatile Memory (NVMe).
• Device: The SCSI, SATA, or NVMe name of the device as found in /dev/.
• H:C:T:L The connection address in Host, Controller, Transport, LUN format. This is useful as it helps understand how many disks are connected to each physically controller. This is not applicable to NVMe devices.
• Size: The storage size of the physical disk.

Model numbers and serial numbers may not be reliable for virtual disks when BEAR is running as a guest virtual machine.

Bear in mind that in the case of RAID arrays with faulted disks, you should use the information in this table to locate a replacement disks of the same type. This could be an attached disk that is not in use or used for locating (or ordering) a compatible disk.

The serial numbers also correspond to the serial number printed somewhere on the physical disk itself. In this way, a properly labelled drive bay (a manual admin task) on the physical server that shows disk model and serial numbers can be used to safely remove and replace (such as a hot-swap scenario) a faulted disk.

Events

This shows all the kernel level events since the last reboot that mention any of the disk or RAID devices at warning level or higher. If you do have storage problems, events here may be useful to your system administrator.

If the events are informational, you can click Clear Faults at the top of the overview and then Rescan to see the current state.