Preconditions

Apply the following steps when…

  • The Osiris app is able to start
  • The Osiris app is able to mount an Osiris volume
  • The bin locking feature does not work in “Avid Media Composer”

Introduction

It may happen that the Osiris app is able to successfully mount Osiris volumes but the bin locking feature in Media Composer is not working. The most common reason for this are leftover third-party kernel extensions from other bin locking solutions such as SAN Fusion, Nexis, etc. In this manual chapter, you will learn how to identify and remove these leftover Kernel extensions.

1. Check if the Requirements for Bin Locking are in Met

  1. Make sure that any third-party bin locking tool except for Osiris is uninstalled.
  2. Make sure the Osiris app is closed.
  3. Make sure Avid Media Composer is closed.
  4. Open a macOS Terminal.
  5. In the Terminal, type mount and then press enter.
  6. Look for a volume that includes both, io.projective.osiris.pamloopfs@pamfs0 and (AvidUnityISIS, local, nodev, noexec, nosuid, synchronous) in its parameters.

If both io.projective.osiris.pamloopfs@pamfs0 and (AvidUnityISIS, local, nodev, noexec, nosuid, synchronous) are in place, then Osiris bin locking is supposed to work properly. This means that the origin of the non-functioning bin looking likely is a leftover kernel extension from another bin locking tool. The next chapter will address how to identify and remove those kernel extensions.

Removing Third-Party Kernel Extensions

  1. Make sure the Osiris app is closed.
  2. Make sure Avid Media Composer is closed.
  3. Make sure that any third-party bin locking tool except for Osiris is uninstalled.
  4. Open a macOS Terminal
  5. Type kextstat | grep -v com.apple to load a list of third-party kernel extensions.
  6. Look for kernel extensions that include the words SAN Fusion, Nexis, etc.
Last modified: Mar 31, 2022

Need more help with this?
Visit the Projective Support Websites

Thanks for your feedback.