Just an aside, I have booted Tara 3 times today, the 20th, and tried timeshift each time, but there are no logs in /var/logs for this date. Why might that be?
My problem is trying to recover a timeshift snapshot from recovery mode boot in Tara. I get a lot of read-only errors when I try this. I don't understand the errors because I had immediately prior to the timeshift command created a directory in the root folder to test the write ability of the volume. If I'm root and I can create a folder, shouldn't I be able to create it anywhere in the system? Anyway, IMG_237a is what I first get when I type "timeshift --restore --snapshot '2018-09-18_11000-01 --target /dev/sda2'. The next image, IMG_233a, shows what after hitting Enter. Again the same type of errors.
I'm using Paragon's Linux File System for Windows to check the file system and it looks OK to me.
Probably irrelevant but when I am in root recovery and I type mount to show the volumes, I get many cgroup lines. Do you know why?
Here is fstab from Windows
Code: Select all
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc2 during installation
# swap was on /dev/sdc3 during installation
UUID=854aeb0f-69c4-47ff-afbf-6aaaa56ae354 none swap sw 0 0
/dev/disk/by-uuid/72A4CBA4A4CB68E5 /mnt/72A4CBA4A4CB68E5 auto nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=8TB,x-gvfs-icon=8-TB,x-gvfs-symbolic-icon=8tb 0 0
/dev/disk/by-uuid/0C204DDD204DCE80 /mnt/0C204DDD204DCE80 auto nosuid,nodev,nofail,x-gvfs-show,noatime 0 0
UUID=20e86fe9-bca1-4cf8-b70d-f90c7b9465ef / ext4 noatime,remount-ro,noauto 0 1