Hello, thats the problem after trying to install Lubuntu:
Boost.Python error in job "unpackfs".
Command '['mount', '/cdrom/casper/filesystem.squashfs', '/tmp/tmpy_7p65oo/filesystem', '-t', 'squashfs', '-o', 'loop']' returned non-zero exit status 32.
None
Traceback:
File "/usr/lib/x86_64-linux-gnu/calamares/modules/unpackfs/main.py", line 340, in run
return unpackop.run()
File "/usr/lib/x86_64-linux-gnu/calamares/modules/unpackfs/main.py", line 201, in run
self.mount_image(entry, imgmountdir)
File "/usr/lib/x86_64-linux-gnu/calamares/modules/unpackfs/main.py", line 250, in mount_image
"-o", "loop"
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
First thing I would do is verify your install media is perfect (ie. download of ISO & write to media was flawless). You can do this with the Check disk for defects option at the boot menu.
Barring Chris’ suggestion identifying the problem, please provide your installation log file. You can send it to paste.ubuntu.com by doing the following in terminal: pastebinit -i ~/.cache/Calamares/session.log. Include the resulting URL here.
One thing I find strange is that it looks like partitions on the target drive are mounted. The installer should not let you even attempt the install if that’s the case. That may be a bug. In any case, if you unmount them and try again, does everything work fine?
Then you need to either download the ISO again, copy it to installation media again, or both. Keep doing it until the check succeeds.
In Linux, though you have a partition/device connected to the system, the file system is not accessible until you attach it to the root file tree. To access the file system, you mount it, or at least that’s what we call it because the command to do so is mount . You can use the “KDE Partition Manager” in “System Tools” to unmount your partitions and then everything should work correctly.
Presuming you want to install to /dev/mmcblk0p2 (the ext4 partition), you need to make sure to unmount it as I said. See the “mount point” column? That’s the problem. Otherwise, it looks like you have plenty of room on it and you should be good to go.
Also there’s clearly something wrong in your partitioning scheme as it seems like your boot got named boot but not given a boot flag or even a filesystem:
Error: /dev/mmcblk0boot1: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Given you are a self-professed noob, why are you trying to do this complicated partitioning scheme? Just use the default erase disk option and save yourself the trouble.
I reinstalled with bootloader but still doesnt open ia the hard disk.
Changed to UEFI boot but it turns worse: doesnt open the live-stick lubuntu (it presents a black screen)
I will delete all partitions and install Lubunto again in that one general partition (unmounted).
