[Installer crashes] Bento antiX i486 Sept. respin

Forum Forums antiX-development antiX Respins [Installer crashes] Bento antiX i486 Sept. respin

  • This topic has 17 replies, 5 voices, and was last updated Sep 22-3:01 pm by skidoo.
Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • #67090
    Member
    melodie

    Hello!

    I am preparing new ISOS 32 and 64bits with some cosmetic improvements and refined choices. I stared about 10 days ago and was stopped by the installer crashing on my new respins when testing in Virtualbox : the installed DOES NOT SEE the storage unit!

    The base I use is antiX 19.

    This is what the output of the line in error looks like when I start minstall manually from the console:

    SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”

    I have pinpointed when and how : I had first thought it might be caused by me removing some packages that I should not have removed (it had happened before), so I reverted to a previous version I had done which works perfectly, and I restarted rebuilding on it.

    Then I decided to do all I wanted in it except one thing : I didn’t update the distro before redoing the snapshot!

    And this one works!

    So I reused it immediatly, installed, this time I updated, redid a respin and BAM ! This time the installer does not see the virtual disk!

    This is why I am now coming here to ask for help.

    I have prepared some files, screenshots, outputs of console, logs from the live where the installer fails.

    $ su-to-root -X -c minstall
    Gkr-Message: 19:13:16.809: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
    Gkr-Message: 19:13:21.120: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
    Gkr-Message: 19:13:21.122: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    qt5ct: using qt5ct plugin
    QFSFileEngine::open: No file name specified
    Cannot write to installer log: “/var/log/minstall.log”
    Installer version: 1.5.4
    +++ void MInstall::startup() +++
    check for remastered home demo folder: false
    Exec #1: du -sb /live/aufs/boot
    Exit #1: 0 QProcess::ExitStatus(NormalExit)
    linuxfs file is at : “/live/boot-dev/antiX/linuxfs”
    Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
    Exit #2: 0 QProcess::ExitStatus(NormalExit)
    linuxfs compression type is “4” compression factor is 25
    Exec #3: df /live/linux –output=used –total |tail -n1
    Exit #3: 0 QProcess::ExitStatus(NormalExit)
    linuxfs file size is 2756706304 rootfs file size is 0
    Minimum space: 268435456 (boot), 3830448128 (root)
    Exec #4: uname -m | grep -q i686
    Exit #4: 0 QProcess::ExitStatus(NormalExit)
    Exec #5: grep -q 64 /sys/firmware/efi/fw_platform_size
    SErr #5: “grep: /sys/firmware/efi/fw_platform_size: Aucun fichier ou dossier de ce type\n”
    Exit #5: 2 QProcess::ExitStatus(NormalExit)
    uefi = false
    +++ void MInstall::setupAutoMount(bool) +++
    Exec #6: ps -e | grep ‘udisksd’
    SOut #6: ” 2590 ? 00:00:00 udisksd\n”
    Exit #6: 0 QProcess::ExitStatus(NormalExit)
    Exec #7: egrep -l ‘^[^#].*mdadm (-I|–incremental)’ /lib/udev/rules.d
    SErr #7: “grep: /lib/udev/rules.d: est un dossier\n”
    Exit #7: 2 QProcess::ExitStatus(NormalExit)
    MkPath(SUCCESS): “/run/udev/rules.d”
    Exec #8: echo ‘SUBSYSTEM==”block”, ENV{UDISKS_IGNORE}=”1″‘ > /run/udev/rules.d/91-mx-udisks-inhibit.rules
    Exit #8: 0 QProcess::ExitStatus(NormalExit)
    Exec #9: udevadm control –reload
    Exit #9: 0 QProcess::ExitStatus(NormalExit)
    Exec #10: udevadm trigger –subsystem-match=block
    Exit #10: 0 QProcess::ExitStatus(NormalExit)
    Exec #11: /bin/ls -1 /home | grep -Ev ‘(lost\+found|demo|snapshot)’ | grep -q [a-zA-Z0-9]
    Exit #11: 1 QProcess::ExitStatus(NormalExit)
    check for possible snapshot: false
    +++ void MInstall::setupkeyboardbutton() +++
    Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
    Exit #12: 0 QProcess::ExitStatus(NormalExit)
    Exec #13: locale -a | grep -Ev ‘^(C|POSIX)\.?’ | grep -E ‘utf8|UTF-8’
    Exit #13: 0 QProcess::ExitStatus(NormalExit)
    Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
    Exit #14: 1 QProcess::ExitStatus(NormalExit)
    Exec #15: dpkg -s samba | grep ‘^Status.*ok.*’ | sed -e ‘s/.*ok //’
    SErr #15: “dpkg-query: le paquet \xC2\xAB\xC2\xA0samba\xC2\xA0\xC2\xBB n’est pas install\xC3\xA9 et aucune information n’est disponible\nUse dpkg –info (= dpkg-deb –info) to examine archive files.\n”
    Exit #15: 0 QProcess::ExitStatus(NormalExit)
    +++ void MInstall::buildServiceList() +++
    +++ void MInstall::updatePartitionWidgets(bool) +++
    +++ void BlockDeviceList::build(MProcess&) +++
    Exec #16: partprobe -s
    SOut #16: “/dev/sda: msdos partitions 1 2\n/dev/sr0: msdos partitions 2\n/dev/zram0: loop partitions 1\n”
    SErr #16: “Warning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\n”
    Exit #16: 0 QProcess::ExitStatus(NormalExit)
    Exec #17: blkid -c /dev/null
    SOut #17: “/dev/loop0: TYPE=\”squashfs\”\n/dev/sda1: UUID=\”74321680-92b7-48cb-87af-43cce4a47526\” TYPE=\”swap\” PARTUUID=\”9e343378-01\”\n/dev/sda2: LABEL=\”rootantiX19\” UUID=\”cc346124-ba70-4900-ab3a-8c124b99e21d\” TYPE=\”ext4\” PARTUUID=\”9e343378-02\”\n/dev/sr0: UUID=\”2021-09-13-07-00-58-00\” LABEL=\”antiXLIVE\” TYPE=\”iso9660\” PTUUID=\”5082fcfe\” PTTYPE=\”dos\”\n/dev/zram0: LABEL=\”SWAP_ZRAM0\” UUID=\”32e1350d-9255-48ba-9499-85596e8fccf3\” TYPE=\”swap\”\n”
    Exit #17: 0 QProcess::ExitStatus(NormalExit)
    Exec #18: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS
    SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”
    Exit #18: 32 QProcess::ExitStatus(NormalExit)
    Name Size Model FS | isDrive isGPT isBoot isESP isNative isStart isNasty
    Exec #19: lsblk -T -bJo TYPE,NAME,UUID,SIZE,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
    Exit #19: 32 QProcess::ExitStatus(NormalExit)
    Segmentation fault
    [demo@antix1:/usr/share/applications/antix]
    $

    (same result using sudo).

    Here is a full zip also including the content from /etc/apt and /var/live : https://nextcloud.orditux.org/s/Lo3qoGg9jf6DBEQ

    Thanks for your help! “:-)

    #67098
    Member
    Xecure
    Helpful
    Up
    0

    3 things:

    A. versions of packages antix-installer (it says in yours 1.5.4), antix-libs, installer-data-antix, gdisk, parted
    apt policy antix-installer antix-libs installer-data-antix gdisk parted

    B. Is your iso snapshot Personal or General?

    C. Did you try using the iso-build tools instead of snapshots?

    antiX Live system enthusiast.
    General Live Boot Parameters for antiX.

    #67099
    Member
    melodie
    Helpful
    Up
    0

    3 things:(…)

    Hi Xecure,

    A :
    antix-installer 1.5.4
    antix-libs 0.8.9
    installer-data-antix 0.2.1
    gdisk 1.0.4-3
    parted 3.2-26
    apt 1.8.4

    policy ? I look closer

    you wrote the rest twice.

    B: General, for redistribution (https://downloads.linuxvillage.org : the lastest free from the issue are being uploaded now)

    C: No I didn’t. I don’t even know what that is. I always use Snapshot.

    I have put the full list of packages extracted from the ISO of the faulty version here : http://pastebin.fr/95300

    Thank you.

    #67103
    Forum Admin
    anticapitalista
    Helpful
    Up
    0

    Another question – does it also fail if you use English rather than French?

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #67106
    Member
    melodie
    Helpful
    Up
    0

    Another question – does it also fail if you use English rather than French?

    Hello,

    do you mean when rebuilding or with the live when starting the installer? I’ll suppose the latter and will try right away.

    #67107
    Member
    melodie
    Helpful
    Up
    0

    I have tested using the default English/default timezeone, it fails the same way.

    I think the issue is likely to come from the packages installed by the last update, at least when using antix-installer 1.35 no problem occurred.

    • This reply was modified 1 week, 5 days ago by melodie.
    #67110
    Forum Admin
    anticapitalista
    Helpful
    Up
    0

    Not sure if this helps you or not.
    I just booted live antiX-19.4 (64 bit) which ships with installer version 1.5.1
    Before installing I upgraded the installer to 1.5.4 then ran it.
    No issues.

    Possible suggestions:

    1. Can you build/remaster Bento from a later antiX-19 iso?
    2. I just noticed that you are referring to the 32 bit version.
    Does your 64 bit one have the same issue?

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #67117
    Member
    melodie
    Helpful
    Up
    0

    Not sure if this helps you or not.
    I just booted live antiX-19.4 (64 bit) which ships with installer version 1.5.1
    Before installing I upgraded the installer to 1.5.4 then ran it.
    No issues.

    Ok…

    1. Can you build/remaster Bento from a later antiX-19 iso?

    I would rather avoid, the process takes lots of time as I build manually + aim 700MB max.

    2. I just noticed that you are referring to the 32 bit version.
    Does your 64 bit one have the same issue?

    The 64bits is also up to date (rebuilt the day before I did the 32bits). It works perfectly and can see the storage device fine, as you can see (attaching a screenshot now).

    #67161
    Member
    melodie
    Helpful
    Up
    0

    If someone saavy who can take time want to help, this is what can be done to reproduce this issue:

    – download the last successful one:
    http://downloads.linuxvillage.org/?C=M;O=D

    [ ] bento-antiX-i486-20210913.iso.sha512 2021-09-13 07:18 160
    [ ] bento-antiX-i486-20210913.iso.md5 2021-09-13 07:18 64
    [ ] bento-antiX-i486-20210913.iso 2021-09-13 07:18 673M

    – Install it to Virtualbox (or any box);

    – update it;
    – make a distributable snapshtot;
    – install the distributable snapshot.

    I have meanwhile, tried to add the debug package for antix-installer, but I don’t know how to use it afterwards so it is pointless.

    Here is a picture of the desktop. (The 64bits has the same image but reversed).

    • This reply was modified 1 week, 4 days ago by melodie.
    • This reply was modified 1 week, 4 days ago by melodie.
    #67165
    Member
    melodie
    Helpful
    Up
    0

    PS: worse case scenario I will rebuild using a native version of antiX when the next stable edition is out. Meanwhile if I can’t fix it in this one I will mark the antix-installer package and all of its dependencies on hold.

    However I hope with your help and the files I have provided (ie : the list of packages brought in by the latest update before the issue which I provided as attachment in the first post + the error message on line #18 for example) that you may be able to help me.

    #67168
    Forum Admin
    anticapitalista
    Helpful
    Up
    0

    I just tested with 32 bit antiX-19.4 in Virtualbox (I don’t have any older versions).
    Ran live, did a dist-upgrade then ran the installer (1.5.4) – no issues.
    So the problem isn’t the installer per se as it works for me and the 64 bit one works for you.
    Something else is missing from your 32 build to cause the error.

    I’ll take a look at your version later today to see if I can see what’s wrong.

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #67182
    Forum Admin
    anticapitalista
    Helpful
    Up
    0

    I can confirm that installer crashes on Bentoo 32 bit.
    Comparing Bentoo 32 and 64 I see the 32 bit has live-boot and live-boot-initramfs-tools plus their dependency packages. They are not in 64 bit version.
    Also 32 bit has more qt5 packages than 64.
    This/they might be the cause.

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #67246
    Member
    melodie
    Helpful
    Up
    0

    Hi,

    then I remove live-boot and live-boot-initramfs-tools. I don’t see any dependency package for them, however. I have searched in Synaptic and couldn’t find any. As for the qt5 packages I am now removing all the ones listed in this screenshot. On the second picture it is the qt5 packages kept.

    I’ll rebuild right after and test the new ISO from there, and report back.

    #67294
    Member
    melodie
    Helpful
    Up
    0

    I have tried that but it didn’t help. However it gave me the idea of doing a diff text file between both 32 and 64bits packages lists, so asap I will work with that and report back here.

    If someone wants to help, I copy it here : http://pastebin.fr/95383

    Thanks a lot for your help. 🙂

    • This reply was modified 1 week, 3 days ago by melodie.
    #67522
    Member
    melodie
    Helpful
    Up
    0

    Hello,

    after some thinking I have marked antix-installer and iso-snapshot-antix on hold, in the console and in Synaptic. From there I have updated the rest of the system and rebuilt the ISO. Now I am installing it in Virtualbox : it works!

    Whenever I can take time next, I’ll try to add and remove packages to make it get approximately the same list of packages that are in the 64bits.

    One thing that I might have done wrong some time ago may have triggered the system to have different versions for the cpp and the gcc packages, which seems strange to me.

    One question which is unclear to me, after one or more rebuilds done using the next versions will the “on hold” on antix-installer and iso-snapshot-antix stick in the next builds ?

    • This reply was modified 6 days, 4 hours ago by melodie.
Viewing 15 posts - 1 through 15 (of 18 total)
  • You must be logged in to reply to this topic.