search

graham8 / osmc-backup

Backup scripts for copying osmc installations to and from system partitions
27 stars 0 forks source link

media reported as not mounted while it is definitely mounted #5

Closed fzoet69 closed 8 months ago

fzoet69 commented 8 months ago

my mounted backup drive does not pass the test for it being mounted.

in osmc-backup I added 2 echo lines after line 126: DRIVE=${BASH_REMATCH[$i]} echo "Drive = " $DRIVE echo "findmnt = " $(findmnt -l | grep ^"$DRIVE ") and changed the backup drive to /media/user/backuposmc

testing the mounted drive: ls /media/user/backuposmc ...reports back a whole list of files...

sudo ./osmc-backup

reports back the following: di 27 feb 2024 22:31:27 CET Backup version 0.1.12a Going to back up to /media/user/backuposmc/2024-02-27 (unless I can't find it). looking for mounted media

Drive = /media/user/backuposmc findmnt = /media/user/backuposmc /dev/loop30p1 vfat ro,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro

Drive = /media/user findmnt =

media for /media/user/backuposmc not mounted in /media or /mnt

graham8 commented 8 months ago

I wrote this expecting drives to be mounted as /media/volume not /media/user/volume as that is how osmc mounts them. I think I did make some changes here to handle deeper trees because I have used this to back up LinuxMint but I'll need to check. It was a long time ago.

fzoet69 commented 8 months ago

Hi Graham Thank you for your response. I run into the same issue on my Ubuntu and on my raspberry pi. Raspberry mounts under /mount/drive. Ubuntu under /mount/user/drive. I gave the results of the Ubuntu test environment because it is much easier to troubleshoot and edit than on my raspberry through ssh. I have some basic bash coding knowledge but troubleshooting your code is beyond my current capacities. Thank you for looking into this. Floris

Op di 27 feb 2024 22:54 schreef Graham @.***>:

I wrote this expecting drives to be mounted as /media/volume not /media/user/volume as that is how osmc mounts them. I think I did make some changes here to handle deeper trees because I have used this to back up LinuxMint but I'll need to check. It was a long time ago.

— Reply to this email directly, view it on GitHub https://github.com/graham8/osmc-backup/issues/5#issuecomment-1967674066, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNHUBYKWLD7OO7UUEM7ZHTYVZI2NAVCNFSM6AAAAABD44JIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXGY3TIMBWGY . You are receiving this because you authored the thread.Message ID: @.***>

graham8 commented 8 months ago

OK it's getting late here, I'll check it out tomorrow.

graham8 commented 8 months ago

It's not the depth of the file tree that's the problem but findmnt = /media/user/backuposmc /dev/loop30p1 vfat

vfat is not a supported filesystem. Please use ext3 or ext4. The error message is misleading so I've fixed that. Maybe you could grab this latest version and let me know if the error reported makes more sense before you try with a ext formatted disk.

fzoet69 commented 8 months ago

I confirm it does work on the Ubuntu system when writing to ext4. I notice it's copying the system files into the given folder. How would I turn that copy into img file? That would be easier to earmark as the backup from date x.

Op wo 28 feb 2024 12:44 schreef Graham @.***>:

It's not the depth of the file tree that's the problem but findmnt = /media/user/backuposmc /dev/loop30p1 vfat

vfat is not a supported filesystem. Please use ext3 or ext4. The error message is misleading so I'll fix that.

— Reply to this email directly, view it on GitHub https://github.com/graham8/osmc-backup/issues/5#issuecomment-1968808421, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNHUB6XT4J7DKK4QWPFVD3YV4KBTAVCNFSM6AAAAABD44JIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYHAYDQNBSGE . You are receiving this because you authored the thread.Message ID: @.***>

graham8 commented 8 months ago

This is a file-by file backup, not an image. The advantage is it takes up less space and you can poke around in the backups for previous versions of files. If you want an image backup there are other tools to do that.

fzoet69 commented 8 months ago

Thank you, I didn't realize that file by file takes less space than an image. I thought it's the same. Unless the image includes empty disk space

Thank you for your efforts Graham! Grateful. Have a great evening Floris

Op do 29 feb 2024 22:48 schreef Graham @.***>:

This is a file-by file backup, not an image. The advantage is it takes up less space and you can poke around in the backups for previous versions of files. If you want an image backup there are other tools to do that.

— Reply to this email directly, view it on GitHub https://github.com/graham8/osmc-backup/issues/5#issuecomment-1972021829, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNHUB46X4FZC6Z6XYITVUDYV6Q27AVCNFSM6AAAAABD44JIY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGAZDCOBSHE . You are receiving this because you authored the thread.Message ID: @.***>

graham8 commented 8 months ago

A single backup with this script should up the same space as an image with the unused disk sectors taken out. Or less space if the image is of the whole disk. Subsequent backups only take up the space of the files that have changed - maybe 10% of the first backup - because unchanged files are hardlinked. That's why you can't use vfat for this.