Both "Use a best-effort default partition layout" and "Suggest partition layout" end with abnormal exit code #2043
Comments
|
i have the same issue |
|
Yeah, I happened for me too. In my case, it failed on bootloader installation. I thought it happened in #2046 too. |
|
I've tried with different version (master, etc.) and none of them is working. As you said, issue start with the disk error. I tried manual portioning, formatting disks, etc. with no success since this morning. |
|
I have the same issue. Is there any solution？ |
|
I didn't find anything. I think you can switch to |
i tried grub and failed |
|
I think this happens because of systemd upgrade. The user creation process is also effected. |
|
it failed for me as well, downgrade the ISO image and it started to work again. I was using M.2 SSD drives from Intel in 2 slots and the installation failed with whatever parameter combination i've tried. Would be nice to understand what is so that it couldn't figure out a working installation configuration. Is there a way to upload the crashlog somehow to this project? |
which ISO version did you downgrade to? |
i have been trying to install since yesterday afternoon, i've tried 9-1, 8-1 and 7-1 iso and failed, only 7-1 successfully installed once and then it stopped working again. Following this to get an update from @smangels |
|
I have the same thing while trying to install on virt-manager. |
|
I think there may be something wrong with archinstall. If I used archinstall to install yesterday, it failed, but if I installed it step by step, it was successful. I just tried it on virtualbox. |
|
It has been an issue with the current version of systemd. And there is a discussion in this ticket. https://bugs.archlinux.org/task/79619. I've switched from systemd to grub and was able to run the complete installation without any issues.
|
|
even downgrading didn't solve the issue because during installation the latest stable version of systemd has been fetched and used. :-) So grub is working. Once the release is out I will reinstall to migrate back to systemd-boot. |
|
Enable core testing in /etc/pacman.conf and then run archinstall. Select testing repo while configuring your options inside the script, i installed successfully with my normal options. |
|
tested without enabling the core testing repos and installs successfully, the new systemd package in is the core repo now 254.3-1 |
so @insidesources does that mean that archinstall will work without errors now? (I am using an arch iso from a few days ago) |
|
I would say yes, the version of systemd that solved arrived yesterday in the stable tree of the package repository - and archinstall will automatically make use of it.
BR,
Re:
…
> tested without enabling the core testing repos and installs successfully, the new systemd package in is the core repo now 254.3-1
>
so @insidesources <https://github.com/insidesources> does that mean that archinstall will work without errors now? (I am using an arch iso from a few days ago)
—
Reply to this email directly, view it on GitHub <#2043 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABC3BOVSPS43M46GR3SG6T3XZZDU5ANCNFSM6AAAAAA4RMI3BE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
So should this issue be closed now (btw I didn't try |
|
The systemd update seems to have solved this problem, I was able to successfully install Arch with the "Suggest partition layout" option and systemd-boot, without needing to enable the testing repo |
install.log
user_configuration.json and user_credentials.json turned up to be binaries, so it's no use uploading them.
From maybe 50 attempted installations so far, 3 have worked so far. If have no idea how to reproduce this. Doesn't seem to make any difference formatting the drive before running archinstall with
wipefsandsgdisk. I don't know if this is coincidental or not, but one install of archinstall has worked being installed on a drive with Arch already installed (by following the official Arch Wiki Installation guide). The soonest moment I know an installation will fail is when the firstPartprobe was not able to inform the kernel of the new disk state (ignoring error): ['/usr/bin/partprobe', '/dev/nvme0n1p2'] exited with abnormal exit code [1]: tition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/nvme0n1p2 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.appears in terminal, if you see these lines you can basically cancel the installation, it will not work anyway
The text was updated successfully, but these errors were encountered: