Installation fails on Phase 2

[Tuhoiisa]

Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)

[Tuhoiisa]

Booting now from the MX-Installer-to-USB stick:

Code: Select all

Snapshot created on: 20241121_1904
System:
  Kernel: 6.11.9-1-liquorix-amd64 [6.11-14~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.11.9-1-liquorix-amd64 root=UUID=<filter> ro
    quiet menu_timeout=6 module_blacklist=floppy overlay.index=0 splash init=/lib/systemd/systemd
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_ahs_x64 Libretto September 15  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop Mobo: AZW model: SER v: V1 serial: <superuser required> UEFI: American Megatrends
    LLC. v: SER6proMax_P5C8V20 date: 08/15/2023
CPU:
  Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
    stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1293 high: 3651 min/max: 400/4829 boost: enabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 400 2: 400 3: 400 4: 400 5: 3169 6: 400
    7: 400 8: 400 9: 3651 10: 400 11: 3150 12: 400 13: 3159 14: 400 15: 3167 16: 400
    bogomips: 102210
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, Writeback-1 bus-ID: e6:00.0
    chip-ID: 1002:1681 class-ID: 0300 temp: 34.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: MD20581 built: 2016 res: 1920x1080 hz: 60 dpi: 82
    gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 676mm (26.6") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon 680M (radeonsi rembrandt LLVM
    15.0.6 DRM 3.59 6.11.9-1-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: e6:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x v: kernel
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_acp_pci, snd_rpl_pci_acp6x,
    snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: e6:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: e6:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.11.9-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:2 chip-ID: 8087:0029
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2184 hci-v: 5.2 rev: 2184
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 2.78 TiB used: 17.89 GiB (0.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:12 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P9CR40A temp: 25.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 5B2QGXA7 temp: 24.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 57.05 GiB size: 55.86 GiB (97.90%) used: 17.89 GiB (32.0%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 40.4 C mobo: 29.5 C gpu: amdgpu temp: 34.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2350 libs: 1201 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
    2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nala-sources.list
    1: deb http://debian.intergenia.de/debian/ bookworm main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64] https://repo.librewolf.net librewolf main
  Active apt repos in: /etc/apt/sources.list.d/mx-repo-ahs.nl-hh-fau-bookworm.sources
    1: deb https://mirror.plusserver.com/mxlinux/mxlinux/mx/repo/ bookworm main non-free ahs
    2: deb https://ftp.fau.de/mxlinux-packages/mx/repo bookworm main non-free ahs
    3: deb https://mxlinux.mirror.iphh.net/packages/mx/repo bookworm main non-free ahs
Info:
  Processes: 397 Uptime: 2m wakeups: 1 Memory: 58.6 GiB used: 2.09 GiB (3.6%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

TBH, I'd rather prefer creating an MX LiveUSB instead of directly installing onto a USB-stick,
but anyway seems to work now.

i looked about creating mx liveusb but that looked complicated so i directly installed it

[fehlix]

Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)

We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:

Code: Select all

Info:
  Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Instead of directly installing onto USB-key, you may consider to create a MX LiveUSB, with help of MX LiveUSB Maker,
where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.

[Tuhoiisa]

Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)

We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:

Code: Select all

Info:
  Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

You may consider to create a MX LiveUSB, where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.

like in this video?
https://www.youtube.com/watch?v=sGVgGMhP1d4

[fehlix]

Sorry i forgot to inform lol creating partitions manually worked but mx linux was soo laggy so i deleted it (probably pendrive issue)

We have meanwhile a fixed version of the MX Installer within the repos.
Note: With this amount of ram:

Code: Select all

Info:
  Processes: 374 Uptime: 14m wakeups: 10 Memory: 15.44 GiB used: 3.22 GiB (20.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

You may consider to create a MX LiveUSB, where you can choose dynamic root persistence, which makes
the system work from ram and any changes can be saved at once, reducing permanent read/write to the USB.
So, you have two advantages: Faster I/O and reduced write cycles onto the USB.
One disadvantage is that you would have to remaster regularly to squeeze back system changes into the read-only, squashed linuxfs file,
thereby releasing the accumulated changes in the rootfs persistence file.

like in this video?
https://www.youtube.com/watch?v=sGVgGMhP1d4

You would use MX Live USB Maker with full featured mode (the default) to create a MX LiveUSB.
Also I do always change under "Advanced.." to GPT and instead of MSDOS/MBR partition table.
Persistence option and other LiveUSB boot options can be set during Liveboot, and also "saved" be be pre-set next live boot.

[Tuhoiisa]

doing it now

[fehlix]

doing it now

You can boot with toram live boot options (found with the live boot options sub menu.)
just for test, which make the whole system running from ram - even faster then installed onto an internal drive.

[Tuhoiisa]

doing it now

You can boot with toram live boot options (found with the live boot options sub menu.)
just for test, which make the whole system running from ram - even faster then installed onto an internal drive.

so if i choose dynamic persistance my system will run on ram and save changes to disk when i shutdown it?

[Tuhoiisa]

Also do u mean static? Because there is no dynamic option

[fehlix]

Also do u mean static? Because there is no dynamic option

root to RAM = dynamic, else static ( this the original terminologie, which we tried to avoid using)