Archiso not working!

krolmiki2011 · 2024-10-19 10:15:41

Hello!, I have a "tiny" problem with archiso i have part of logs:
:: Synchronizing package databases...
error: could not open file /home/mikolaj/Pulpit/SummitOS/work/x86_64/airootfs/var/lib/pacman/sync/download-VCUYh1/summitos.db.part: Permission denied
error: failed to setup a download payload for summitos.db
error: failed to synchronize all databases (failed to retrieve some files)
==> ERROR: Failed to install packages to new root
Somebody please help!!!!

gromit · 2024-10-19 10:25:27

Please always post full logs and use code tags for them ...
So where is this summitos.db coming from? Is this even an arch installation?

The problem is that the download user is not able to access the db due to the sandboxing options in pacman.conf. This could probably be fixed by setting DisableSandbox in the pacman.conf of archiso .. https://gitlab.archlinux.org/archlinux/ … quests/393

Last edited by gromit (2024-10-19 10:30:46)

Lone_Wolf · 2024-10-19 11:25:10

Moving to Installation

gromit · 2024-10-20 16:58:12

For reference: https://gitlab.archlinux.org/archlinux/ … issues/232

bingma · 2024-10-31 05:41:11

gromit wrote:

This could probably be fixed by setting DisableSandbox in the pacman.conf of archiso .. https://gitlab.archlinux.org/archlinux/ … quests/393

I disabled DownloadUser and set DisableSandbox, but the iso can't boot. It produces an iso, but when booting the iso:
Error: device '' not found. Skipping fsck.
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel-device mapper driver.
Command failed

bingma · 2024-10-31 06:02:15

And I want to know how to add microcode to initrd parameter for custom iso. If I don't add the parameter to initrd, the kernel will load microcode very late, which is late loading, the CPU already used the old instructions.

seth · 2024-10-31 07:25:01

I disabled DownloadUser and set DisableSandbox, but the iso can't boot.

Disabled where if the iso doesn't even boot?
Also "Error: device '' not found. Skipping fsck." looks like you added some bogus kernel parameter? Why would the iso be looking for

This thread is more about some custom repo having turned inaccessible w/ pacman v7 than any installation iso.
It's not really clear what you're doing there to access DM.

What iso are you trying to boot, where did you get it, how did you write it and what adjustments are you trying to make at the bootloader?

progandy · 2024-10-31 09:20:18

seth wrote:

I disabled DownloadUser and set DisableSandbox, but the iso can't boot.
Disabled where if the iso doesn't even boot?

It looke like krolmiki2011 is buiding their own iso and the first permissions error was during the iso build process. (Edit: Probably they are in the process of creating a new arch based distribution)

Have you tried booting the current official arch iso file, does that work? And what about building a default arch iso without your custom configuration, does that boot?

Last edited by progandy (2024-10-31 09:25:48)

bingma · 2024-10-31 09:52:55

seth wrote:

I disabled DownloadUser and set DisableSandbox, but the iso can't boot.
how did you write it and what adjustments are you trying to make at the bootloader?

I use Ventoy to boot an image, Ventoy allows a USB device to contain multiple system images, allowing people to select an image to boot, so I didn't write the iso to USB directly but put it into Ventoy partition. I added "noautomount noswap" and cow_spacesize parameters.

Lone_Wolf · 2024-10-31 11:40:07

Bingma , you are not the thread starter.
Please start a new thread or use the report button to ask for splitting off post #5 and later to a new thread with you as TS.

seth · 2024-10-31 12:47:41

Also try not-ventoy, write the iso w/ dd.
(Looking around for the DM invocation, ventoy actually showed up as cause)

To be clear: this is the regular install iso or a custom iso you're trying to cook yourself?

bingma · 2024-11-01 04:10:21

seth wrote:

ventoy actually showed up as cause)

No, it's not problem of Ventoy, I saw there're unwanted services in airootfs, e.g cloud-init. I don't want cloud-init to boot over network. So I emptied airootfs, but later, mkarchiso says it requires etc/shadow, so I must copy the shadow file into airootfs; But mkarchiso doesn't hint about other necessary files.

seth · 2024-11-01 07:30:49

Please continue at your new thread, https://bbs.archlinux.org/viewtopic.php?id=300661

Arch Linux

#1 2024-10-19 10:15:41

Archiso not working!

#2 2024-10-19 10:25:27

Re: Archiso not working!

#3 2024-10-19 11:25:10

Re: Archiso not working!

#4 2024-10-20 16:58:12

Re: Archiso not working!

#5 2024-10-31 05:41:11

Re: Archiso not working!

#6 2024-10-31 06:02:15

Re: Archiso not working!

#7 2024-10-31 07:25:01

Re: Archiso not working!

#8 2024-10-31 09:20:18

Re: Archiso not working!

#9 2024-10-31 09:52:55

Re: Archiso not working!

#10 2024-10-31 11:40:07

Re: Archiso not working!

#11 2024-10-31 12:47:41

Re: Archiso not working!

#12 2024-11-01 04:10:21

Re: Archiso not working!

#13 2024-11-01 07:30:49

Re: Archiso not working!

Board footer