Installation Failes due to Pacman crashing

General system EndeavourOS installation
1

Hello,

while installing endeavour os on a previously whiped ssd I encounter the error that pacman Crashes withing calameres.

This leads to calamares trying to unmount the filessystem which hangs indevinetly.

This then results in an rsync error -1 or 12.
Or it leads to the message: Installation Failed. The package manager couldnt make changes to the installed system.

Sorry for the bad formatting. I never encountered this problem. Could anyone help me with this?

I can supply logs and stuff if needed

2

If you post the install.log someone maybe could.

Provide Installer Logs (calamares ISO LiveSession):

While you are still on the ISO Live Session logs are stored inside livusers home:

/home/liveuser/endeavour-install.log

You can open with text editor or from file browser, or send via tools (needs internet connection):

cat ~/endeavour-install.log | eos-sendlog

You can simply share the short URL it produces inside a terminal.

3

Hmm, I started the install and still cant see the file in /home/liveuser
Am I missing something?

4

Did you try installing online or offline ?

5

I only tried installing online

6

Which version are you using the latest version or an older version ?

7

https://termbin.com/15nr

This is a log of a failed offline installation

8

When the installation fails, use eos-log-tool. Check the relevant boxes and post the URL.

1 Like
9

I used the latest available ISO on the website

1 Like
10

Hmm,
my DE seems to crash after the failed installation. The only thing I can do is reboot my system.
But the above link is a a canceled install that failed. So it should help determining the problem

11 
void Calamares::RequirementsChecker::addCheckedRequirements(Calamares::Module*)
2025-04-23 - 17:02:08 [6]:     Got 5 requirement results from "welcome" 
2025-04-23 - 17:02:08 [6]:     .. Loading "/etc/calamares/branding/endeavouros/show.qml" 
2025-04-23 - 17:02:08 [6]:     .. No translation for "kb_" "de" using default (en) 
2025-04-23 - 17:02:08 [6]: void Calamares::QmlViewStep::loadComplete()
2025-04-23 - 17:02:08 [6]:     QML component "qrc:/packagechooserq.qml" QQmlComponent::Ready 
2025-04-23 - 17:02:08 [6]:     .. QML component complete "qrc:/packagechooserq.qml" creating object 
2025-04-23 - 17:02:08 [6]: DEBUG (Qt): getting temp failed for  "/dev/nvme0n1" :  No such file or directory
2025-04-23 - 17:02:08 [6]: DEBUG (Qt): getting powered on time failed for  "/dev/nvme0n1" :  No such file or directory
2025-04-23 - 17:02:08 [6]: DEBUG (Qt): getting power cycles failed for  "/dev/nvme0n1" :  No such file or directory
2025-04-23 - 17:02:09 [6]: DEBUG (Qt): smartctl initialization failed for  "/dev/sdb" :  No such file or directory
2025-04-23 - 17:02:09 [6]: DEBUG (Qt): error during smart output parsing for  "/dev/sdb" :  No such file or directory
2025-04-23 - 17:02:09 [2]: WARNING (Qt): unknown file system type  "dos"  on  "/dev/sdb"

Thats the only thing that seems weird. But I ereased my m2 ssd multiple times. I dont see how there could be an instance of DOS on there…

12

I know tried creating a new partitions on the ssd and a new partition table on the other harddrive.

I am currently running the offline isntaller again

13

https://termbin.com/w0b6

Is the new log

I found the following reddit-thread:

https://www.reddit.com/r/archcraft/comments/w8zyjh/archcraft_installation_hangup_calamares_unable_to/

Could this be my problem. When using gparted it shows locks on my partitions

14

https://termbin.com/1bmj

New logs…

15

Before starting the installer (Calamares), you could use partitionmanager to create a new GPT on your disk. This will erase every partition and data on the disk so do this if you will be installing EOS on the whole disk.

1 Like
16

https://termbin.com/rtya

These are the results with a new partition-table

It says something about there being a read-only filesystem. This smells like a permission problem. Can I somehow say calamares to use the superuser?

17

You could try a manual install.
I would do this:
Reboot the Live ISO.
Create a new GPT.
Make 2 partitions:

  1. 2048 MiB FAT32
  2. the rest of the disk, filesystem of your choice: EXT4 or Btrfs (for example)

Start the installer. Choose manual installation.

Mount the FAT32 partition at /efi flag boot
Mount the other partition at /

Go with the default for the rest.