Systemback

Boot error: aufs mount failed

Asked by MBWD

I'm trying to boot from a Systemback-created USB Live system from Ubuntu 15.04 running the 4.1.2 kernel. Systemback created the .sblive with no problem. It ended up being 4.3GB, so I had to use the .sblive file (not an .iso) to create the USB Live System. When I boot from the USB, it starts on the Systemback splash page. But when I select any of the 4 options it fails with:

    stdin: I/O error
    mounting aufs on /root failed: No such device
    aufs mount failed

I tried this suggestion from https://answers.launchpad.net/systemback/+question/240163:

    grep AUFS '/boot/config-4.1.2-040102-generic'

But it returned nothing (although that file is in the /boot directory). In response to the previous question (240163), you wrote "If you not got this command output with your current kernel, not use Systemback Live system creator." But I'm not sure if that means that Systemback can't be used -- or something else.

THANKS!

Question information

Language:
English Edit question
Status:
Solved
For:
Systemback Edit question
Assignee:
No assignee Edit question
Solved by:
MBWD
Solved:
Last query:
Last reply:

This question was reopened

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

This 4.1.2-040102-generic kernel (downloaded from http://kernel.ubuntu.com/~kernel-ppa) does not contains any aufs supports, but includes the new overlayfs (CONFIG_OVERLAY_FS=m).
Your aufs error messages are printed by the Casper (see the /usr/share/initramfs-tools/scripts/casper script). Try the union=overlay option, see the following screenshot:
http://logout.hu/dl/upc/2016-01/180556_union.png
If this solution does not work, please use the default Ubuntu kernel from the repository.

Revision history for this message
MBWD (xmbwd) said : 		#2

Thanks Kendek, that solved my question.

Revision history for this message
MBWD (xmbwd) said : 		#3

I apologize: I marked that solved too soon. A few follow up questions.

I tried inserting the phrase "union=overlay" using the .sblive created with kernel 4.1.2, and that did not work. I got the same error.

I then installed kerel 4.1 from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-wily/, and when inserting the "union=overlay" phrase at startup the aufs error went away. Now, the sole error is:

    [1.166496] tmp_tis 00:07 [Firmware Bug]: TPM interrupt not working, polling instead
    starting version 219

    BusyBox v.1.22.1 (ubuntu 1:1.220-9ubuntu1) built in shell (ash) ....
    (initramfs)

Is this progress?

Is there a specific kernel that you suggest?

Revision history for this message
MBWD (xmbwd) said : 		#4

So I went down to the 3.19.0-26-generic kernel, and that worked right away on boot.

I guess I'll have to create my .sblive backups using that kernel.

Revision history for this message
MBWD (xmbwd) said : 		#5

Thanks Kendek, that solved my question.

Revision history for this message
MBWD (xmbwd) said : 		#6

Follow up question that would REALLY help me out: how do I find and install a kernel, say 4.3, that has AUFS?

I know from one of your prior posts how to determine if one of my installed kernels has AUFS support:

grep AUFS /boot/config-KERNEL_NAME

But I don't know how to find a kernel that I want (I'm on a Chromebook right now, so I need either 4.2 or 4.3 to keep everything functioning) that has AUFS.

Hopefully, this may help others as well.

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

Just download and install a kernel from the Ubuntu repository:
- 15.10, 4.2:
http://packages.ubuntu.com/wily-updates/linux-image-4.2.0-34-generic
http://packages.ubuntu.com/wily-updates/linux-image-extra-4.2.0-34-generic
http://packages.ubuntu.com/wily-updates/linux-headers-4.2.0-34-generic
http://packages.ubuntu.com/wily-updates/linux-headers-4.2.0-34
- 16.04, 4.4:
http://packages.ubuntu.com/xenial/linux-image-4.4.0-16-generic
http://packages.ubuntu.com/xenial/linux-image-extra-4.4.0-16-generic
http://packages.ubuntu.com/xenial/linux-headers-4.4.0-16-generic
http://packages.ubuntu.com/xenial/linux-headers-4.4.0-16

Revision history for this message
MBWD (xmbwd) said : 		#8

Thank you!

Revision history for this message
MBWD (xmbwd) said : 		#9

I wanted to append this information to the answer, in case anyone is using alternative kernels and would like AUFS support. I was in this scenario because I am running Ubuntu 15.10 on a Toshiba Chromebook 2, and most of the default/stable kernels regress a particular function, like the sound, touchpad, suspend, etc. I found some mainline kernels that worked great on all fronts except AUFS support. And I NEED Systemback. It is such a great way to keep Live System backups.

Anywho, here is a terrific guide to adding AUFS support to a (maybe mainline) kernel that works for you: http://zackreed.me/articles/90-ubuntu-14-04-with-4-0-4-kernel-and-latest-aufs-from-source. I looked at a bunch of other guides, and they all resulted in errors. This one works great, with a few very minor caveats:

1. Skip wget'ing the mainline kernel and patches (step 2) if you want to build from a downloaded xz.gz
2. Depending on what kernel you want, it may not be at kernel.org's main page. Instead, go to https://www.kernel.org/pub/linux/kernel/v4.x/ and find the one you want.
3. If you use one of those kernels, you won't need to patch the kernel, but you will need to #Apply AUFS patches
4. Check to confirm that the copy from AUFS to the Kernel directory is at the right place in /include/uapi/linux! It's a long haul to get this thing compiled, only to find out later you put it in the wrong directory.
5. When you do the make menuconfig the default may already be right (check the picture), and it IS correct for the main AUFS to have <M> instead of a *. Don't forget to Save!!!
6. After reboot, the rest of the guide is for NFS, which you don't need.

With this guide, you can find a kernel that works for you, then add AUFS, then use Systemback to your heart's content. Thanks again Kendek!
7. You get a header error, but it still works!