Systemback works fine in Sparky

[eightbit]

Just figured I'd chime in as I had a really difficult time creating a live ISO using sparky remastersys fork. I am using Gnome 3 built on top of Sparky minimalCLI (which is working great by the way!) and it would go through the steps but the final iso would not be bootable. Then I downloaded the Systemback installer from Sourceforge and gave it a try. It had Debian 8 on the list when launched but complained about not being compatible with this version. I selected the Debian 8 option anyway and initially it would not install because of the current live-installer. Uninstalled it along with the sparky remastersys and it went through without a hitch. I used it today to create a live image and it boots and works perfectly. Systemback has really grown up over the years that I have been testing it and it is in my personal opinion way superior to the old remastersys technology. This should be included in Sparky in my opinion as it just works. Just throwing this out there for anyone else having issues creating a live backup.

Edit: I also just tested reinstalling my live image created with systemback and it went through perfectly. Looks like a winner :)

[banerd]

hi eightbit, i too am a big fan of Systemback. however, i am having trouble installing. would you please put a link to the systemback version you used. and anyother specific's you used to get it installed. thanks.

[eightbit]

Well, it was not that hard.

Download the latest version from:

https://sourceforge.net/projects/systemback/

Unzip to a folder and:

Code Select Expand

sudo ./install.sh

Use the Debian Jessie 8 option.



Systemback does not officially support Debian testing but it *had* worked for me for months. Only recently with recent updates it only creates a live image that kernel panics when run. It did not do this until last week. So, if you want to create a live image you should do it on a pre-v4.3 version of sparky. My image is using kernel 4.4.0.1 and Gnome 3.20.1 and it is fine. If I install it and update it it is also fine. But if I install it, update it and then try to create a new image it is not bootable. In short, something broke it (creating live images using systemback) in testing VERY recently.

[banerd]

Got it . Thank you. I have a restore point . i will test it out during the week.

[J.Jay]

Systemback does not officially support Debian testing but it *had* worked for me for months. Only recently with recent updates it only creates a live image that kernel panics when run. It did not do this until last week. So, if you want to create a live image you should do it on a pre-v4.3 version of sparky. My image is using kernel 4.4.0.1 and Gnome 3.20.1 and it is fine. If I install it and update it it is also fine. But if I install it, update it and then try to create a new image it is not bootable. In short, something broke it (creating live images using systemback) in testing VERY recently.
« Last Edit: May 02, 2016, 06:47:49 am by eightbit »

have you tried a different kernel (maybe the 'Jessie' one?)(can download from debian packages)  or uninstalling the package 'kernel-image(amd64?) and upgrading system (would act like pinning so sys upgrade won't pull newer kernel?

J.Jay

[eightbit]

Systemback does not officially support Debian testing but it *had* worked for me for months. Only recently with recent updates it only creates a live image that kernel panics when run. It did not do this until last week. So, if you want to create a live image you should do it on a pre-v4.3 version of sparky. My image is using kernel 4.4.0.1 and Gnome 3.20.1 and it is fine. If I install it and update it it is also fine. But if I install it, update it and then try to create a new image it is not bootable. In short, something broke it (creating live images using systemback) in testing VERY recently.
« Last Edit: May 02, 2016, 06:47:49 am by eightbit »

have you tried a different kernel (maybe the 'Jessie' one?)(can download from debian packages)  or uninstalling the package 'kernel-image(amd64?) and upgrading system (would act like pinning so sys upgrade won't pull newer kernel?

J.Jay

Some package is doing it, but I don't think it is the kernel as I have tried updating the system and suppressing the kernel (leaving it at 4.4.0.1) and still a new live image will freeze. If you want to give it a go, download my custom Gnome spin (here in this forum), install and update it and then try creating a new live image. Maybe you can get to to bottom of it.

[pavroo]

Creating Sparky 4.3 iso images I found two separated issues:
1. Busybox 1.22.0-19 makes the kernel panic so downgrade it to version 1.22.0-18, download from:
https://sourceforge.net/projects/sparkylinux/files/files/apps/
2. Even the live system boots up, it stopped and did not run the x server.
If Linux kernel 4.5.x is pre-installed as default, make sure you have not 'virtualbox-utils' packege installed.

[eightbit]

Creating Sparky 4.3 iso images I found two separated issues:
1. Busybox 1.22.0-19 makes the kernel panic so downgrade it to version 1.22.0-18, download from:
https://sourceforge.net/projects/sparkylinux/files/files/apps/
2. Even the live system boots up, it stopped and did not run the x server.
If Linux kernel 4.5.x is pre-installed as default, make sure you have not 'virtualbox-utils' packege installed.

Thanks for the advice. I will try it!

[eightbit]

It WAS busybox that was causing my issue. I can't thank you enough for the advice. I was banging my head against the keyboard for weeks on this!

[pavroo]

The issue is fixed now (by Debian devs).
The latest 'live-boot' and 'live-boot-intramfs-tools' 20160511 packages work fine with the latest version of BusyBox now.

[godstand2]

Why not Systemback???I really love SparkyLinux the most of all distros for it is sooooo fast on all computers Old and new(by the way the 32bit is what I use even on 64bit computers). I was wondering after I have already set up my sparky how can I make a backup disk with all my settings and apps and not just a hybrid iso like sparkybackup dist does and keep it for an emergencies to install it to say another computer, Like I can with Systemback does.It also gives you the option to install for a new user. I had installed System back on Sparkylink test machines and tried to use the copy user data and settings box checked and it said that it could not read Live image even when i tried to install the same thing happened, from the ISO I had made of the system using Systemback. I could run the live cd but not copy or install even with out box checked for user data and settings always "Could not read Live image error." I have made an ISO from Sparkybackup dist and it runns with all the the stuff i put in root folder including wine,games and programs as long as I installed them in root folder running as root also settings for root like themes and cursors the live disk ran with out a hitch even installed on another hdd but not with users setting or data was the image made so i would have to start all over again to set up slimjet browser for the user that is only browser I use as well have to setup appearance,screensavers,cursors and so on.All this work time and energy makes johnny boy here tired. It would be so nice to copy my system to my other computers with all settings and data intact and also from same disk install for new user with the little bit of the extras I have installed in root.The Sparkybackup ISO was 1.9GB size when I got done making it using the xz setting.