Yes, since 20.04, I have not had the problem, but I thought it was due
to using a linux server and smb which solved the problem.
The original problem was localized to my desktop machine and a local
drive, which would fail after bootup because the dedicated backup
drrive/partition was not
Yes, it is listed in fstab and yes, I entered the path as a local
storage device.
All drives are SSD's connected to the computer's internal SSD ports and
seen as local. The server is running XIGMANAS with SMB shares for each
of the SSD's. I am not running SAMBA server.
The local OS is Unbuntu
I have not found the bug you describe to be true.
Work-a-round. If you mount the backup destination before the scheduled
backup begins, everything is fine and the backup runs without error.
If you don't mount the backup destination before the scheduled backup,
it will fail, with destination
I tried using "Disks" to allow for the partition on which the backups
live on a local drive to "mount on startup".
Instead of mounting the disk for which the partition was marked "mount
on startup", at reboot, it seem to hide the drive all together. The
drive was not mounted, but hidden from the
This was on 18.04 Beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761216
Title:
Backup fails if backup destination is not mounted
To manage notifications about this bug go to:
Public bug reported:
I don't know why
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-37-generic (not installed)
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture:
Public bug reported:
In "user accounts", click on the picture icon, browse for a picture
(stock) or (user) and size it. Accept it and no change appears in the
"login/logout/shutdown" menu. I did this with "unlock" and "lock".
Reproducible in 16.04 LTS.
I think this is the wrong place for this
