My Pegasis indicates the drive is full

  • Last Post 16 October 2018
Brad Warner posted this 07 October 2018

My Pegasis says I have only 2 Terabytes of data remaining of the 20 total Terabytes. When I add up the files listed on my Finder, I calculate the total Terabytes used is only about 10. How do I delete what I can't see?

Order By: Standard | Latest | Votes
Ranjith kumar posted this 07 October 2018

Hi Brad,

We need the subsystem report to get more information on your Pegasus.So could you please visit and create a web support case.In that case kindly attach the subsystem report to help you.

Steps to save the subsystem report:

- Open promise utility

- Click subsystem information icon on the top of the Promise Utility window

- Click the lock symbol on the left bottom corner of the screen to unlock the utility

- Click on save service report button to save the subsystem report and attach it to this case.


Below is the Promise KB link to know how to attach files to the web support case:








PROMISE Technology Inc. posted this 16 October 2018

Hi Brad,

To copy a previous reply to the same issue...


The Pegasus is a block storage device, it appears to a Windows instance or a macOS instance as a range of disk blocks, exactly the same as the boot disk. The OS places a filesystem on the block storage and the OS manages everything that happens to the filesystem. The Pegasus has no knowledge of files, folders or even the filesystem. The OS says read LBA 1231234 and the Pegasus tells the OS the content of that block. The OS says to write this data to LBA 4123123 and the Pegasus writes that data to that block. This is what block storage does. This is all that block storage does.

To restate this, this is an OS issue, not a Pegasus issue. 

There are many MAC users asking similar questions.

This apple forum suggests rebuilding the spotlight index.

There seem to be many potential root causes for this issue and from the comments some solutions work for some but not for others.


Reading the MAC forums will probably help, as the exact root cause seems to vary depending on the macOS version, time machine settings and probably several other things.