During a recent upgrade, autosnap for timeshift encountered an error when deleting the oldest snapshot (kept on an encrypted external drive, sdb). The deletion was stuck at 9.33% and after 20 min, I closed the terminal and restarted the computer. When I try to mount this drive, I now receive the error:
"An error occurred while accessing ‘1.8 TiB Encrypted Drive’, the system responded: An unspecified error has occurred: Object does not exist at path “/”
This external drive used to mount to /run or /run/media, I don’t recall but the only way I can now access it is by opening timeshift and unlocking it. When it do so, it mounts to /run/timeshift/5622/backup/ and I can use the drive as I had in the past but only if timeshift remains open.
So timeshift was accessing the drive, failed to delete an old snapshot, was unable to finish/close the task because I restarted the computer, and now it seems that timeshift has exclusive access to this external drive. Is that because it wasn’t allowed to finish its task previously?
Most importantly, how do I return this drive to normal functionality that does not rely on timeshift to open?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 1000M 0 part /boot/efi
├─sda2 8:2 0 896.2G 0 part
│ └─luks-86014d7c-b36f-4a1b-885c-80dcc1269916
│ 254:1 0 896.2G 0 crypt /
└─sda3 8:3 0 34.3G 0 part
└─luks-8bc08da4-a9d4-40d2-99d2-831542484d23
254:0 0 34.3G 0 crypt [SWAP]
sdb 8:16 0 1.8T 0 disk
└─sdb1 8:17 0 1.8T 0 part
└─sdb1_crypt 254:2 0 1.8T 0 crypt /run/timeshift/2224/backup
sdc 8:32 0 238.5G 0 disk
├─sdc1 8:33 0 50M 0 part
├─sdc2 8:34 0 237.9G 0 part
└─sdc3 8:35 0 509M 0 part