Systemback

Unable to create iso file and errors during installation

Asked by TMG1961

Hi,

I am using Linux Lite 2.0 and installed systemback.
I cant make a iso file, the option is grayed out and the created backup file isnt visible..also cant change the folder were the backups are stored.

During the installation of systemback i get the following message;
W: Possible missing firmware /lib/firmware/radeon/hainan_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hainan_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hainan_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hainan_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hainan_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hainan_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/oland_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/verde_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/pitcairn_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/tahiti_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_sdma.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_mec.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/mullins_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_sdma.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_mec.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kabini_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_sdma.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_mec2.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_mec.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/kaveri_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_sdma.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_mec.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/hawaii_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_smc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_sdma.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_mec.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/bonaire_pfp.bin for module radeon

Is there something i am missing or is systemback not compatible with linux lite 2.0?

Thanks for your help.

Question information

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

The "Create new" button (in "Live system create" menu) is disabled if:
- Live system name is wrong (not 'auto' or the pipe isn't visible)
- The current - Linux - kernel isn't compatible (missing aufs, unionfs or overlayfs support), or unionfs-fuse package isn't installed (this is very slow solution); use stock Ubuntu kernel
- The working directory isn't accessible (red background)

"the created backup file isnt visible..also cant change the folder were the backups are stored"
Please explain this out more.
What backup file? Maybe restore point? This isn't just a file...
What folder? Maybe restore points storage directory? What's wrong with setting up this directory?

Revision history for this message
TMG1961 (theo-gijzen) said : 		#2

Hi,

Thanks for the answer.

I do mean the restore point with the created backup file and yes i also mean the restore points storage directory

When i use the live system create button i cant convert to iso or any other option. All the buttons are greyed out and in the created live images box there isnt a live image visible although i did create one. That is stored in /home/systemback. The working directory points to /home

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

The default storage directory is '/home'. The 'Systemback' subdirectory is created there (always created automatically in storage directories), and this isn't selectable (reserved name). If you already created a restore point, just select the directory with green point (existing storage directory).

If the Live image (.sblive file in working directory) is succesfully created (not get error), it will appear in the "Created Live images" box. If you select a created Live image (with mouse click), you can delete it, if you select a write target device, then you can write it, and if the image size is smaller than 4 GiB (ISO limit) and there is enough free space (SBLIVE size * 2), you can convert it to ISO.

These things are OK?

Revision history for this message
TMG1961 (theo-gijzen) said : 		#4

The first part is clear,

The second part is something i cant do.

Here is what i did and see:
1. i clicked on create new under point operations.
2. after the restore point is made i see it listed under resyore points
3. i clicked on live system create
4. i can see my usb device that is plugged in under write target
5. under working directory it says /home
6. under name of live system it says auto
7. under created live images..no entries
8. under live operations..no buttons selectable..all greyed out

The size of the restore point is 3.2 GB, Free space is 42 GB

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

If you using non-compatible kernel (no aufs, unionfs or overlayfs support) and if unionfs-fuse package isn't installed (very slow solution), then this is a normal thing. Because Live system isn't working with incompatible kernel, the filesystem cannot be writable. Please install stock Ubuntu kernel (linux-image-generic), boot it and try again the Live creation.

Revision history for this message
TMG1961 (theo-gijzen) said : 		#6

This is what i got out of the systems information. I dont have a clue what the things are that you mentioned in previous post and dont think it is installed. I will have to look into it and see if i can find out how to install it and see if it will run ok then. If not then just hope for the best and if all fails then reinstall once again.

Kernel : Linux 3.17.0-linuxlite (x86_64)
Compiled : #1 SMP Tue Oct 7 14:09:29 NZDT 2014
C Library : Unknown
Default C Compiler : GNU C Compiler version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
Distribution : Ubuntu 14.04.1 LTS
Desktop Environment : XFCE 4

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

I don't know this 3.17.0-linuxlite kernel. This isn't the stock Ubuntu kernel, and maybe not compatible with Live systems. I need the source code to tell, but if Systemback isn't detected aufs, unionfs or overlayfs support, it's probably not good.
Please install unionfs-fuse package

sudo apt-get install unionfs-fuse

and check the "Create new" button again. If this button will enable, the kernel is the problem.

Revision history for this message
TMG1961 (theo-gijzen) said : 		#8

Thank you so much for helping me. I did install unionfs-fuse and all is working now.

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

Ok, but please keep in mind that this is a very slow solution. If you would like high speed, then you must use a compatible kernel.

Revision history for this message
TMG1961 (theo-gijzen) said : 		#10

i will keep it in mind. Most important is that its working. I got time enough so no problem if it is slow.