Installing Antix21: “Failed to prepare required partitions”

Forum Forums Official Releases antiX-21/22 “Grup Yorum” Installing Antix21: “Failed to prepare required partitions”

  • This topic has 18 replies, 9 voices, and was last updated Apr 3-5:42 pm by crantix.
Viewing 4 posts - 16 through 19 (of 19 total)
  • Author
    Posts
  • #90671
    Moderator
    BobC
      Helpful
      Up
      0
      ::

      Next time run the antiX updater after you boot and get connected to the internet. Take defaults on any questions.

      after it finishes, then run the installer from the desktop

      Also, I had better luck running the Modern Kernel. It took trying to do the whole disk the first time, aborting on the error, then going back in and customizing it. It was not straightforward at all.

      • This reply was modified 6 months, 4 weeks ago by BobC.
      #91206
      Member
      Arsenallish
        Helpful
        Up
        0
        ::

        Hello. I tried to install antiX 22 onto my Thinkpad T400. I tried doing the “Customize the disk layout” and then took the encrypted layout in the right click menu and didn’t modify it. At 9% it gives the “Failed to open LUKS container.” error message and installation stops just like with OP. This also occurs when I choose the full disk install with encryption. I think it will happen any time there is LUKS involved.

        Looking at gparted, the partitions seem to have been created but doing “open encryption” on the root partition does not work after putting in the password, probably because it was never created completely in the first place.

        I disabled the auto mount, and it still is not working. I would really like to be able to try out antiX, so I would love to know how to fix this. Thanks.

        Here is the system inxi output from the installation media:

        System:
          Kernel: 4.9.0-326-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
            v: 10.2.1 Desktop: IceWM v: 3.0.1 dm: slimski v: 1.5.0
            Distro: antiX-22_x64-full Grup Yorum 18 October 2022
            base: Debian GNU/Linux 11 (bullseye)
        Machine:
          Type: Laptop System: LENOVO product: 2768HH4 v: ThinkPad T400
            serial: <superuser required> Chassis: type: 10 serial: <superuser required>
          Mobo: LENOVO model: 2768HH4 serial: <superuser required> BIOS: LENOVO
            v: 7UET94WW (3.24 ) date: 10/17/2012
        Memory:
          RAM: total: 7.79 GiB used: 552.1 MiB (6.9%)
          RAM Report:
            permissions: Unable to run dmidecode. Root privileges required.
        CPU:
          Info: dual core model: Intel Core2 Duo P9500 bits: 64 type: MCP
            smt: <unsupported> arch: Penryn Yorkfield rev: A cache: L1: 128 KiB
            L2: 6 MiB
          Speed (MHz): avg: 800 min/max: 800/2534 boost: enabled cores: 1: 800
            2: 800 bogomips: 10108
          Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
            cx16 cx8 de ds_cpl dtes64 dtherm dts est flexpriority fpu fxsr ht ida
            kaiser lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm
            pebs pge pni pse pse36 rep_good sep smx ss sse sse2 sse4_1 ssse3 syscall
            tm tm2 tpr_shadow tsc vme vmx vnmi xsave xtpr
        Graphics:
          Device-1: AMD RV620/M82 [Mobility Radeon HD 3450/3470] vendor: Lenovo
            driver: radeon v: kernel arch: TeraScale ports: active: LVDS-1
            empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:95c4 class-ID: 0300
          Device-2: Lenovo Integrated Webcam type: USB driver: uvcvideo
            bus-ID: 1-6:4 chip-ID: 17ef:1004 class-ID: 0e02 serial: <filter>
          Display: server: X.Org v: 1.20.11 driver: X: loaded: radeon
            unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1
          Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
            s-diag: 449mm (17.69")
          Monitor-1: LVDS-1 mapped: LVDS model: Lenovo 0x4036 res: 1440x900 hz: 60
            dpi: 120 size: 304x190mm (11.97x7.48") diag: 358mm (14.1") modes:
            max: 1440x900 min: 640x480
          OpenGL:
            renderer: AMD RV620 (DRM 2.49.0 / 4.9.0-326-antix.1-amd64-smp LLVM 11.0.1)
            v: 3.3 Mesa 20.3.5 compat-v: 3.0 direct render: Yes
        Audio:
          Device-1: Intel 82801I HD Audio vendor: Lenovo ThinkPad T400
            driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e
            class-ID: 0403
          Sound Server-1: ALSA v: k4.9.0-326-antix.1-amd64-smp running: yes
        Network:
          Device-1: Intel 82567LM Gigabit Network vendor: Lenovo ThinkPad T400
            driver: e1000e v: 3.2.6-k port: 1840 bus-ID: 00:19.0 chip-ID: 8086:10f5
            class-ID: 0200
          IF: eth0 state: down mac: <filter>
          Device-2: Intel Ultimate N WiFi Link 5300 driver: iwlwifi v: kernel
            bus-ID: 03:00.0 chip-ID: 8086:4236 class-ID: 0280
          IF: wlan0 state: up mac: <filter>
          IP v4: <filter> scope: global broadcast: <filter>
          IP v6: <filter> scope: link
          WAN IP: <filter>
        Bluetooth:
          Message: No bluetooth data found.
        Logical:
          Message: No logical block device data found.
        RAID:
          Message: No RAID data found.
        Drives:
          Local Storage: total: 935.29 GiB used: 1.39 GiB (0.1%)
          ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
            speed: 3.0 Gb/s type: SSD serial: <filter> rev: 043 scheme: MBR
          ID-2: /dev/sdb type: USB vendor: USBest
            model: Technology USB Mass Storage Device size: 3.77 GiB type: N/A
            serial: <filter> rev: 0.00 scheme: MBR
          Message: No optical or floppy data found.
        Partition:
          ID-1: /live/boot-dev size: 3.76 GiB used: 1.39 GiB (37.0%) fs: vfat
            dev: /dev/sdb1 label: ANTIX-LIVE uuid: D63C-0DDB
        Swap:
          Alert: No swap data was found.
        Unmounted:
          ID-1: /dev/sda1 size: 1024 MiB fs: ext4 label: boot
            uuid: 4c12db23-dced-42d8-923b-9d72fe2379f9
          ID-2: /dev/sda3 size: 8 GiB fs: <superuser required> label: N/A uuid: N/A
        USB:
          Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s
            chip-ID: 1d6b:0002 class-ID: 0900
          Device-1: 1-1:2 info: Transcend Information 2GB/4GB/8GB Flash Drive
            type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
            speed: 480 Mb/s power: 98mA chip-ID: 1307:0165 class-ID: 0806
            serial: <filter>
          Device-2: 1-6:4 info: Lenovo Integrated Webcam type: Video
            driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
            chip-ID: 17ef:1004 class-ID: 0e02 serial: <filter>
          Hub-2: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0
            speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
          Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-5: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-6: 6-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-7: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-8: 8-0:1 info: Full speed or root hub ports: 2 rev: 1.1
            speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
          Hub-9: 9-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
            speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
          Hub-10: 10-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s
            chip-ID: 1d6b:0003 class-ID: 0900
        Sensors:
          System Temperatures: cpu: 42.0 C mobo: 40.0 C
          Fan Speeds (RPM): fan-1: 3424
        Info:
          Processes: 147 Uptime: 3h 3m wakeups: 3 Init: SysVinit v: 2.96 runlevel: 5
          default: 5 Compilers: gcc: 10.2.1 alt: 10 Packages: apt: 1569 Shell: Bash
          v: 5.1.4 running-in: roxterm inxi: 3.3.19
        #91210
        Member
        Arsenallish
          Helpful
          Up
          0
          ::

          Next time run the antiX updater after you boot and get connected to the internet. Take defaults on any questions.

          after it finishes, then run the installer from the desktop

          Also, I had better luck running the Modern Kernel. It took trying to do the whole disk the first time, aborting on the error, then going back in and customizing it. It was not straightforward at all.

          This seems to have worked. Thank you.

          #104005
          Member
          crantix
            Helpful
            Up
            0
            ::

            I have also been struggling with the encrypted installation with the same error message: “Failed to open LUKS container”. After numerous intents I finally managed to get it done, so I share the setup for future reference.

            I created the necessary partitions with GParted:
            EFI system in fat32 (500MB), boot in ext4 (1GB) and two more partitions for the encrypted root and swap.

            I then created the LUKS partitions from the terminal as it cannot be done with GParted:
            sudo cryptsetup luksFormat /dev/sdaNUMBER
            where sdaNUMBER is the corresponding root and swap partition.

            With GParted I opened the encrypted partitions and formatted them accordingly: root as ext4 and swap as swap. Then I closed the partitions again.

            In the installer, I selected the EFI partition for the use as ESP and the boot partition for the use as /boot, which I selected as the active partition right clicking on it. I then rightclicked on the root and swap partitions to unlock them and confirm that they be included in the crypttab. Those two encrypted partitions then appear below as virtual volumes and can be selected for the use as /root and swap.

            I hope this can be reproduced by anyone who might be having difficulties with the encrypted installation, as there seems to be no step to step guide to help with it. It is a bit tricky indeed.

            • This reply was modified 1 month ago by crantix.
          Viewing 4 posts - 16 through 19 (of 19 total)
          • You must be logged in to reply to this topic.