bedna

A bit necro thread, but did you try using systemd instead? Something like: sudo nano /etc/systemd/system/mnt-NAS.service (the name "mnt-NAS" should be your actual location you want to mount it, ie: /mnt/NAS) [Unit] Description=File server network mount (samba) After=network-online.target Requisite=network-online.target [Mount] What=//192.168.15.150/15tb_NAS/Data/ Where=/mnt/NAS Type=cifs Options=vers=3,_netdev,cache=loose,credentials=/home/YOUR_USERNAME/.smbcredentials,nofail,noatime,uid=YOUR_USERNAME,gid=YOUR_USERGROUP,dir_mode=0755,file_mode=0644 TimeoutSec=15 [Install] WantedBy=multi-user.target (note that I am not sure about the "what" line here. I think that has to be the same as the [name] you created in your samba server config, so this might be why it is not working properly, you will have to experiment around that) Then just activate the mount to run at boot with: systemctrl daemon-reload systemctrl enable mnt-NAS.mount Add --now to the enable line if you want to mount it immediately and not have to reboot. If you want to unmount: sudo systemctl stop mnt-NAS.service And to start it again: sudo systemctl start mnt-NAS.service That has nothing to do with "windows friendly" that is just a big hole in your security. Just add a user on the windows server (I understand it as that is where you have your samba server?). IIRC you can access the old windows user manager with typing "manage" and starting the "manage computer" in the windoze start menu, you only need a local user, not a complete user with a microsoft account with email address and all. I honestly do not remember exactly how I did it, but it CAN absolutely work without problems. I think the samba user (that you add with smbpasswd -a on linux, I do not remember how to do that on windows, it was a while ago and I no longer use it, i am only looking at my old notes here) has to have the same name as the windows user you created. I use a .smbcredentials file, but you can try without any credentials I guess. Also, obv remove the fstab lines if you want to mount it using systemd instead. Just comment them out with adding a # in front of the lines. Good luck!

Might I interest you in my little project? https://github.com/UnconnectedBedna/shrink-backup It creates a bootable img file to your liking that you can just "burn" if you want to restore. Easily kept updated with the script (uses rsync to synchronize). If you want to move it back and forth between usb, ssd, sd-card etc you have to make sure that works yourself for this board (works automatically on rpi), but the img file should be writable back to the medium you backed it up from with the script. Please note though, this is not a clone, it is a backup of root and boot to a bootable img file (extra partitions, like if you have separate /home partition will be baked in the same partition as root on the img unless excluded). That will most likely change in the future as I am in the planning process of how to also be able to include a separate /home (and potentially other partitions as well, my thought process is still in the planning stage) If you want to make a complete clone, dd is probably your best friend (from the system not running at the time), but this will obv be as big as the total device size, my script only copies the actual data on the device and creates an img "as small as possible" (depending on what options you start the script with). Maybe you can find it useful.

Well, you DID ask for a way to run a script, not a gui desktop application. Glad you figured it out. Did you check what that option does? And you removed the invocation of bCNC so, not that strange.

OPI PC2 here. I had a missing release error the other day and just assumed it was because it was no longer supported. That is no longer the case and I also get: Hit:1 http://deb.debian.org/debian bullseye InRelease Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Get:3 http://security.debian.org bullseye-security InRelease [48.4 kB] Get:4 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB] Err:6 http://apt.armbian.com bullseye InRelease 502 Bad Gateway [IP: 130.185.239.78 80] Get:5 https://cli.github.com/packages stable InRelease [3917 B] Hit:7 https://download.docker.com/linux/debian bullseye InRelease Get:8 http://security.debian.org bullseye-security/main arm64 Packages [342 kB] Get:9 https://cli.github.com/packages stable/main arm64 Packages [346 B] Fetched 488 kB in 3s (167 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. W: Failed to fetch http://apt.armbian.com/dists/bullseye/InRelease 502 Bad Gateway [IP: 130.185.239.78 80] W: Some index files failed to download. They have been ignored, or old ones used instead. Nobody confirmed bullseye so I have to ask..

Really strange! Refuses to work here, keep getting host errors, but then works, but reports no other than one more seed. I guess it is something on my side. I'll just grab the file on the webpage and move on.

The minimal (Bookworm) torrent of Orange Pi PC2 was only shared by one source when I added it today, and that source is only at 71%. Not sure if this is another person also trying to download and the original source no longer shared, or if this is the original source and it is broken. I can ofc download the file via https, but felt I wanted to let you know.

I think it's the other way around (MBR vs GPT). Using grub f.ex, with GPT you can have the boot partition wherever you want, as long as you define it with UUID, but it USUALLY is the first partition. With MBR this is not a choice EVEN if you use uefi, I think you MUST have the partition first (and leave 5MiB or smthn before the partition).

Ah, then maybe it has something to do with my "skip redirect" plugin. You can never be too careful. OOOOOH, YOU HAVE HOODIES TOO! 💓

This does not look good... Did someone forget to renew the certificates?

Yes, you can obviously reinstall the boot completely instead of backing up what you have on your system. This is great info in the thread! I opted for a backup rather than a reinstall. Not only may, I have learned it is more of a rule than an exception. This an example with the opi5 img: Model: Loopback device (loopback) Disk /dev/loop0: 7315MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 16,8MB 285MB 268MB fat16 bootfs bls_boot 2 285MB 7315MB 7030MB ext4 rootfs Witch is the reason I do a dd of the entire boot sector (including any existing boot partitions if they exist) in the initial backup, sup-sequential backups, I just mount both partitions (if there is a boot partition) on the img and backs up the entire file system.

I am running a nfs share on my rpi4 and got curious (I use ip addresses rather than host-names, so that could be an extra layer you have to make sure is loaded before it is trying to connect), because I just created the /etc/exports, exportfs -ra, reloaded the systemd daemon and enabled nfs-server.service. So I checked the service file itself. This is on raspberry pi os, not armbian. Mine contains way more dependencies than just network-online.target, maybe you can use this to figure it out: $ cat /lib/systemd/system/nfs-server.service [Unit] Description=NFS server and services DefaultDependencies=no Requires=network.target proc-fs-nfsd.mount Requires=nfs-mountd.service Wants=rpcbind.socket Wants=nfs-idmapd.service After=local-fs.target After=network.target proc-fs-nfsd.mount rpcbind.socket nfs-mountd.service After=nfs-idmapd.service rpc-statd.service Before=rpc-statd-notify.service # GSS services dependencies and ordering Wants=auth-rpcgss-module.service After=rpc-gssd.service gssproxy.service rpc-svcgssd.service # start/stop server before/after client Before=remote-fs-pre.target Wants=nfs-config.service After=nfs-config.service [Service] EnvironmentFile=-/run/sysconfig/nfs-utils Type=oneshot RemainAfterExit=yes ExecStartPre=/usr/sbin/exportfs -r ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS ExecStop=/usr/sbin/rpc.nfsd 0 ExecStopPost=/usr/sbin/exportfs -au ExecStopPost=/usr/sbin/exportfs -f ExecReload=/usr/sbin/exportfs -r [Install] WantedBy=multi-user.target

Version 0.9.5 released. Support added for OrangePi 5. (gpt partition table) Experimental support for btrfs. For more information, please see https://github.com/UnconnectedBedna/shrink-backup

I was wrong about the rpi5 thing, they are still in mbr. Not really important, because it boots, but why is the sector before the boot partition so freakishly large (16,8MB)? Looped img of Armbian 23.11 Jammy-amazingfated GNOME for orangepi 5 $ parted /dev/loop0 print Model: Loopback device (loopback) Disk /dev/loop0: 7315MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 16,8MB 285MB 268MB fat16 bootfs bls_boot 2 285MB 7315MB 7030MB ext4 rootfs

I got an issue from a user on a bash script I am sharing on github. The script is to make shrunk img backups on a running system on a lot of different sbc:s. After some testing on the users side (I did not have access to hardware to test) it turned out the script fails because of the partition table, it is GPT while in the past they have always been MBR (msdos). I downloaded the latest opi5 gnome desktop image and looped it and parted shows it is in GPT. We figured out a way to solve it but my question is: is this because rpi5 uses gpt partition table (I do not own a rpi5 either)? Will this be the future of most armbian builds? On a side note, `armbian-resize-filesystem.service` still works to autoexpand after I restore a backed up img, so thank you for providing this. ❤️

It's not a "detection system" (other than it registers attempts to connect both successfully and unsuccessfully) but it is incredible competent about blocking access per app/protocol/ip level. I installed because I "just want to see what it is", Portmaster and ended up starting to rely on it. GUI based. I use a pihole so I do not feel I have the need to pay for anything but only use the free utilities in the program. For me it's so efficient that I quite a few times have scratched my head trying to figure out why stuff doesn't work, and then I remember, "aaah, portmaster"... xD

Attention, attention, version 0.9.1 released!! come get your free copy! xD A lot has happened: Device being backed up is what root resides on, ie works on any device now, not just mmcblk. No need to specify, script is smart enough to figure it out. ArchLinuxArm autoexpansion now supported without the need for any AUR downloads, only parted is needed. Tested to update with same image through kernel and boot changes on Armbian on orangePi-PC2 and no issues detected. Tested to update with same image through kernel and boot changes on ManjaroArm and no issues detected. Generally a more user friendly interface and the debug function is beyond explanatory. hint hint Hope you find it useful! Edit: Sadly I can no longer edit the original post to update with current information, but the link to github is still valid and all new info is available there. 😄

I'm not sure what armbian-config does exactly, but from what I read on a quick search about your hardware and booting from usb it seems OdroidC4 demands you having the inital boot sequence kick off from the sd-card and no way of getting around it. This guide seems to cover it without you needing to use armbian-config, because again, I don't know, but I suspect it moves everything, incl boot to your usb-device, and that won't work on your hardware.

My gut feeling was using systemd to run the script, that way root, or in this case systemd issues the commands. If it is to be run at startup just enable the service and specify `After` and `required` options. Not sure how you call the script, but you can probably play around it. https://www.freedesktop.org/software/systemd/man/systemd.service.html Bonus is you get access to journalctl that logs what is going on, extremely useful when debugging.

Good news everyone! Yesterday a new kernel update (5.15.93-sunxi64 > Linux 6.1.42-sunxi64) was pushed to my armbian on an opiPC2 and u-boot was triggered. Made tests by updating my old image instead of creating a new, then trying to boot from that image with GREAT success! I did not look deeper into what the u-boot actually did, but this time it worked at least.

Oh, My bad, I though your question "How to make a sd card bootable?" was the issue. Great that you solved that! If other people find this thread, can you explain how you solved that? Yes, I removed it because the whole sentence did not make sense to me. It seemed you misunderstood what you quoted. I even gave you an example of how I restored to sda from a backup from mmcblk0 and that that worked. What I have learned I HAVE to do to make a backup that I can restore and boot from is that I HAVE to do EXACTLY what you describe above. Not only that, I need to first resize both the backup file AND the partition on that backup, THEN resize the filesystem before backing up to it. But I am here to learn, if I do not need to do that and can somehow remove 500 lines of code in my script, I would LOVE to do that. So again, how do you restore your backups so they become bootable? A backup is NOT A BACKUP until you have restored from it Edit. I'm starting to believe this is an xy problem/question. You are looking for confirmation rather than the actual answer to your question. https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem I have a LOT of knowledge in these things, but always open to learn if I am ill informed. Edit 2 I just realized, in OP you mentions grub, that demands a second partition. If you back up a system with boot mounted on either /boot or /boot/efi, how do you backup (rsync) those so those gets restored tp a different partition?

That is exactly what the script does. Just with an extra bonus of you being able to write the img to a device and that filesystem will boot, and autoexpand if it's supported (witch armbian is). The FIRST img created obv is of the whole system, but subsequent updates on that img files ONLY rsyncs the changed files. If you only want to access the files, just mount the img file with a loop. I urge you to read the description. Edit Thought I comment on this as well: That is not true, as long as the img fits it can be written to any device. I even tried it with the script. I backed up a raspberry pi os from mmcblk0, wrote that img file to a usb that became sda and booted up from it. Worked like a charm. But that should work on any img (as long as its created with the same UUID), the os is looking for the uuid, not the device, devices can switch places between boots so they are NEVER reliable to expect to be the same.

If I may be so frank, I very recently made a post on this forum that would solve this for you. Might I offer you my piece of software to manage your backups?

A few changes introduced a bug that made armbian detect 2 partitions instead of one so If you have cloned it since op was made, you have to re clone it, the bug is now fixed. Sorry about that.

shrink-backup is a bash script for backing up your SBC:s into an img file Version 1.2 Info updated: 20 Oct, 2024. shrink-backup I made this script because I wanted a universal method of backing up my SBC:s into img files as fast as possible (with rsync), no matter what os is in use. Supports backing up root & boot (if existing) partitions. Data from other partitions will be written to root if not excluded (exception for btrfs, all existing subvolumes in /etc/fstab will be created). Please see Info section. Autoexpansion tested on Raspberry Pi os (bookworm and older), Armbian, Manjaro-arm, DietPi and ArchLinuxARM for rpi with ext4 or f2fs root partition. (Now also experimental btrfs functionality, please read further down) Full support for usage inside webmin (including "custom command" button). Latest release: shrink-backup.v1.2 Testing branch if you want to have the absolute latest version. There might be bugs. Very fast restore thanks to minimal size of img file. Can back up any device as long as root is ext4 or f2fs (experimental btrfs) Default device that will be backed up is determined by scanning what disk-device root resides on. This means that if boot is a partition, that partition must be on the same device and before the root partition. Backing up/restoring, to/from: usb-stick /dev/sdX with Raspberry pi os has been tested and works. Ie, writing an sd-card img to a usb-stick and vice versa works. Ultra-fast incremental backups to existing img files. See wiki for information about installation methods, usage and examples. Ideas and feedback is always appreciated, whether it's positive or negative. Please just keep it civil. If you find a bug or think something is missing in the script, please file a Bug report or Feature request Don't forget to ensure the script is executable. To restore a backup, simply "burn" the img file to a device using your favorite method. When booting up a restored image with autoresize active, wait until the the reboot sequence has occured. The login prompt may very well become visible before the autoresize function has rebooted. Usage: shrink-backup -h Script for creating an .img file and subsequently keeing it updated (-U), autoexpansion is enabled by default Directory where .img file is created is automatically excluded in backup ######################################################################## Usage: sudo shrink-backup [-Uatyelhz] [--fix] [--loop] [--f2fs] imagefile.img [extra space (MiB)] -U Update existing img file (rsync to existing img) Optional [extra space] extends img size of root partition -a Autoresize root partition (extra space is ignored) When used in combination with -U: Expand if partition is >=256MiB smaller than resize2fs recommended minimum Shrink if partition is >=512MiB bigger than resize2fs recommended minimum -t Use exclude.txt in same folder as script to set excluded directories One directory per line: "/dir" or "/dir/*" to only exclude contents -y Disable prompts in script (please use this option with care!) -e DO NOT expand filesystem when image is booted -l Write debug messages to logfile shrink-backup.log located in same directory as script -z Make script zoom at light-speed, only question prompts might slow it down Can be combined with -y for UNSAFE ultra mega superduper speed --fix Try to fix the img file if -a fails with a "broken pipe" error --loop [img] Loop img file and exit, works in combination with -l & -z If optional [extra space] is defined, the img file will be extended with the amount before looping NOTE that only the file gets truncated, no partitions Useful if you for example want to manually manage the partitions --f2fs Convert root filesystem on img from ext4 to f2fs Only works on new img file, not in combination with -U Will make backups of fstab & cmdline.txt to: fstab.shrink-backup.bak & cmdline.txt.shrink-backup.bak Then change ext4 to f2fs in both files and add discard to options on root partition in fstab --version Print version and exit -h --help Show this help snippet ######################################################################## Examples: sudo shrink-backup -a /path/to/backup.img (create img, resize2fs calcualtes size) sudo shrink-backup -e -y /path/to/backup.img 1024 (create img, ignore prompts, do not autoexpand, add 1024MiB extra space) sudo shrink-backup -Utl /path/to/backup.img (update img backup, use exclude.txt and write log to shrink-backup.log) sudo shrink-backup -U /path/to/backup.img 1024 (update img backup, expand img size/root partition with 1024MiB) sudo shrink-backup -Ua /path/to/backup.img (update img backup, resize2fs calculates and resizes img file if needed) sudo shrink-backup -Ua --fix /path/to/backup.img 1024 (update img backup, automatically resizes img file if needed, fix img free space) sudo shrink-backup -l --loop /path/to/backup.img 1024 (write to log file, expand IMG FILE (not partition) by 1024MiB and loop) -t (exclude.txt) The folder where the img file is created will ALWAYS be excluded in the backup. If -t option is selected, exclude.txt MUST exist (but can be empty) within the directory where the script is located or the script will exit with an error. Use one directory per line in exclude.txt. /directory/* = create directory but exclude content. /directory = exclude the directory completely. If -t is NOT selected the following folders will be excluded: /lost+found /proc/* /sys/* /dev/* /tmp/* /run/* /mnt/* /media/* /var/swap Please see info section further down. -l (Log file) Use -l to write debug info into shrink-backup.log file in the same directory as the script. -z (Zoom speed) The -z "zoom" option simply removes the one second sleep at each prompt to give the user time to read. By using the option, you save 15-25s when running the script. When used in combination with -y warnings will also be bypassed! PLEASE use with care! --fix (Broken pipe) Add --fix to your options if a backup fails during rsync with a "broken pipe" error. You can also manually add [extra space] instead of using -a to solve this. Example: sudo shrink-backup -Ua --fix /path/to/backup.img The reason it happens is because rsync normally deletes files during the backup, not creating a file-list > removing files from img before starting to copy. So if you have removed and added new data on the system you backup from, there is a risk rsync tries to copy the new data before deleting data from the img, hence completely filling the img. Using --fix makes rsync create a file-list and delete data before starting to transfer new data. This also means the backup takes a little longer. Having a "broken pipe" error during backup has in my experience never broken an img backup after either using --fix (can be used in combination with -a) or adding [extra space] while updating the backup with -U. --loop (Loop img file) Use --loop to loop an img file to your /dev. Example: sudo shrink-backup --loop /path/to/backup.img If used in combination with [extra space] the amount in MiB will be added to the IMG FILE NOT any partition. With this you can run for example run: sudo gparted /dev/loop0 (if you have a graphical interface) to manually manage the img partitions in a graphical interface with gparted. If you added [extra space] this will then show up as unpartitioned space at the end of the device where you can create partition(s) and manually copy data to by mounting the new loop partition that will become visible in lsblk. If you do this, don't forget to create or update the img with -e (disable autoexpansion) first. Autoexpansion will not work since the space will be occupied by your manually managed partition. Example: sudo shrink-backup --loop /path/to/backup.img 1024 This functionality works on any linux system, just use the script on any img file anywhere available to the computer. To remove the loop: sudo losetup -d /dev/loop0, change loop0 to the correct dev it got looped to. To remind yourself: lsblk /dev/loop* (if you forgot the location after using --mount) --f2fs (Convert ext4 into f2fs on img file) ONLY use this for CONVERTING filesystem into img file, if you already have f2fs on your root, do not use this option. The script will detect what filesystem is used on root and act accordingly. Only supported with new backups, not when using -U. Autoexpansion at boot is not supported for f2fs (there is no way of resizing a mounted f2fs filesystem, unlike with ext4) so resizing root partition have to be made manually after writing img to sd-card. Resize operations (when updating backup with -U) is not available for f2fs as of now. The script will make backups of fstab & cmdline.txt into fstab.shrink-backup.bak & cmdline.txt.shrink-backup.bak on the img. It will then change from ext4 to f2fs in fstab & cmdline.txt and add discard to the options on the root partition in fstab. Please read information about f2fs further down. Info Rsync WILL cross filesystem boundries, so make sure you exclude external drives unless you want them included in the backup. (separate /home for example) The script will ONLY create boot (if exits) and root partitions on the img file. The script will ONLY look at your root partition when calculating sizes. Not excluding other partitions will copy the data to the img root partition, not create more partitions so make sure to manually add [extra space] if you do this. Experimental btrfs is an exception to this, all subvolumes will be created. Applications used in the script: fdisk sfdisk dd parted e2fsck truncate mkfs.ext4 rsync gdisk (sgdisk is needed if the partition table is GPT, the script will inform you) ######################################################################## Image creation To create a backup img using recomended size, use the -a option and the path to the img file. Example: sudo shrink-backup -a /path/to/backup.img Theoretically the script should work on any device as long as root filesystem is ext4, f2fs or experimental btrfs. Since the script uses lsblk to crosscheck with /etc/fstab to figure out where the root resides it does not matter what device it is on. Even if you forget to disable autoexpansion on a non supported system, the backup will not fail. Order of operations - image creation Reads the block sizes of the partitions Uses dd to create the boot part of the system + a few megabytes to include the filesystem on root (this can be a partition) Removes and recreates the root partition, size depends on options used when starting the script Creates a new ext4 filesystem with the same UUID and LABEL as the system you are backing up from Uses rsync to sync both partitions (if more than one) Uses lsblk & /etc/fstab to figure out the correct disk device to back up. Reads the block sizes of the system's root (and boot if it exists) partition. Uses dd to create the boot part of the system + a few megabytes to include the filesystem on root. (this can be a partition) Uses df & resize2fs to calculate sizes by analyzing the system's root partition. (For btrfs: btrfs filesystem du + 192MiB is used instead of resize2fs) Uses truncate to resize img file. Loops the img file. Removes and recreates the root partition on the loop of the img file. Creates the root filesystem on loop of the img file with the same UUID and LABEL as the system you are backing up from. Creates a temp directory and mounts img file root partition from loop. Checks if boot partition exists, if true, checks fstab and creates directory on root and mounts accordingly from loop. Uses rsync to sync filesystems. Tries to create autoresize scripts if not disabled with -e. Unmounts and removes temp directory and file (file created for rsync log output). Added space is added on top of df reported “used space”, not the size of the partition. Added space is in MiB, so if you want to add 1GB, add 1024. The script can be instructed to set the img size by requesting recommended minimum size from e2fsck by using the -a option. This is not the absolute smallest size you can achieve bit is the “safest” way to create a “smallest possible” img file. If you do not increase the size of the filesystem you are backing up too much, you can most likely keep it updated with the update function (-U) of the script. By using -a in combination with -U the script will resize the img file if needed (not supported on f2fs). Using combination -Ua on an img that has become overfilled works, if not add --fix and retry. Please see --fix and image update sections for more information. Smallest possible image To get the absolute smallest img file possible, do NOT set -a option and set “extra space” to 0 Example: sudo shrink-backup /path/to/backup.img 0 This will instruct the script to get the used space from df and adding 128MB “wiggle room”. If you are like me, doing a lot of testing, rewriting the sd-card multiple times. The extra time it takes each time will add up pretty fast. Example: -rw-r--r-- 1 root root 3.7G Jul 22 21:27 test.img # file created with -a -rw-r--r-- 1 root root 3.3G Jul 22 22:37 test0.img # file created with 0 Disclaimer: Because of how filesystems work, df is never a true representation of what will actually fit on a created img file. Each file, no matter the size, will take up one block of the filesystem, so if you have a LOT of very small files (running docker f.ex) the “0 added space method” might fail during rsync. Increase the 0 a little bit and retry. This also means you have VERY little free space on the img file after creation. If the filesystem you back up from increases in size, an update (-U) of the img file might fail. By using -a in combination with -U the script will resize the img file if needed (not supported on f2fs). Using combination -Ua on an img that has become overfilled works, if not add --fix and retry. Please see --fix and Image update sections for more information. ######################################################################## Image update To update an existing img file simply use the -U option and the path to the img file. Example: sudo shrink-backup -U /path/to/backup.img Order or operations - image update Loops the img file. Probes the loop of the img file for information about partitions. If -a is selected, calculates sizes by comparing root sizes on system and img file by using fdisk & resize2fs. Expands filesystem on img file if needed or if manually added [extra space] is used. Creates temp directory and mounts root partition from loop. Checks if boot partition exists, if true, checks fstab and creates directory on root and mounts accordingly from loop. Uses rsync to sync filesystems. Shrinks filesystem on img file if -a was used and conditions were met in point 3. Tries to create autoresize scripts if not disabled with -e. Unmounts and removes temp directory and file (file created for rsync log output). Resizing img file when updating If -a is used in combination with -U, the script will compare the root partition on the img file to the size resize2fs recommends as minimum (or du calculations depending on filesystem). The img file root partition needs to be >=256MB smaller than resize2fs recommended minimum to be expanded. The img file root partition needs to be >=512MB bigger than resize2fs recommended minimum to be shrunk. This is to protect from unessesary resizing operations most likely not needed. If manually added [extra space] is used in combination with -U, the img file's root partition will be expanded by that amount. No checks are being performed to make sure the data you want to back up will actually fit. Only expansion is possible with this method. ######################################################################## f2fs The script will detect f2fs on root automatically and act accordingly. Do NOT USE --f2fs unless you are converting from a ext4 filesystem (on your system) into f2fs on the img file. Autoexpansion at boot is not possible with f2fs. User will have to manually expand img to cover entire storage media (f.ex sd-card) when restoring. Resizing of img root partition while updating img (-U) is not possible with f2fs as of now. User will have to create a new backup if img runs out of space. This is something I am planning to implement further down the line. btrfs ALL testing has been done on Manjaro-arm THIS IS NOT A CLONE, IT IS A BACKUP OF REQUIRED FILES FOR A BOOTABLE BTRFS SYSTEM! All options in the script should work just as on ext4. The script will detect btrfs and act accordingly. The script will treat snapshots as nested volumes, so make sure to exclude snapshots if you have any, or directories and nested volumes will be created on the img file. This can be done in exclude.txt, wildcards should work. When starting the script, the initial report window will tell you what volumes will be created. Make sure these are correct before pressing Y. As of now, top level subvolumes are checked for in /etc/fstab and mounted accordingly, mount options should be preseved (if you for example changed compression). Autoresize function works on Manjaro-arm. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Thank you for using my software ❤️ A backup is not really a backup until you have restored from it.

Before I do something that breaks forum rules I'd rather ask. Can I post a link to githyb with a script I made to backup sbc:s (incl Armbian ofc)? The reason it even exists is because of when I first started using armbian and wanted something I could backup both rpi os and armbian. Can I post it here or is it prefered to keep it in the "anything" thread? Regards.