iso is booting to ash shell

No, this isn't normal, but please test it with other machines (VirtualBox). And if you got error, please create .sblive again.

with the new .sblive i got the same result.
i'd cleaned 'splash quiet' commands and error message (last 2 lines after ash prompt) is:
"mount: mounting aufs on /root failed: no such device
aufs mount failed"

command-line parameters are: /casper/vmlinuz boot=casper initrd=/initrd.gz , maybe I can add something manually?

I performed some test with Lubuntu 13.10, but everyfing is fine. I use (upgraded) default Ubuntu kernel from Saucy repository, and I not got any aufs mounting error. If you use a custom kernel, please create .sblive file again with another Linux kernel with aufs support.

i'm using kernel 3.12 from ppa-mainline.
do not think that downgrade to vanilla 3.11 which ships with ubuntu 13.10 shoud solve the problem, but i'll try right now.

thank you for your answers.

hope, that in an hour question would be marked as solved. ;-)

you are totally right: grep with 3.11-0.14-generic returned exactly your results, and on the other hand

# grep AUFS '/boot/config-3.12.0-999-generic'
#

thank you again for the answers.

Thanks Kendek, that solved my question.

Excellent. :-)
Now, when you launch the Systemback GUI on created Live system, the installer will open. But if you don't want to install, then click the 'back' button.

thanks a lot again, all works fine - i'd checked thoroughly.

btw, maybe it would be sensible to add AUFS check to future releases?
and may i suggest additional button - for full cleaning of all systemback's activities (for touchpads with a not big drives it would be a great help)?

thanks again.

Yeah, I add this little checking feature, soon. Thanks for the report.

Please explain this better:

"and may i suggest additional button - for full cleaning of all systemback's activities (for touchpads with a not big drives it would be a great help)?"

What purpose does it serve this button?

it would delete all files, leaved on the harddrive by systemback: sblive, iso and directory with checkpoint(s) by one tap.

if the system is not set properly on a touchpad, or the touchscreen does not work properly (xfce from 13.10 on viewpad 10, for example), one had a great difficulties in clearning free space after creating rescue usb-stick with systemback.

Hm, this situation isn't simple. Live system work with 'UNIONFS=overlayfs' and 'UNIONFS=aufs' options (and more), not just one of them. But Casper check all if it has not been set, and if not available any of the modules, set the aufs (if all else fails fall back to aufs <- while? But true, the filesystem can not be mounted not at all). First, if overlayfs module is available, using it.

Hm, what if this time you connect a mouse (if possible)? Or use a file manager with root permissions.
But anyway, how the Systemback works with touch screen? I use a few specific solutions, but I couldn't try with touch screen.

as to UNIONFS - it's your choice of correct handling the unworkable user's conditions, my point is that user never should create a rescue usb-stick which would never boot, program had to warn him, suggesting a solution (boot with another kernel, checking it if possible), and close itself.

on my viewpad systemback works fine except first opening: all programs, which require root's password, are divided into two groups - first accept input from onscreen keyboard (it's called onboard in ubuntu now), second does not (they block all other windows and accept input only from physical keyboard). it would be nice to change systemback's behaviour. ;-)

Thanks, I will think over these observations.