Latest KB Articles

How to Save a Service Report from the PegasusM4 by using Promise Utility Pro

2025-11-06T07:10:15.7270000

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

1.Open the Promise Utility Pro, make sure that Pegasus M4 could be detected, and select it.

2.Go to controls tab > select M4 device > select three dots > Device Service Report.

The output will be a zip file.

Generating a service report is vital in assisting Technical Support with the resolution of Pegasus issues.

How to save a SMART log of HDD/SSD for further analysis?

2025-11-05T07:32:31.5630000

A SMART log (Self-Monitoring, Analysis, and Reporting Technology) is built into PROMISE Vtrak and Vess RAID storage systems that monitors the health and performance of the drive and SSD and then can predict potential failures. It logs various attributes like read error rates, seek error rates, spin-up time, and temperature, providing insights into the drive's condition. By analyzing these logs, technician can identify potential problems before they lead to data loss or drive failure.

Please follow these procedures to collect the SMART log.

1].Login the WebPAM PROe

1.1] Open browser and put the management portal IP

1.2] put administrator account

1.3] default password is password

2].Enable SMART log.

Go to Devices > Component List > Controller > Settings > Controller settings

3].Export SMART log.

Go to Administration > Import/Export > Export > Select "SMART log" from Drop-down menu

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.

Vess R2600: unable to SMB connect with Windows 11 24H2.

2025-10-24T17:20:05.4300000

Intro:

After updating to Windows 11 24H2 users find themseves unable to SMB mount a Vess R2600 share.

Discussion:

In Windows 11 24H2 Microsoft introduced SMB 3.1.1 and included many SMB security enhancements that broke older SMB implementations. This affects all older storage devices.

Many are searching for answers in the various forums and there are a lot of potential solutions, none of which have worked in practice.

We do not have a solution for this. The storage is working as designed but Microsoft has broken SMB.

Some work arounds...

Roll back to Windows 11 23H2.
Use NFS. The Windows NFS client will have to be installed.
Use FTP. Filezilla is an easy to use graphical interface FTP browser.

Other Promise Storage affected by the new Microsoft SMB:

Apollo SMB mount, cloud access is not affected.
SmartStor series.

How to save a SMART log of HDD/SSD for further analysis?

2025-07-09T05:22:30.6500000

Please follow these procedures to collect the SMART log.

1].Login the WebPAM PROe

1.1] Open browser and put the management IP portal

1.2] put administrator account

1.3] default password is password

2].Enable SMART log.

Go to Devices > Component List > Controller > Setting > Controller settings

3].Export SMART log.

Go to Administration > Import/Export > Export > SMART log

How to expand existing POOL for Pegasus R12

2025-06-02T03:32:02.9500000

The numbers of the chosen physical drives should support the current pool's RAID Level ; The same RAID level should be used for pool expansion.

1].Click the lock to Unlock first after lunch the Promise Utility Pro

2].Click the Controls tab

3].Put the password of the login user

4]. Go to Pools tab and select your pool and then click Expand function

5].Select physical drives you would like to expand. For this case, original pool is with RAID5 level so you at least select 3 disks to expand the pool.

6].Check these drives for the pool at Dashboard tab when pool-expand is done.

7]. Go to Pools tab and select your pool and then click Add Volume function

8].A new Pegasus Volume (VolumeName2) will be mounted after formatting it.

PegasusPro R8 Power consumption

2025-06-02T01:56:52.3870000

PegasusPro R8

System status	AC Input		Current (A)	Power Consumption (W)	Thermal Output
System status	Voltage (V)	Frequency (Hz)	Current (A)	Power Consumption (W)	(BTU/Hr)
Operation	110	60	2.394	262	894.206
Operation	230	50	1.133	259.2	884.6496

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

How to Change or Reset Your Apollo Password

2025-02-04T14:12:48.9200000

Method 1: Change Password via Settings

Log in to Apollo.
Go to "Settings."
Select "Change Password."
Enter your current password and set a new one.
Save the changes.

Method 2: Reset Password via "Recover Password" Option

If you forgot your password, follow these steps:

Go to the Apollo login page.
Click on "Recover Password."
Enter your registered email address (must be unchanged).
Follow the reset instructions sent to your email.

Note for macOS Users

Apollo may also appear on your Mac login screen. If available, you can access password recovery directly from there.

How to Generate a Service Report for the Pegasus R12

2025-02-03T23:14:18.2800000

Before reaching out to Promise Technical Support for assistance with your Pegasus R12, please follow these steps to generate and prepare a Service Report.

Method 1: Using Promise Utility Pro

Open Promise Utility Pro.
- If you don’t have it installed, you can download it here
Select the Pegasus R12.
- Once opened, click on your Pegasus R12 to access its Dashboard.
Generate the Service Report.
- Click Controls > Click the 3-dot menu > Select Device Service Report (bottom of the list).
Save the Report.
- Depending on your browser settings, the file will either be automatically saved to your Downloads folder or prompt you to choose a save location.

Method 2: Manual Collection via Terminal (MacOS)

If you cannot generate a Service Report using Promise Utility Pro, follow these manual steps:

1. Open Terminal:

Navigate to Applications > Utilities and open Terminal.

2. Enter the Following Commands:

At the "$" prompt, type the following and press Enter after each line:

cd /Applications/PROMISE\ Utility\ Pro.app/Contents/Resources
./promiseutil

The prompt will change to:

cliib>

Now, enter each of the following commands one at a time:

subsys -v
enclosure -v
ctrl -v
phydrv
phydrv -v
array -v
logdrv -v
checktable -l 0
event
event -l nvram
smart
bga

3. Save the Logs:

Open TextEdit (Applications > TextEdit).
Create a New Document.
Copy all the Terminal output and Paste it into TextEdit.
Save the file as a Rich Text File (.rtf) and name it servicereport.rtf.

Final Step: Attach to Support Case

These logs are essential for troubleshooting. Please attach the Service Report when submitting a support case.

For instructions on attaching files to a web support case, refer to this Promise KB article:
How to Attach Files to Your Web Case

How to Locate the OS Label Sticker with License Code on Your Machine

2025-02-02T14:18:54.4130000

If you own one of our machines (models 3340, 6120, or 6600), you might need to locate the Operating System (OS) label sticker with the license code for activation or troubleshooting. This guide will help you quickly find the sticker on each machine.

Model 3340

Location of the Sticker:
- The OS label sticker is located on the left panel of the machine.
- It is positioned near other labels, including the warning stickers and the serial number tag.
Description of the Sticker:
1. The OS label is rectangular and includes text such as "Windows® IoT" or "windows server."
2. The license code is a 25-character alphanumeric string.Look for a distinct color or design (e.g., green or blue background) that stands out among other labels.

Model 3120

Location of the Sticker:
- On this model, the OS label sticker is also on the Left panel, placed near the power supply warning label and the product serial number sticker.

Model 6600

Location of the Sticker:
- The OS label is located on the top surface near the back panel of the machine.
- It is placed adjacent to the compliance and certification labels (CE, UKCA, FCC).

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.

Enabling Jumbo Frame on Promise VTrak D5000 Series

2025-01-23T14:21:40.3370000

Jumbo Frames allow larger data packets to be transmitted, enhancing data transfer speeds. Follow these steps to configure Jumbo Frames effectively on your VTrak D5000 Series.

Step-by-Step Guide

Accessing the Management Interface
- Log in to the Promise VTrak management interface using your administrator credentials.
Navigating to Ethernet Port Settings
- Go to 'Device' and select 'Network Management'.
- Identify the specific 'IO Port' you want to modify under the 'Port' section.
Accessing IO Port Settings
- Within the chosen IO Port, click on 'Settings' to access the Ethernet port configurations.
Enabling Jumbo Frames
- Locate the 'Jumbo Frame' setting within the IO Port settings.
- Enable the Jumbo Frame option to allow larger data packets to be transmitted.
- Save the changes to activate Jumbo Frames for the selected IO Port.

Important Notes

Portals or Trunks Restrictions:
- Portals: If a portal exists on the port, it must be deleted before enabling Jumbo Frames. Afterward, you can recreate the portal.
- Trunks: If a trunk exists, delete any associated portals and then remove the trunk. Jumbo Frames can only be enabled once the trunk and portals are removed. After enabling, you can recreate the trunk and portals.

Optimizing Network Performance

For optimal performance, Jumbo Frames must also be enabled on both the Ethernet switch and the host clients connected to the VTrak D5000 Series.

A. Ethernet Switch Configuration

Refer to your Ethernet switch documentation.
Look for settings related to Jumbo Frames or Maximum Transmission Unit (MTU).
Adjust these settings for the ports connected to the VTrak D5000.

B. Host Client Configuration

Access the network adapter settings on your host client.
Locate the Jumbo Frames or MTU configuration.
Match the settings with those on the VTrak D5000 and Ethernet switch.

Ensure that all related devices (switches and host clients) are configured with matching MTU values. For more specific guidance, refer to the documentation for your Ethernet switch and host client network adapters.

Need Further Assistance?

For additional support:

Register your product and create a support case on our website.
Detailed instructions for submitting a support case can be found here:
Submitting a Support Case
Contact us at Support@promise.com

How to Reset the Admin Password for PegasusPro or VTrak N1616

2025-01-23T13:30:16.6700000

Follow these steps to reset the admin password for your PegasusPro R8/R16 or VTrak N1616:

Steps to Reset the Admin Password

Access the WebPAM InSight Login Page:
- Open your browser and navigate to the WebPAM InSight login page.
- Click on "Forgot Admin Password?"
Enter the Unit's Serial Number (S/N):
- Follow the on-screen prompts to input the unit's Serial Number (S/N).
- The Serial Number can be found on the back of the unit.

Need Further Assistance?

For additional support:

Register your product and create a support case on our website.
Detailed instructions for submitting a support case can be found here:
Submitting a Support Case

Warranty Information for VTrak D5000/E5000 and Vess R3600 Batteries

2025-01-17T15:39:50.1370000

The battery for the VTrak D5000/E5000 and Vess R3600 comes with a one-year warranty.

If the battery is over one year old, you will need to purchase a replacement.

Where to Purchase

The replacement battery module can be purchased here:
Battery Module for VTrak x5000 and Vess R3000

Battery Replacement Resources

For guidance on replacing the battery, refer to the following resources:

Vess R3600 Battery Replacement: KB Article
D5000/E5000 Series Battery Replacement: KB Article

For Further Assistance

If you have additional questions, please contact the Promise Sales Team at: 📧 sales@promise.com

How to Save a Service Report from the VTrak N1616

2025-01-17T15:21:22.0600000

When facing issues with the VTrak N1616, it is essential to prepare a Service Report before contacting Promise Technical Support. The Service Report provides crucial information to aid in troubleshooting and resolving issues.

Steps to Generate and Save a Service Report

Access WebPAM Insight
- Open a browser and navigate to the WebPAM Insight interface using the IP address of your VTrak N1616.
- Log in with your credentials.
Create the Service Report
- Locate the arrow icon in the WebPAM interface to reveal a drop-down menu.
- Select Create Service Report and click Download Service Report.
Save the Report
- A new window will appear, prompting you to choose a folder to save the Service Report.
- Select the desired folder and confirm.
- Use Finder (on macOS) or File Explorer (on Windows) to verify that the report has been saved in the chosen location.

Why the Service Report is Important

The Service Report contains vital details about the system's status and recent events, enabling Technical Support to diagnose and address your issue.

How to Attach the Service Report to a Support Case

Refer to this Promise KB article for detailed instructions on attaching files to a web support case.

How to Save a Service Report from the PegasusPro R8 or PegasusPro R16

2025-01-17T15:17:52.0100000

When facing issues with the PegasusPro R8 or PegasusPro R16, it is essential to prepare a Service Report before contacting Promise Technical Support. The Service Report provides crucial information to aid in troubleshooting and resolving issues.

Steps to Generate and Save a Service Report

Access WebPAM Insight
- Open a browser and navigate to the WebPAM Insight interface using the IP address of your PegasusPro.
- Log in with your credentials.
Create the Service Report
- Locate the arrow icon in the WebPAM interface to reveal a drop-down menu.
- Select Create Service Report and click Download Service Report.
Save the Report
- A new window will appear, prompting you to choose a folder to save the Service Report.
- Select the desired folder and confirm.
- Use Finder (on macOS) or File Explorer (on Windows) to verify that the report has been saved in the chosen location.

Why the Service Report is Important

The Service Report contains vital details about the system's status and recent events, enabling Technical Support to diagnose and address your issue.

How to Attach the Service Report to a Support Case

Refer to this Promise KB article for detailed instructions on attaching files to a web support case.

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 and Connecting to the Management Port on VTrak J5000 Series via Serial Connection

2025-01-06T14:46:02.5800000

Default Configuration:

DHCP Enabled by Default – Connect the VTrak J5000 to a DHCP-enabled network to automatically assign an IP address.
Retrieve the IP address from your router or use an IP scanner to locate the device.
Optionally, configure a static IP address after initial setup.

Steps for Serial Connection Setup

1. Identify the COM Port

Use Device Manager to check the available COM ports.
COM1 and COM2 are typically reserved by the OS, even if no physical port is available.
For modern systems without built-in serial ports, use a USB-to-Serial adapter (as shown in the example image).

Example: Adapter is recognized as COM10 in Device Manager.

2. Select a Terminal Emulator

Recommended Tool: Tera Term (Free Terminal Emulator).
- Displays active COM ports for easier selection.
- Quick and simple configuration.

Alternative Tools:

PuTTY
HyperTerminal (Windows Legacy).

3. Connect to the VTrak J5000

Baud Rate: 115200
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None

Open the terminal emulator and select the correct COM port (e.g., COM10).
Configure the connection settings as listed above.
Press Enter after connecting to see the login prompt.

4. Login and Configure Settings

Enter your login credentials (default: administrator/password).
Use CLI commands to retrieve or configure settings:
- To Check Current IP Address:
```
net -l
```
- To Set a Static IP Address:
```
net -m -i <IP_ADDRESS> -s <SUBNET_MASK> -g <GATEWAY>
```

Additional Tools and Documentation

Windows Utility – Use for network configuration and monitoring.
Product Manual – For in-depth configuration and troubleshooting steps.
Utility Product Manual – Additional information about the management utility.

Important Notes

Ensure the USB-to-Serial adapter drivers are installed and up-to-date.
For networks without DHCP, manual static IP assignment will be required.
Avoid using COM1/COM2, as these are often reserved by the operating system.
Keep the terminal log file if contacting Promise Technical Support for assistance.

Setting up a serial connection to Vess R3600 and collecting all logs using the Command Line Interface (CLI)

2024-12-30T13:45:33.9970000

Here’s a structured guide on setting up a serial connection to Vess R3600 and collecting all logs using the Command Line Interface (CLI).

1. Hardware Requirements

RJ11-to-DB9F cable (provided in the accessories box).
Computer (PC, Mac, Linux) with:
- Embedded Serial Port or
- USB-to-Serial Adapter for computers without serial ports.
Terminal Emulation Application such as:
- PuTTY (Windows)
- Tera Term (Windows)
- Minicom (Linux)
- Screen (Mac/Linux).

Promise RJ11-to-DB9F Cable

2. Connecting the Serial Cable

Plug the RJ11 end of the cable into the Vess RAID controller (left-hand serial connector).

2. Plug the DB9F end into your computer’s serial port or USB-to-Serial adapter.

USB-Serial Adapter

Computer Serial Port

3. Configuring the Terminal Emulator

Launch your terminal application.
Locate and select the appropriate COM port assigned to your serial connection. (For USB adapters, check your device manager to identify the assigned COM port).
Set the following serial communication settings:
- Baud Rate: 115200
- Data Bits: 8 bits
- Parity: None
- Stop Bits: 1
- Flow Control: None
Open the connection.
Press Enter or Return—you should see a login prompt.

4. Logging in to CLI

Enter your username and password.(Note: The default user name is administrator.The default password is password)
You will be greeted with the CLI prompt:
```
administrator@cli
```

5. Collecting Log Data

Enable session logging (if supported by the terminal application) or manually copy outputs into a text file.

Run the following commands one by one and save the outputs:

System Information

subsys -v
ctrl -v
enclosure -v
battery -v
net -v

Background Activities
```
bga
```

Fibre Channel Information

fc -v
fc -a list -t device
fc -a list -t initiator

Physical Drives
```
phydrv
phydrv -v
```
Array Information
```
array
array -v
```
Logical Drive Details
```
logdrv
logdrv -v
```
LUN Mapping
```
lunmap
```
Event Logs
```
event
event -l nvram
```
(Note: Last command has a lowercase 'L', not number '1').

6. Saving Logs

Enable Log Capture in the terminal emulator to save logs directly to a file.
Or, copy-paste the session output into a text document.

7. Provide Logs to Support

Send the saved log file to the Promise Technical Support Team as part of your support request.

Start Support Request Online:

Visit Promise Technology Support to create a support case.

Additional Notes

Custom Cable Requirements:
If building your own cable, refer to the serial pinout diagram below or attached in this article

Network Unavailability:
Serial access is a reliable fallback if network access is down.
Permissions:
Ensure you have administrator-level access to the RAID system for complete log collection.

This process ensures you can securely gather logs for troubleshooting even without network access.

ReInstalling a New OS on Promise VessA Series

2024-12-19T10:08:06.9830000

If you lose your old OS or accidentally remove critical system files, follow these steps to reinstall the operating system using the Promise VessA Image Writer Utility and the specified images for each VessA product:

Preparation Steps

Download Required Tools and Files
- Download the Promise VessA Image Writer Utility:
  - Download VessA Image Writer Utility
- Download the Appropriate OS Image for Your Machine:
  - Locate the OS version on the OS Sticker on the chassis.
  - Visit the Download Center on the Promise website, select the VessA product, and download the respective installation image under the Image Tab

Creating the Bootable USB Drive

Start the Image Writer Utility
- Insert a USB drive into your computer.
- Open the Image Writer Utility.
Set Up the USB Drive
- Select the USB drive from the list of available drives.
- Check the Perform Quick Format option.
Load and Write the OS Image
- Select the downloaded OS image.
- Click Write! to start writing the OS image to the USB drive.
- Wait for the process to finish.

Installing the New OS on the VessA Machine

Boot from the USB Drive
- Insert the prepared USB drive into the VessA machine.
- Power on the machine. It will boot directly from the USB.
Select Installation Options
- When prompted, choose between the following options:
  - Option C:
    - Updates the BIOS.
    - Installs the OS to the DOM module (includes drivers and software tools).
    - Deletes the old RAID configuration and creates a new RAID disk.
    - Warning: Selecting this option will erase the existing RAID configuration.
  - Option I:
    1. Updates the BIOS.
    2. Installs the OS to the DOM module (includes drivers and software tools).
      Important Notes
      - Power Stability: Keep the power source stable during the BIOS update to avoid corruption.
      - VessA3340 or certain Models: These may require additional reboots during the BIOS update phase.
      - RAID Warning: Selecting C Option will erase existing RAID configurations.
Choose RAID Configuration
- Select the desired RAID type for your setup.
- Wait for the installation to finish.

Finalizing the Installation

System Reboot
- During the process, the BIOS will be updated, and the system may reboot automatically.
- Do Not Remove Power during this process.
Shutdown and Remove USB
- Once the installation is complete, press Space to shut down the machine.
- Remove the USB drive before powering on the system again.
Set Up the Operating System

Power on the machine. It will boot directly into Windows.
Configure the initial settings:
- Select your language.
- Create a password.
- Add the activation key from the sticker on the chassis.

Your VessA Machine is Now Ready for Use

For any additional configurations, consult the VessA Product manual or contact Promise Technical Support.

Note: Always ensure a stable power source throughout the installation process to avoid interruptions.

Vess A3340p Power consumption

2024-12-04T13:52:56.9770000

These numbers are derived from fully populated Vess A3340P chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3340p	Operation	110	60	153.2	522.872
		240	50	157.2	536.524

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3340p	Standby Mode	110	60	102.9	351.198
		240	50	106.8	364.508

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3340p	Power on Max	110	60	183.1	624.920
		240	50	184.4	629.357

Vess A8600 Power consumption

2024-12-04T13:49:52.9100000

These numbers are derived from fully populated Vess A8600 chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A8600	Operation	110	60	259	883.967
		240	50	256.9	876.800

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A8600	Standby Mode	110	60	211	720.143
		240	50	210.1	717.071

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A8600	Power on Max	110	60	446	1522.198
		240	50	432.3	1475.440

Vess A6800p Power consumption

2024-12-04T13:46:21.7530000

These numbers are derived from fully populated Vess A6800P chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A6800p	Operation	110	60	315	1075.095
		240	50	312.9	1067.928

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A6800p	Standby Mode	110	60	243	829.359
		240	50	243.3	830.383

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A6800p	Power on Max	110	60	556	1897.628
		240	50	549	1873.737

Vess A3120p Power consumption

2024-12-04T13:35:19.7930000

These numbers are derived from fully populated Vess A3120P chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3120p	Operation	110	60	90.4	308.535
		240	50	92.2	314.679

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3120p	Standby Mode	110	60	57	194.541
		240	50	55.7	190.104

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3120p	Power on Max	110	60	116.9	398.980
		240	50	114.8	391.812

SMB Signing and Performance Issues on VTrak D5000 Series

2024-12-02T19:44:31.9930000

Overview of SMB Signing

SMB (Server Message Block) protocol facilitates file sharing, print services, and remote administration over networks.
SMB signing secures data by adding a digital signature to packets, preventing unauthorized tampering during transmission.
SMB Signing is supported across all SMB protocol versions.

Performance Impact
Enabling SMB Signing can cause a significant performance drop due to the additional CPU workload required to digitally sign each packet. For example:

Throughput can drop from 875 MiB/s to approximately 250 MiB/s during sequential read tests without multichannel support.

Mitigating Performance Issues
To reduce the performance degradation:

1. Deactivate SMB Signing on the D5000 Series

- Use the SMB Settings option in the D5000 series GUI to turn off Server Signing : NAS Share > Protocol > SMB > Settings

2. Deactivate SMB Signing on Clients

Procedures for disabling SMB Signing vary by operating system:

Windows: Modify registry or Group Policy settings.
Linux: Update smb.conf in Samba configuration.
Mac OS: Use terminal commands or modify SMB preferences.

Refer to reliable online resources or OS-specific documentation to find detailed steps for disabling SMB signing on client systems.

Updating Firmware for Pegasus M4 Using Promise Utility Pro

2024-12-02T12:45:46.6930000

To ensure optimal performance and security of your Pegasus M4, follow these steps to update the firmware seamlessly:

1. Access PROMISE Support

Visit the PROMISE support website:
Download Firmware for Pegasus M4.
Download the latest firmware image file (.img) to your Host PC or a TFTP server.

2. Preparation

Ensure no background activities are running on the RAID subsystem to avoid interruptions during the update process.

3. Open Promise Utility Pro

Launch Promise Utility Pro.
On the main page displaying connected Thunderbolt devices, locate the Firmware Update option.

4. Choose a Download Method

Select one of the two available options based on your setup:

a. Local File via HTTP

Click Choose File and locate the firmware image file saved on your system.
Select the file and click Open to proceed.

b. TFTP Server

Enter the TFTP server's host name or IP address, port number, and the file name of the firmware image.

5. Upload the Firmware File

Click the Choose File button and navigate to the firmware file location on your system.
Select the .img file and upload it.

6. Update the Firmware

Check the checkbox on the update window to confirm the update.
Initiate the update by selecting the Update option.

7. Wait for the Update Process

Allow the system a few seconds to complete the firmware update.

8. Restart the System

Once the update is finished, restart the system to apply the changes.

9. Verify the Firmware Version

After restarting, re-open Promise Utility Pro to verify that the firmware has been successfully updated.
The updated firmware version will be displayed in the device information section.

Important Notes:

Ensure a stable power source during the update process to avoid interruptions.
For any issues encountered during the update, refer to the user manual or contact PROMISE Technical Support.

Vess A RAID driver Update

2024-12-01T09:50:34.3130000

In this article, we delve into the essential steps and considerations involved in updating Vess-A RAID drivers.

First of All, you have to check the PKG version already installed on your machine.
Go to Promise WebPAM PROe.
After adding your credentials go to controllers and expand the list.

Click on the controller name.

Check the PKG version installed to download the latest one.

Now you can download the latest package.
Go to https://www.promise.com/Support/downloadcenter
Click the Vess Logo
Click on your machine

go to the drivers section select the Latest package from the list and download it.

Firstly you should stop any VMS services running as (Recording or Management).
Now you can install the downloaded package.
Now click the package to start the installation.

Click yes in the popup dialog.

Wait till extracting is finished.
Click yes in the popup dialog (Be note machine will reboot during the installation process).

Click Next, Click Install.

Wait till all Command Line windows finish and disappear.

Click Next.

Click Finish.

Click Restart Now to apply changes.

After reboot you can open WebPAM PROe and check the PKG version as mentioned before.
Also, you can check the new features and solved Issues in the new PKG by downloading the release notes from the Download Center

Importing a Certificate to Resolve SSL Error in Internet Explorer

2024-12-01T09:36:25.2270000

Follow these steps to resolve the SSL error encountered when using webPROe in Internet Explorer:

Introduction

When starting the Promise Server for the first time and configuring RAID via webPROe, you may encounter an SSL error while accessing the web interface through the desktop shortcut or system IP address.
To fix this issue, you need to install a trusted certificate for the server.

Download the certificate file here:
Certificate Download Link

Installing the Certificate

1. Access the Webpage

Click More Information on the SSL error screen.
Select Go on to the WebPage (Not Recommended) to proceed.

2. View the Certificate

On the browser's address bar, click the Certificate Error notification.
Select View Certificate from the dropdown menu.

3. Install the Certificate

Click Install Certificate in the certificate details window.
Choose Local Machine and click Next.

4. Specify the Certificate Store

Select Place all certificates in the following store and click Browse.
In the store selection window, choose Trusted Root Certification Authorities and click OK.
Click Next and then Finish to complete the installation.

5. Restart the Browser

Close Internet Explorer completely.
Reopen webPROe from the desktop shortcut or IP address.

Outcome

The SSL error should no longer appear when accessing webPROe.

Note

If the issue persists, ensure the downloaded certificate file is valid and that you followed the steps correctly.
For additional assistance, contact Promise Technical Support.

PROMISE Vess A8000 Series Introduction Video

2024-11-22T16:05:12.2800000

Pegasus M4 Product Introduction Video

2024-11-22T16:03:04.1870000

VessA 6600/6800 Power consumption

2024-11-21T14:08:15.0270000

The following data outlines the power consumption and thermal output for Vess A6600 and Vess A6800 systems under full load with fully populated SATA drives:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
Product	System status	Voltage (V)	Frequency (Hz)	Power Consumption (W)	(BTU/Hr)
Vess A6600 #1	Operation	110	60	236	805,468
	Operation	230	50	228	778,164
	Power on Max	110	60	538	1836,194
	Power on Max	230	50	523	1784,999
Vess A6600 #1	Operation	110	60	229	781,577
	Operation	230	50	227	774,751
	Power on Max	110	60	550	1877,15
	Power on Max	230	50	526	1795,238
Vess A6800 #2	Operation	110	60	312	1064,856
	Operation	230	50	307	1047,791
	Power on Max	110	60	773	2638,249
	Power on Max	230	50	750	2559,75
Vess A6800 #2	Operation	110	60	326	1112,638
	Operation	230	50	327	1116,051
	Power on Max	110	60	771	2631,423
	Power on Max	230	50	753	2569,989

VessA 7600/7800 Power consumption

2024-11-21T14:06:49.2730000

The following data outlines the power consumption and thermal output for Vess A7600 and Vess A7800 systems under full load with fully populated SATA drives:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A7800	Operation	110	60	356	1215,028
		240	50	355,9	1214,687

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A7600	Operation	110	60	262	894,206
		240	50	256,3	874,752

VTrak E5000 Series Tutorial Videos : Intro, Cabling, Initial Setup, Mount and Access and Support and Component Replacement

2024-11-20T17:58:25.0070000

Introduction

Cabling

Initial Setup

Mount and Access

Support and Component Replacement

VTrak J5960 Tutorial Videos

2024-11-20T17:49:35.2070000

Product Introduction

Product Installation and Cabling

Initial Configuration

Technical Support

PROMISE Vess A-Series Tutorial Videos

2024-11-20T17:46:30.7030000

Product Introduction

Product Installation And Cabling (Vess A3340)

Product Installation And Cabling (Vess A6800)

Initial Setup And Management

Support Case Registration

PROMISE Vess R3000 Series Tutorial Videos

2024-11-20T17:37:14.9330000

Product Introduction

Product Installation and Cabling

Web Configuration

Technical Support Case Registration

PROMISE VTrak D5000 Series Tutorial Videos

2024-11-20T14:57:08.3100000

Introduction

Hardware Installation & Cabling

Software Setup

I/O Testing & Bandwidth Capability

Service & Support

How to configure RAID on Vess A-Series Appliance for Milestone XProtect VMS

2024-11-20T14:53:25.7630000

PROMISE Pegasus Pro R8/R16 Tutorial Videos

2024-11-20T14:51:56.7300000

Product introduction

Hardware Cabling

Initial setup, management, and access

Service & Parts Replacement

Mac Pro with Pegasus R4i Performance

2024-11-20T14:48:00.2130000

Promise Pegasus R4i and Pegasus J2i Intro

2024-11-20T14:47:16.6030000

Instructional Video : How to Rebuild Drive in Promise Utility - Pegasus R4i

2024-11-20T14:45:55.3970000

Instructional Video: 1-Minute Pegasus R4i Installation on Mac Pro

2024-11-20T14:44:02.0530000

Instructional Video : 1-Minute Pegasus J2i Installation on Mac Pro

2024-11-20T14:43:06.9270000

Addressing Temperature Differences in the Pegasus R4i with Mac Pro

2024-11-20T14:41:15.8300000

The Pegasus R4i integrates seamlessly with the Mac Pro, leveraging its unique design to ensure proper cooling. However, in certain cases, users may observe higher temperatures in the last two drives (PDs 2 and 4), located closest to the front grille fans.

Key Considerations:
1. Adequate Airflow by Design:
- The Mac Pro's cooling system provides sufficient airflow for optimal performance.
- The Pegasus R4i has no reported systemic temperature-related issues under normal operation.

2. Temperature Variations:
- PDs 2 and 4 may have slightly higher temperatures due to their position closer to the front grille fans.

3. Automatic Fan Adjustments:
- The Mac Pro dynamically adjusts fan speeds if ambient temperatures rise, ensuring consistent cooling.

Options to Manually Adjust Fan Speeds:
If you wish to manually control fan speeds, third-party software such as Macs Fan Control by CrystalIdea can be used.

- Download Link: Macs Fan Control
- Features:
- Allows manual or automatic adjustment of fan speeds.
- Provides real-time temperature monitoring.

Recommendations:
- Regularly monitor drive temperatures through Promise Utility or similar tools to ensure they remain within acceptable ranges.
- Use Macs Fan Control if specific workloads or environments require additional cooling adjustments.
- Ensure the Mac Pro is operating in a well-ventilated environment to avoid unnecessary thermal buildup.

Instructional Video: How to swap a drive inside of the Pegasus R4i module.

2024-11-20T14:37:53.7200000

Instructional Video: How to save a Promise Utility Service report - PegasusR4i/J2i

2024-11-20T14:36:34.5770000

Instructional Video: Installing a second Promise drive to the J2i

2024-11-20T14:34:10.8430000

Expected Performance Results for Default RAID 5 Configuration on Pegasus32 R4, R6, and R8

2024-11-19T18:52:38.1970000

The 1MB sequential results are indicative of performance scenarios typical for video ingest and playback applications. These benchmarks measure the ability of the storage system to handle large, sequential data streams, which is crucial for smooth media workflows.

Key Insights:
- 1MB Sequential Benchmarks reflect real-world use cases such as video editing, rendering, and playback.
- The results align closely with performance expectations when tested with industry-standard tools like the Blackmagic Disk Speed Test.

Performance Testing:
- The benchmark used for these results is an internal tool developed for accurate assessments.
- Similar outcomes can be replicated using widely-available utilities such as Blackmagic Speed Test, which evaluates storage performance for media applications.

Application Context:
1. Video Ingest:High sequential read/write speeds ensure fast file transfers from cameras or other media sources.
2. Playback: Smooth and uninterrupted playback relies on the ability to deliver sequential data streams efficiently.

The Pegasus32 series provides high-performance storage solutions with Thunderbolt 3 and USB compatibility. Below are the expected performance results for the default RAID 5 configuration:

RAID 5	Pegasus32 R4	Pegasus32 R6	Pegasus32 R8
1MB Sequential READ (MBps)	702	1205	1643
1MB Sequential WRITE (MBps)	751	1241	1527

These benchmarks demonstrate the suitability of Pegasus systems for professional video workflows, providing confidence in their ability to meet the demands of media professionals.

Notes:

RAID 5 Configuration: Offers a balance between performance, capacity, and redundancy. This setup provides protection against a single drive failure while maintaining good speed.

For maximum performance, it is recommended to:

Use high-quality drives with matching specifications.
Ensure the Thunderbolt 3 connection is utilized for full throughput.
Keep firmware and software up to date.

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.

Replacing a Physical Drive in Pegasus R12

2024-11-15T15:56:49.9400000

A failed or problematic drive in the Pegasus R12 system is indicated by:

- Red Drive: Indicates a failed drive.
- Orange Drive: Indicates a problematic drive that may require replacement.
- Events Log: Provides additional information about drive issues.

Steps to Replace a Failed Drive:

1. Obtain a Replacement Drive:
Ensure the new drive matches the specifications of the original drive:
- Type: Hard Disk Drive (HDD)
- Interface: SATA (3 Gb/s or 6 Gb/s)
- Spin Speed: 7,200 RPM or 15,000 RPM
- Capacity: Equal to or larger than the failed drive

Note: While it is not mandatory to use the same make and model, doing so simplifies the replacement process.

2. Prepare for Replacement:
- You can replace the drive without shutting down the Pegasus unit.
- Identify the failed or problematic drive through the Promise Utility Pro user interface.

3. Replace the Drive:
- Remove the failed drive carefully.
- Insert the replacement drive into the same slot.

Follow detailed instructions for steps 2 and 3 using the references below:

4. Verify Drive Status:

- Check the Promise Utility Pro interface to ensure the system recognizes the new drive.
- Monitor the rebuild process if the RAID array starts rebuilding automatically.

Additional Notes:
- Always verify the new drive meets or exceeds the original drive's specifications.
- Use the Promise Utility Pro to monitor system health and log events for troubleshooting.

Drive numbering and LED indicators - Pegasus R12

2024-11-15T15:46:23.5730000

The drive carriers are numbered as shown below:

Drive LEDs are visible when the top of the enclosure is removed.

A green LED on the drive carrier indicates normal functionality, while a red LED signifies a problem with the drive.

Removing/Replacing a Drive in the Enclosure - Pegasus R12

2024-11-15T15:43:11.4930000

To replace a physical drive:

1. Slide the top cover of the enclosure toward the front of the device.

2. Lift the cover to expose the hard disk drives.

3.To remove a drive carrier, firmly grasp the handle and slide the carrier upward to fully remove the drive and carrier assembly. Each hard disk drive is secured to the carrier with four screws designed for this purpose. Remove the screws, replace the faulty hard disk with a new one of the same type and size, and secure it with the screws.

4. To replace the hard disk drive and carrier assembly, insert them in the same orientation as when they were removed. Slide the assembly in until it is firmly seated. The drive stays securely in place without any additional hardware, such as a latch, as it fits snugly into position.

5. To replace the top of the enclosure, follow the removal procedure in reverse. Slide the top toward the back of the device until it snaps into place. The new drive is now ready for use.

VTrak E5000 Series Power Consumption

2024-11-15T14:49:45.6370000

These numbers are derived from fully populated VTrak E5x00 chassis utilizing SAS drives under full load:

Product	Input Voltage (VAC)	Power (Watts)	Thermal Output (BTU/hour)
E5300fD	120	308	1051
E5320fD	120	357	1218
E5600fD	120	335	1143
E5800fD	120	421	1437
E5300fD	230	296	1011
E5320fD	230	348	1188
E5600fD	230	334	1140
E5800fD	230	417	1423

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.

Vess A3340d - Collecting Service Logs

2024-11-12T12:02:30.1300000

Vess A3340d - Collecting Service Logs

Service logs help diagnose issues by analyzing events, physical drive status, component details, firmware versions, and other system aspects. The Vess A3340d supports two methods for collecting these logs:

Method 1: Collect Service Logs via WebPAM PROe

Access WebPAM PROe:
- Open the WebPAM PROe desktop shortcut or use a browser.
- Enter: https://localhost:8443/ (Replace localhost with the configured IP address if accessing remotely)
Login:
- Enter the credentials:
  - Username: administrator
  - Password: password (default)
Navigate to Local Host:

Select Local Host from the left panel
Generate Report:
On the right side, click the Save button.
Download OPAS Logs:
The service report will generate, and OPAS logs will be downloaded.
Attach Logs to Support Case:
- Save the report and attach the logs when submitting a support case.
- Refer to the KB article for steps on creating and submitting a case.

Method 2: Collect Logs via USB (OPAS)

This method does not require GUI access and can be used if network access is unavailable.

Steps:

Prepare USB Drive:
- Format an empty USB drive as FAT32.
- Create a folder on the USB named: OPAS.
Insert USB into Vess A3340d:
- Eject the USB from the PC and insert it into the front USB port of the 3340d.
Wait for Beep Signals:
- A repeated beep will sound, indicating the logs are being collected.
- Wait until a long beep is heard and the USB LED stops flashing.
Remove USB Drive:
- Safely eject the USB from the Vess A3340d.
Retrieve Logs:
- Open the USB drive on your PC.
- Locate the OPAS output folder within the OPAS directory created earlier.

Important Notes:

Always format the USB to FAT32 for compatibility.
Use the long beep signal and LED stop as confirmation that the process has completed successfully.
Attach the logs collected to your support case when contacting Promise Technology Support for further assistance.

For additional help, visit Promise Technology Support.

Managing a Pegasus R12 with a modern macOS

2024-11-11T14:36:33.2030000

Using Pegasus R12 on a Modern Mac

To use a Pegasus R12 on a modern Mac, install the latest Pegasus R12 DEXT driver and PROMISE Utility Pro for storage management.

Downloads:

Installing the Pegasus R12 DEXT Driver for Thunderbolt Connection on macOS

The Pegasus R12 DEXT Driver must be installed before connecting the Pegasus R12 to the Thunderbolt port of your Mac with the Thunderbolt Cable. This driver supports macOS 12.4 or later.

Preliminary Check

Verify macOS Version: Click on the Apple symbol in the upper left corner and select About This Mac to confirm your system meets the macOS 12.4 or later requirement.

Installation Steps

1. Download the Driver: Use the provided link.

2. Run the Installer:

Double-click the downloaded .pkg file.
Click Continue when the installer menu appears.

3. Standard Installation:

Click Install and enter your password to authorize.
If reinstalling, enter your password to modify the existing driver.

4. Enable Driver Extensions:

If prompted with Driver Extension Blocked, go to System Settings > Extensions > Driver Extensions.
Click Allow and confirm with your Mac password.

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

5. Complete Installation: Once you see a success message, click Close.

6. Verify Installation: Check for the DEXT Driver Installer in Applications or Mac Terminal.

Use either of these methods to confirm successful installation:

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

Method #2: Mac Terminal

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 driver is installed but requires manual approval in your Mac security settings before it can function properly. Enable the PegasusPro DEXT Driver Installer via Driver Extensions and restart your Mac . After rebooting, run the following command again (systemextensionsctl list | grep pegasus) to confirm the driver status says "activated enabled"

Final Steps

Power Down the Pegasus R12: Press the power button to shut down the device
Reconnect and Restart: Power on the Pegasus R12 and connect it to the Mac with the Thunderbolt Cable.

Your Pegasus R12 is now ready to use with Thunderbolt on macOS.

Updating Firmware in a Pegasus R12

A. Online Firmware Update

Open PROMISE Utility Pro and go to the Firmware Update menu.
Use the Online option to check the firmware version. If an update is available, click Update.
The utility downloads and updates the firmware automatically.
Restart the computer once the process is complete. After rebooting, the Pegasus R12 will be ready to use.

B. Manual Firmware Update

Download Firmware: Pegasus R12 Firmware
Update Using PROMISE Utility Pro:
- Open PROMISE Utility Pro and go to Firmware Update.
- Click Update, then confirm the action in the pop-up menu.
- Drag the downloaded .img firmware file into the utility.
- The utility uploads and updates the firmware.
Complete Update: Restart the Mac after the process finishes.

The firmware update process is the same for both online and manual methods.

Notes

Always eject the Pegasus R12 volume before disconnecting it from the Mac.
Keep the PROMISE Utility Pro software updated for optimal performance.
Contact Promise Technology Support for assistance if you encounter any issues.

Battery Replacement Procedure on the D5000/E5000 Series

2024-11-06T15:10:00.4930000

This document provides a step-by-step guide for system administrators or technicians on how to properly replace the battery on Promise D5000 Series and Promise E5000 Series devices.

Applicable Models:

Battery Replacement Procedure

Step 1 – Shutdown the Controller

Access the GUI and navigate to Administration > Subsystem Information.
Select Shutdown for the subsystem or individual controllers (Controller 1 or Controller 2).
In this example, shutdown Controller 1.

Step 2 – Unplug the Target Controller

When the GUI connection to the controller is lost or shows the controller is shutting down, unplug the target controller.
If shutting down the entire subsystem, the PSU (Power Supply Unit) will stop output after completing its shutdown.
Turn off the PSU switch manually if needed and unplug Controller 1 to replace the battery.

Step 3 – Check LEDs and Disable Battery Power

Verify that all LEDs on the controller FRU (Field Replaceable Unit) are off after shutdown.
- If any LED remains ON or Flashing, the controller may be in C2F (Cache to Flash) mode.
- Wait 5 minutes; if LEDs remain on, press the Password Reset Switch (RSVD) to interrupt. If LEDs still remain on, document the case and contact Technical Support.

Step 4 – Wear Electrostatic Gloves and Bracelet

Wear electrostatic gloves and bracelet to prevent EMI damage to hardware components.

Step 5 – Unmount Screws and Cover

Remove the three screws securing the cover.

Step 6 – Unmount Screws and Battery

Remove the three screws securing the battery.

Step 7 – Mount the New Battery and Screws

Attach the new battery to the 2 x 13 battery connector header on the controller.
Secure it with the three screws.

Caution: Carefully align the battery to avoid damaging the connector.

Step 8 – Mount the Cover and Screws to the FRU

Reattach the top cover and secure with the three screws.

Step 9 – Insert Controller into Enclosure

Reinsert the controller FRU into the enclosure.
Wait for the controller to boot completely.
Verify in the GUI or CLI that the controller is recognized and has booted successfully.
- If the whole subsystem was shut down, manually turn on the two PSU switches after battery replacement on both controllers.

Additional Information – Battery Part Number (PN)

Always verify the part number (PN) on the battery's label:

G32800011007300 – 7.3V, 2000mAh Rechargeable Lithium-ion battery pack with two LG Cells (18650HD2, 2000mAh, 2S1P).

Contact Promise Technology Support

For further assistance, initiate your support request online for faster service. A technical support agent will be assigned to your case.

Promise Technology Technical Support >

How to save the Service Report in VTrak E5000 Series

2024-11-05T19:51:41.7000000

In most troubleshooting scenarios, Promise Support will require the Service report to diagnose the problem effectively. This report contains event logs, configuration details, and the status of all hardware components.

Saving from the Home Page :

Log in to the Web Interface of the unit.
Click the “Save Service Report” icon located at the top right corner of the screen to generate the report.

The report will be saved as a compressed zip folder.
Unzip the folder to view the generated report.

Note: Generating the report may take a few minutes depending on the size of the array configuration.

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

Troubleshooting USB Connection Issues with Pegasus 32

2024-11-04T13:21:55.1630000

If you experience connectivity issues when using a USB connection with your Pegasus 32, please ensure that the connection is made through Port A. Here’s a quick guide to resolve this:

1. Verify USB Port A Usage: Ensure the USB cable connects to Port A on the Pegasus 32. Port A is the USB 3.2 port marked with a computer icon.

2. Reconnect to Port A: To switch to Port A safely, follow these steps:
- Power Down the Host Computer: Completely shut down your computer to avoid data transfer interruptions.
- Switch the Cable to Port A: Move the USB connection to Port A on the Pegasus 32.
- Power On the Computer: Turn the computer back on, and the connection should now be stabilized through the correct port.

Using the designated Port A for USB connections ensures proper compatibility and performance with the Pegasus 32.

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

Managing a Pegasus32 with a modern macOS

2024-11-01T13:00:56.2770000

To use a Pegasus32 on a modern MAC, use the latest Pegasus32 driver. For Intel macOS, the driver is builtin. For M1/M2/M3 macOS use the DEXT driver v21.1.0-2

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

After installation, ensure to 'allow' the driver in System Settings on your Mac. For assistance, please refer to the Guide.

Managing a Pegasus32 with a modern macOS

To manage a Pegasu32 on a modern MAC, Use the latest Promise Utility, v4.06.0000.04

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

Updating firmware in a Pegasus32

Prior to utilizing the Pegasus32 with your Mac computer, it's crucial to complete the update procedure. Please be aware that the Pegasus32 firmware file isn't intended for Mac use; instead, it's utilized by the Promise Utility to update the Pegasus32 firmware.

Download and use the latest Pegasus32 firmware v6.06.0000.45

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

To update the firmware using the latest Promise Utility:

1. From the Admin drop-down menu in the menu bar of the Promise Utility, choose Firmware Update.

2. Click on the padlock icon to unlock the menu, and type in the password for your computer when the prompt appears.

3. Click the Choose File button and locate the .img file you downloaded.

4. Click the Submit button.

5. In the Confirmation box, type the word “confirm” in the field provided and click the Confirm button.

6. The process will take several seconds to complete. Once the process has completed, it is necessary to restart the computer.Once the computer is powered on and booted up, you may continue to use the Pegasus32.

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

Resolving SATA SSDs Compatibility Issues in VTrak/Vess Storage

2024-11-01T12:46:50.3370000

Issue:

When configuring your VTrak/Vess Storage, all SATA SSDs are showing as "not usable" despite being tested and qualified on our compatibility list.

Solution:

If you're encountering the "not usable" status for SATA SSDs in your VTrak/Vess Storage configuration, follow these steps to ensure proper setup:

1. Verify SSD Type: Confirm whether the SSD drives are SATA.
2. Use SATA to SAS Dongle: If the SSDs are SATA, you'll need a SATA to SAS dongle to ensure compatibility with your VTrak/Vess Storage. This dongle acts as an adapter, connecting SATA SSDs to the SAS interface of the storage system. SAS SSDs do not require the dongle.
3. Contact Sales Team: If you require a SATA to SAS dongle, get in touch with our regional Sales Team to place an order and purchase the necessary adapter for your SATA SSD drives.

Removing/Replacing a Drive in the Disk Carrier - Pegasus R12

2024-10-31T15:06:27.7770000

The Pegasus R12 arrives with all HDDs pre-installed in their carriers and securely seated in the enclosure. If an HDD needs replacement, follow these instructions to safely remove and replace the HDD within its carrier.

Important Notes:
- Use Identical Replacement Drives: Ensure the replacement HDD is the same model as the one being replaced. For the best performance and compatibility, all HDDs in the enclosure should match in model and type.

Steps to Replace an HDD in a Disk Carrier

Removing the HDD from the Disk Carrier:
1. Position the Assembly: Place the HDD and disk carrier assembly on a stable, secure surface (e.g., a table).

2. Unscrew the HDD: Remove the four screws securing the HDD in the carrier.
3. Detach the HDD: Carefully lift the carrier off the HDD without twisting or bending it.

Installing the New HDD in the Carrier:
1. Insert the New HDD: Place the new HDD (of the same type) into the carrier, aligning it properly.
2. Secure the Screws: Reinsert and tighten the four screws to secure the new HDD within the carrier.
3. Orient the Carrier Correctly: Ensure the handle on the carrier is positioned at the top of the HDD, while the bottom, where the SATA and power connectors are located, faces downwards to align with the enclosure’s SATA ports.

This orientation allows the connectors to engage properly, ensuring reliable contact and power transfer for the new drive.

Maintaining Proper Airflow for Pegasus R12

2024-10-31T15:00:12.1800000

To prevent overheating and ensure optimal performance of the Pegasus R12, it's essential to maintain proper ventilation around the device.

Key Guidelines:
- Clear Ventilation: Ensure that the air intake (top) and exhaust vents (bottom) are unobstructed, as blocking airflow may cause the system to overheat.
- Fan Functionality: The cooling fans pull cool air in through the top of the enclosure and expel heated air through the bottom. Keeping these areas clear allows the fans to regulate internal temperatures effectively.

- Secure HDDs and Top Cover: Confirm that all HDDs are properly seated and that the top cover is securely in place to maintain both airflow efficiency and protection of internal components.

Following these steps helps to prevent potential thermal issues, extending the lifespan and reliability of your Pegasus R12.

Thunderbolt Connection and Sleep Mode Behavior for Pegasus R12

2024-10-31T14:55:14.5670000

When the Thunderbolt connection to the Pegasus R12 is interrupted—either by powering off or restarting the connected Mac, or physically disconnecting the Thunderbolt cable—the Pegasus R12 will enter sleep mode rather than a complete shutdown.

This means the Pegasus R12 remains powered on but in a low-power state, ready to quickly resume operation when the Thunderbolt connection is restored.

Important Points
Interruption scenarios: The Pegasus R12 will enter sleep mode in the following cases:
- The connected Mac is powered off or restarted.
- The Thunderbolt cable is disconnected from the Pegasus R12.
- Not a complete shutdown: Entering sleep mode does not fully power down the device. To fully shut down the Pegasus R12, follow the shutdown procedures using either PROMISE Utility Pro or the Power Button as described here.

Note: Always ensure volumes are ejected or dismounted properly before disconnecting the Thunderbolt connection to avoid data issues.

How to Safely Shut Down the Pegasus R12

2024-10-31T14:50:41.4100000

Before proceeding with shutdown, always eject or dismount the connected Pegasus R12 volume(s). This ensures data integrity and safe power-down of the storage system.

Option 1: Using PROMISE Utility Pro

1. Open PROMISE Utility Pro.

2. Go to the Controls menu and click on the Device.

3. Click the Power Button icon and select Shut down the device.

4. A warning dialog will appear to prevent accidental shutdown. If your Pegasus R12 is part of a daisy chain (connected via Thunderbolt to other devices), those devices will also shut down.

5. Wait a few minutes for the shutdown process to complete. The Power Button LED on the front will light red during shutdown. Once the LED is off, you can safely disconnect the power cord.

Option 2: Using the Power Button

1. Eject or dismount the connected Pegasus R12 volume(s) first.
- On Mac, drag the volume icon into the Trash/Eject symbol, or right-click and choose Eject.
2. Touch and hold the Power Button on the device for about four seconds.
3. The shutdown process will begin, lighting the Power Button LED red during shutdown. Any devices connected via Thunderbolt behind the R12 will also enter shutdown mode.
4. Once the LED turns off, it’s safe to disconnect the power cord if needed.

Important: Always eject or dismount connected volumes before shutting down to prevent data loss or corruption.

Enabling multipathing (MPIO) on Windows Server 2019

2024-10-31T14:35:37.2000000

Introduction

In some storage configurations, it is possible to have multiple paths from the server to the storage. This is often done for redundant paths or higher bandwidth. Typically multipathing is used in Fibre Channel SANs, in SAS attached storage and in some iSCSI connections.

When there is a multipath configuration, Windows Disk Magagment tool will show the same device multiple times. In the example below the same LUN is seen 4 times by Windows Server.

But there is only (1) LUN. It will be necessary to enable Windows MPIO to see only that one LUN.

Enabling Windows MPIO

To enable Windows MPIO , from the Server Manager select Add Roles and Features.

MPIO is a feature, click Next until you get to the features. Scroll down and enable MPIO.

Click Next and click the Install button.

Once the install is complete, close the Wizard and reboot the server.

Once the server is booted, click the Start menu and type in MPIO

Click MPIO to open the MPIO applet. Select the Discover Multi-Paths tab on top, select the Promise device in Others and click Add.

Another restart will be required. After the reboot the Disk Management tool shows only one disk.

To change the pathing policy open the device manager and select properties for the multipath promise LUN.

Select the MPIO tab at the top and the drop-down menu shows the pathing policies Windows supports.

For best bandwidth Least Queue Depth is suggested.

For iSCSI

iSCSI multipathing is an option in the MPIO applet. Select the Discover Multi-Paths tab and click Add Support for iSCSI devices. Another reboot will be required.

Once Multipathing has been enabled the LUN can be formatted NTFS from the Disk Management console.

VessA 8020 Power consumption

2024-10-31T14:30:26.4630000

These numbers are derived from fully populated Vess A8020 chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
Product	System status	Voltage (V)	Frequency (Hz)	Power Consumption (W)	(BTU/Hr)
Vess A8020	Power on Max	110	60
	Power on Max	230	50
	Idle	110	60	36,7	125,2571
	Idle	230	50	36,2	123,5506
	Operation	110	60	77,9	265,8727
	Operation	230	50	80,7	275,4291

VessA 3340s / 3340d Power consumption

2024-10-31T14:29:31.4970000

These numbers are derived from fully populated Vess A 3340s / 3340d chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3340s	Operation	110	60	129,8	443,007
		240	50	127,9	436,523

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3340d	Operation	110	60	148,7	507,513
		240	50	151,3	516,387

VessA 3120 Power consumption

2024-10-31T14:28:43.5100000

These numbers are derived from fully populated Vess A 3120 chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
		Voltage (V)	Frequency (Hz)		(BTU/Hr)
A3120s	Operation	110	60	87,3	297,955
		240	50	86,2	294,201

PegasusPro R16 Power consumption

2024-10-31T14:27:48.3230000

These numbers are derived from fully populated PegasusPro R16 chassis utilizing SATA drives under full load:

Product	System status	AC Input		Power Consumption (W)	Thermal Output
Product	System status	Voltage (V)	Frequency (Hz)	Power Consumption (W)	(BTU/Hr)
PegasusPro R16	Operation	110	60	380	1296.94
	Operation	230	50	362.1	1235.8473
	Power on Max	110	60	450	1535.85
	Power on Max	230	50	430.7	1469.9791

Ex10: Password Reset

2024-10-31T14:26:15.2900000

Introduction:

There are many reasons why an Ex10 user might need to reset the administrator password. Some common reasons are...

Purchased the unit from a 3rd party
Password was forgotten or lost
IT admin who knew the password is no longer with the company

Unfortunatly, the password reset on the Ex10 is not as simple as with newer units where a button press will do the trick.

Requirements:

In order to reset the password there are several requirements.

confuser file
tftp server
access to the Ex10 on the same subnet
a serial connection to the Ex10

Warning:

If the Ex10 is dual controller, it is recommended to unseat controller 2 before doing a password reset on controller 1. That is, power down, unseat controller 2, then power on and do the password reset on controller 1. Then after controller 1 is booted with the reset password hot insert controller 2 and it will take it's configuration information (including the user database) from controller 1.

Process:

This KB will demonstrate the process with Windows 10, the process is the same for MAC or Linux, but different tools will be needed.

First, an appropiate serial cable will be needed. Promise ships 1 serial cable with each controller, so a dual controller Ex10 would ship with 2 cables. Often these are lost or unavailable, so a correct cable will have to be obtained.

This KB shows how to make the serial connection. The part about collecting logs is not relevant here.

https://kb.promise.com/thread/how-to-set-up-a-serial-connection-to-a-vtrak-system-and-collect-the-logs-using-the-command-line-interface

A tftp server will also be required. For windows I find the free tftpd32 or tftpd64 work well. Be advised that tftp is a very old protocol and won't work across subnets. The computer used should be on the same subnet or direct connected to the Ex10 for the tftp connection to be established.

The confuser files can be obtained here.

Channel:

https://www.dropbox.com/s/ou85k47a1zvnype/ex10_confuser_3_36_0000_00.zip?dl=0

MAC:

https://www.dropbox.com/s/iv4e63raf2nw2uc/ex10_confuser_10_6_2270_00.zip?dl=0

The tftp server root folder must be changed to the folder that contains the confuser file.

After connecting the serial port, power up the Ex10.

There are 2 possibilities. The first possibility is the the CMOS battery is dead and booting will take you directy to PBL_RAM, which is were the password reset will be done from.

The second possibility is that the CMOS battery is still working and it will be necessary to interrupt the boot with a ^C. This can be done during the 'Executing boot script in 30.000 seconds' countdown.

Built 10:56:48, Mar 18 2009

Platform Setup completed
+execs
Load & Run: PBL_RAM
+Request IP addr from DHCP server: .............................................
Ethernet eth0: MAC address 00:01:55:30:87:50
Can't get BOOTP info for device!

DHCP Enabled
Ethernet MAC address: 00:01:55:30:87:50
IP: 0.0.0.0/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0, DNS server IP: 0.0.0.0

PBL_RAM Ver 1.02.0000.03
Built 14:49:31, Aug 25 2009

== Executing boot script in 30.000 seconds - enter ^C to abort
^C> 26.190 sec
==> 26.180 sec
PBL_RAM>

Here DHCP is enabled but failed. So we will have to set a static IP. If DHCP is enabled and finds an IP address a static IP won't have to be set.

To set a static IP the 'net' command will have to be used. The syntax of the command is...

Ethernet Management Configuration Utility
net -d | -c | -i <Static IP> [-n <DNS Sever IP>] [-s <Subnet Mask>] [-g <Gateway>]

The command on the local network looks like this...

PBL_RAM> net -i 192.168.9.241 -s 255.0.0.0 -g 192.168.9.1
Set Virtual port options

DHCP Disabled
Setting IP Address to 192.168.9.241
Setting Subnet Mask to 255.0.0.0
Setting Gateway Address to 192.168.9.1
PBL_RAM>

Please note the netmask used is 255.0.0.0. For some reason if the actual netmask (255.255.255.0) is used, the port won't work. The netmask 255.0.0.0 should work with just about any network.

We can check the port by pinging a server, we will ping the gateway as a test.

PBL_RAM> ping -i 192.168.9.241 -h 192.168.9.1
Network PING - from 192.168.9.241 to 192.168.9.1
PING - received 10 of 10 expected
PBL_RAM>

We can now configure the tftp server by setting the root folder to the location of the confuser file...

Now we are ready to update the user information using the confuser file. From the PBL_RAM prompt. Be sure to write down the filename for the last step. Copying and pasting it in may not work. Also, tftpd64 shows you the computer's IP address (in the 'Server Interfaces' line), you can use this or find the IP from a cmd window with the 'ipconfig' command.

PBL_RAM> ptiflash -t -h 192.168.9.181 -f ex10_confuser_3_36_0000_00.img
-
... Erase from 0xf0160000-0xf0300000: .............
... Program from 0x02000908-0x021a0908 at 0xf0160000: .............
... Erase from 0xf1fe0000-0xf2000000: .
... Program from 0x04000000-0x04020000 at 0xf1fe0000: .
... Erase from 0xf1f80000-0xf1fa0000: .
... Program from 0x04020000-0x04040000 at 0xf1f80000: .
PBL_RAM>

The Ex10 user information and passwords have now been reset to defaults. To continue the boot...

Note: To boot from PBL_RAM the comand is 'execs'. If the controller battery is dead it will only boot to PBL_RAM and to boot the firmware the 'execs' command must be used. For a dual controller Ex10 let one controller boot to the login prompt before moving the serial cable to controller 2 and booting it with 'execs'.

PBL_RAM> execs
Software modules check OK
SDRAM Size: 0x20000000, OS Size: 0x0c000000
Flash size: 0x02000000, Flash blk size: 0x00020000, blk count: 0x00000100
Using base address 0x01008000 and length 0x001c3460
Loading software modules .......

-------------------------------------------------------------
Promise VTrak Command Line Interface (CLI) Utility
Version: 3.33.0000.00 Build Date: Sep 24, 2009
-------------------------------------------------------------

Login: administrator
Password: ********
-------------------------------------------------------------
Type help or ? to display all the available commands
Type menu to enter Menu Driven Configuration Utility
-------------------------------------------------------------

administrator@cli>

The default username/password, which is administrator/password should now work.

Note: the confuser file does not affect any data on disk.

After the Password Reset:

It is recommended that if the firmware is downrev, the first thing that should be done after the password reset and before putting the storage into production should be to update the firmware to the latest version available. It is recommended to update sequentially since it is not possible to update to the latest Ex10 service release from many of the older firmware releases.

Note: a firmware update also does not affect any data on disk.

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.

Newer browsers may block WebPAM on some EOL devices.

2024-10-31T14:20:52.2400000

Introduction:

Over the year browser security protocols have changed and improved. Web based interfaces use what is called Transport Layer Security (TLS). TLS has gone through 4 revisions, from TLS 1.0 to TLS 1.1 to TLS 1.2 and the current version is TLS 1.3.

Many web pages used to support only TLS 1.0, especially some government services web pages. All the major browser creators were planning on dropping all support for TLS 1.0 a few years back, but then Covid 19 hit and because many of those governemnt services required TLS 1.0, browsers allowed exceptions to be made for certain web sites. Today the ability to mark a webpage an exception is no longer an option. If an exception was not made in the browser several years ago, one cannot be added from any modern browser.

Problem:

Many older embedded devices, storage devices, home routers, etc... are still in service and work properly. But as only TLS 1.0 is suported by these devices, no modern browser will connect to the management interface. This includes some older Promise devices as well.

This is the error message from Firefox 102.0.1.

---

It will not be possible to connect to the Web Interface from this browser.

If an exception had been set several years ago connections to this IP will be allowed.

Once removed, an exception cannot be re-added.

Workaround:

While it is not possible to use the latest browsers, it is possible to use an older browser that allows TLS 1.0, and ideally use this browser only for this purpose. Chromium is perfect for this as it does not auto-update like Firefox and Chrome or like Safari which updates with macOS updates. Chromium is available for Linux, macOS and Windows.

Unfortunately the Chromium website does not have older builds available, and the instructions given are not easy to follow.

https://www.chromium.org/getting-involved/download-chromium/

There are many 3rd party repositaries which are better organized.

https://chromium.en.uptodown.com/windows/versions

The version tested with was build 93.0.4531, the current build is 105. Build 93.0.4531 can be downloaded from here...

https://chromium.en.uptodown.com/windows/download/3727432

This Chromium does not install, it's a portable version. Point the file manager to the downloads folder and unzip the file. Navigate to the Chrome folder, with Windows it's named Chrome-Win and run the Chrome.exe file. WebPAM for the device will work from this browser.

With Chromium it is possible to connect to the Ex30 WebPAM which only supports TLS 1.0.

The following Promise products will not connect with a modern browser.

VTrak Ex10
VTrak Ex30
VTrak A-class
Vess 1840i
SmartStor and other EOL NAS devices

For these systems please use the appropriate version of Chromium for your OS or an older version of any browser.

Enabling File Sharing of a Pegasus32 Volume

2024-10-31T14:18:17.4430000

Open Settings > System Preferences > Sharing
Make sure the service File Sharing is enabled ✔.

Click the + to open sub-Finder window and select your Pegasus volume that you would like to reshare.
Then click Add.

(Adding Pegasus Volume "Pegasus R32 R4")

You have now added your Pegasus volume as a Network Share with SMB. Select user permissions...

And now the file share is ready.

Users can access the Pegasus Volume by going to the Finder menu, click Go and then click Connect to Server

Creating a Service Report from the Pegasus32 Series using Promise Utility

2024-10-31T13:16:28.6030000

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.

The output will be an html file.

Generating a service report is vital in assisting Technical Support with the resolution of Pegasus 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/

VTrak J5960 Power Consumption

2024-10-31T13:14:16.0070000

VTrak J5960 Power Consumption

System status	Input Voltage	Frequency	Current (A)	Power Consumption (W)	Thermal Output
System status			Current (A)	Power Consumption (W)	(BTU/Hr)
Operation	110V	60Hz	6.14	673	2303.78
Operation	230V	50Hz	2.852	655	2235.52
Power on Max	110V	60Hz	9.36	1029	3511.98
Power on Max	230V	50Hz	4.647	1068	3645.08

VTrak N1616 Power Consumption

2024-10-31T13:12:45.1330000

VTrak N1616 Power Consumption


System status	AC Input		Current (A)	Power Consumption (W)	Thermal Output
System status	Voltage (V)	Frequency (Hz)	Current (A)	Power Consumption (W)	(BTU/Hr)
Normal Operation	110V	60Hz	2.643	290	989.77
Normal Operation	230V	50Hz	1.234	280.3	956.66
Max Power	110V	60Hz	3.714	408	1392.50
Max Power	230V	50Hz	1.742	400.7	1367.59

Updating Firmware on the VTrak D5000 Subsystem

2024-10-31T13:09:08.3500000

To update the firmware on the VTrak D5000, follow these steps:

1. Download the latest firmware image file from PROMISE support by visiting the website at http://www.promise.com/support/. Save the file to your Host PC or TFTP server.

2. Before proceeding, ensure that no background activities are running on the RAID subsystem.

3. Access the Administration tab and navigate to the Firmware Update section.

4. Choose a download option:
- Local File through HTTP: Click the "Choose File" button, locate the firmware image file on your system, select it, and click "Open."
- TFTP Server: Enter the TFTP Server host name or IP address, port number, and file name.

5. Optionally, you can check the "Non-disruptive Image Update (NDIU)" box. This feature updates the RAID controllers and I/O modules one at a time, allowing I/O operations to continue during the firmware update. Note that updates with this option take longer to complete and are only supported by dual controller models.

6. Click the "Download" button. The subsequent screen will display the Flash Image (firmware image file) Version Number and Build Date.

7. Click "Submit" to initiate the firmware update. The progress of the update will be shown.

Important: Do not power off the subsystem during the update and refrain from navigating to other screens until the firmware update operation is completed.

Once the update is finished, a message will prompt you to reboot the subsystem. Click "OK."

- If you selected the Disruptive Flash Method, the RAID subsystem and JBOD expansion units will automatically restart.
- If you chose the Non-Disruptive Flash Method, the system will automatically flash and restart the RAID controllers one at a time.

Automatic Restart: If the NDIU box was not checked, the RAID subsystem and JBOD expansion units will automatically restart. This action temporarily disrupts I/O operations and may cause your WebPAM PROe connection to drop. To reestablish the connection, follow these steps:

1. Wait for a minimum of two minutes.
2. Click "Logout" in the WebPAM PROe Header and then log in again. If you encounter login issues, wait for 30 seconds and try again.
3. In your browser, click "Logout" in the WebPAM PROe Header and then log in again. If you cannot log in immediately, wait for 30 seconds and try again.

Updating Firmware on the VTrak E5000 Subsystem

2024-10-31T13:07:17.6630000

To update the firmware on the VTrak E5000, follow these steps:

1. Download the latest firmware image file from PROMISE support by visiting the website at http://www.promise.com/support/. Save the file to your Host PC or TFTP server.

2. Before proceeding, ensure that no background activities are running on the RAID subsystem.

3. Access the Administration tab and navigate to the Firmware Update section.

6. Click the "Download" button. The subsequent screen will display the Flash Image (firmware image file) Version Number and Build Date.

7. Click "Submit" to initiate the firmware update. The progress of the update will be shown.

Important: Do not power off the subsystem during the update and refrain from navigating to other screens until the firmware update operation is completed.

Once the update is finished, a message will prompt you to reboot the subsystem. Click "OK."

Battery Reconditioning Process on VTrak E5000 Subsystem

2024-10-31T13:05:51.6930000

Battery reconditioning plays a crucial role in maintaining the power supply to the controller cache, ensuring data integrity in the event of a power failure, particularly for unwritten data residing in the cache. The process of reconditioning involves discharging and subsequently recharging the battery to optimize its overall capacity and performance. It is important to note that reconditioning is performed in the background, potentially impacting the input/output (I/O) performance. Once the reconditioning process is completed, the cycle count of the battery increases by one.Battery reconditioning is enabled and scheduled by default. It is set to run on the first Saturday of January, March, May, July, September, and November. However, it is possible to modify the reconditioning status and schedule according to specific requirements

For an immediate battery reconditioning, follow these steps:

1. Navigate to the Device tab.
2. Click on the Component List icon.
3. Select the desired battery, then click on the Recondition button.
4. If a battery reconditioning is already scheduled, a dialog menu will appear, providing an explanation. To proceed with immediate reconditioning, enter "confirm" in the designated field and click on the Confirm button.
- Please note that during the reconditioning process, the battery's remaining capacity and estimated hold time will fluctuate as a result of the discharge and recharge cycles. This behavior is normal.

To modify the scheduled battery reconditioning, follow these steps:

1. Access the Administration tab.
2. Click on the Background Activities icon, displaying the list of Background Activities.
3. Click on the Scheduler button.
4. Hover over Battery Reconditioning and click on the Settings button.
5. Make the necessary adjustments to the settings, such as:
- Start Time
- Uncheck the Enable This Schedule box to disable the activity.
- Recurrence Pattern
- Start From
- End On

Remember to save the changes by clicking on the Save button to apply the new settings.

Storage Migration from previous Promise storage solutions

2024-10-31T13:02:42.0500000

Introduction

Over time all things change, usually for the better. At one point the horse and buggy was the primary means of transportation, but with the invention of the horseless carriage travel by horse become less and less prevelant. Today you can ride a horse for recreation and almost any old-west landmark site will have a horse and buggy ride where they explain the history of the area and it's more interesting people.

The same is true with storage. Promise storage solutions started with the first IDE RAID card for the ISA bus in 2001 and in 2005 Promise introduced it's first storage subsystem, the M200 which came in form factors for 12 or 15 drives and supported RAID levels 0/1/1e/10/5/6 and 50.

Over the years Promise storage solutions have been favored for popular SAN solutions like XSAN.

Many who have gone the XSAN route have had a decade of service, but with the lessened support for XSAN and the improved storage and storage interfaces of today many are looking to migrate to a newer storage solution.

Migration Paths

Ex10/Ex30

For those with an Ex10 or Ex30 SAN, the Ex50 is the latest in the product line. The Ex50 has 16Gb Fibre Channel, 12Gb SAS for drives and in the backend, more memory and supports larger drives.

E5800 datasheet.

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

A-class/XSAN

There are several possible migration paths for the A-class and XSAN.

For those requiring large storage and full redundancy, the Vess R3600 and VTrak D5800 is the obvious migration path. The Vess R3600 and VTrak D5800 both support 10Gbe for NAS or iSCSI, 12Gb SAS for drives and all interconnects, and 16Gb fibre channel for those selecting the FC SKU.

Vess R3600 Datasheet

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

VTrak D5800 Datasheet

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

For those requiring less storage, the Pegasus Pro comes in 8 and 16 drive SKUs. The Pegasus Pro is single controller and single power supply, but offers 10Gbe for NAS.

Pegasus Pro datasheet

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

Pegasus 1/2/3

For Pegasus users the latest Pegasus is the Pegasus 32, supporting both USB 3 and Thunderbolt 3. Also available is the Pegasus M4 with 4 SSDs and Pegasus R12, supporting Thunderbolt 4.

Pegasus 32 datasheet

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

Pegasus M4 datasheet

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

Pegasus R12 datasheet

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

Product Comparison

Product	drives	Migrate to	drives	DAS	NAS	iSCSI	controllers	power supplies
Pegasus 1/2/3	2, 4 or 8	Pegasus 32/Pegasus M4/Pegasus R12	2, 4 or 8	x			1	1
SmartStor	2 or 4	PegasusPro / VTrak N1616	8 or 16	x	x	x	1	1 or 2
Ex10/Ex30	16 / 24	Ex50	16 or 24	x			2	2
Vess R2600	16	Vess R3600/D5800	16 / 24	x	x	x	2	2 or 3
A-class / XSAN	24	Vess R3600/D5800	16 / 24	x	x	x	2	2

Notes:

Pegasus Pro R8 has 1 power supply, the Pegasus Pro R16 / VTrak N1616 has 1 or optionally 2 power supplies
The Vess R2600 has 3 power supplies with a 4th optional
Fibre Channel products are DAS, the Vess R2600/R3600 and D5800 have SKUs with FC
XSANs were often built with the 16-drive Ex10
The Pegasus 1/2/3/32 are Thunderbolt 1/2/3/3 connected DAS
The Pegasus Pro supports both Thunderbolt 3 DAS and 10Gbe NAS
The Vess R2600, Vess R3600 and D5800 support 10Gbe for NAS
The Pegasus32 and Pegasus M4 supports USB 3 connections in addition to Thunderbolt 3
Smartstor supports NAS and iSCSI, but not DAS. the Pegasus Pro does not support iSCSI

Resolving Certificate Error by Importing Promise Root CA Certificate

2024-10-31T12:40:28.5100000

Overview

When you connect to Promise VTrak/Vess subsystems through a web browser, you might see a screen like the following.

Example of Chrome screen when connect to VTrak/Vess subsystem:

Example of Firefox screen when connect to VTrak/Vess subsystem:

This is very commonly seen on HTTPS with embedded devices. The HTTPS service from VTrak/Vess subsystem does not actually impose any security threat. You can click on the “Advanced” button to continue and accept risks for unsecure communications.

For secure communication between web browser and VTrak/Vess subsystem, here is the solution to import Promise Root CA certificate to web browser’s trusted root certificate list.

Before importing a Promise Root CA certificate, your web browser will alert you when connecting to VTrak/Vess subsystem using HTTPS, it is because the web browser is unsure if the fields received from the Promise certificate are valid. After importing Promise Root CA certificate, the web browser will recognize received Promise certificate as authentic, because the received certificate matches trusted Promise self-signed root CA certificate.

Using Promise certificate and Promise root CA certificate can improve the security and credibility from VTrak/Vess subsystem’s web server.

The procedure is simple, just follow these instructions:
First, download the Promise Root CA certificate
Second, follow the instructions below to import Promise Root CA certificate to the web browser’s trusted certificate list on your computer.

Please check procedure below for the detailed operations for Chrome, Firefox and Edge browser.

Import Promise Root CA Certificate in Chrome browser

Open Google Chrome, then click icon from menu icon on right top of screen, then choose ‘Settings’ from menu options.

On the Chrome Settings page and click ‘Privacy and Security’ in the left-hand column.

Then click 'Security' and scroll down to 'Manage device certificates'

Under the ‘Certificates’ window, please choose ‘Trusted Root Certification Authorities’ tab and then click ‘Import’ button to choose certificate file ‘Promise root certificate.cer’ and start the certification installation process.

Once the Promise root CA certificate is installed it will be displayed under the ‘Trusted Root Certification Authorities’ tab.

Import Promise Root CA Certificate on Firefox browser

Open Mozilla Firefox, then click icon from menu icon on right top of screen, and then choose ‘Settings’ from menu options.

On the Firefox Settings page, please click ‘Privacy and Security' and then scroll down to choose ‘Certificates’ in the left-hand column. Then click ‘View Certificates’ button.

Under the ‘Certificates Manager’ window, please choose ‘Authorities’ tab and then click ‘Import’ button to choose certificate file ‘Promise root certificate.cer’ and enable ‘Trust this CA to identify websites.’ checkbox to start the certification installation process.

Once the Promise root CA certificate is installed it will be displayed under ‘Authorities’ tab.

Import Promise Root CA Certificate on Edge browser

Open Microsoft Edge, and then choose ‘Settings’ by clicking icon from menu icon on right bottom of screen.

On the Edge ‘Settings page’, please click ‘Privacy, search and services' and then scroll down to choose ‘Security’ and ‘Manage certificates’ in the left-hand column.

Under the ‘Certificates’ window, please choose ‘Trusted Root Certification Authorities’ tab and then click ‘Import’ button to choose certificate file ‘Promise root certificate.cer’ and start the certification installation process.

Once the Promise root CA certificate is installed it will be displayed under the ‘Trusted Root Certification Authorities’ tab.

Disable VMware ATS-only Flag in D5000/R3000

2024-10-31T12:33:02.6930000

8.1 Check ATS-only command list

The problem arises when mounting the VMware datastore while the D5000/R3000 VAAI is enabled, as it results in the datastore being marked as ATS-only. Consequently, disabling the D5000/R3000 VAAI at this stage leads to the VMware datastore being flagged as abnormal.Follow the steps below to avoid this exception.

8.1.1 Check the volume or datastore ATS status:

vmkfstools -Ph -v1 /vmfs/volumes/VMFS-volume-name(Datastore name)

8.1.2. Change the ATS status:

vmkfstools --configATSOnly 0 device path(Volume name)

vmkfstools --configATSOnly 1 device path(Volume name

8.2. Example

The following steps demonstrate the change of VMware ATS-only flag for several cases.

A. Mount VMware datastore while D5K/R3K VAAI disabled.

ATS-only flag will not be enabled for the datastore in such condition.

B. Mount VMware datastore while D5K/R3K VAAI enabled.

ATS-only flag will be enabled for the datastore in such condition.

C. Disable D5K/R3K VAAI while VMware datastore is mounted.

Datastore with ATS-only flag enabled will become abnormal.

D. Disable ATS-only flag before disable VAAI support in D5K/R3K

Make sure the ATS-only flag is not enabled before disable VAAI support in D5K/R3K, so the datastore can be normal.

8.2.1 Mount VMware datastore while D5K/R3K VAAI disabled.

A. Mount 4*VMware datastores while D5K/R3K VAAI disabled.

Refer “8.2.1.a” as below.

4*VMware datastores not support VAAI, VMware field “Hardware Acceleration” is unknown.
The 4 datastores named “p1v1_vaai_d_std”,”p1v2_vaai_d_std”,”p2v1_vaai_d_adv” and “p2v2_vaai_d_adv”.

[Figure 8.2.1.a]

B. ATS-only flag will not be enabled for these 4 datastores.

Refer “8.2.1.b” as below.

In ESXi CLI excute “vmkfstools –Ph –v1 /vmfs/volumes/p1v1_vaai_d_std”
The field “Mode” value is “public”, it’s means no “ATS-only” enabled.

[Figure 8.2.1.b]

8.2.2 . Mount VMware datastore while D5K/R3K VAAI enabled.

A. Mount VMware datastore while D5K/R3K VAAI enabled. Refer “8.2.2.a” as below.

The old 4 VMware datastores support VAAI, VMware field “Hardware Acceleration” is supported.
The old 4 VMware datastores named “p1v1_vaai_d_std”,”p1v2_vaai_d_std”, ”p2v1_vaai_d_adv” and “p2v2_vaai_d_adv”.
The new 4 VMware datastores support VAAI, VMware field “Hardware Acceleration” is supported.
The new 4 VMware datastores named “p1v1_vaai_e_std”,”p1v2_vaai_e_std”,”p2v1_vaai_e_adv” and “p2v2_vaai_e_adv”.

[Figure 8.2.2.a]

b.Check ATS-only flag for the 4 old datastores, the datastores created before VAAI enable.Refer “8.2.2.b” as below.

In ESXi CLI excute “vmkfstools –Ph –v1 /vmfs/volumes/p1v1_vaai_d_std”
The field “Mode” value is “public”, it means no “ATS-only” enabled.

[Figure 8.2.2.b]

C. ATS-only flag will be enabled for the new 4 datastores created after VAAI enable. Refer to “8.2.2.C” as below.

In ESXi CLI excute “vmkfstools –Ph –v1 /vmfs/volumes/p1v1_vaai_e_std”
The field “Mode” value is “public ATS-only”, it means “ATS-only” enabled.

[Figure 8.2.2.C]

8.2.3. Disable D5K/R3K VAAI while VMware datastore is mounted

In 8.2.1 and 8.2.2, we created 8 datastore.

4 datastores are created before the VAAI enabled and the other 4 are after VAAI enabled.

We disable the VAAI function in D5K/R3K and get the following result. Refer to “8.2.3.a” as below.

A. Disable VAAI function on D5K/R5K.

B. 4 datastores created when VAAI disabled, is good

“p1v1_vaai_d_std”,”p1v2_vaai_d_std”,”p2v1_vaai_d_adv” and “p2v2_vaai_d_adv”.

C. 4 datastores created when VAAI enabled, might be fail, miss, or inaccessible.

“p1v1_vaai_e_std”,”p1v2_vaai_e_std”,”p2v1_vaai_e_adv” and “p2v2_vaai_e_adv”.

D. “ATS-only” flag of VMware datstore will be affected when storage’s VAAI enable/disable.

[Figure 8.2.3.a]

We can use VMware tools “vmfstool” to check datastore status and disable the ATS-only flag.

E. Use VMware “vmfstool” to check datastore ATS-only will fail. Refer “8.2.3.e” as below.

In ESXi CLI excute “vmkfstools –Ph –v1 /vmfs/volumes/p1v1_vaai_e_std”
The 4 failed datastore cannot be manipulated and “vmkfstools” show the error message.

[Figure 8.2.3.e]

F. Use VMware “vmfstool” to remove datastore ATS-only flag will fail. Refer “8.2.3.f” as below.

In ESXi CLI excute “vmkfstools –configATSOnly 0 eui.22980001552754a2
The 4 failed datastore cannot be manipulated and “vmkfstools” show the error message.

[Figure 8.2.3.f]

G. Disable ATS-only flag before disable VAAI support in D5K/R3K

We must disable datastore ATS-only flag before disable VAAI in D5K/R3K.

Refer “8.2.3.g” as below.

In ESXi CLI execute “vmkfstools –configATSOnly 0 eui.22980001552754a2

Refer “8.2.3.h” as below.

In ESXi CLI execute “vmkfstools –Ph –v1 /vmfs/volumes/p1v1_vaai_e_std”

[Figure 8.2.3.g]

[Figure 8.2.3.h]

H. Disable VAAI support in D5K/R3K.

I. Check VAAI status in VMware ESXI/VCenter.

Refer “8.2.3.i” as below.

Best Practices for VMware for VTrak D5000 and Vess R3000

2024-10-31T12:22:07.7370000

This guide provides best practices for utilizing D5000/R3000 with VMware ESXi version 5 or higher. The following topics will be covered in this article: RAID Levels, Expansion Chassis, LUN Affinity, ALUA and VAAI Support

RAID: RAID stands for Redundant Array of Independent Disks. When it comes to VMware usage, we recommend using one of the two RAID configurations mentioned below:

RAID 5 (Stripe with Parity): This configuration offers optimal read/write speeds with less overhead, resulting in superior performance.
RAID 6 (Stripe with Dual Parity): This configuration is ideal for Archival Storage, providing dual redundancy and superior fault tolerance.

RAID 0 (Stripe): It is not recommended to use a stripe volume as it offers little performance benefit and does not provide any fault tolerance for the volume.

J3000/J5000 Expansion Chassis: If you have an expansion chassis connected to your VTrak D5000 and Vess R3000 unit, you have the option to increase storage capacity for your VM configuration. However, it is not recommended to span enclosures and create a single large RAID array volume using the RAID Engine.

For optimal performance, it is recommended to have each enclosure contain separate disk arrays. RAID configurations spanning enclosures will require either RAID 50 or RAID 60.

LUN Affinity: To optimize performance, it is recommended to enable LUN Affinity for Dual controller in VTrak D5000 and Vess R3000 units. Enabling LUN Affinity improves write performance and enhances stability. While VMware has been certified with LUN Affinity disabled, Promise Technology recommends enabling it for the best performance.

ALUA: ALUA, which stands for Asynchronous Logical Unit Access, must be enabled for VMware optimization. VMware 5x and higher are ALUA aware, and it is recommended to have this feature enabled for improved overall performance on the unit.

VAAI (VMware API Array Integration): VAAI is a VMware special configuration API that allows offloading of certain storage tasks from the ESXi server to the storage array. It is also referred to as hardware acceleration.

The latest firmware versions for both VTrak/Vess storage units offer VAAI support, which can be enabled or disabled. Since VAAI is specific to VMware, only VMware systems make use of this feature.

To enable the VAAI feature on the VTrak D5000 and Vess R3000, you may use the WEBPAM PROe GUI or the Command Line Interface (CLI).

VTrak D5000 and Vess R3000 Configuration Details

1.1. Enable VTrak D5000 and Vess R3000 VAAI Function

1.1.1 Use the CLI mode to enable VAAI function in D5000/R3000

A. SSH/Console go to controller CLI and login(administrator/password)

B. Check controller1 VAAI function status -> ctrl –v –i 1

Check controller2 VAAI function status -> ctrl –v –i 2

Check controller1 & controller2 -> ctrl -v

C. Controller list information “VAAIsupport” default is disabled.

->VAAIsupport=disabled

D. Enable controller1 VAAIsupport -> ctrl –a mod –s “vaaisupport=enable”

E. Check controller1 VAAI function status -> ctrl –v –i 1.

Check controller2 VAAI function status-> ctrl –v –i 2

1.1.2 Use the GUI to enable VAAI function in D5000/R3000

A. Login to Web-GUI (administrator/password)

B. In “HOME” page, click following step to go to the VAAI setup page:

Click “Device”
Click “Component List”.
In “Component List”, select the controller ID=1 (or ID=2).

Click the setup button and slect “Settings”.

C. In “Controller Setting” page, click as following step to enable the VAAI function :

Select the “Enable VAAI” and enable the checkbox.
Click “SAVE” button

2.1 Disable VTrak D5000 and Vess R3000 VAAI

Note: If the datastore is using ATS-only locking, please refer to KB article to disable the ATS-only flag.

https://kb.promise.com/thread/disable-vmware-ats-only-flag-in-d5000-r3000/

2.1.1 Use the CLI mode to enable VAAI function in D5000/R3000

A. SSH/Console enter controller CLI and login (administrator/password)

B. Check controller1 status -> ctrl –v –i 1

Check controller2 status -> ctrl –v –i 2

※ Check controller1 & controller2 -> ctrl -v

C. Controller list information “VAAIsupport” is enabled.

VAAIsupport=enabled

D. Disable controller1 VAAIsupport -> ctrl –a mod –s “vaaisupport=disable”

E. Check controller1 VAAI function status -> ctrl –v –i 1

Check controller2 VAAI function status -> ctrl –v –i 2

2.1.2 Use the GUI to disable VAAI function in D5000/R3000

A. Login to Web-GUI (administrator/password)

B. In “HOME” page, click following step to go to the VAAI setup page:

Click “Device”
Click “Component List”.
In “Component List”, select the controller ID=1 (or ID=2).

Click the setup button and slect “Settings”.

C. In “Controller Setting” page, click as following step to enable the VAAI function :

Select the “Enable VAAI” and enable the checkbox.
Click “SAVE” button.

VTrak J5000 Series Power Consumption

2024-10-30T19:20:08.3730000

Power and BTU data for J5000 family.

These values are measured from fully populated VTrak J5x00 chassis utilizing SAS drives at idle and under full load (Max value).

Product	Input Voltage (VAC)	Power (Watts)	Thermal Output (BTU/hour)	Max Power (Watts)	Max Thermal Output (BTU/hr)
J5600sD	120	225.5	769.6	398	1358.4
J5800sD	120	304	1037.6	474	1617.8
J5300sD	120	192	655.3	357	1218.4
J5320sD	120	228	778.2	272	928.3

J5600sD	230	220.4	752.2	383.6	1309.2
J5800sD	230	298.9	1020.1	458.5	1564.9
J5300sD	230	189.3	646.1	351.1	1198.3
J5320sD	230	242.4	827.3	374.4	1277.8

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.

Replacing a Power Supply on Vess A6600

2024-10-30T18:51:01.1270000

The Vess A6600 systems can accommodate two AC power supplies in the bay at the rear of the chassis. The Vess A6800 systems can accommodate three AC power supplies in the bay at the rear of the chassis. Each unit provides up to 550 Watts of power. Only a single power supply is required for operation, with the second power supply purely as a redundant, load-sharing backup. It can be removed without affecting system operation.

Installing and Removing the Power Supply

Align the power supply unit with the power supply slot. Ensure that the LED appears on the left when you are installing the power supply unit.
Carefully slide the PSU all the way into the power supply bay until it clicks into place.

Removing the Power Supply Unit

To remove a failed power supply, please first identify the failed power supply .

Hold onto the power supply handle while pressing the locking lever towards the power supply handle.
Pull to remove the power supply from the chassis.

NOTE:

Before replacing the power supply, power off the server, unplug the power cord, and disconnect all wiring from the power supply.
In a redundant system, you do not need to power down the server.

Setting up Email Service in Vess A6600

2024-10-30T18:50:04.5330000

Email service enables the RAID subsystem to send you Email messages about events and status changes. By default, Email service is set to Automatic.

Stop Email Service To stop the Email service:

Click the Administrative Tools icon.
Click the Software Management icon.
Click on Email in the Service List of the Service Management menu.
Click the Stop button under Service Status -- Email.
Click the Confirm button.

To start the Email service after stopping it:

Click the Administrative Tools icon.
Click the Software Management icon.
Click on Email in the Service List of the Service Management menu.
Click the Start button under Service Status -- Email.
Click the Confirm button.

Restarting Email Service

To restart the Email service:

Click the Administrative Tools icon.
Click the Software Management icon.
Click on Email in the Service List of the Service Management menu.
Click the Restart button under Service Status -- Email.
Click the Confirm button.

Email Settings

To change Email service settings:

Click the Administrative Tools icon.
Click the Software Management icon.
Click on Email in the Service List of the Service Management menu.
Make settings changes as required:

Under Service Setting -- Email choose a startup type:

• Automatic – (default) Starts and runs with the subsystem.

• Manual – You start the service when you need it.

Under Email Server Settings

• SMTP Server IP address

• SMTP Authentication under Email Server Settings -The Yes option enables authentication. The No option disables.

• SMTP Authentication under Email Server Settings: Username – Required if SMTP authentication is enabled, SMTP Authentication Password – Required if SMTP authentication is enabled.

Under Email Content Customization

• Email Sender (From) Address – The sender’s name shown on notification messages.

• Email Subject – The subject line of the notification message.

5. Click the Submit button.

6. Click the Confirm button.

Sending A Test Email Message

After email settings are completed, you can send a test email. To send a test email message, complete email settings as described above and check the Send a test email option box, then click the Submit button. A test email message is sent to the address you specified.

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

Creating and Managing Data Pools in VTrak D5000 Series / Vess R3600 Series

2024-10-30T18:32:02.6800000

To set up a new storage pool, start by deciding which type of pool fits your needs. There are two options:

1. Standard Pool: This is best for applications that require performance and enhanced response times. It's great for uses like video surveillance, rich media, and IT applications. Keep in mind that standard pools don't offer data services such as Snapshot, Clone, Replication, or Migration.

2. Advanced Pool: This is tailored for backup and archive purposes and includes various data services.

For Standard Pools, remember the following limitations:
- They can't be expanded.
- NAS shares or volumes within standard pools can't exceed the largest contiguous space available.

Vtrak D5000/E5000/EX10/EX30 Hard Drives Compatibility list Summary

2024-10-30T18:30:13.6970000

D5000

The D5000 (5320,5300,5600,5605,5800,5805) systems are compatible with various hard drives, including SATA, SAS Hard Drives and SAS, SATA Solid State Drives.

Some supported hard drive models include the Toshiba Enterprise series, Western Digital Gold, HGST Ultrastar and Seagate EXOS for SATA and SAS HDD. Huawei, micron, Samsung and KIOXIA for SAS and SATA SSD.

The largest capacity compatible with the D5000 systems is 22TB for The HGST Ultrastar DC HC570 SATA, SAS / 3.5". For SAS SSD 7.68TB for the KIOXIA PM7-R Series 2.5" and 4TB for Western Digital RED SA500 NAS Serien for SAS SSD.

The D5000 systems are compatible with a range of interface speeds 12Gb/s for SAS HDD and 6,12,24 Gb/s for SAS SSD.

D5000 Supports various OS systems, the supported versions include Mac OS 10.12.6 and MacOS Ventura 13.1. On the Windows side, the compatible versions are Windows Server 2008,2012,2016,2019 and 2022. Also RED hat, VMware and Citrix. Veeam Backup Applications Certified.

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

E5000

The E5000 (FA5310,5320,5300,5600,5800) systems are compatible with various hard drives, including SATA, SAS Hard Drives and SAS, SATA Solid State Drives.

Some supported hard drive models include the Toshiba Enterprise series, Western Digital Ultrastar Enterprise, HGST Ultrastar and Seagate Enterprise, EXOS for SATA and SAS HDD. Huawei, micron, Samsung and KIOXIA for SAS and SATA SSD.

The largest capacity compatible with the E5000 systems is 22TB for The HGST Ultrastar DC HC570 SAS, 20TB Toshiba MG10 Series and WD Ultrastar DC HC560 SATA / 3.5". For SAS SSD 7.68TB for the KIOXIA PM7-R Series 2.5" and 4TB for Western Digital RED SA500 NAS Serien for SAS SSD.

The E5000 systems are compatible with a range of interface speeds,12Gb/s for SAS HDD and 6,12,24 Gb/s for SAS and SATA SSD.

E5000 Supports various OS systems, the supported versions include Mac OS 10.12.6 and MacOS Ventura 13.1. On the Windows side, the compatible versions are Windows Server 2008,2012,2016,2019 and 2022. Also RED hat, VMware and Citrix. Veeam Backup Applications Certified.

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

Ex10

The Ex10 (E310f, E310s, E610f, E610s, J310s, J610s, J630s, J830s) systems are compatible with various hard drives, including SATA, SAS Hard Drives and Solid State Drives.

Some supported hard drive models include the Fujitsu/ Toshiba, Western Digital, HGST, Seagate, Samsung for SATA and SAS HDD.Intel,OCZ Technology, Pliant Technology, STEC, Super Talent for SSD.

The largest capacity compatible with the Ex10 systems is 4000GB HGST Ultrastar 7K4000, Seagate ContellationES.3 for SAS. 2000GB FujitsuMKx001, HGST Ultrastar A7K2000, Seagate Constellation ES and Western Digital RAID Edition 4 for SATA. For SSD 480GB Super Talent TeraDrive CT.

The Ex10 systems are compatible with a range of interface speeds, 3/6Gb/s for SAS and SATA HDD and 1.5/3Gb/s for SSD.

E5000 Supports various OS systems, Windows Server 2003 and 2008. Also RED hat, VMware and Oracle.

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

Ex30

The Ex30 (E630F, E830F, J630S, J830S, J930S, J5000) systems are compatible with various hard drives, including SATA, SAS Hard Drives and Solid State Drives.

Some supported hard drive models include the TOSHIBA, Western Digital, HGST, Seagate for SATA and SAS HDD. Micron, intel, and Toshiba for SSD.

The largest capacity compatible with the Ex30 systems is 10TB HGST Ultrastar He10 for SAS and 6TB HGST Ultrastar 7K6000, Western Digital WD Eiger RE, ToshibaTomcat+, Seagate Constellation ES.3 for SATA. For SSD 1TB Micron M510DC.

The Ex10 systems are compatible with a range of interface speeds, 3/6/12Gb/s for SAS and SATA HDD and 3/6/12Gb/s for SSD.

E5000 Supports various OS systems, Windows Server 2008 and 20012. Also RED hat, VMware and Macintosh 10.9/10.12.

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