Cannot mount live image aborted install

Asked by john

Good evening,

I installed SystemBack on Linux Mint Sarah and had some initial issues I sorted out (the issues with casper / "missing operating system error at boot). Now I can boot from and run live systemback images without issue, however, I run into issues during install. Namely, I get the error "Installation Aborted / Cannot mount live system." Does anyone have any experience with or ideas regarding this error?

Question information

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

First, please start the Systemback from a terminal emulator (on the Live System), with the following command:

DBGLEV=3 systemback-sustart

and try to install the system. After the error message, show me the terminal output.

Revision history for this message
GMaq (info-bandshed) said :
#2

Hi,

I just ran into the exact same issue with a Systemback ISO made from Debian testing which I've been using successfully with Systemback for quite some time, unfortunately that machine is not connected to the internet but the issue is that /lib/live/mount/medium/live/filesystem.squashfs doesn't mount. I will try and post the exact output from the terminal tomorrow.

Could there be a permissions issue with 'filesystem.squashfs'?

Revision history for this message
GMaq (info-bandshed) said :
#3

Hi, here is the output of a failed install:

isotester@avl64box:~$ DBGLEV=3 systemback-sustart

 Systemback

 Version: 1.8.402_05.16.2016_Qt5.7.1(5.3.2)_GCC4.9.2_amd64
 Compilation date and time: May 16 2016 13:50:15
 Installed files: /etc/xdg/autostart/sbschedule-kde.desktop
                  /etc/xdg/autostart/sbschedule.desktop
                  /usr/bin/systemback
                  /usr/bin/systemback-cli
                  /usr/bin/systemback-sustart
                  /usr/lib/systemback/libsystemback.so
                  /usr/lib/systemback/libsystemback.so.1
                  /usr/lib/systemback/libsystemback.so.1.0
                  /usr/lib/systemback/libsystemback.so.1.0.0
                  /usr/lib/systemback/sbscheduler
                  /usr/lib/systemback/sbsustart
                  /usr/lib/systemback/sbsysupgrade
                  /usr/share/applications/systemback-kde.desktop
                  /usr/share/applications/systemback.desktop
                  /usr/share/systemback/efi-amd64.bootfiles
                  /usr/share/systemback/lang/systemback_ar_EG.qm
                  /usr/share/systemback/lang/systemback_ca_ES.qm
                  /usr/share/systemback/lang/systemback_cs.qm
                  /usr/share/systemback/lang/systemback_da_DK.qm
                  /usr/share/systemback/lang/systemback_de.qm
                  /usr/share/systemback/lang/systemback_en_GB.qm
                  /usr/share/systemback/lang/systemback_es.qm
                  /usr/share/systemback/lang/systemback_fi.qm
                  /usr/share/systemback/lang/systemback_fr.qm
                  /usr/share/systemback/lang/systemback_gl_ES.qm
                  /usr/share/systemback/lang/systemback_hu.qm
                  /usr/share/systemback/lang/systemback_id.qm
                  /usr/share/systemback/lang/systemback_pt_BR.qm
                  /usr/share/systemback/lang/systemback_ro.qm
                  /usr/share/systemback/lang/systemback_ru.qm
                  /usr/share/systemback/lang/systemback_tr.qm
                  /usr/share/systemback/lang/systemback_uk.qm
                  /usr/share/systemback/lang/systemback_zh_CN.qm
 Operating system: Debian GNU/Linux stretch/sid
 Mounted filesystems: /dev/sr0 /lib/live/mount/medium iso9660 ro,noatime 0 0
                      /dev/loop0 /lib/live/mount/rootfs/filesystem.squashfs squ
                      ashfs ro,noatime 0 0
                      /dev/sda1 /media/SB@ ext4 rw,nosuid,relatime,data=ordered
                       0 0
 System language: en_CA
 Translation: -

 An error occurred while executing the following command:

  modprobe efivars

 Exit code: 1

mke2fs 1.43.3 (04-Sep-2016)
/dev/sda1 contains a ext4 file system labelled 'SB@'
 last mounted on / on Fri Dec 23 13:53:10 2016
Creating filesystem with 3931904 4k blocks and 983040 inodes
Filesystem UUID: 1bf10334-1860-411b-885e-f8d733f3537e
Superblock backups stored on blocks:
 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

mkswap: /dev/sda2: warning: wiping old swap signature.
Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
LABEL=SB@SWAP, UUID=51236f85-7798-4969-a5f5-483a4033a69d

 An error occurred while mounting the following partition/image:

  /lib/live/mount/medium/live/filesystem.squashfs

 /lib/live/mount/medium/live/filesystem.squashfs
  f r--r--r-- 1 0 0 2816 3.24GiB
 /lib/live/mount/medium/live
  d r-xr-xr-x - 0 0 2816 -
 /lib/live/mount/medium
  d r-xr-xr-x - 0 0 2816 -
 /lib/live/mount
  d rwxr-xr-x - 0 0 19 -
 /lib/live
  d rwxr-xr-x - 0 0 19 -
 /lib
  d rwxr-xr-x - 0 0 19 -

 Errno: 2

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

Hm, Debian stretch/sid? I think it is a simple incompatibility issue, because a Debian changes...

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

So the Systemback try to use the old
/lib/live/mount/medium/live/filesystem.squashfs
instead of
/lib/live/mount/rootfs/filesystem.squashfs

Revision history for this message
GMaq (info-bandshed) said :
#6

Hi,

OK in Debian you can roll back packages to previous versions, what system packages do you think would cause the change?

Revision history for this message
GMaq (info-bandshed) said :
#7

Hi,

Systemback was working for me with the same system previously, I have Debian Testing based ISO's from August 2016 that still install properly. If I can determine with your help if 'live-boot' or 'squashfs-tools' are the cause I can try to roll them back since the change happened sometime since August

Revision history for this message
Launchpad Janitor (janitor) said :
#8

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.