Live System creation aborted
Hello,
A new user to Linux, and Systemback.
I have just been testing Systemback, I created a restore point, all O.K
I then tried to create a "Live System" and it starts 1 /3, then I get a message after a few seconds:
Live System creation aborted
There has been critical changes in the file system during this operation.
I then ran it from a terminal and got:
dave@asus-mini-2 ~ $ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
dave@asus-mini-2 ~ $
I have verified that the above file exists,
I can copy and open that file, it appears to be a 128x128 png image file.?
Any Help Welcome
Many Thanks... Dave
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Systemback Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Kendek
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#3 |
Hm, this is very interesting. Please try the following command:
sudo link /home/dave/
and report back the result. If everything is OK, the /home/tmplnk hardlink will be created. Otherwise you get an error message.
Workaround in the meantime, you can add the file to the excludes list.
Revision history for this message
|
#4 |
Hi Kendek,
Thanks for quick response, here is the output/result:
Ran the command
dave@asus-mini-2 ~ $ sudo link /home/dave/
[sudo] password for dave:
dave@asus-mini-2 ~ $
Seemed to run, no errors
I ran Systemback again:
dave@asus-mini-2 ~ $ sudo systemback
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
I ran Systemback again, and excluded the file
dave@asus-mini-2 ~ $ sudo systemback
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
Same result
Thanks... Dave
Revision history for this message
|
#5 |
I have many same file in own ~/.thumbnails directory, but I don't get any error.
Try to delete this file (it doesn't cause any problems), and check others with Live creation process.
Besides you can add the entire .thumbnails directory to the excludes list.
Revision history for this message
|
#6 |
Hi Kendek,
This is very, very strange.??
First I deleted that file, 6236d1cdc77e89c
then,
dave@asus-mini-2 ~ $ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
So it now fails with a different .png file in that directory.
Then...
I now exclude the entire . thumbs Directory
dave@asus-mini-2 ~ $ sudo systemback
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
dave@asus-mini-2 ~ $
It still fails with the file above from the excluded directory.???
One last attempt, I re-booted, just in case something is cached somewhere.??
dave@asus-mini-2 ~ $ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Warning: No support for locale: en_GB.utf8
Systemback worker thread error because the following item:
@/home/
dave@asus-mini-2 ~ $
It is still failing with the file above from the excluded directory.???
This is very strange...
Revision history for this message
|
#7 |
Hm, you checked "Include user data files" option (this is a checkbox)? If you don't, maybe not these files the problem.
Please show me the contents of the /home/dave/
XDG_DESKTOP_DIR
XDG_DOWNLOAD_DIR
XDG_TEMPLATES_DIR
XDG_PUBLICSHARE_DIR
XDG_DOCUMENTS_DIR
XDG_MUSIC_DIR
XDG_PICTURES_DIR
XDG_VIDEOS_DIR
Is likely to be the problem here. If so, then if you include user data files, the problem doesn't occur.
Revision history for this message
|
#8 |
Hi Kendek,
Maybe some more info, the above was done on LM17 Cinannamon(
I have now tried this on another PC/Laptop with Linux Lite 2.0(Ubuntu14.04)
I'm still getting similar issues like above on Linux Lite 2.0
dave@hp-laptop:~$ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Systemback worker thread error because the following item:
@/home/
Then try again excluding /home/dave/
update-initramfs: Generating /boot/initrd.
Systemback worker thread error because the following item:
@/home/
Here is the file:
XDG_DESKTOP_
XDG_DOWNLOAD_
XDG_TEMPLATES_
XDG_PUBLICSHARE
XDG_DOCUMENTS_
XDG_MUSIC_
XDG_PICTURES_
XDG_VIDEOS_
I'm not sure if it is significant?, but on both my systems my disk set-up is:
dev/sda1 is /
dev/sda2 is /home
dev/sda3 is /mnt/myfiles
dev/sda5 is swap
/home/dave/
are for example then bound to
/mnt/myfiles/
I find this easier for backup.
Many Thanks... David
Revision history for this message
|
#9 |
Ah, these are the problems:
XDG_MUSIC_
XDG_PICTURES_
XDG_VIDEOS_
contains wrong paths.
I fix this in the next stable version (this weekend, 1.1.0), and fix the debug string too. Or try the next daily version tonight.
Revision history for this message
|
#10 |
Hi Kendek,
Many Thanks for such prompt action.
I will wait till next stable version.
David
Revision history for this message
|
#11 |
Hi Kendek,
I have updated to the latest version, 1.1.0.100_
I seem to have partial success.
On Linux Mint17 Cinnamon,
Can create live image, write to USB stick and it Boots fine.
However on Linux Lite 2.0(Ubuntu 14.04)
I still have issues.?
First run,
dave@hp-laptop:~$ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Systemback worker thread error because the following item:
@/home/
so I do a second run, with the .mozzilla excluded,
dave@hp-laptop:~$ sudo systemback
[sudo] password for dave:
update-initramfs: Generating /boot/initrd.
Systemback worker thread error because the following item:
@/home/
dave@hp-laptop:~$
please let me know if there is anything else to try, or information you need.?
Thanks for your support
David
((sorry for posting this on wrong thread/topic))
Revision history for this message
|
#12 |
Hi Kendek,
Further positive update...
I never checked on Linux Lite, it appears that it did not update to 1.1.0100 like it did on LM17.
I have now tried update again, and it is at 1.1.0.100, and it is now working fine on Linux Lite 2.0
Many Thanks for your help & support
Will mark "Problem Solved"
Revision history for this message
|
#13 |
Thanks Kendek, that solved my question.
Revision history for this message
|
#14 |
It's cool, because I changed the debug operation, and what you wrote it would have been impossible. :-)
Revision history for this message
|
#15 |
Not sure what happened.?
I saw the Systemback updates listed in LL2 updates, I applied, and assumed it updated.
Obviously it didn't, when I looked in about, still old version.
Anyway now working.
Will test each option properly.
Thanks... David
Revision history for this message
|
#16 |
I don't know, I use Systemback built-in system upgrader. But really not matter, the point is that good now.
And feel free to let me know if you experience any problems yet.
Revision history for this message
|
#17 |
Hi Kendek.
I have the same problem in System install for SystemBack v 1.2.0_202_
If include the file /etc/skel/
When remove this file work all ok.
I'm testing this in VirtualBox.
Thanks, Ezequiel.
Revision history for this message
|
#18 |
What the source system, and runned from where (currently r. s., restore p. or Live)?
Are you uncheck the "Transfer user configuration and data files" checkbox (so this file is copied to the user directory)?
I ran a few tests, but I could not reproduce this problem. If you try to copy this file with "cp -a" command, do not you get any errors?
Revision history for this message
|
#19 |
The source system is linux mint 17.1 xfce (Linux Mint 17 Qiana).
This happen when select option "System install" and no matter if select the option "Transfer user configuration and data files" , the error is the same.
The command "cp -a" works ok.
Other files in the same directory don't reproduce this error. Only this file. The size is 2.7GB.
Output of command : usr/lib/
mke2fs 1.42.9 (4-Feb-2014)
Etiqueta del sistema de ficheros=SB@
OS type: Linux
Tamaño del bloque=4096 (bitácora=2)
Tamaño del fragmento=4096 (bitácora=2)
Stride=0 blocks, Stripe width=0 blocks
1248480 inodes, 4986624 blocks
249331 blocks (5.00%) reserved for the super user
Primer bloque de datos=0
Número máximo de bloques del sistema de ficheros=0
153 bloque de grupos
32768 bloques por grupo, 32768 fragmentos por grupo
8160 nodos-i por grupo
Respaldo del superbloque guardado en los bloques:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: hecho
Escribiendo las tablas de nodos-i: hecho
Creating journal (32768 blocks): hecho
Escribiendo superbloques y la información contable del sistema de ficheros: 0/hecho
Configurando la versión swapspace 1, tamaño = 1023996 KiB
LABEL=SB@SWAP, UUID=8901dd67-
Systemback worker thread error because the following item:
@/etc/
Thanks, Ezequiel
Revision history for this message
|
#20 |
Please show me the
ls -l /etc/skel/
command output. I will run some other test. So far I can not find the cause.
Revision history for this message
|
#21 |
Hi Kendek.
the output is:
fcuyo@ubuntu ~ $ ls -l /etc/skel/
-rw-rw-rw- 1 root root 2666856448 ene 27 13:08 /etc/skel/
Thanks
Revision history for this message
|
#22 |
Kendek, i don't know if this can help you.
I split the file vm-disk1.vmdk into 3 files of 1024MB and then works ok.
Probe also divided into 2 files of 2048MB but failed with the same error.
Thanks, Ezequiel
Revision history for this message
|
#24 |
Yes.
uname -a
Linux fc-hostname 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux
Revision history for this message
|
#25 |
Okay, now I know what the problem is. :-)
Revision history for this message
|
#26 |
Cool :-)
Back in a few hours.
Thanks.
Revision history for this message
|
#27 |
In principle, this problem has been fixed. But please test it with version 1.2.0.999+bzr190 from nemh/systemback
Revision history for this message
|
#28 |
Hi Kendek, now works perfect.
Thank you very much, Ezequiel
Revision history for this message
|
#29 |
Ok. I updated the stable version too. So this large file problem is gone. :-)