Skip to content

Pre-Backup Bash script (.sh) not mounting (mount) drive #2219

@MrSiO

Description

@MrSiO

Description

Hi.
I tried to launch a bash script in the "Pre-Backup" under "Shell Commands".
This script is pretty simple. I use it to "mount" a drive before backup, and a simlar "Post-Backup" bash script to "unmout".

#!/bin/bash sudo /bin/mount -t cifs -o rw,user=me,uid=me,vers=3.0,credentials=/root/.mycredential //10.100.10.50/NAS-User-Backups /mnt/NAS-User-Backups/

As "user" if I manually lauch the script from folder, drive mounts without any problem and unmounts with my post-backup script.
But when lauched at "pre-backup" like this in the APP, mount simply won't mount, BUT script is executing other commands within the script so I know Vorta has successfully lanched the script.

Command line set in the app under Pre-Backup:
/home/user/BorgBackup/Scripts/Vorta-Backup-Script-PRE.sh

Note: my user is configured in "sudoers" to "sudo mount" without password.

Thx for any ideas...

Reproduction

  • I tried to reproduce the issue.
  • I was able to reproduce the issue.

OS

Linux Mint - 22.01

Version of Vorta

0.10.3

What did you install Vorta with?

Flatpak

Version of Borg

1.4.0

Logs

This is the log when launching the backup manually:

2025-03-18 16:11:01,169 - vorta.keyring.abc - DEBUG - No module named 'objc'
2025-03-18 16:11:01,175 - asyncio - DEBUG - Using selector: EpollSelector
2025-03-18 16:11:01,178 - vorta.keyring.abc - DEBUG - Using VortaSecretStorageKeyring
2025-03-18 16:11:01,178 - vorta.borg.borg_job - DEBUG - Using VortaSecretStorageKeyring keyring to store passwords.
2025-03-18 16:11:01,180 - asyncio - DEBUG - Using selector: EpollSelector
2025-03-18 16:11:01,183 - vorta.keyring.secretstorage - DEBUG - Found 1 passwords matching repo URL.
2025-03-18 16:11:01,185 - vorta.keyring.secretstorage - DEBUG - Retrieved password for repo /mnt/NAS-User-Backups/VORTA-MINIMAL
2025-03-18 16:11:21,273 - vorta.notifications - DEBUG - notification not suppressed
2025-03-18 16:21:37,412 - vorta.scheduler - DEBUG - Refreshing all scheduler timers
2025-03-18 16:21:37,420 - vorta.scheduler - INFO - Setting timer for profile 1
2025-03-18 16:21:37,424 - vorta.scheduler - DEBUG - Scheduling next run for 2025-03-24 18:53:07.159169
2025-03-18 16:21:37,432 - vorta.scheduler - DEBUG - Scheduler for profile 2 is disabled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedThis issue is available, comment if you want to fix it

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions