Hi All, BACKGROUND: Am a single-system home-office user of Linux. Not a professional sysadmin. Running Linux Mint 17 Qiana, desktop, 64-bit Intel. My "total system backup" scheme has been (for the last ~10 years) to run rsync (in a script, from / recursively), onto similarly-formatted/installed disks. Has worked perfectly over the years, on Fedora, Ubuntu, and Mint... as backups are essentially clones, and become new master disks in the event of crashes. Am currently doing backups while in Recovery mode, after mounting the target as an external USB drive. (I originally powered up with the backups as a second IDE or SATA, but recent versions of Ubuntu/Mint won't allow booting like that. Found that going via USB does work, although probably much slower.) Have spent MANY hours researching the bootup process, and sending questions relevant to my objectives to LUV, SiliconValley LUG, LinuxMint Forum, GRUB Developers, etc. Questions not suitably answered. So gave up getting help, and have edited... /etc/default/grub /usr/share/grub/grub-mkconfig_lib /etc/fstab /etc/initramfs-tools/conf.d/resume ... in ways that worked previously and/or seemed the most logical to one barely grasping the mechanisms. Then ran update-grub If interested: I can email you directly with copies of those 4 files, or lists of the 4 edits that I performed. I can also email you the you-beaut backup script utilising rsync. PROBLEM: When booting up with a backup (near-clone), in place of the master disk, I get the following error message, just after the GRUB2 (?) menu... Error: No such device: c2oc...07CB (i.e. the UUID of the master/source disk) Press any key to continue... Then, after ~4 seconds, and without tapping any key, it just continues with the boot-up sequence and the entire system seems to run normally. QUESTIONS: Should I harbour any concerns? Suggestions on how to refine/bulletproof the current general scheme (rather than use a different scheme)? Thanks very much in advance. Carl Turney Bayswater, Victoria