Thunderbolt™ Pegasus Family Articles

Why won't my Pegasus go to sleep or stay asleep?

2025-10-28T22:23:38.6300000

Many owners of all kinds of direct attached storage (DAS) have complained that their external drives (firewire, USB and thunderbolt) won't go or stay asleep. This is a legitmate issue, unfortunatly it is also a macOS issue.

Thunderbolt 3/4/5/+ devices (Pegasus 3 and above) are powered on and off by Apple's Thunderbolt driver.

If you plug a Pegasus into the wall socket (but leave the Thunderboilt cable unplugged) the Pegasus will neither power on or boot and you will not be able to turn a Pegasus on with the power switch..
If you remove all promise software and drivers from the MAC and plug in the Thunderbolt cable, the Pegasus will turn on. Promise software does not control the Pegasus power state (on or off).

The Pegasus 1 and Pegasus 2 are Thunderbolt 1/2. They use the mini-displayport connector.

When a Pegasus 1 or Pegasus 2 is connected to the wall socket, it will power on and boot even if the Thunderbolt cable is not plugged.
After the initial power on, the power state is controlled by the Mac's Thunderbolt driver, which tells the Pegasus to power on or power off.

Of course, with no Promise STEX driver, you won't be able to access the storage. And that's what the Promise driver does, it tells the Mac how to access the storage. The Promise Utility allows you to manage the storage.

If your Pegasus or any other kind of external storage won't stay asleep, this is a macOS issue and the Pegasus driver/utility plays no part. No Pegasus settings determine when the Pegasus sleeps or wakes. And this is an issue for all external storage, regardless of which manufacturer.

If you do a google search you will find that many users have been trying to find ways to have their external storage sleep when they want it to, with varying success. Things tend to change with every macOS update, a fix that worked with macOS 15.1 may be broken with macOS 15.2.

There are many possible things that can wake external storage when the MAC still appears to be sleeping.

A few possibilities are...

Power naps, macOS wakes occasionally to check email, etc...
Power saver settings, which change with macOS versions.
Notifications.
Bluetooth
Applications.

For reference, here's Apple's web page on this issue...

https://support.apple.com/guide/mac-help/if-your-mac-wont-go-to-or-stay-in-sleep-mchlp2995/mac

Here's the MacRumours forum on the issue...

https://forums.macrumors.com/threads/external-drives-will-not-stay-asleep.1840232/

Here's some suggested fixes...

https://www.stellarinfo.com/blog/resolve-mac-external-hard-drive-sleep-problem/

The root cause of this issue is that the MAC itself won't stay asleep, it wakes but the display stays off, and there's no end of web pages trying to help with this. A google search gives 2,930,000 results.

https://www.google.com/search?q=mac+won%27t+stay+asleep
About 2,930,000 results (0.48 seconds)

Curiously, Chrome is capable of keeping a Mac from sleeping or staying alseep.

https://apple.stackexchange.com/questions/205228/chrome-prevents-macbook-from-sleeping

Some say that it's Chrome with an open youtube tab, but I'm not sure this is necessary, many sites have embedded youtube videos.

You can tell which apps wake up your MAC from the pmset logs in the system profiler.

This is not a simple issue. But it is a macOS issue. The Pegasus wakes and sleeps when macOS tells it to.

And to keep things interesting, Apple often makes changes the macOS settings app, so a setting in the Setting's energy saver tab in Big Sur may not be present in Sequoia.

Sequoia: Increasing the Storage Capacity of a Pegasus LUN by rebuilding with larger drives.

2025-05-22T21:55:44.3470000

Introduction:

Several years back a Knowledge Base article on increasing the size of a Pegasus LUN by rebuilding with larger drives was created.

https://kb.promise.com/thread/increasing-the-storage-capacity-of-a-pegasus-lun-by-rebuilding-with-larger-drives/

Resently this was restested with macOS Sierra and while the process is the same, something has changed and only 2 terminal commands will resize the Pegasus Volume.

Process:

To save time rebuilds were not done, the LUN size was increased by adding a disk to the array and resizing the LUN to use the additional space.

For everone who wants to increase the size of their macOS Volume, please rebuild one drive at a time. I will leave the process of rebuilding disks to the reader.

The purpose of this KB is to show how to expand the macOS filesystem from Sierra, a 1-disk RAID0 was created and another disk was added to increase the capacity, then the HFS+ filesystem was expanded.

This is the original 1-disk RAID 0, PD2 was added to the RAID and the LUN was grown to use the additional space.

cliib> phydrv
===============================================================================
PdId Model        Type      Capacity  Location      OpStatus   ConfigStatus
===============================================================================
1    Samsung SSD  SATA SSD  499GB     Encl1 Slot1   OK         Array0 No.0
2    Samsung SSD  SATA SSD  499GB     Encl1 Slot2   OK         Unconfigured
3    Samsung SSD  SATA SSD  499GB     Encl1 Slot3   OK         Unconfigured
4    Samsung SSD  SATA SSD  499GB     Encl1 Slot4   OK         Unconfigured

cliib> logdrv
===============================================================================
LdId Alias       OpStatus      Capacity  Stripe RAID    CachePolicy     SYNCed
===============================================================================
0                OK            499GB     1MB    RAID0   NoCache/WThru   Yes

This command was used to add disk 2 to the array and expand the LUN.

cliib> migrate -a start -d 0 -p 2 -l "id=0,raid=0,capacity=998gb"

cliib> logdrv
===============================================================================
LdId Alias       OpStatus      Capacity  Stripe RAID    CachePolicy     SYNCed
===============================================================================
0                OK            499GB     1MB    RAID0   NoCache/WThru   Yes

cliib> logdrv
===============================================================================
LdId Alias       OpStatus      Capacity  Stripe RAID    CachePolicy     SYNCed
===============================================================================
0                OK            998GB     1MB    RAID0   RAhead/WBack    Yes

The LUN went from 499GB to 998GB after the migration.

macOS still sees a 499GB disk.

The process to expand the filesystem is to first run diskutil repairdisk.

Note that for repairdisk use the disk, disk4 and not the slice.

promise@promises-Mac-mini% sudo diskutil repairdisk disk4
Password:
Repairing the partition map might erase disk4s1, proceed? (y/N) y
Started partition map repair on disk4
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Did grow entire partition map
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
The partition map appears to be OK
Finished partition map repair on disk4
promise@promises-Mac-mini%

The important difference here is that in Sequoia adjusted the GPT partition to see the entire disk. Prior macOS versions did not do this and it required an fsck to fix the filesystem on that partition.

Also note the warning...

Repairing the partition map might erase disk4s1

I have not seen this happen and I expect this is a very rare occurance, but the message is clear, do this at your own risk.

Next step is to resize the HFS+ filesystem.

Note, for this step use the slice, disk4s2.

promise@promises-Mac-mini% sudo diskutil resizevolume disk4s2 R
Resizing to full size (fit to fill)
Started partitioning on disk4s2 (Pegasus M4 499GB)
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk4s2
Executing fsck_hfs (version hfs-683.120.3)
Checking Journaled HFS Plus volume
The volume name is Pegasus M4 499GB
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Pegasus M4 499GB appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Modifying partition map
Growing file system
Finished partitioning on disk4s2 (Pegasus M4 499GB)
/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *998.0 GB   disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                  Apple_HFS Pegasus M4 499GB        997.7 GB   disk4s2
promise@promises-Mac-mini%

As you can see, the volume named Pegasus M4 499GB now has a size of 997.7 GB.

2 relatively simple steps and no reboots needed.

The previous KB linked to above goes into more detail about how to find which /dev/disk the Pegasus is, but you can find it with this command. You can identify the Pegasus disk by it's size and the Volume name.

diskutil list

Resolving Thunderbolt Connection Errors with Pegasus3 & Pegasus32

2025-01-29T15:54:09.8330000

If you encounter these Thunderbolt error messages when connecting a Thunderbolt 3 device like the Pegasus3 or Pegasus32 to your Mac or Windows PC, the issue is often related to the cable being used.

Common Error Messages

Mac:
"Cannot use Thunderbolt Accessory. Connect accessory to a Thunderbolt port on this Mac. All of the ports on this Mac are Thunderbolt ports."

Windows:
"Thunderbolt device functionality might be limited. Make sure the Thunderbolt device you’re connecting to is supported by your PC."

Cause of These Errors

These messages usually indicate that the cable used is not a Thunderbolt 3 cable but rather a USB-C charging or data cable. While USB-C cables can physically fit into Thunderbolt 3 ports, they do not support Thunderbolt data transfer. The system detects a connection but cannot establish proper communication with the Pegasus device.

How to Identify a Thunderbolt 3 Cable

Look for the Thunderbolt Logo:

A genuine Thunderbolt 3 cable will have a small lightning bolt symbol on it.
USB-C only cables do NOT have this marking.

Check the Original Cable:

Use the Thunderbolt 3 cable that came with your Pegasus3 or Pegasus32 device.

Verify Cable Type:

If unsure, test with a known working Thunderbolt 3 cable or purchase a new one.

Solution

If you receive either of these error messages:

Ensure you are using a certified Thunderbolt 3 cable.
Avoid using generic USB-C cables, as they might only support charging or limited data transfer.
If needed, purchase a new Thunderbolt 3 cable from a reputable source.

Understanding RAID 0 on Pegasus: Rebuild Options and Alternatives

2025-01-09T17:37:12.8030000

Introduction

RAID configurations are tailored to meet diverse storage needs, balancing performance and data protection. On the Promise Pegasus Series, RAID 0 is a popular choice for maximizing performance and capacity by striping data across multiple drives. However, RAID 0 lacks redundancy, meaning a single drive failure results in complete data loss.

Why RAID 0 Cannot Be Rebuilt

RAID 0 enhances performance by splitting data into "stripes" and writing them across all drives in the array. Unlike redundant RAID levels like RAID 1 or RAID 5, RAID 0 does not store parity or duplicate data. As a result:

No Redundancy: There are no backups or parity data within the array.
Dependency on All Drives: The array requires all drives to function. A single failure makes the entire dataset unrecoverable.
No Rebuild Mechanism: Without redundancy, there is no way to reconstruct the lost data.

Summary: RAID 0 prioritizes performance and capacity over data protection, making it impossible to rebuild after a drive failure.

Alternative Solutions

For users considering RAID 0 on their Pegasus, or those already using it, the following measures can help protect your data:

1. Maintain Regular Backups

RAID 0 lacks redundancy, so backups are essential.
Use external drives, NAS devices, or cloud storage to ensure up-to-date copies of your data.

2. Use a Redundant RAID Level

If data protection is a priority, opt for RAID levels like RAID 5, or RAID 6.
These configurations offer a balance of performance and redundancy, safeguarding against drive failures.

3. Monitor Drive Health

Use the Promise Utility to monitor drive status and performance.
Replace drives that show signs of degradation to prevent sudden failures.

4. Consider a Hybrid Approach

Combine RAID 0 with RAID 1 in a RAID 10 setup to merge the performance of RAID 0 with the redundancy of RAID 1.
While this requires additional drives, it ensures data protection without compromising speed.

Conclusion

RAID 0 on the Pegasus is ideal for performance but unsuitable for data protection. Its lack of redundancy means rebuilding is not an option after a drive failure. To mitigate risks, ensure you:

Maintain regular backups.
Choose a RAID level that meets your redundancy needs.
Monitor and proactively manage drive health.

Connecting the Legacy Pegasus1 and Pegasus2 to M1/M2/M3/M4 Mac Systems Using a Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter

2025-01-08T13:33:39.9830000

To connect the legacy Pegasus1 or Pegasus2 chassis to an M1/M2/M3/M4 Mac system, you must use the original Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter.

Recommended Adapter:

Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter
Purchase Link from Apple Store: Apple Store - Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter

Compatibility Notes:

Pegasus1 and Pegasus2 require this adapter for connection to modern Mac systems equipped with USB-C/Thunderbolt 3/4 ports.
Pegasus3 , Pegasus M4, and Pegasus32 do not require an adapter. These models natively support Thunderbolt 3/4 connections.

Important Setup Steps:

Adapter Connection:
- Plug the Thunderbolt 2 cable from the Pegasus1/Pegasus2 into the Apple Adapter.
- Connect the USB-C end of the adapter into your Mac's Thunderbolt 3/4 port.
Power On the Pegasus Unit.
Check Connection:
- Open Mac System Information → Thunderbolt section.
- Confirm the Pegasus device is detected.

4. Install the DEXT Driver (macOS Sequoia or Later) if you haven't done so

Follow the steps outlined in the KB Article: Install DEXT Driver

For any further issues or troubleshooting, contact Promise Technology Support or or visit the Promise Knowledge Base.

Configuring Email Notifications via Promise Utility on macOS for Pegasus Series

2024-11-18T16:36:03.6800000

Follow these steps to set up email notifications for the Pegasus series using the Promise Utility:

1. Access Promise Utility Settings
- Open Promise Utility from the menu bar at the top of your screen.
- Select Settings.

2. Enable Email Notifications
- Click Turn On Email Service.
- Enter your system administration password when prompted.

3. Configure Email Settings
A . Add your email and server details in the provided fields:
- SMTP Email Server: Enter your SMTP email server address.
- Email Sender (From) Address: Specify the email address to send notifications.
B. For corporate email accounts, include SMTP authentication information if required by your email server (e.g., username and password).

Note:The default Server Port is `25`. Adjust if your SMTP server uses a different port.

4. Adjust Notification Level
A . Set the notification Level to your preference: Warning,Minor (default), Major, Critical or Fatal.

5. Save and Test Configuration
1. Click Save to apply the settings.
2. Test the configuration:
- Click the Test Email button to send a sample notification.
- Verify receipt of the test email.

6. Address Email Server Blocking Issues (for Public Servers)
- If using public email providers (e.g., Gmail, Yahoo):
A. Notifications may fail due to server security mechanisms.
B. Check your email account for blocking notifications (e.g., Gmail’s “Blocked sign-in attempt” message).

- To resolve this with Gmail:
1. Allow less secure apps access in your Gmail settings.
2. Retry sending a test email via the Test Email button in Promise Utility.
3. Confirm that no blocking messages appear in your email account.

7. Notes on Public Email Providers
- Security limitations vary across providers:
- Some providers allow adjustments for less secure apps.
- Others may block notifications entirely without options to adjust settings.

If you encounter issues with email notifications and cannot resolve them through your email provider's security settings, contact your email server administrator or provider for assistance.

By following these steps, you can successfully configure email notifications to stay informed about your Pegasus system's events and alerts.

Pegasus Icon Not Showing on Desktop

2024-11-18T16:26:31.4870000

If the Promise RAID icon does not appear on the desktop, it may be due to the default Finder settings. Follow these steps to resolve the issue:

1. Verify Finder Settings
- Click on the Finder icon or an unused section of the desktop to bring up the Finder menu in your Mac.
- From the top menu bar, select Finder > Settings.

2. Adjust Finder Settings
- In the Finder Preferences window, click the General tab.
- Ensure the "External disks" box is checked.
- Optionally, check "Hard disks" for additional visibility of connected storage devices.

Once these options are selected, the Promise Pegasus icon should appear on the desktop.

3. Check in Disk Utility and Promise Utility
- If the icon still does not appear:
- Open Disk Utility to verify if the Pegasus is detected.
- Open Promise Utility to check the system status.

4. Contact Support
- If the Pegasus RAID is not visible in Disk Utility or Promise Utility, contact Promise Technical Support for further assistance.

These steps should help ensure the Pegasus is properly detected and visible on your Mac system.

Guide to Change the Apache Port in Promise Utility

2024-11-18T16:04:02.0630000

Follow these steps to change the Apache port in Promise Utility on a Mac system:

1. Launch Promise Utility
- Open the Mac System Menu and navigate to Go > Applications.
- Locate and launch Promise Utility.

2. Access Preferences
- In Promise Utility, go to Settings.

3. Unlock General Tab
- Double-click the lock icon in the General tab.

4. Authenticate User
- Enter your Mac system username and password when prompted.

5. Change the Port
- Locate the Promise Utility Port field.
- Enter the new port number and click the Apply button.

6. Restart Promise Utility
- Close Promise Utility.
- Relaunch the application to apply the changes.

Your Apache port has now been successfully updated in Promise Utility.

Using the Pegasus with Windows

2024-11-14T19:11:49.6470000

Using the Pegasus with Windows

While most Pegasus owners use macOS, some Pegasus owners use only Windows and some Pegasus owners use their Pegasus to move files between Windows and Macs (using exFAT). But the Pegasus comes configured with HFS+ for use in a Mac. This guide shows how to configure a Pegasus for Windows.

The equipment used for this guide is a Pegasus M4 and a Windows Server 2019 computer with no Thunderbolt port. The steps are the same if a Thunderbolt port is available in the Windows computer except that the Pegasus driver needs to be installed. The connection is via a USB2 to USB3 cable to the USB port of the Pegasus M4.

First step:

Connect the Pegasus. For USB connections use Port A.

The Pegasus USB-C port with a monitor icon under it supports USB. This is also true with the Pegasus 32.

Configuring the storage for Windows:

After connecting wait for the Pegasus to boot and be detected by Windows. The Pegasus should appear in the Disk Management console.

As the Pegasus comes pre-formatted with the macOS HFS+ filesystem, it must be removed. The HFS+ filesystem includes a 200MB EFI partition, a data partition, and an unallocated 128MB partition. We need to clean the disks of these partitions. The Disk Management console won't delete the EFI partition, we will have to use the Windows Promise Utility.

Open the Promise Utility and select Background Activities (blue icon at the far right) > Initialization > Start. This will take you to the screen below. Then select the LD and quick initialization.

Click Confirm to start the quick init, it will take a few seconds to run. You will get a popup window asking you to confirm the quick init, type confirm and click confirm.

Now the boot block and all partition information has been erased, select Rescan Disks in the Disk Managemnt console.

The Pegasus LUN is now all unallocated space.

All we need to do now is put an NTFS or exFAT filesystem on the LUN.

First initialize the disk. Right click over the Disk 1 area at the left and select Initialize Disk.

The disk (Disk 1 in this case) should be selected with a GPT partition table.

Click OK. The disk is now initialized and ready to be formatted.

Right click in the Unallocated space and select New Simple Volume.

The New Simple Volume Wizard will appear.

Click Next till you get to the Format Partition page.

You can leave everything at the default but you should change the Volume Label to name the disk.

Click Next to format the disk.

Quick Format is very quick, in a minute at most you should see a new NTFS formatted Windows disk.

The Pegasus disk is now Windows disk D:. You can access drive D from File explorer and any applications.

Installing the Pegasus Thunderbolt DEXT Driver on macOS Sequoia

2024-11-05T09:06:14.5300000

To enable the Pegasus Thunderbolt connection on a Mac, follow these steps to install the Pegasus DEXT Driver before connecting your Pegasus device to the Thunderbolt port. This driver is compatible with macOS 12.4 or later.

Step-by-Step Installation

Download the Driver:
- Go to the Promise Download Center.
- Click Drivers and select the Pegasus32 / 3 Series DEXT Driver for Apple-Silicon Macs.
- The installation package file will download to your Downloads folder.

. 2.Install the DEXT Driver:

Locate the file (Pegasus DEXT Driver V21.1.0-2.dmg) in the Downloads folder and double-click it to extract.
Double-click the .pkg file to start the installer. Click Continue to proceed.

Click Install to initiate a standard installation, then enter your Mac password when prompted.

When the System Extension Blocked message appears:
- Open System Settings and navigate to General > Extensions > Driver Extensions.
- Enable the Pegasus DEXT Driver Installer by entering your password again.

Enable the Pegasus DEXT Driver Installer by entering your password again.

Click Done to complete the installation.

Confirming the Driver Installation

Use either of these methods to confirm successful installation:

Method #1: Pegasus DEXT Driver Installer
- Go to Applications and double-click Pegasus DEXT Driver Installer.
- If installed, you’ll see an "Uninstall" option in the pop-up window.

Method #2: Terminal Commands

Open Terminal and enter: sudo -s . Input your password when prompted.
Then, enter: systemextensionsctl list | grep pegasus
Look for "activated enabled" in the output to confirm activation.

Note : If the screenshot output below says "activated waiting for user" after entering systemextensionsctl list | grep pegasus , This indicates that the Pegasus driver is installed but requires manual approval in your Mac security settings before it can function properly. Allow the driver and restart your Mac . After rebooting, run the following command again (systemextensionsctl list | grep pegasus) to confirm the driver status says "activated enabled"

Following these steps will ensure your Pegasus Thunderbolt connection functions properly on macOS Sequoia.

Troubleshooting Notes:

If the status still shows "activated waiting for user", repeat the steps and verify that the driver approval was successful.
Confirm the macOS version is compatible with the Pegasus driver.
Uninstall and Reinstall the driver if needed.
Contact Promise Technical Support for additional assistance

Unreadable Disk Warning on Pegasus

2024-11-04T13:15:21.7830000

Your Pegasus logical drive may appear as a removable-drive icon on your computer's desktop. If your computer’s operating system recognizes the logical drive but cannot access it, a warning message might be displayed.

Under normal circumstances, the Promise Utility automatically formats your logical drives, typically avoiding the occurrence of such warning messages for Pegasus' logical drives. However, if you encounter this warning message, consider the following steps:

1. Attempt Repair Using Disk Utility:Try using your computer's disk utility to address the issue with the problematic logical drive. Refer to the utility’s online help or consult the computer’s User Manual for detailed instructions.

2. Contact Technical Support if Repair Fails:Should the disk utility fail to repair the logical drive, it's advisable to seek advice and assistance from our Technical Support team. You can reach out to us at Support@promise.com.

CAUTION: If a logical drive has been in use and suddenly displays this warning message, do NOT format the logical drive. Formatting erases all of your data on your logical drive

Installing the macOS Pegasus DEXT driver

2024-11-01T12:53:10.9630000

Installing the macOS Pegasus DEXT driver

Introduction

The DEXT driver does not require changing boot permissions, please leave boot permissions at the default, which is Full Security.
The Pegasus32 DEXT driver is compatible with all Pegasus models except the Pegasus Pro.
macOS first supported DEXT drivers in Big Sur (v11.0), however the Pegasus DEXT driver supports Monterey (v12.0) and above.
Do not try to install the both the KEXT and the DEXT, install only the DEXT with the process below.

Note, this

Installation

First download the DEXT driver. Here is a link to the current DEXT driver.

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6963

This driver is from the Pegasus32 downloads page.

Currently the Pegasus32 downloads page is where to look for the latest DEXT.

The download is a disk image (dmg file). Double click to open it.

Double click on the installer package and the install will begin.

Enter your password.

Next, Apple requires that the user manually approve the driver as a security measure.

Select Open System Settings and the installer will take you to the correct place to Allow the driver.

Click Allow and the driver will load.

If you have the latest MacOS Sequoia, enable the extensions as it is a little different with previous OS versions. You can refer to the installation guide from here

Enable the Pegasus DEXT Driver Installer by entering your password again.

Click Done to complete the installation.

If the Pegasus is attached to the Mac, the Volume should mount in less than a minute.

Final Cut...

The installer creates an app in the Applications folder.

The driver has already been installed, do not run this app now.

If you run the app when the driver is installed, it will uninstall the driver.

if you run the app when the driver uninstalled, it will install the driver.

If you delete the app it will uninstall the driver.

Run this app only when you want to uninstall the DEXT driver.

So generally, pay no attention to the app behind the Applications folder.

Confirming the Driver Installation

Use either of these methods to confirm successful installation:

Method #1: Pegasus DEXT Driver Installer
- Go to Applications and double-click Pegasus DEXT Driver Installer.
- If installed, you’ll see an "Uninstall" option in the pop-up window.

Method #2: Terminal Commands

Open Terminal and enter: sudo -s . Input your password when prompted.
Then, enter: systemextensionsctl list | grep pegasus
Look for "activated enabled" in the output to confirm activation.

Note : If the screenshot output below says "activated waiting for user" after entering systemextensionsctl list | grep pegasus , This indicates that the Pegasus driver is installed but requires manual approval in your Mac security settings before it can function properly. Allow the driver and restart your Mac . After rebooting, run the following command again (systemextensionsctl list | grep pegasus) to confirm the driver status says "activated enabled"

Following these steps will ensure your Pegasus Thunderbolt connection functions properly.

Troubleshooting Notes:

If the status still shows "activated waiting for user", repeat the steps and verify that the driver approval was successful.
Confirm the macOS version is compatible with the Pegasus driver.
Uninstall and Reinstall the driver if needed.
Contact Promise Technical Support for additional assistance for further assistance

Increasing the Storage Capacity of a Pegasus LUN by rebuilding with larger drives.

2024-10-31T14:23:15.1770000

Introduction:

A question often asked in the forum is whether it is possible to increase the size of a Pegasus macOS volume by rebuilding all the array drives to larger disks. This is a very good question and previously no process for this was available. As it turns out, there is a way to make this work, the process is documented here.

This process requires the use of the MAC terminal and promise CLI and is probably not for newbies. Also macOS issues a warning about possible loss of files at one point, so use at your own risk. So far it has been used twice successfully in the lab. The steps are readily available at various websites, although not all on the same page.

Note, these process steps are for journaled HFS+ only.

Process:

This process requires a redundant LUN, preferably RAID5 or RAID6. This process should also work with RAID 1 and RAID 10 LUNs. This process will not work with a RAID0 or passthru disks.

The first step is to replace the drives with larger drives through a series of rebuilds. For this KB a Pegasus 2 R6 was used attached to a MacBook Pro running Yosemite. The first 3 drives were 2TB with a RAID5 LUN and a journaled HFS+ filesystem. The last 3 drives were 4TB. The following commands are run from the Promsie CLI. To access the Promise CLI open a MAC terminal and entre promiseutil.

cliib> phydrv
===============================================================================
PdId Model        Type      Capacity  Location      OpStatus  ConfigStatus    
===============================================================================
1    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot1   OK        Array0 No.0     
2    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot2   OK        Array0 No.1     
3    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot3   OK        Array0 No.2     
4    Hitachi HUS7 SATA HDD  4TB       Encl1 Slot4   OK        Unconfigured    
5    WD      WD40 SAS HDD   4TB       Encl1 Slot5   OK        Unconfigured    
6    WD      WD40 SAS HDD   4TB       Encl1 Slot6   OK        Unconfigured    
cliib> phydrv -a offline -p 1
                               WAIT FOR REBUILD TO COMPLETE
cliib> phydrv -a offline -p 2                               
                               WAIT FOR REBUILD TO COMPLETE
cliib> phydrv -a offline -p 3
                               WAIT FOR REBUILD TO COMPLETE
cliib> phydrv
===============================================================================
PdId Model        Type      Capacity  Location      OpStatus  ConfigStatus    
===============================================================================
1    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot1   Stale     StaleConfig     
2    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot2   Stale     StaleConfig     
3    TOSHIBA DT01 SATA HDD  2TB       Encl1 Slot3   Stale     StaleConfig     
4    Hitachi HUS7 SATA HDD  4TB       Encl1 Slot4   OK        Array0 No.0     
5    WD      WD40 SAS HDD   4TB       Encl1 Slot5   OK        Array0 No.1     
6    WD      WD40 SAS HDD   4TB       Encl1 Slot6   OK        Array0 No.2

The 2TB disk (PD1) was forced offline and a manual rebuild was started in the Promise Utility on the first 4TB disk (PD4).

After the rebuild was completed the second 2TB disk (PD2) was forced offline and a manual rebuild was started in the Promise Utuility on the second 4TB disk (PD4).

After the rebuild was completed the third 2TB disk (PD3) was forced offline and a manual rebuild was started in the Promise Utility on the third 4TB disk (PD6).

This can also be done from the Promise Utility.

When this process is complete macOS will still see a 4TB LUN but the array will have been moved to the 4TB disks.

The next step is to expand the LUN on the Pegasus to use all of the disk space. For unknown reasons 'migration' was greyed out in the Promise Utility so this step had to be done in the CLI.

The promise CLI command is...

migrate -a start -d 0 -l "id=0,capacity=8tb"

Be sure to use the correct array number (-d 0), logical drive id (id=0) and capacity of the new LUN, in the case it's 8TB (capacity=8tb). For most 0 will be correct for both the arrayID and logical driveID.

cliib> logdrv
===============================================================================
LdId Alias       OpStatus      Capacity  Stripe RAID    CachePolicy     SYNCed
===============================================================================
0    expandtest  OK            4TB       1MB    RAID5   RAhead/WBack    Yes   
Cliib>
cliib> migrate -a start -d 0 -l "id=0,capacity=8tb"
cliib> logdrv
===============================================================================
LdId Alias       OpStatus      Capacity  Stripe RAID    CachePolicy     SYNCed
===============================================================================
0    expandtest  Synchronizing 8TB       1MB    RAID5   RAhead/WBack    No   
cliib>

Note, this command will be slow, possibly it will finish overnight.

When finished the LUN will be using all the disk space of the 4TB drives.

The last step is to let macOS see and use the extra space in the LUN.

First it is necessary to find which disk on the MAC is the Pegasus LUN. Open a terminal and run 'disutil list'.

Promises-MacBook-Pro:~ promise$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         60.9 GB    disk0s2
   3:                 Apple_APFS Container disk2         60.2 GB    disk0s3 
/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *8.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Pegasus 4TB RAID5       4.0 TB     disk3s2

The Pegasus disk is named Pegasus 4TB RAID5, and it's disk3s2.

Next we repair the filesystem with diskutil list. Note that this command requires the disk (disk3) and not the partition (disk3s2). The command is...

sudo diskutil repairdisk disk3

Make sure to use the proper disk. The results will look like this.

Promises-MacBook-Pro:~ promise$ sudo diskutil repairdisk disk3
Password:
Repairing the partition map might erase disk3s1, proceed? (y/N) y
Started partition map repair on disk3
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Did grow entire partition map
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
The partition map appears to be OK
Finished partition map repair on disk3
Promises-MacBook-Pro:~ promise$ sudo diskutil resizevolume  disk3s2 R
Resizing to full size (fit to fill)
Started partitioning on disk3s2 Pegasus 4TB RAID5
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk3s2
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Volume bitmap needs minor repair for orphaned blocks
Checking volume information
The volume Pegasus 4TB RAID5 was found corrupt and needs to be repaired
File system check exit code is 8
Restoring the original state found as mounted
Error: -69803: Couldn't modify partition map because file system verification failed; 
    please verify and repair each volume individually and then try again
Promises-MacBook-Pro:

First, take note the warning, you must type yes to continue.

Repairing the partition map might erase disk3s1, proceed? (y/N) y

SInce the filesystem was not previously damaged, it seems unlikely to fail in trying to repair said damage, and indeed it has caused no damage in testing, but still, the warning is there, do this at your own risk.

As you can see the repair failed.

Error: -69803: Couldn't modify partition map because file system verification failed

If this happens it is necessary to boot macOS to safe mode and manually run fsck. To boot to safe mode with Intel macOS first properly shut down the the MAC, then holding command + s power the mac back on.

The MAC will boot to a text screen with a root# prompt.

It will take a minute or two after the prompt appears for the Pegasus disk to mount, you will see messages in the window. Wait till after the disk has mounted before continuing.

We know from before that the Pegasus is at disk3s2. The fsck command would be....

fsck -fy /dev/disk3s2

If the results are that some errors were fixed run it again as many times as is necessary for the results to show that the disk is OK. Exit with...

reboot

If the disk is not OK the next step will fail.

The last step after the MAC has rebooted is to run this command from a terminal...

sudo diskutil resizevolume disk3s2 R

The R tells diskutil to resize to use all the disk space available.

Promises-MacBook-Pro:~ promise$ sudo diskutil resizevolume disk3s2 R
Resizing to full size (fit to fill)
Started partitioning on disk3s2 Pegasus 4TB RAID5
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk3s2
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Pegasus 4TB RAID5 appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Modifying partition map
Growing file system
Finished partitioning on disk3s2 Pegasus 4TB RAID5
/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *8.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Pegasus 4TB RAID5       8.0 TB     disk3s2
Promises-MacBook-Pro:~ promise$

As you can see, disk3s2 is now 8TB in size.

2: Apple_HFS Pegasus 4TB RAID5 8.0 TB disk3s2

Finder shows all files are present and viewable.

End Notes:

These macOS commands will probably not run on OS-X and it is not clear when these diskutil options became available and stable. But they should work with any recent macOS.

And again, if not comfortable with the terminal and manual commands, this process is probably not for you.

Guide to using legacy and modern Pegasus storage.

2024-10-30T19:18:04.6870000

IMPORTANT NOTE: The M1 macOS does not include a Pegasus Driver, a Pegasus driver must be installed on all M1 Macs, preferably the DEXT (user space) driver.

The Pegasus line has been evolving for over a decade.

Model	Year	Macos
Pegasus 1	2011	Lion
	2012	Mountain Lion
	2013	Mavericks
Pegasus 2	2014	Yosemite
	2015	El Capitan
Pegasus 3	2016	Sierra
	2017	High Sierra
	2018	Mojave
	2019	Catalina
Pegasus 32	2020	Big Sur
	2021	Monterey
Promise M4 (SSD)	2022	Ventura
	2023	Sonoma
	2024	Sequoia

During this time macOS has evolved from OS X Lion to macOS Ventura and soon Sonoma.

Windows 7 was primarily used in 2011 but many still used XP. Windows 11 is the current Windows version and support for Windows 10 will be ending in 2025.

Thinderbolt has evolved from Thunderbolt 1 to Thunderbolt 4.

Hard drives were from 1TB to 2TB in 2011, today drives of over 20TB are available with 30TB drives announced for the future.

In 2011 SSDs were a curiosity, slow with low capacity. Today SSDs are reliable, fast and have taken over as boot disks.

Much has changed over the decade. And using a device from 2011 like the Pegasus 1 is complicated by all these changes.

Here are some basic rules.

For any legacy Pegasus device, please update to the last firmware released for that Pegasus. Firmware from other generations of Pegasus cannot not be used.

Drivers and the Promise Utility from the shipping Promise Pegasus should be used, today that means the Pegasus32. Drivers written for macOS High Sierra won't work in M1 Ventura. Promise drivers are backwards compatible. The Pegasus32 Promise Utility is backwards compatible. The Promise Utility Pro has limited backwards compatibility.

Drivers and the Promise Utility are backwards compatible, but they are not forward compatible. When an older macOS like Mojave is used, the latest Pegasus32 driver and Promise Utility probably will not work due to changes in macOS. The suggestion is to use the drivers and Promise Utility that were released in the same timeframe as the macOS. The article beginning shows the timeframes of macOS and the Pegasus line.

----

For a Pegasus 1 with a modern macOS.

Use the latest Pegasus 1 firmware v5.04.000061

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=4530

There is a KB on updating firmware on the Pegasus 1 and Pegasus 2

https://kb.promise.com/thread/updating-firmware-on-the-pegasus-1-and-pegasus-2/

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6963

Do not use the latest Promise Utility, use a slightly older version v4.06.0000.01

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6738

----

For a Pegasus 2 with a modern macOS.

Use the latest Pegasus 2 firmware v5.04.0000.64

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6360

There is a KB on updating firmware on the Pegasus 1 and Pegasus 2

https://kb.promise.com/thread/updating-firmware-on-the-pegasus-1-and-pegasus-2/

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6963

Do not use the latest Promise Utility, use a slightly older version v4.06.0000.01

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6738

----

For a Pegasus 3 with a modern macOS.

Use the latest Pegasus 3 firmware v6.06.0000.45

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7024

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6963

Use the latest Promise Utility, v4.06.0000.04

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6878

----

For the Pegasus 32 and Pegasus M4 with a modern macOS.

Use the latest Pegasus 32 firmware v6.06.0000.45

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7024

Use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1 macOS use the DEXT driver v21.1.0-2

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6963

Use the latest Promise Utility, v4.06.0000.04

https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6878

----

Note: M1 is an architecture (actually ARM architechure), M2 and M3 are the next generations of Apple Silicon, but they use the same M1 architechure, an M1 driver will work with an M2 or M3.

How To Rebuild The Replacement Drive into Pegasus Unit using Promise Utility

2024-10-30T19:07:02.3370000

When you need to rebuild a disk array, you are essentially reconstructing the data on one of its physical drives. In case there is no available spare drive with sufficient capacity, you must replace the failed drive with an unconfigured physical drive and perform a Manual Rebuild.

Identifying the Failed Drive

1. Locate the carrier with the failed drive. The Drive Power/Status LED will be red, and the Drive Activity LED will be dark. This is the physical drive that requires replacement.

Replacement and Rebuild Process

Follow these steps when replacing the drive and initiating the rebuild process:

1. Ensure that the unit is powered on before plugging in the new drive.Open Promise Utility and unlock the utility by clicking the lock symbol at the bottom left of the page.

2. Insert the new drive, and check the Physical Drive status.The status of the new drive should be Unconfigured.If the status is shown as Passthru,change the status of the new drive to Unconfigured in order to enable the Rebuild process and confirm the settings.

3. Please select Background Activities on the top right of the utility and then click the Start button in the Rebuild row.

4. Please check the Target Physical Drive, make sure that it is the replacement drive, and then click Confirm.

5. Once you confirm, the Rebuild process starts immediately. Please do not write any data during the rebuild process, to prevent any data lost. After the PD Progress shows 100%, then you can start writing data to Pegasus again.

Please note that Rebuilding may take several hours, depends on the HDD capacity and file size.

In order to speed up the Rebuild process, you can click Background Activities, and then set the Rebuild Rate to High.

Pegasus Hard Drives Compatibility list Summary (including Pegasus 1/2/3/32 M4, R4i and J2i)

2024-10-30T18:37:29.7470000

Pegasus 1

The Pegasus1 R4/R6 systems are compatible with various hard drives, including SATA Hard Drives.

Some supported hard drive models include Seagate Barracuda, Toshiba DT01ACA and Hitachi Deskstar.

The largest capacity mentioned in the hard drive compatibility list of the Pegasus1 R4/R6 systems is 4TB for The Seagate Barracuda ST4000DM000 SATA / 3.5" and 4TB for the Toshiba MD04ACA400 SATA / 3.5".

The Pegasus2 systems are compatible with a range of host systems, including Mac systems such as MacBook Pro 2011, MacBook Air 2012, Mac mini 2011, iMac 2011, and Mac Pro 2012. For Windows systems, compatibility has been verified with motherboards from vendors like Gigabyte, ASUS, HP, Intel, and MSI.

For Mac systems, the supported versions include from Mac OS 10.6.7 to MacOS 15. On the Windows side, the compatible versions are From Windows 7 SP1 to Windows 10 x64.

for the Full detailed Compatibility list please download the following file:https://www.promise.com/DownloadFile.aspx?DownloadFileUID=4127

Pegasus 2

The Pegasus2 systems are compatible with various hard drives, including SATA Hard Drives for Pegasus2 R4/R6/R8 models and SATA/SSD drives for Pegasus2 M4.

Some supported hard drive models include Seagate Barracuda, Toshiba DT01ACA, Samsung 840 EVO, HGST Deskstar NAS HD, Seagate Ironwolf, and more.

The largest capacity mentioned in the hard drive compatibility list of the Pegasus2 R4/R6/R8 systems is 10TB for The Seagate Ironwolf ST10000VN0004 SATA / 3.5" and 8TB for the Toshiba MG05ACA800E SATA / 3.5". drives offer substantial storage space for users requiring high-capacity storage solutions in their Pegasus2 setups.

The Pegasus2 systems are compatible with a range of host systems, including Mac systems such as MacBook Pro, MacBook Air, Mac mini, iMac, and Mac Pro. For Windows systems, compatibility has been verified with motherboards from vendors like Gigabyte, ASUS, HP, Intel, and Dell.

For Mac systems, the supported versions include from Mac OS 10.8.5 to MacOS 15. On the Windows side, the compatible versions are From Windows 7 SP1 to Windows 10 x64.

for the Full detailed Compatibility list please download the following file: https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6600

Pegasus 3

The Pegasus3 systems are compatible with various hard drives, including SATA Hard Drives for Pegasus3 R4/R6/R8 models and SATA/SSD drives.

Some supported hard drive models include HGST, Seagate, Toshiba, WD, micron and Samsung.

The largest capacity mentioned in the hard drive compatibility list of the Pegasus3 R4/R6/R8 systems is 20TB for The Toshiba MG10 MG10ACA20TE SATA / 3.5" , 24TB for the Seagate Exos X24 and 18TB for the Western Digital RED PRO WD181KFGX-68AFPN0 SATA / 3.5". The largest capacity mentioned for the SATA SSD is 4TB for the Western Digital PC SA530 SATA / 2.5".

The Pegasus3 systems are compatible with a range of host systems, including Mac systems such as MacBook Pro, MacBook Air, Mac mini, iMac, and Mac Pro. For Windows systems, compatibility has been verified with motherboards from vendors like Gigabyte, ASUS, HP, Intel, and Dell. For Mac systems, the supported versions include from Mac OS 10.12 to MacOS 15. On the Windows side, the compatible versions are From Windows 7 SP1 to Windows 11.

For the Full detailed Compatibility list please download the following file:https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7369

Pegasus 32

The Pegasus32 systems are compatible with various hard drives, including SATA Hard Drives for Pegasus32 R4/R6/R8 models and SATA/SSD drives.

Some supported hard drive models include HGST, Seagate, Toshiba, WD, Kingston, Transcend, micron and Samsung.

The largest capacity mentioned in the hard drive compatibility list of the Pegasus32 R4/R6/R8 systems is 20TB for The Toshiba MG10 MG10ACA20TE SATA / 3.5" and 18TB for the Western Digital RED PRO WD181KFGX-68AFPN0 SATA / 3.5". The largest capacity mentioned for the SATA SSD is 7TB for the Kingston DC 600M SEDC600M SATA / 2.5".

The Pegasus32 systems are compatible with a range of host systems, including Mac systems such as MacBook Pro, MacBook Air, Mac mini, iMac, and Mac Pro. For Windows systems, compatibility has been verified with motherboards from vendors like Gigabyte, ASUS, HP, MSI, and Dell. For Mac systems, the supported versions include from Mac OS 10.14 to MacOS 15. On the Windows side, the compatible versions are Windows 10 and Windows 11.

For the Full detailed Compatibility list please download the following file: https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7370

Pegasus M4

The PegasusM4 systems are compatible with various SATA/SSD drives for PegasusM4 R4/R6/R8 models.

Some supported hard drive models include WD, Kingston, Transcend and Intel.

The largest capacity mentioned in the SSD drives compatibility list of the PegasusM4 R4/R6/R8 systems is 7TB for The Toshiba DC 600M SEDC600M and 4TB for the Western Digital RED SA500 WDS400T1R0A and Transcend dSSD470 TS4TSSD470K-I.

The PegasusM4 systems are compatible with a range of host systems, including Mac systems such as MacBook Pro, MacBook Air, Mac mini, iMac, and Mac Pro. For Windows systems, compatibility has been verified with motherboards from vendors like Gigabyte, ASUS, HP, and Dell. For Mac systems, the supported versions include from Mac OS 12 to MacOS 15. On the Windows side, the compatible versions are Windows 10 and Windows 11.

for the Full detailed Compatibility list please download the following file:https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7372

Pegasus R4i

The PegasusR4i systems are compatible with various SATA/Hard drives From Toshiba.

The largest capacity mentioned in the SSD drives compatibility list of the PegasusR4i systems is 20TB for The Toshiba MG10 MG10ACA20TE and 18TB for the Toshiba MG09 MG09ACA18TE.

The PegasusR4i systems are compatible with a range of host systems, including Mac systems, the supported versions include from Mac OS 10.15 to MacOS 15. On the Windows side, the compatible version is Windows 10 (through Boot Camp).

for the Full detailed Compatibility list please download the following file:https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7371

Pegasus J2i

The PegasusJ2i systems are compatible with various SATA/Hard drives From Toshiba.

The largest capacity mentioned in the SSD drives compatibility list of the PegasusJ2i systems is 20TB for The Toshiba MG10 MG10ACA20TE and 18TB for the Toshiba MG09 MG09ACA18TE.

for the Full detailed Compatibility list please download the following file: https://www.promise.com/DownloadFile.aspx?DownloadFileUID=7340

Moving from a Legacy Pegasus to a Pegasus32 chassis

2024-10-30T18:22:29.9570000

Introduction

As times slowly passes it leaves it's mark on the world. The mountains rise up and wear down, the continents shift and change configuration, and worst of all, the dinosaurs have become extinct.

But on shorter timescales we also grow older, as does our equipment. Most things we use, like cars, furniture and most of all, computers either fail or become obselete. Few today use a computer based upon the venerable i486.

Storage has also changed over the years, in capacity, speed, and price.

Updating our equipment is an ongoing process. There are many reasons for updating our equipment, it could be because of equipment failures, or it could be that the storage speed of yesterday's equipment may not be up to the today's task of editing a 4k video.

Moving from a Legacy Pegasus to a Pegasus32 chassis

The promise Pegasus has a builtin capacity for upgrading. The disk set from a Pegasus1, a Pregasus2, or a Pegasus3 can be moved to a Pegasus32 chassis and the Volume will mount.

The process is simple...

Make sure both Pegasus units are powered off.
Move the Hard Drive carriers from the Legacy Pegasus to the Pegasus32. It's best to move the Legacy Pegasus drives to the corresponding slot on the Pegasus32.
Connect the Pegasus32 power cable and Thunderbolt cable.
After the Pegasus32 boots, the Volume should mount.

Some Limitations

The macOS version must support the Pegasus32 driver. macOS High Sierra for example, does not support the Pegasus32 driver. The Pegasus32 FCS (First Customer Shipment) driver supports macOS 10.14 (Mohave), 10.15 (Catalina) and above on Intel Macs.

If the Mac being used has Thunderbolt 2 ports, then a Thunderbolt 2 > Thunderbolt 3 adapter will be needed. The Apple adapter is recommended.

Creating a Service Report from the Pegasus32 Series using Promise Utility

2024-10-29T18:20:41.4130000

How to Save a Service Report from the Pegasus32 Series using Promise Utility

Prior to calling Promise Technical Support for any Pegasus32 related issues, please capture and prepare the Service Report:

Open the Promise Utility,click on Subsystem Information, then unlock the padlock, and then click Save Service Report.

If this is successful, then it will open a new window for you to choose a folder to save the report. After that, you may use Finder to see that the file has been created in the folder.

If a Service Report can't be saved for some reason, this is the manual method.

Open the Mac OS Terminal session: In Finder, go to Applications, then open Utilities, then open Terminal.
At the "$" prompt, type
```
promiseutil
```
and press Enter. If Promise Utility Pro is installed, this command will change the prompt to
```
cliib> 
```
At the cliib> prompt, type each of the following commands on their own line, pressing Enter after each one:

subsys -v

enclosure -v

ctrl -v

phydrv

phydrv -v

array -v

logdrv -v

checktable -l 0

event

event -l nvram

Once that is done, then in the Applications folder, open TextEdit, and from File select New Document.

Select All from the Terminal window and Copy the entire terminal session to your clipboard; then, Paste it into the TextEdit document. Finally, Save the TextEdit document as a "Rich Text File" with the name servicereport.

These logs are vital in assisting Technical Support for resolution of any issues.

This links to a Promise KB article on how to attach files to a web support case:

http://kb.promise.com/thread/how-to-attach-files-to-your-web-case/

Conducting Media Patrol on Your Physical Drives with Pegasus

2024-10-29T17:56:22.1530000

Media Patrol is a routine maintenance procedure that checks the magnetic media on each disk drive. Media Patrol checks are enabled by default on all disk arrays and spare drives. Media Patrol is concerned with the media itself, not the data recorded on the media. If Media Patrol encounters a critical error, it triggers PDM if PDM is enabled on the disk array. Media Patrol checks all physical drives one at a time.

Running Media Patrol

To run Media Patrol on your physical drives:

Click on the Background Activities icon. The list of background activities appears.
Mouse-over Media Patrol and click the Start button.

Pausing and Resuming a Media Patrol

To pause or resume a Media Patrol:

Click on the Background Activities icon. The list of background activities appears.
Mouse-over Media Patrol and click the Pause or Resume button.

Stopping a a Media Patrol

To stop is to cancel the Media Patrol:

Click on the Background Activities icon. The list of background activities appears.
Mouse-over Media Patrol and click the Stop button.
In the Confirmation box, type the word “confirm” in the field provided and click the Confirm button.

Conducting Redundancy Check on Your Drives with Pegasus

2024-10-29T17:54:05.4630000

Redundancy Check is a routine maintenance procedure for fault-tolerant disk arrays (those with redundancy) that ensures all the data matches exactly. Redundancy Check can also correct inconsistencies.

Making Redundancy Check Settings

To make Redundancy Check settings:

1. Click on the Background Activities icon.

2. Click the Settings button.

3. Click the Redundancy Check Rate dropdown menu and choose a rate:

Low – Fewer system resources to Redundancy Check, more to data read/write operations.
Medium – Balances system resources between Redundancy Check and data read/write operations.
High – More system resources to Redundancy Check, fewer to data read/write operations.

4. Click the Confirm button.

5. Click the X icon to close the background activities panel.

Stale or PFA Condition with Pegasus

2024-10-29T17:52:28.6500000

Stale Condition:
- This happens when the physical drive has outdated disk array information.
- To fix it, replace the physical drive or perform a rebuild operation. Once done, follow these steps to clear the condition:
1. Click on the Physical Drive icon.
2. Hover over the drive you want and click the Clear button.
3. Confirm by clicking the Confirm button.

PFA Condition:
- This occurs when the physical drive has errors, predicting a failure.
- Make sure to address this by replacing the physical drive and then clearing the condition using the steps mentioned above.

Important Note:
- If a physical drive has both Stale and PFA conditions, it's best not to reuse the drive as it has failed.
- Similarly, if the drive has a PFA condition alone, avoid reusing it as it signifies a failure.

Excluding the Pegasus Drive from Spotlight Indexing

2024-10-29T17:47:57.3200000

At times, Spotlight indexing can impact Pegasus performance. To address potential performance issues, consider the following steps, as Spotlight's continuous indexing of files on your Pegasus might be a contributing factor:

- Exclude the External Drive from Spotlight Indexing:
It is recommended to permanently exclude the external drive from Spotlight indexing.Detailed instructions can be found here

Additionally, while running First Aid is a good idea, please note that it cannot be performed while the Volume is in use. Therefore, before attempting First Aid, ensure to:

Close any apps that may be using the Volume.
Ensure that Finder is not open in the Volume, and Spotlight is not indexing the Volume.
Confirm that the Terminal is not currently cd'd to the Volume.

By following these precautions, you will be able to unmount the Volume and successfully run First Aid.

The primary objective here is to disable Spotlight's indexing for the Pegasus drive without completely disabling Spotlight functionality.

Pegasus: Basic Troubleshooting

2024-10-29T17:39:51.8170000

Pegasus: Basic Troubleshooting

Introduction

As technology progresses, our daily life is getting more complicated. The devices we use are also getting more complicated and when things go wrong, the often unanswered question is, how do I fix this? This guide show you the steps to troubleshooting Pegasus issues.

Troubleshooting Steps

The following items should be checked in the order given.

Power
Thunderbolt connection
Driver
Disk Utility
Filesystem

Power

Verify that the Pegasus powers on.

The Pegasus 1 (Thunderbolt 1) and the Pegasus 2 (Thunderbolt 2) will power on when the power cable is plugged in.

The Pegasus 3 (Thunderbolt 3) and Pegasus 32 (Thunderbolt 3) will power on only when both the power cable is plugged in and the Pegasus Thunderbolt port is connected to an operating Mac or Windows Thunderbolt port.

Perhaps the most common reason for a Pegasus to not power on is a bad or intermittant Thunderbolt cable, the first thing to check is the Thunderbolt cable, try another (ideally known working) cable.

If after replacing the Thunderbolt cable the Pegasus still does not power up, it might help to leave the Thunderbolt cable plugged in and to remove the power cable for about 1 minute and plug it back in again.

Also, users with a UPS sometimes see that the Pegasus won't power on. Often the UPS is very old and it can't deliver enough voltage. Or it may be oversubscribed, that is, have too many devices attached and can't provide enough power for all of them. Either way, the simplest way to check is to unplug the Pegasus from the UPS and connect it to a wall socket.

Thunderbolt connection

Make sure there is a connection to the computer's Thunderbolt bus.

To check, get a System Report and check under the Thunderbolt section.

If the Pegasus does not show in the Thunderbolt section, then the Mac cannot see it.

In this case, even if the Pegasus powers on, the Thunderbolt cable is suspect.

Some common reasons why there might be no Thunderbolt connection are...

The Thunderbolt cable is plugged into a USB3 port. Most windows computers have no Thunderbolt port, and many Macs have USB only ports. For example the two front ports in a Studio Max are USB only.
There may be issues with the Thunderbolt 3 > Thunderbolt 2 adapter needed when connecting a Pegasus 1 or Pegasus 2 to a modern Mac. The Apple converter works well and there have been no connection issues with them. Some other manufacturers adapters have not worked with the Pegasus.

Driver

Intel macOS has a Pegasus driver builtin. But with the M1 macOS, a driver needs to be installed.

Follow this guide to correctly install the DEXT driver.

https://kb.promise.com/thread/installing-the-macos-pegasus-dext-driver/

For Intel macOS, on occasion after an update, the Pegasus kext driver won't load for some reason. To check if this is the case, use this command.

promise@promises-Mac-mini-2 ~ % kextstat | grep promise
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
promise@promises-Mac-mini-2 ~ %

From the above the STEX driver is not loaded.

To manually load the builtin STEX driver...

promise@promises-Mac-mini-2 ~ % sudo kextload /System/Library/Extensions/PromiseSTEX.kext
Password:
Executing: /usr/bin/kmutil load -p /System/Library/Extensions/PromiseSTEX.kext
promise@promises-Mac-mini-2 ~ %

There are no errors, the driver load succeedded. To verify...

promise@promises-Mac-mini-2 ~ % kextstat | grep promise
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
  194    0 0xffffff8003473000 0xb000     0xb000     com.promise.driver.stex (6.2.13) AE253556-66D8-38D2-B9D1-179B78F29153 <191 16 7 6 3>
promise@promises-Mac-mini-2 ~ %

The Pegasus STEX driver, v6.2.13 is now loaded.

Disk Utility

If the Pegasus powers up, shows in Thunderbolt section of the System Report and the correct driver is installed, but the Volume still does not mount, check Disk Utility. If the Pegasus disk does not show, try reseating the Thunderbolt cable. After reconnecting the Thunderbolt cable, it may take 1 or 2 minutes for the LUN to show in Disk Utility. Once Disk Utility sees the disk, the should not mount.

Filesystem

If the Volume shows in Disk Utility but does not mount, there may be issues with the filesystem.

First step, use the Disk Utility mount option.

If the mount option fails, try First Aid. First Aid is useful and will often work, but occasionally it does not work. Some 3rd party recovery tools are available. Promise does not endorse any company or tool, but for many years the goto tool for this kind of problem has been Disk Warrior. Be advised that this is not a free tool.

If software tools are ineffective, there are various data recovery services. A quick google will show any in your local area as well as non-local companies. Be advised that data recovery is not inexpensive.

Conclusion

This KB gives the basic procedure for troubleshooting Pegasus issues. Most issues can be solved by following this procedure. For those where there is filesystem damage, there are 3rd party tools and data recovery companies that can help.

Setup a Size Limit for Time Machine Backup Volumes

2018-04-06T18:03:50.8900000

Time Machine by default, will use all the available disk space on an external drive or a external server volume. You can setup a limit how much disk space Time Machine may use. Use this defaults write Terminal command:

defaults write /Library/Preferences/com.apple.TimeMachine MaxSize 405600

Where MaxSize 405600 is the MB equivalent of 400GB (400 * 1024)

To remove the limit:

defaults delete /Library/Preferences/com.apple.TimeMachine MaxSize

Contact Promise Technology Support
Need more help? Save time by starting your support request online and a technical support agent will be assigned to your case.

Promise Technology Technical Support >

How do I Create a Volume on a Pegasus?

2017-12-13T20:32:21.7870000

Table of Contents

Section I. Identifying the Pegasus Model and Specifications
A. Pegasus3 Models
B. Pegasus2 Models

Section II. Creating Disk Array and Logical Drive
A. Example with macOS
B. Example with macOS with APFS
C. Example with Windows

Description: This article will illustrate to all Pegasus customers on how to configure a Pegasus from scratch.

Section I. Identifying the Pegasus Model and Specifications

Note: Review the tables below indicating which RAID levels each Pegasus Model supports.

A. Pegasus3 Models

Pegasus3 Specifications Table

Model	Pegasus3 R4	Pegasus3 R6	Pegasus3 R8
Form Factor	4-Bay Hardware RAID Enclosure	6-Bay Hardware RAID Enclosure	8-Bay Hardware RAID Enclosure
Interface	2x Thunderbolt™ 3 Technology Ports (40Gbps)
OS Support	macOS 10.12 and macOS 10.13 Windows 7, Windows 10
RAID Levels	0,1,5,6,10	0,1,5,6,10,50	0,1,5,6,10,50,60

For the full specifications table for the Pegasus3 Series, please download the datasheet.

B. Pegasus2 Models

Pegasus2 Specifications Table

Model	Pegasus2 R4	Pegasus2 R6	Pegasus3 R8
Form Factor	4-Bay Hardware RAID Enclosure	6-Bay Hardware RAID Enclosure	8-Bay Hardware RAID Enclosure
Interface	2x Thunderbolt™ 2 Technology Ports (20Gbps)
OS Support	Mac OS X 10.8.5 or higher macOS 10.12 and 10.13 Windows 7, Windows 10
RAID Levels	0,1,5,6,10	0,1,5,6,10,50	0,1,5,6,10,50,60

For the full specifications table for the Pegasus2 Series, please download the datasheet.

Section II. Creating Disk Array and Logical Drive

A. Example with macOS

Open the Promise Pegasus Utility.
Unlock the Utility by click in on the lock icon
In order to make any changes to the Pegasus, the utility must be unlocked
Click on the Physical Drive icon to get the list of the disks.
You want to ensure that all the drives (or the drives that you want to use for your new array) have a Configuration Status as Unconfigured:
Once you've verified that all the drives have a Configuration Status of Unconfigured, proceed to the Disk Array icon. There should be no configured disk arrays in the subsystem.
Click on Create Disk Array
You will be brought to the Disk Array sub-menu.
A. Input the Alias label (i.e. MyArray01)
B. Ensure that Media Patrol and PDM (Predictive Data Migration) are enabled.
C. Media Type will be Hard Disk Drive for non-SSD SATA drives.
Select the drives you will allocate to the array. In this example, all (8) drives are being used in this illustration.
Device in Example: Pegasus3 R8
Click Submit and you will receive a message that the disk array was created successfully.
A. Click Finish
You will be presented back to the Disk Array menu with the Status of your Disk Array.
Click on the Logical Drive icon.
A. Click on Create Logical Drive.
In the Logical Drive sub-menu, locate the array you created on step 10.
A. Ensure the radio button is selected next to the array that you will use to configure the Logical Drive.
B. Once confirmed, click Next.

You will be presented with the Create Logical Drive sub-menu. In this screen you will be able to dictate the settings for your Logical Drive.

Note: Carefully elect the options that best suits your environment's need.

You can modify the following parameters in this screen:
A. Alias – Alias of Logical Drive
B. RAID Level – RAID Level of your Logical Drive
C. Capacity – The size you want to allocate to the Logical Drive.
D. Stripe – The Stripe Size of your Logical Drive.
You can choose a stripe size of 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB.
E. Sector – The Sector Size (512 Bytes is the most common sector size and the default used)
F. Read Policy

Read Cache	The read cache is enabled but no pre-fetch action.
Read Ahead	The read cache and predictive pre-fetch feature are enabled.
No Cache	The read cache is disabled

G. Write Policy

Write Back	Data is written first to the cache, then to the logical drive. This provides better performance.
Write Thru	Also "Write Through." Data is written to the cache and the logical drive at the same time. This is safer.

I. Format - If you leave the checkbox selected, it will format the volume HFS+ and automatically mount the volume on your machine.

Input your desired parameters and click Add.
Once you've clicked Add, your Logical Drive will be presented under the New Logical Drives section. Verify your settings and click Submit.
You will wait a few seconds for the Logical Drive to initialize and it will be presented to the main Logical Drive menu. You will see the Status of the Logical Drive as Synchronizing.
You can always check the status of the Synchronization process under:
Background and Activities > Synchronization
You will see the HFS+ Volume labeled as Promise RAID. The name of the volume can be changed.

B. Example with macOS with APFS

Formatting a Filesystem with Disk Utility (Without the format option in the Pegasus Utility)

If you would like to create an APFS volume or simply elect not to have the utility format your filesystem with the Pegasus Utility, create your Logical Drive without the Format checkbox selected. (Repeat steps 1-17)
Use will need to initialize your disk manually. Click Initialize to open Disk Utility.
In Disk Utility, locate and select the Logical Drive you created. The drive will state Uninitialized.
Click the Erase icon on the top menu to begin the initialization process.
Select the desired filesystem format. In this example, we are illustrating standard APFS.
Click Erase.
You will receive a dialogue once the formatting has completed successfully.
Click Done.
You have now created an APFS volume and is ready for use.

C. Example with Windows

Open the Promise Pegasus Utility.
Click on the Physical Drive icon to get the list of the disks.
You want to ensure that all the drives (or the drives that you want to use for your new array) have a Configuration Status as Unconfigured:
Once you've verified that all the drives have a Configuration Status of Unconfigured, proceed to the Disk Array icon. There should be no configured disk arrays in the subsystem.
Click on Create Disk Array
You will be brought to the Disk Array sub-menu.
A. Input the Alias label (i.e. MyArray01)
B. Ensure that Media Patrol and PDM (Predictive Data Migration) are enabled.
C. Media Type will be Hard Disk Drive for non-SSD SATA drives.
Select the drives you will allocate to the array. In this example, all (8) drives are being used in this illustration.
Device in Example: Pegasus3 R8
Click Submit and you will receive a message that the disk array was created successfully.
A. Click Finish.
You will be presented back to the Disk Array menu with the Status of your Disk Array.
Click on the Logical Drive icon.
A. Click on Create Logical Drive.
In the Logical Drive sub-menu, locate the array you created on step 8.
A. Ensure the radio button is selected next to the array that you will use to configure the Logical Drive.
B. Once confirmed, click Next.

Read Cache	The read cache is enabled but no pre-fetch action.
Read Ahead	The read cache and predictive pre-fetch feature are enabled.
No Cache	The read cache is disabled

G. Write Policy

Write Back	Data is written first to the cache, then to the logical drive. This provides better performance.
Write Thru	Also "Write Through." Data is written to the cache and the logical drive at the same time. This is safer.

I. Format - If you leave the checkbox selected, it will format the volume NTFS and automatically mount the volume on your machine.

Input your desired parameters and click Add.
Once you've clicked Add, your Logical Drive will be presented under the New Logical Drives section. Verify your settings and click Submit.
You will wait a few seconds for the Logical Drive to initialize and it will be presented to the main Logical Drive menu. You will see the Status of the Logical Drive as Synchronizing.
You can always check the status of the Synchronization process under:
Admin > Background and Activities > Synchronization
You will see the NTFS volumed labeled as PromiseRAID under Devices and Drives in This PC.
The name of the volume can be changed.

A. Properties of NTFS volume:
Viewing the volume in Computer Management > Disk Management:

How to setup Email Notification for Pegasus Events

2016-12-01T22:30:52.6500000

This example will illustrate how to configure Email Notifications via the Promise Utility on Mac OS X for the Pegasus series.

(1) Click on Promise Utility at the top of the menu bar, and select Preferences.

(2) Click Turn On Email Service. You are required to have system administration privileges.

(3) Add your own email & server information accordingly.

Note: You have to put in the SMTP authentication info if your sender's email account is under any corporation email server and firewall. The Pegasus will not be aware of the user's email authentication info if it's not provided.
The Server Port is 25 default.

(4) Change the Level to a desirable setting. The default is setting is Minor.

(5) Click on Save. You may click on the Test Email button to verify if the settings work for your environment.

(6) If you are using a public email server, such as Google Gmail or Yahoo mail, for the Email Sender address, you may not be able to receive the Pegasus Event Email Notification and you'll receive an email server blocking notification. This kind of problem is related to the email server's security mechanism. For example, if you use Google Gmail as your Email Sender Address, Gmail's server will block the Pegasus from signing into your Gmail account for email notifications and will send you a blocking notice as the example below.

(7) Different public email servers may have different security limitations. In this case, Gmail server allows users to lower their security settings for using less secure apps, such as Promise Utility app. You may change your Gmail account security level with the instructions provided.

(8) After changing your public email server account's setting for less secure apps, attempt sending a test email by clicking the Test Email button in the Pegasus Utility. Check your Google Gmail account to verify if you didn't receive the "Blocked sign-in attempt" notification.

Note: This is just an example to illustrate how the Pegasus Email Notification works with common public email servers such as Google Gmail. Of course, there are many Email servers / programs out there having different levels of security limitations. Some can be resolved by lowering the security blocking, or some may not have these options. You may contact your email server provider for assistance if you can't receive any Email Notification from Pegasus.

My Pegasus J4 Crashes when I plug into a Mac running macOS Sierra 10.12.x. What do I do?

2016-10-12T18:29:31.4470000

We have fixed a kernel panic issue when the Pegasus J4 is plugged into a Mac host running 10.12.x.

The fix requires the user to install a beta driver located here:

Pegasus J4 Beta Driver for MacOS 10.12

Note that this driver is a beta and, therefore, is unsupported by our engineering and technical support department.

Increasing Storage Capacity on a Pegasus R(x) / Pegasus2 R(x)

2016-10-07T22:08:42.5930000

Increasing the Storage Capacity on a Pegasus R(x)/Pegasus2 R(x) Series

The storage capacity can be increased by purchasing higher capacity physical drives. In addition, Promise recommends that the drives that will be utilized have been cross-referenced with our Pegasus Compatibility List found on our Promise Support Site.

Pegasus Compatibility List V1.17

Pegasus2 Compatibility List V2.10

If you’re inquiring about upgrading the storage capacity for an array, you should purchase and replace each drive with the same capacity per each physical drive slot. If you replace a drive that has a larger space capacity, the drive will reduce its capacity to the smallest drive in the array.

For example, if you have a Pegasus2 R4 with 4 X 2TB drives and replace only one slot with a 4TB drive, the drive will actually allocate and equate to 2TB as the other three slots are configured with 2TB drives in the array. The remaining 2TB will be unusable. Therefore, you will not see an increase in the logical drive’s size after you’ve successfully rebuilt the previous drive’s sequence to the new drive.

Promise recommends to execute the following when upgrading the physical drive capacity on a Pegasus R(x)/Pegasus2 R(x)

1. Execute a backup of the data from the Pegasus volume to another destination volume.
2. After the data has been successfully copied to the destination volume, unmount the volume and shutdown the unit.
3. You can shut down the Pegasus unit by accessing the Pegasus Utility or accessing the CLI (OS X).
3A. [OS X]
Shutdown the unit by opening the [Pegasus Utility > Subsystem Information > Shutdown]
3B. You can also open a Terminal session (OS X):

HostName:~ user$ promiseutil
cliib> shutdown -a shutdown

3C. [Windows]
[Pegasus Utility > Admin > Subsystem Information > Shutdown]
4. After the unit has been shutdown, proceed in installing the new physical drives.
5. Turn the Pegasus unit back on.
6. Once the Pegasus unit has booted, proceed in configuring a new array and logical drive.
7. Once you created your new array and logical drive, proceed in copying the data from your backup.

If you have any questions or concerns, please open a support request via https://support.promise.com

Does Pegasus2 M4 Support TRIM?

2016-09-01T21:05:21.4870000

For TRIM feature to work, both the host Operating System and the devices must support the feature, and it must be enabled in both sides.

TRIM feature in Pegasus2 M4:

Promise’s Pegasus2 M4 is recognized as Serial Attached SCSI (SAS) device by Operating System regardless of what type of SSD is being used. With the latest FW version 5.04.0000.57, Pegasus2 M4 support TRIM feature is enabled by default. Users can manually disable the TRIM feature support in Pegasus2 M4 by command line: ctrl –a mod –s “trim=disable, but it is not recommended.

TRIM feature in Mac Operating System:

Current OS X (even the latest 10.11.x) ONLY supports TRIM feature for SSD in AHCI mode of SATA (Serial ATA) device, but not support for SAS device. Since Promise’s Pegasus2 M4 is recognized as SAS (Serial Attached SCSI) device under Mac Operating System. Therefore, the TRIM command will not be sent to Pegasus M4 SSD.

Mac OS X 10.12 may support TRIM feature for SAS device. We will update this document after next OS X version release.

TRIM feature in Windows Operating System:

In Windows 7, the situation is same as current Mac OS X situation.

Pegasus2 M4 SSD does not get benefit of TRIM feature because Windows 7 only support TRIM feature for SATA devices. TRIM feature in Windows 7 does not benefit to Pegasus2 M4 because it is recognized as SAS device by operating system.

In Windows 8.1 and Windows 10, TRIM feature is supported for SAS device and the setting is always enabled by default. Pegasus2 M4 SSD fully function with TRIM feature in these two operating systems.

My Mac cannot boot from my Pegasus device. What is wrong?

2016-03-23T14:12:03.7100000

Starting with systems that shipped with OS X 10.11.0, Apple no longer supports booting from external storage devices.

However, there is a workaround:

First enter Startup Manager by holding the Option key during boot
While in Startup Manager, press Shift+CMD+Option+Period. This will load the option ROMs and allow the user to select the bootable device. Note that this setting is not persistent and you will need to do this each time you’d like to boot from the external device.

For more information, please see here:

https://support.apple.com/en-us/HT205311

How do I disable Power Management on the Pegasus

2012-03-28T09:28:55.0000000

Start PromiseUtil to enable the Pegasus CLI.

Open a Terminal window on your Mac.
In the Mac Terminal window, type promiseutil to start the Pegasus Command Line Interface.
You will see a list of each Pegasus attached, and be given a cliib> prompt.

To disable Pegasus Power Management functions.

At the cliib> prompt type: ctrl -a mod -s "powermanagement=disable"

To enable Pegasus Power Management functions.

At the cliib> prompt type: ctrl -a mod -s "powermanagement=enable"

To view Pegasus Power Management status.

At the cliib> prompt type: ctrl -v
You will see in the settings: PowerManagement: Enable ( or Disable)

Pegasus Information Requirements when Contacting Technical Support

2011-10-28T12:03:42.0000000

Prior to calling Promise Technical Support for any Pegasus related problems, please capture and prepare the Service Report:

Open the Promise Utility, click on Subsystem Information, then unlock the padlock, and then click Save Service Report.
If this is successful, then it will open a new window for you to choose a folder to save the report. After that, you may use Finder to see that the file has been created in the folder.

If it is unable to save the Service Report, you can manually gather information using the method below.
Open the Mac OS Terminal session: In Finder, go to Applications, then open Utilities, then open Terminal.
At the "$" prompt, type promiseutil and press Enter. If Promise Utility is installed, this command will change the prompt to "CLIIB>".
At the "CLIIB>" prompt, type each of the following commands on their own line, pressing Enter after each one:

subsys -v

enclosure -v

ctrl -v

phydrv -v

array -v

logdrv -v
checktable -l 0
event

event -l nvram

Once that is done, then in the Applications folder, open TextEdit, and from File select New Document.

Select All from the Terminal window, and Copy the entire terminal session to your clipboard; then, Paste it into the TextEdit document. Finally, Save the TextEdit document as a "Rich Text File".

These logs are vital in assisting Technical Support for resolution of any issues.