Can't install live image created using Systemback

Asked by Sam Quintanar

My Ubuntu 18.04 OS got corrupted, so I thought, no problem, just install the Live Image of my system I created 3 weeks earlier using Systemback.

Upon each live image install attempt, I get:
'The system installation is aborted!
There has been critical changes in the file system during this operation.'

When I boot from the USB, my system appears as it should, so the Live image is not corrupt.

I created a USB live image of an Ubuntu 18.04 system including configuration & data. The size is 63.94 GB.

These are the steps taken to install the USB live image of the Ubuntu 18.04 system onto the hard drive:
1. Entered full name of new user
2. Entered username to login
3. Entered user account password
4. Did not enter a system password since it is not recommened for Ubuntu
5. Entered new hostname
6. The '>>Next' button activates, so I click on it
7. Arrived at 'Partition setting' window (Here, is where I may be doing something wrong)
8. Selected /dev/sdb 931.51 GiB (the correct hard drive) and clicked on 'Delete' button
9. /dev/sdb? 931.51 GiB appears under /dev/sdb 931.51 GiB
10. In 'Create new' spin box, entered 4000 MiB for swap space and clicked on green arrow pointing left
11. Selected /dev/sdb1 3.91 GiB SB@
12. Clicked on 'Mount point' dropdown box and selected 'SWAP'
13. Ensured 'Format' is checked
14. Clicked on green arrow
15. Selected /dev/sdb? 927.61 GiB which appears under /dev/sdb1 3.91 GiB SB@
16. In 'Create new' spin box, entered 100000 MiB for root space and clicked on green arrow pointing left
17. Selected /dev/sdb2
18. Clicked on 'Mount point' dropdown box and selected '/'
19. Ensured 'Format' is checked
20. Clicked on green arrow
21. Checkmarked 'Transfer user configuration and data files'
22. 'Install GRUB2 bootloader' set to 'Auto' (My conputer is dual boot; Ubuntu & Win10, so I hope 'Auto' selection is ok)
23. The partitions appear as:
        Partition Size Label New Mount Point Filesystem Format
        /dev/sdb 931.51 GiB
        /dev/sdb1 3.91 GiB SB@ SWAP swap x
       /dev/sdb2 97.66 GiB SB@ / ext4 x
       /dev/sdb3 829.95 GiB /home ext4 x
24. Clicked on '>>Next' button
25. A popup window titled 'Systemback' appears with 'Installing the system...' message and a progress bar and an '!Interrupt!' button
26. The progress bar makes it to 100 (and I think the installation should complete), then takes a while until the following appears:
'The system installation is aborted!
There has been critical changes in the file system during this operation.'

What am I to do?

Question information

Language:
English Edit question
Status:
Expired
For:
Systemback Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kendek (nemh) said :
#1

Ubuntu 18.04 is not compatible with this version of Systemback.

But if you want to see where the installer stops, start Systemback with the following command:

DBGLEV=3 systemback-sustart

Revision history for this message
Sam Quintanar (samq) said (last edit ):
#2

Kendek,
Thank you so much for such a timely response!

In several URLs on the internet, it is stated that Systemback for Ubuntu 16.04 is compatible with 18.04 etc.
Obviously this may be mistaken?!

Is there any version of Systemback that is fully operational for Ubuntu 18.04? How about Ubuntu 20.04 & 22.04?

Sam

Revision history for this message
Kendek (nemh) said :
#3

I'm sorry but I do not know, I haven't touched the Systemback source code in years.

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Joe Kirchner (pelle989) said :
#5

Sam, I've had this issue before and was able to resolve it by making sure that the device was not online when booting into the Live USB. If it's online, there is something that is causing the same behavior as your describe. I've tried stopping unattended upgrades and such, but that didn't resolve it. I'm not sure what part of being online is making the installer fail.