Live System Creation is Aborted - no error shown in teminal

Asked by Colbak

I installed Systemback and used it for restore points and system creation for a few days without any problem.

Then I started getting the same error message as other have reported:

"Live system creation is aborted!"

"There has been critical changes in the file system during this operation"

I tried running from a terminal, and there was no error message shown.

I tried with no other programs running in the background, just in case, but the error was the same.

Any ideas?

Question information

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

Are you get this error immediately after the button is pressed?
If so, Systemback is trying these operations:
- Create items in working directory
- Open (for read) the /etc/fstab, /etc/lsb-release and /etc/hostname files
- Change some files permissions in /usr/share/initramfs-tools/scripts/casper-bottom directory
- Create some files (if necessary) in /usr/share/initramfs-tools/scripts/init-bottom directory
- Create a new initramfs image

The last one is a lengthy process, and output some texts to the terminal (so even jammed ago).
Please check these things. So if the /etc/hostname file is missing, the process is terminated (I have met this one).

Revision history for this message
Colbak (colbak) said :
#2

Hi Kendek

It is almost immediately

I will poke around those files and see what might have changed.

I remember that I did change the hostname on this PC at some time in the last week or so - might be related?

Revision history for this message
Colbak (colbak) said :
#3

That fixed it :)

Both the hosts file and the hostname file were missing.

I am building a distro from the Ubuntu mini iso, and have been installing and cloning from one partition to another using remastersys, qt-fsarchiver and systemback at different times. Somewhere along the way, I guess the files got missed.

I recreated them, and the problem has gone.

Thanks for your rapid response on this.

Col