Android USB Tethering to a newbie arch freshinstall

JTWALLON · 2023-02-03 18:50:25

Hi guys,

this will be my first post here so, I will have to trust whatever you say, so please dont lie to me

Here is my issue:

for purposes I would love not to share,
I have to "share" my mobile internet
over USB from my Android to my machines for now.

However the speed is at max a 200KiB/s on Arch,
on my other machines that run Mint or even Windows,
the speed is around 20Mb/s.
(I had similar speeds on this exact machines before I did Arch)

Would be very helpful to know how I could speed thing up

thanks

Head_on_a_Stick · 2023-02-03 20:48:42

How did you configure tethering? Please provide the exact command(s) and/or configuration file(s).

JTWALLON wrote:

I will have to trust whatever you say

Don't worry — if I try to bullshit you the community will be on me like a pack of rabid dogs. Peer review ftw!

And please don't add linebreaks. If I want the text to be narrow I will reduce the size of the browser window.

JTWALLON · 2023-02-03 20:51:30

I just used the UI an the android to enable the USB tethering, and it somehow worked without any setting up on the machine side.

Head_on_a_Stick · 2023-02-03 20:53:44

Which networking services are enabled?

Please post the output of

ls -lR /etc/systemd/system

JTWALLON · 2023-02-03 21:00:23

/etc/systemd/system:
total 24
lrwxrwxrwx 1 root root   48 Feb  1 12:54 dbus-org.freedesktop.network1.service -> /usr/lib/systemd/system/systemd-networkd.service
lrwxrwxrwx 1 root root   48 Feb  1 12:54 dbus-org.freedesktop.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
lrwxrwxrwx 1 root root   49 Feb  1 13:32 dbus-org.freedesktop.timesync1.service -> /usr/lib/systemd/system/systemd-timesyncd.service
lrwxrwxrwx 1 root root   39 Feb  1 13:31 display-manager.service -> /usr/lib/systemd/system/lightdm.service
drwxr-xr-x 2 root root 4096 Feb  1 12:50 getty.target.wants
drwxr-xr-x 2 root root 4096 Feb  1 12:54 multi-user.target.wants
drwxr-xr-x 2 root root 4096 Feb  1 12:54 network-online.target.wants
drwxr-xr-x 2 root root 4096 Feb  1 12:54 sockets.target.wants
drwxr-xr-x 2 root root 4096 Feb  1 13:32 sysinit.target.wants
drwxr-xr-x 2 root root 4096 Feb  1 12:50 timers.target.wants

/etc/systemd/system/getty.target.wants:
total 0
lrwxrwxrwx 1 root root 38 Feb  1 12:50 getty@tty1.service -> /usr/lib/systemd/system/getty@.service

/etc/systemd/system/multi-user.target.wants:
total 0
lrwxrwxrwx 1 root root 40 Feb  1 12:50 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target

lrwxrwxrwx 1 root root 48 Feb  1 12:54 systemd-networkd.service -> /usr/lib/systemd/system/systemd-networkd.service

/etc/systemd/system/network-online.target.wants:
total 4
lrwxrwxrwx 1 root root 60 Feb  1 12:54 systemd-networkd-wait-online.service -> /usr/lib/systemd/system/systemd-networkd-wait-online.service

/etc/systemd/system/sockets.target.wants:
total 0
lrwxrwxrwx 1 root root 47 Feb  1 12:54 systemd-networkd.socket -> /usr/lib/systemd/system/systemd-networkd.socket

/etc/systemd/system/sysinit.target.wants:
total 0
lrwxrwxrwx 1 root root 57 Feb  1 12:54 systemd-network-generator.service -> /usr/lib/systemd/system/systemd-network-generator.service
lrwxrwxrwx 1 root root 48 Feb  1 12:54 systemd-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
lrwxrwxrwx 1 root root 49 Feb  1 13:32 systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service

/etc/systemd/system/timers.target.wants:
total 0
lrwxrwxrwx 1 root root 36 Feb  1 12:50 fstrim.timer -> /usr/lib/systemd/system/fstrim.timer

Last edited by JTWALLON (2023-02-03 21:26:45)

Head_on_a_Stick · 2023-02-03 21:05:21

Please use code tags when posting terminal output.

Looks like you're using systemd-networkd but I thought that had to be configured to connect with a specific network interface

How did you install Arch, exactly? Which guide did you follow?

JTWALLON · 2023-02-03 21:17:00

I just used archinstall and nothing else that would be of network importance

Head_on_a_Stick · 2023-02-03 21:25:05

So was the box tethered during installation? Please provide the installation log.

In respect of the actual problem perhaps try https://wiki.archlinux.org/title/Networ … tification.

And please edit post #5 and add code tags. It greatly aids readability.

JTWALLON · 2023-02-03 21:30:50

Here is the install log, and yes the machine was being tethered from the start.

Hardware model detected: LENOVO 3238AA5; UEFI mode: False
Processor model detected: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz
Memory statistics: 7605084 available out of 8023628 total installed
Could not detect virtual system: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
System is not running in a VM: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
Virtualization detected: None; is VM: None
Graphics devices detected: dict_keys(['Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)'])
Disk states before installing: {'blockdevices': [{'name': 'loop0', 'fstype': 'squashfs', 'fsver': '4.0', 'label': None, 'uuid': None, 'fsavail': '0', 'fsuse%': '100%', 'mountpoints': ['/run/archiso/airootfs'], 'type': 'loop', 'size': '689.8M'}, {'name': 'sda', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'disk', 'size': '465.8G', 'children': [{'name': 'sda1', 'fstype': 'vfat', 'fsver': 'FAT32', 'label': None, 'uuid': '817B-A3FE', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'part', 'size': '200M'}, {'name': 'sda2', 'fstype': 'ext4', 'fsver': '1.0', 'label': None, 'uuid': 'dce9396c-6da1-4260-a158-6acf358792dd', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'part', 'size': '465.6G'}]}, {'name': 'sdb', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202207', 'uuid': '2022-07-01-13-20-00-00', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'disk', 'size': '7.3G', 'children': [{'name': 'sdb1', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202207', 'uuid': '2022-07-01-13-20-00-00', 'fsavail': '0', 'fsuse%': '100%', 'mountpoints': ['/run/archiso/bootmnt'], 'type': 'part', 'size': '782M'}, {'name': 'sdb2', 'fstype': 'vfat', 'fsver': 'FAT16', 'label': 'ARCHISO_EFI', 'uuid': '4D09-F5F8', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'part', 'size': '13M'}]}]}
Testing connectivity to the Arch Linux mirrors ...
Updating archlinux-keyring ...
Setting font: LatGrkCyr-8x16
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Password strength: very weak
 * Passwords did not match * 
Password strength: very weak
Password strength: very weak
 -- Chosen configuration --
{
    "HSM": null,
    "__separator__": null,
    "additional-repositories": [
        "multilib"
    ],
    "archinstall-language": "English",
    "audio": "pulseaudio",
    "bootloader": "grub-install",
    "config_version": "2.5.1",
    "debug": false,
    "harddrives": [
        "/dev/sda"
    ],
    "hostname": "archlinux",
    "kernels": [
        "linux"
    ],
    "keyboard-layout": "cz",
    "mirror-region": {
        "Czechia": {
            "http://ftp.fi.muni.cz/pub/linux/arch/$repo/os/$arch": true,
            "http://ftp.linux.cz/pub/linux/arch/$repo/os/$arch": true,
            "http://ftp.sh.cvut.cz/arch/$repo/os/$arch": true,
            "http://gluttony.sin.cvut.cz/arch/$repo/os/$arch": true,
            "http://mirror.dkm.cz/archlinux/$repo/os/$arch": true,
            "http://mirror.it4i.cz/arch/$repo/os/$arch": true,
            "http://mirror.vpsfree.cz/archlinux/$repo/os/$arch": true,
            "http://mirrors.nic.cz/archlinux/$repo/os/$arch": true,
            "https://europe.mirror.pkgbuild.com/$repo/os/$arch": true,
            "https://ftp.sh.cvut.cz/arch/$repo/os/$arch": true,
            "https://gluttony.sin.cvut.cz/arch/$repo/os/$arch": true,
            "https://mirror.dkm.cz/archlinux/$repo/os/$arch": true,
            "https://mirror.it4i.cz/arch/$repo/os/$arch": true,
            "https://mirrors.nic.cz/archlinux/$repo/os/$arch": true
        }
    },
    "nic": {
        "dhcp": true,
        "dns": null,
        "gateway": null,
        "iface": null,
        "ip": null,
        "type": "iso"
    },
    "no_pkg_lookups": false,
    "ntp": true,
    "offline": false,
    "packages": [
        "firefox",
        "htop",
        "neofetch"
    ],
    "parallel downloads": 0,
    "profile": null,
    "save_config": null,
    "script": "guided",
    "silent": false,
    "swap": true,
    "sys-encoding": "UTF-8",
    "sys-language": "en_US",
    "timezone": "Europe/Prague",
    "version": "2.5.1"
}
{
    "/dev/sda": {
        "partitions": [
            {
                "boot": true,
                "encrypted": false,
                "filesystem": {
                    "format": "fat32"
                },
                "mountpoint": "/boot",
                "size": "203MiB",
                "start": "3MiB",
                "type": "primary",
                "wipe": true
            },
            {
                "encrypted": false,
                "filesystem": {
                    "format": "ext4",
                    "mount_options": []
                },
                "mountpoint": "/",
                "size": "100%",
                "start": "206MiB",
                "type": "primary",
                "wipe": true
            }
        ],
        "wipe": true
    }
}
Creating a new partition label on /dev/sda
Adding partition to BlockDevice(/dev/sda, size=465.8GB, free_space=3145kB+3146kB+24.6kB, bus_type=sata), 3MiB->203MiB
Adding partition using the following parted command: /dev/sda mkpart primary fat32 3MiB 203MiB
Retrieving partition PARTUUID=b62f3701-01 or UUID=None
Matched PARTUUID=b62f3701-01 against b62f3701-01
Formatting /dev/sda1 -> vfat
/usr/bin/mkfs.vfat -F32 /dev/sda1
Marking partition Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat) as bootable.
Setting boot on on (parted) partition index 1
Adding partition to BlockDevice(/dev/sda, size=465.8GB, free_space=3145kB+3146kB+24.6kB, bus_type=sata), 206MiB->100%
Adding partition using the following parted command: /dev/sda mkpart primary ext4 206MiB 100%
Retrieving partition PARTUUID=b62f3701-02 or UUID=None
Matched PARTUUID=b62f3701-02 against b62f3701-02
Formatting /dev/sda2 -> ext4
Mounting / to /mnt/archinstall/ using Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4)
Mounting /boot to /mnt/archinstall/boot using Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat)
Using mount order: [('/', <function Installer.mount_ordered_layout.<locals>.<lambda> at 0x7fa851deb2e0>), ('/boot', <function Installer.mount_ordered_layout.<locals>.<lambda> at 0x7fa851deb130>)]
Mounting Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4) to /mnt/archinstall/
Getting mount information for device path /mnt/archinstall
Mounting Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat) to /mnt/archinstall/boot
Getting mount information for device path /mnt/archinstall/boot
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Filtering available mounts {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat, mounted=/mnt/archinstall/boot)} to those under /mnt/archinstall
Available partitions: {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat, mounted=/mnt/archinstall/boot)}
Waiting for automatic mirror selection (reflector) to complete.
Waiting for dbus-org.freedesktop.timesync1.service to enter running state
A new package mirror-list has been created: /etc/pacman.d/mirrorlist
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Filtering available mounts {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat, mounted=/mnt/archinstall/boot)} to those under /mnt/archinstall
Available partitions: {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=465.6, PARTUUID=b62f3701-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=b62f3701-01, fs=vfat, mounted=/mnt/archinstall/boot)}
System is not running in a VM: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
The multilib flag is set. This system will be installed with the multilib repository enabled.
The testing flag is not set. This system will be installed without testing repositories enabled.
Installing packages: ['base', 'base-devel', 'linux-firmware', 'linux', 'grub', 'intel-ucode']

Could not strap in packages: ['/usr/bin/pacstrap', '-C', '/etc/pacman.conf', '/mnt/archinstall', 'base', 'base-devel', 'linux-firmware', 'linux', 'grub', 'intel-ucode', '--noconfirm'] exited with abnormal exit code [None]: b'-6.1.8.arch...    48.1 MiB   730 KiB/s 02:42 [######----------------]  29%\r\x1b[1E Total (  1/145)       218.2 MiB   730 KiB/s 07:53 [########--------------]  39%\r\x1b[1F linux-6.1.8.arch...    48.2 MiB   660 KiB/s 02:59 [######----------------]  29%\r\x1b[1E Total (  1/145)       218.4 MiB   660 KiB/s 08:43 [########--------------]  39%\r\x1b[1F linux-6.1.8.arch...    48.2 MiB   511 KiB/s 03:52 [######----------------]  29%\r\x1b[1E Total (  1/145)       218.4 MiB   511 KiB/s 11:15 [########--------------]  39%\r'

Hardware model detected: LENOVO 3238AA5; UEFI mode: False
Processor model detected: Intel(R) Core(TM) i5-3470T CPU @ 2.90GHz
Memory statistics: 7599960 available out of 8023628 total installed
Could not detect virtual system: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
System is not running in a VM: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
Virtualization detected: None; is VM: None
Graphics devices detected: dict_keys(['Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)'])
Disk states before installing: {'blockdevices': [{'name': 'loop0', 'fstype': 'squashfs', 'fsver': '4.0', 'label': None, 'uuid': None, 'fsavail': '0', 'fsuse%': '100%', 'mountpoints': ['/run/archiso/airootfs'], 'type': 'loop', 'size': '689.8M'}, {'name': 'sda', 'fstype': None, 'fsver': None, 'label': None, 'uuid': None, 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'disk', 'size': '465.8G', 'children': [{'name': 'sda1', 'fstype': 'vfat', 'fsver': 'FAT32', 'label': None, 'uuid': '04F7-549D', 'fsavail': '196.9M', 'fsuse%': '0%', 'mountpoints': ['/mnt/archinstall/boot'], 'type': 'part', 'size': '200M'}, {'name': 'sda2', 'fstype': 'ext4', 'fsver': '1.0', 'label': None, 'uuid': '45986836-9615-4a89-bbc0-47c118872faf', 'fsavail': '433.7G', 'fsuse%': '0%', 'mountpoints': ['/mnt/archinstall'], 'type': 'part', 'size': '465.6G'}]}, {'name': 'sdb', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202207', 'uuid': '2022-07-01-13-20-00-00', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'disk', 'size': '7.3G', 'children': [{'name': 'sdb1', 'fstype': 'iso9660', 'fsver': 'Joliet Extension', 'label': 'ARCH_202207', 'uuid': '2022-07-01-13-20-00-00', 'fsavail': '0', 'fsuse%': '100%', 'mountpoints': ['/run/archiso/bootmnt'], 'type': 'part', 'size': '782M'}, {'name': 'sdb2', 'fstype': 'vfat', 'fsver': 'FAT16', 'label': 'ARCHISO_EFI', 'uuid': '4D09-F5F8', 'fsavail': None, 'fsuse%': None, 'mountpoints': [None], 'type': 'part', 'size': '13M'}]}]}
Testing connectivity to the Arch Linux mirrors ...
Setting font: LatGrkCyr-8x16
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Password strength: very weak
Password strength: very weak
 -- Chosen configuration --
{
    "HSM": null,
    "__separator__": null,
    "additional-repositories": [
        "multilib"
    ],
    "archinstall-language": "English",
    "audio": "pulseaudio",
    "bootloader": "grub-install",
    "config_version": "2.5.1",
    "debug": false,
    "desktop-environment": "i3",
    "gfx_driver": "Intel (open-source)",
    "harddrives": [
        "/dev/sda"
    ],
    "hostname": "archlinux",
    "kernels": [
        "linux"
    ],
    "keyboard-layout": "cz",
    "mirror-region": {
        "Czechia": {
            "http://ftp.fi.muni.cz/pub/linux/arch/$repo/os/$arch": true,
            "http://ftp.linux.cz/pub/linux/arch/$repo/os/$arch": true,
            "http://ftp.sh.cvut.cz/arch/$repo/os/$arch": true,
            "http://gluttony.sin.cvut.cz/arch/$repo/os/$arch": true,
            "http://mirror.dkm.cz/archlinux/$repo/os/$arch": true,
            "http://mirror.it4i.cz/arch/$repo/os/$arch": true,
            "http://mirror.vpsfree.cz/archlinux/$repo/os/$arch": true,
            "http://mirrors.nic.cz/archlinux/$repo/os/$arch": true,
            "https://europe.mirror.pkgbuild.com/$repo/os/$arch": true,
            "https://ftp.sh.cvut.cz/arch/$repo/os/$arch": true,
            "https://gluttony.sin.cvut.cz/arch/$repo/os/$arch": true,
            "https://mirror.dkm.cz/archlinux/$repo/os/$arch": true,
            "https://mirror.it4i.cz/arch/$repo/os/$arch": true,
            "https://mirrors.nic.cz/archlinux/$repo/os/$arch": true
        }
    },
    "nic": {
        "dhcp": true,
        "dns": null,
        "gateway": null,
        "iface": null,
        "ip": null,
        "type": "iso"
    },
    "no_pkg_lookups": false,
    "ntp": true,
    "offline": false,
    "packages": [
        "firefox",
        "htop",
        "neofetch"
    ],
    "parallel downloads": 0,
    "profile": {
        "path": "/usr/lib/python3.10/site-packages/archinstall/profiles/desktop.py"
    },
    "save_config": null,
    "script": "guided",
    "silent": false,
    "swap": true,
    "sys-encoding": "UTF-8",
    "sys-language": "en_US",
    "timezone": "Europe/Prague",
    "version": "2.5.1"
}
{
    "/dev/sda": {
        "partitions": [
            {
                "boot": true,
                "encrypted": false,
                "filesystem": {
                    "format": "fat32"
                },
                "mountpoint": "/boot",
                "size": "203MiB",
                "start": "3MiB",
                "type": "primary",
                "wipe": true
            },
            {
                "encrypted": false,
                "filesystem": {
                    "format": "ext4",
                    "mount_options": []
                },
                "mountpoint": "/",
                "size": "20GiB",
                "start": "206MiB",
                "type": "primary",
                "wipe": true
            },
            {
                "encrypted": false,
                "filesystem": {
                    "format": "ext4",
                    "mount_options": []
                },
                "mountpoint": "/home",
                "size": "100%",
                "start": "20GiB",
                "type": "primary",
                "wipe": true
            }
        ],
        "wipe": true
    }
}
Creating a new partition label on /dev/sda
Adding partition to BlockDevice(/dev/sda, size=465.8GB, free_space=3145kB+3146kB+24.6kB, bus_type=sata), 3MiB->203MiB
Adding partition using the following parted command: /dev/sda mkpart primary fat32 3MiB 203MiB
Retrieving partition PARTUUID=2d11db31-01 or UUID=None
Matched PARTUUID=2d11db31-01 against 2d11db31-01
Formatting /dev/sda1 -> vfat
/usr/bin/mkfs.vfat -F32 /dev/sda1
Marking partition Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat) as bootable.
Setting boot on on (parted) partition index 1
Adding partition to BlockDevice(/dev/sda, size=465.8GB, free_space=3145kB+3146kB+24.6kB, bus_type=sata), 206MiB->20GiB
Adding partition using the following parted command: /dev/sda mkpart primary ext4 206MiB 20GiB
Retrieving partition PARTUUID=2d11db31-02 or UUID=None
Matched PARTUUID=2d11db31-02 against 2d11db31-02
Formatting /dev/sda2 -> ext4
Adding partition to BlockDevice(/dev/sda, size=465.8GB, free_space=3145kB+3146kB+24.6kB, bus_type=sata), 20GiB->100%
Adding partition using the following parted command: /dev/sda mkpart primary ext4 20GiB 100%
Retrieving partition PARTUUID=2d11db31-03 or UUID=None
Matched PARTUUID=2d11db31-03 against 2d11db31-03
Formatting /dev/sda3 -> ext4
Mounting / to /mnt/archinstall/ using Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4)
Mounting /boot to /mnt/archinstall/boot using Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat)
Mounting /home to /mnt/archinstall/home using Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4)
Using mount order: [('/', <function Installer.mount_ordered_layout.<locals>.<lambda> at 0x7fe7173ca680>), ('/boot', <function Installer.mount_ordered_layout.<locals>.<lambda> at 0x7fe7173cac20>), ('/home', <function Installer.mount_ordered_layout.<locals>.<lambda> at 0x7fe7173caef0>)]
Mounting Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4) to /mnt/archinstall/
Getting mount information for device path /mnt/archinstall
Mounting Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat) to /mnt/archinstall/boot
Getting mount information for device path /mnt/archinstall/boot
Mounting Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4) to /mnt/archinstall/home
Getting mount information for device path /mnt/archinstall/home
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Filtering available mounts {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)} to those under /mnt/archinstall
Available partitions: {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)}
Waiting for automatic mirror selection (reflector) to complete.
A new package mirror-list has been created: /etc/pacman.d/mirrorlist
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Filtering available mounts {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)} to those under /mnt/archinstall
Available partitions: {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)}
System is not running in a VM: ['/usr/bin/systemd-detect-virt'] exited with abnormal exit code [256]: b'none\r\n'
The multilib flag is set. This system will be installed with the multilib repository enabled.
The testing flag is not set. This system will be installed without testing repositories enabled.
Installing packages: ['base', 'base-devel', 'linux-firmware', 'linux', 'grub', 'intel-ucode']
Enabling periodic TRIM
Enabling service fstrim.timer
Setting up swap on zram
Installing packages: ('zram-generator',)
Enabling service systemd-zram-setup@zram0.service
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb1 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Unreliable results might be given for /dev/sdb2 due to partprobe error: ['/usr/bin/partprobe', '/dev/sdb'] exited with abnormal exit code [256]: b'Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\r\n'
Filtering available mounts {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)} to those under /mnt/archinstall
Available partitions: {PosixPath('/mnt/archinstall'): Partition(path=/dev/sda2, size=19.8, PARTUUID=2d11db31-02, fs=ext4, mounted=/mnt/archinstall), PosixPath('/mnt/archinstall/home'): Partition(path=/dev/sda3, size=445.8, PARTUUID=2d11db31-03, fs=ext4, mounted=/mnt/archinstall/home), PosixPath('/mnt/archinstall/boot'): Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)}
Adding bootloader grub-install to Partition(path=/dev/sda1, size=0.2, PARTUUID=2d11db31-01, fs=vfat, mounted=/mnt/archinstall/boot)
Installing packages: ('grub',)
GRUB uses /dev/sda1 as the boot partition.
Enabling service systemd-networkd
Enabling service systemd-resolved
This audio server will be used: pulseaudio
Installing packages: ('pulseaudio',)
Installing packages: ['firefox', 'htop', 'neofetch']
Installing archinstall profile Profile(desktop)
Installing packages: ['nano', 'vim', 'openssh', 'htop', 'wget', 'iwd', 'wireless_tools', 'wpa_supplicant', 'smartmontools', 'xdg-utils']
Installing archinstall profile Profile(i3)
Installing packages: ['i3lock', 'i3status', 'i3blocks', 'xterm']
Installing archinstall profile Profile(xorg)
Installing packages: ('xorg-server', 'xorg-xinit', 'mesa', 'libva-intel-driver', 'intel-media-driver', 'vulkan-intel')
Installing packages: ['lightdm-gtk-greeter', 'lightdm', 'dmenu']
Enabling service lightdm
Installing packages: ('i3-gaps',)
Creating user glue
Setting password for glue
Enabling sudo permissions for glue.
Activating systemd-timesyncd for time synchronization using Arch Linux and ntp.org NTP servers.
Enabling service systemd-timesyncd
Setting password for root
Setting keyboard language to cz
Keyboard language for this installation is now set to: cz
Updating /mnt/archinstall/etc/fstab
For post-installation tips, see https://wiki.archlinux.org/index.php/Installation_guide#Post-installation
Installation completed without any errors. You may now reboot.

Last edited by JTWALLON (2023-02-03 21:35:29)

Head_on_a_Stick · 2023-02-03 21:54:26

So the tethering was configured by archinstall then. That makes sense now.

Does disabling ECN help? It doesn't quite fit your circumstance but it's the only thing I can think of.

JTWALLON · 2023-02-03 22:12:21

I just noticed that its slow only when getting packages, while in firefox its 10Mb/s, still slower then avg but much faster then the package download.
I have set up my mirrors correctly.
And disabling the ECN did not help or worsen it.

Last edited by JTWALLON (2023-02-03 22:13:11)

Head_on_a_Stick · 2023-02-03 23:35:25

JTWALLON wrote:

I just noticed that its slow only when getting packages

Have you tried a different mirror?

Reference: https://wiki.archlinux.org/title/Mirror … ng_mirrors

Arch Linux

#1 2023-02-03 18:50:25

Android USB Tethering to a newbie arch freshinstall

#2 2023-02-03 20:48:42

Re: Android USB Tethering to a newbie arch freshinstall

#3 2023-02-03 20:51:30

Re: Android USB Tethering to a newbie arch freshinstall

#4 2023-02-03 20:53:44

Re: Android USB Tethering to a newbie arch freshinstall

#5 2023-02-03 21:00:23

Re: Android USB Tethering to a newbie arch freshinstall

#6 2023-02-03 21:05:21

Re: Android USB Tethering to a newbie arch freshinstall

#7 2023-02-03 21:17:00

Re: Android USB Tethering to a newbie arch freshinstall

#8 2023-02-03 21:25:05

Re: Android USB Tethering to a newbie arch freshinstall

#9 2023-02-03 21:30:50

Re: Android USB Tethering to a newbie arch freshinstall

#10 2023-02-03 21:54:26

Re: Android USB Tethering to a newbie arch freshinstall

#11 2023-02-03 22:12:21

Re: Android USB Tethering to a newbie arch freshinstall

#12 2023-02-03 23:35:25

Re: Android USB Tethering to a newbie arch freshinstall

Board footer