- This topic has 11 replies, 2 voices, and was last updated Feb 26-11:19 am by olsztyn.
-
Posts
-
olsztyn
I am not sure if this is an old yet unresolved problem with LUM creating encrypted USB (from running system in my case if it matters) or newly arisen problem:
Creating encrypted Live USB from running (Live) system results in failure with message ‘Error creating Live USB’ shortly into the creation process. Creation of non-encrypted one appears to work fine…
I am trying to go back to history to see which workaround was working if not something new… remembering a variety of similar failures under antiX 19:
– Defaulting to LUKS 1 encryption while Debian kernel using Luks 2 – I do not think this is the one because that one was not booting after creation
– Failure after upgrading kernel to 4.19 from 4.9 – this was due to discrepancy version of vmlinuz between one in antiX and in the boot files. The workaround was in that case to fall back to old 4.9 kernel then run Live USB Maker then update kernel in the Live copy to 4.19 kernel.
– Some other issues creating Live USB that also had some workarounds, not remember all…
Since failure of LUM to create encrypted Live USB from running system is critical (at least to me) I have been trying to find another workaround: Create ISO Snapshot from running Live system then using that ISO as input to Live USB Maker to create an encrypted Live USB. This workaround appears to kind of work but does not preserve any configurations so everything needs to be configured again, including desktop settings, application settings (such as browser settings), all defaults and links to apps in Personal Apps menu… This is a lot of work to consider this a workaround for LUM failure to create encrypted Live from running system
This issue appears to be new unless it is a remote manifestation of one of the old issues but I may be wrong.
I will appreciate suggestions of any workarounds if no fix is in sight yet…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersFor further clarity in result of subsequent testing:
– Having made sure antiX is fully updated, Live USB Maker is failing with error when specifying ‘From running system’ and ‘Encrypted’. It appears to be new manifestation of Live USB Maker challenge…
– When running Live USB Maker with ‘Encrypted’ option but specifying ISO snapshot (created beforehand) it appears to work fine and creates a working encrypted copy.
– This would be a working workaround except that when specifying home persistence on the resulting Live USB copy an error occurs (in red during boot) after answering ‘y’ to whether to copy existing files to the new Homefs. This appears to clear all configurations along with existing user files and in effect renders the resulting Live USB rather useless. I was not able to capture the wording of the error in the booting log but this appeared to me a new bug that I have not seen before.Any ideas how now to resolve this Homefs persistence issue so to make further progress in a workaround to Live USB Maker failure?
These things seemed to work fine in old times under antiX 17 but understandably there are many changes since then in antiX 19 so new challenges are here…
Thanks in advance for some ideas…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
anticapitalista
Confirmed. I assume you are running frugal on hard disk when you say running live.
Post the output of live-usb-maker.error and live-usb-maker.log in /var/log.
I couldn’t get clone to work (frugal install).
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I assume you are running frugal on hard disk when you say running live.
Not Frugal. It is from running Live – Live USB. Running Live USB Maker to create a clone with options ‘Clone Running System’ and ‘Encrypt’ results in error ‘Error encountered in Live USB creation process’ soon in the process.
I am trying to cut the relevant part of LUM log from Var as I was running multiple combinations:====================================================================
/usr/local/bin/live-usb-maker gui -N -E -C off –from=clone -t /dev/sdc
program: live-usb-maker
started: Fri 21 Feb 2020 02:55:13 PM EST
version: 2.41.17 (Thu 12 Dec 2019 01:59:33 AM MST)
kernel: 4.19.83-antix.1-amd64-smp
OS: antiX 19 (Marielle Franco)
found lib: /usr/local/lib/cli-shell-utils/cli-shell-utils.bash
lib version: 2.41.05 (Tue 05 Nov 2019 08:50:59 PM MST)
———————————————————————You will be asked to create a passphrase during the first boot
Found man page: live-usb-maker.1
Found live media device /dev/sdb
Will use target device /dev/sdc (28.7G SanDisk Ultra_Fit)
> mount /dev/sdb1 /run/live-usb-maker/bios
Clone running encrypted live system
Live boot directory /antiX
Found (750M) rootfs persistence file
Will clone rootfs persistence file
Found (2.0G) homefs persistence file
Will clone homefs persistence file
Will use source directory /live/boot-dev
Distro: antiX-19_x64-full Marielle Franco 16 October 2019
Found grub config 2.0Encryption enabled
Estimated extfs overhead for 29127M is 44MTotal Used Extra
entire drive 28.6 GiB 28.6 GiB 1 MiB
main partition 28.4 GiB 5.01 GiB 23.4 GiB
bios partition 150 MiB 32 MiB 118 MiB
uefi partition 50 MiB 16 MiB 34 MiB>> encryption-initrd
Checking to see if the live media will support encryption …
> wait_for_file /run/live-usb-maker/iso/antiX/linuxfs
> mkdir -p /run/live-usb-maker/linux
> mount -t squashfs -o loop,ro /run/live-usb-maker/iso/antiX/linuxfs /run/live-usb-maker/linux
> copy-initrd-programs –no-color –from=/run/live-usb-maker/linux –to=/run/live-usb-maker/initrd –clean
Cleaning out all libraries and these program(s): ntfs-3g eject cryptsetup
> copy-initrd-programs –no-color –from=/run/live-usb-maker/linux –to=/run/live-usb-maker/initrd –encrypt
add program: ntfs-3g
add program: eject
add program: cryptsetup
add 4.19.83-antix.1-amd64-smp encryption modules to initrd
> copy-initrd-modules –quiet –only-encrypt –from=/run/live-usb-maker/linux –to=/run/live-usb-maker/initrd
Ready to make encrypted live-usb on device sdc
… by cloning directory /live/boot-dev>> partition-clear
> dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34
> dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34 seek=64
> dd status=none conv=notrunc if=/dev/zero of=/dev/sdc bs=512 count=34 seek=60063710
> partprobe /dev/sdc>> partition-make
Using msdos partitioning
> parted –script –align optimal /dev/sdc unit MiB mklabel msdos
> dd status=none if=/dev/zero of=/dev/sdc seek=1024 bs=1K count=128
> parted –script –align optimal /dev/sdc unit MiB mkpart primary 1 150
> parted –script –align optimal /dev/sdc unit MiB set 1 boot on
> dd status=none if=/dev/zero of=/dev/sdc seek=153600 bs=1K count=128
> parted –script –align optimal /dev/sdc unit MiB mkpart primary 150 29276
> dd status=none if=/dev/zero of=/dev/sdc seek=29978624 bs=1K count=128
> parted –script –align optimal /dev/sdc unit MiB mkpart primary 29276 29325
> parted –script –align optimal /dev/sdc unit MiB set 3 esp on
> partprobe /dev/sdc
> wait_for_file /dev/sdc1>> makefs-bios
> mkfs.ext4 -O ^64bit -m0 -i100000 -J size=32 /dev/sdc1
mke2fs 1.44.5 (15-Dec-2018)
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 152576 1k blocks and 1672 inodes
Filesystem UUID: 0c79153b-4483-4c9d-bbeb-79208605cc6d
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729Allocating group tables: 0/19 done
Writing inode tables: 0/19 done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: 0/19 done> tune2fs -L antiX-Live-usb /dev/sdc1
tune2fs 1.44.5 (15-Dec-2018)
> wait_for_file /dev/sdc3>> makefs-uefi
> mkfs.vfat -F 32 -n ANTIX-UEFI /dev/sdc3
mkfs.fat 4.1 (2017-01-24)>> encrypt-main
> wait_for_file /dev/sdc1
Error: Directory /run/live-usb-maker/bios is already a mountpoint
_____________________________________________________________________________________________The other error I mentioned when trying to work out a workaround was not related to LUM but rather to setting up Home persistence (persistence = all), where during boot upon question whether to copy existing files. If answered ‘y’ then process fails with red messages, which I could not capture and copy fails.
I did not tesst yet whether this happens with any occurrence of setting home persistence or just on copy made through LUM from system snapshot.
Thanks for understanding.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHaving done lots of testing to narrow down the source of this error I was able to pinpoint this error to Live USB Maker version change from 0.4.5 (synaptic) to 0.4.6. In Live USB log it is change from 2.41.16 to 2.41.17.
I realized I had updated antiX (indiscriminately running antiX Updater) that apparently resulted the error in LUM cloning Live USB (encrypted). Therefore I went back to a saved previous version, before my careless update (trusting only good things may be brought about by update…) and confirmed:
– Previous Version 2.41.16 of Live USB Maker does not experience this error and creates a clone of encrypted Live USB correctly. I just had to remember to fall back the kernel from 4.19 to 4.9 as without that fallback the resulting copy of Live USB fails booting with fatal dm-crypt error. This is a known fact and was extensively explained by BitJam some time ago along with challenge for LUM due to different versions of vmlinuz between antiX and startup files.
– Not having an older version of antiX Live saved, so having just updated antiX, would have presented a challenge of finding a workaround in cloning a Live USB (encrypted).
– One possibility considered was ISO snapshot. This did not work out and actually appears to have exposed another (possibly unrelated to LUM) issue: Although LUM does not complain and creates Live USB (encrypted) from ISO image and the resulting Live USB boots, it does so forgetting all original desktop and application settings and persistence options. Upon specifying persistence at boot time it fails on the step to copy existing files to homefs. This defeats the entire idea of workaround. This error happens both with old version of LUM (2.41.16) and new and new LUM, so perhaps it is not related to LUM but rather to ISO snapshot.To summarize two issues:
– Live USB Maker 2.41.17 fails with error (encrypted clone from running system), while version 2.41.16 worked fine (with kernel 4.9, so kernel 4.19 requires fallback).
– Live USB (encrypted) from ISO snapshot (regardless whether LUM version is old or new) does not remember any desktop and application settings and persistence files. Upon specifying persistence during boot it fails on the step to copy existing files to homefs.- This reply was modified 3 years, 2 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAs the fix for above #1 LUM issue will take some time and #2 above issue (probably not due to LUM as it happens with any recent LUM version) I would like to take separately I have a general question on antiX update:
– Having myself done such foolish thing as to let antiX update without thourough testing beforehand, how can I roll back some piece of update (in this case Live USB Maker) to the version before antiX update? Is there an established process for this, such as deleting such package and separately installing from previous version repository?
Any help will be greatly appreciated.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHaving myself done such foolish thing as to let antiX update without thourough testing beforehand, how can I roll back some piece of update (in this case Live USB Maker) to the version before antiX update?
I apologize for being pain on this but please understand that capability of rolling back version of particular misbehaving package is quite important to be comfortable with maturity of the system.
So can please someone advise me on this:
If e.g. Live-USB-Maker has been updated to the new release in result of antiX update, is this possible (and how) to re-instate the previous version? Any help would be greatly appreciated…
Thanks much in advance.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
Are you sure it’s live-usb-maker or live-usb-maker-gui?
Anyhow, you can manually download the deb from the archive (once you have found it – I found it for you) and install with gdebi or
sudo dpkg -i *.debhttps://repo.antixlinux.com/archive/buster/main/DEBS/19-11-19/
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Thanks. I assume this would be a general process – find specific older package in some archive and install…
I appreciate your help.
On the following:Are you sure it’s live-usb-maker or live-usb-maker-gui?
I am not sure. However my conjecture is Live-USB-Maker, not gui for the reasons:
– Triggered from gui starts execution producing initial log messages and doing some job, such as partitioning and formatting partitions before it errors out means to me the actual program runs at that time, gui left behind.
– Gui did not change from previous release, at least nothing seems to indicate thisThanks and Regards.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAre you sure it’s live-usb-maker or live-usb-maker-gui?
Confirmed. After falling back to the older version of Live-USB-Maker while leaving gui version as is (latest) worked as expected.
This older version of Live-USB-Maker executed without failing and produced a copy of Live-usb antiX just as before antiX update. Just need to remember to fall back kernel version to 4.9 beforehand Live-USB-Maker execution (known but manageable issue).
Thanks again for finding this older version in archives…
Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
I’m surprised that the older version works for encrypting a clone to be honest.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I’m surprised that the older version works for encrypting a clone to be honest.
Originally there were several separate issues such as:
– Luks 1 default in antiX while Debian Buster was Luks 2 and used as default to decrypt. The fix was to force Luks 1.
– If kernel was updated from 4.9 (original antiX) the resulting clone failed to boot. This was caused by vmlinuz version conflicting with one in startup.I remember BitJam and other developers fixed the first issue while the second is manageable (just falling back to 4.9 before making clone). I also remember that BitJam was planning in early December to fix the second issue, which appeared more involved and required more time.
- This reply was modified 3 years, 2 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
