[MacOS] Failing to start runner service when installed on external volume drive

Describe the bug
When installing the runner software on an external ssd on MacOS as a service, the service fails to start, and the runner remains "offline". I have to manually call ./run.sh and keep terminal alive for jobs to be picked up.

To Reproduce

cd /Voumes/<volume> # can be any external drive, I'm using an SSD
mkdir runner; cd runner # create runner dir
curl -o actions-runner-osx-arm64-2.329.0.tar.gz -L  https://github.com/actions/runner/releases/download/v2.329.0/actions-runner-osx-arm64-2.329.0.tar.gz
tar xzf ./actions-runner-osx-arm64-2.329.0.tar.gz; rm ./actions-runner-osx-arm64-2.329.0.tar.gz
./config.sh --url https://github.com/<org>/<repo> --token <token> # configure as usual
./svc.sh install # install service, I see that it does properly register in startup items
./svc.sh start # <--- Fails to start runner

Expected behavior
When starting the runner service, it starts listening for jobs on external drive.

Runner Version and Platform

Latest

OS of the machine running the runner? OSX

What's not working?

Don't see any errors, When calling ./run.sh it seems to start just fine, but I have to leave to terminal open to keep it listening to jobs and manually have to start it when the machine turns on.

Job Log Output

N/A

Runner and Worker's Diagnostic Logs

Start with svc.sh install and svc.sh start, then compare their behavior with run.sh when the runner is located on an external volume. Inspect the registered startup service and available diagnostics; done means the service starts successfully and remains available for jobs after startup without an open terminal.