# Having a problem with calamares **URL:** \ **Category:** EndeavourOS installation\ **Created:** [January 27, 2025, 9:38am UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840 "2025-01-27T09:38:05Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 9:38am UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/1 "2025-01-27T09:38:05Z")
I’ve tried to install EOS 3 times but every time, it shows an error: `Main script file /usr/lib/calamares/modules/bootloader/main.py for python job bootloader raised an exception.` Could anyone help me? ---
**Author:** ![smokey](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/smokey/32/133678_2.png) [@smokey](https://forum.endeavouros.com/u/smokey)\ **Post date:** [January 27, 2025, 9:49am UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/2 "2025-01-27T09:49:50Z")
Not really sure from this, can you get a proper log? (there are instructuons/guides top left) ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 9:51am UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/3 "2025-01-27T09:51:37Z")
Do you mean this: [https://termbin.com/zfxl](https://termbin.com/zfxl) ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 3:04pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/4 "2025-01-27T15:04:40Z")
Aren’t there any who can help me? ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 3:14pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/5 "2025-01-27T15:14:26Z")
the log is cut of… is all prepared properly? - secure boot = off - fastboot on possible Windows install disabled - Firmware/Bios set to EFI mode + disable CSM mode for drives and USB - Any RAID is set to off and it uses AHCI mode - installation Media properly created and fully synced to the USB [https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/](https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/) [https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/](https://discovery.endeavouros.com/installation/create-install-media-usb-key/2021/03/) > [@Main.py for python job bootloader raised an exception](https://forum.endeavouros.com/t/main-py-for-python-job-bootloader-raised-an-exception/60237): > > Hello, I’m relatively new in the Linux universe but I have tried quite a few of them and even dual booted with my Windows setup. But when I’m trying to install EndeavourOS with secured boot turned off and systemd-boot, I’m getting this error near the end of the installation when it’s trying to add the bootloader. Here’s the report it generated: [https://termbin.com/b2i8](https://termbin.com/b2i8) Actually I wanted to use sbctl to create and sign bootloader so that I can dual boot with Windows without turning off Secur… show: ` lsblk -f` `sudo fdisk -l` (corrected ;)) ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 3:53pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/6 "2025-01-27T15:53:14Z")
> [@joekamprad](#): > > lsblk -f > lsblk -f > NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS > loop0 squashfs 4.0 0 100% /run/archiso/airootfs > sda > ├─sda1 ntfs 3-DATA A82A04A92A04771A > ├─sda2 ext4 1.0 endeavouros 2af269de-dcf4-4e87-a500-a724b43224c8 > └─sda3 ntfs 4-Drive-C-Exp CA446A2C446A1C07 > sdb iso9660 Joliet Exte EOS\_202409 2024-09-22-10-45-49-00 > ├─sdb1 iso9660 Joliet Exte EOS\_202409 2024-09-22-10-45-49-00 0 100% /run/archiso/bootmnt > └─sdb2 vfat FAT32 ARCHISO\_EFI 66EF-F55D > nvme0n1 > ├─nvme0n1p1 > │ ntfs A 3C9AC0859AC03D60 > ├─nvme0n1p2 > │ ntfs B 8C24AA4924AA365C > ├─nvme0n1p3 > │ ntfs C 1C807B95807B73DC > └─nvme0n1p4 > ntfs D 9A146B2D146B0B97 > [@joekamprad](#): > > sudo fdoisk -l As far as I know, it must be fdisk; so this is the result: > sudo fdisk -l > Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors > Disk model: ST1000LM035-1RK1 > Units: sectors of 1 \* 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disklabel type: dos > Disk identifier: 0x03921640 > > Device Boot Start End Sectors Size Id Type > /dev/sda1 2048 528297983 528295936 251.9G 7 HPFS/NTFS/exFAT > /dev/sda2 528297984 1282422783 754124800 359.6G 83 Linux > /dev/sda3 1282424832 1953521663 671096832 320G 7 HPFS/NTFS/exFAT > > Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors > Disk model: MSI M371 1TB > Units: sectors of 1 \* 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0xbd6cbd6c > > Device Boot Start End Sectors Size Id Type > /dev/nvme0n1p1 \* 2048 8388607 8386560 4G 7 HPFS/NTFS/exFAT > /dev/nvme0n1p2 988823552 1492140031 503316480 240G 7 HPFS/NTFS/exFAT > /dev/nvme0n1p3 1492144128 1953517567 461373440 220G 7 HPFS/NTFS/exFAT > /dev/nvme0n1p4 8388608 988823551 980434944 467.5G 7 HPFS/NTFS/exFAT > > Partition table entries are not in disk order. > > Disk /dev/sdb: 7.5 GiB, 8054112256 bytes, 15730688 sectors > Disk model: Silicon-Power8G > Units: sectors of 1 \* 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0x4a514722 > > Device Boot Start End Sectors Size Id Type > /dev/sdb1 \* 64 5466911 5466848 2.6G 0 Empty > /dev/sdb2 5466912 5798687 331776 162M ef EFI (FAT-12/16/32) > > Disk /dev/loop0: 2.45 GiB, 2635329536 bytes, 5147128 sectors > Units: sectors of 1 \* 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 5:30pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/7 "2025-01-27T17:30:34Z")
Why are there **41 views** but no one helps me? This is very **annoying**! ---
**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\ **Post date:** [January 27, 2025, 5:35pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/8 "2025-01-27T17:35:13Z")
> [@Parsa](#): > > Main script file /usr/lib/calamares/modules/bootloader/main.py for python job bootloader raised an exception. This error doesn’t seem to match the log you shared. The log appears partial. We need a full log that includes the error to actually help you. > [@Parsa](#): > > Why are there **41 views** but no one helps me? > > This is very **annoying**! Please try to be patient. There are lot of people who read the topic but that doesn’t mean they know how to help with your specific issue. Also, keep in mind that we don’t have paid support staff. Everyone here who helps does it solely because they want to and manages it between things like sleep and work. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 5:43pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/9 "2025-01-27T17:43:24Z")
> [@Parsa](#): > > As far as I know, it must be fdisk; so this is the result: 😅 ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 5:44pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/10 "2025-01-27T17:44:13Z")
Thanks a lot for your message. > [@dalto](#): > > This error doesn’t seem to match the log you shared. The log appears partial. > > We need a full log that includes the error to actually help you. I shared everything that I thought might be useful and you wanted. If you want some more detail, please mention it. > [@dalto](#): > > Please try to be patient. There are lot of people who read the topic but that doesn’t mean they know how to help with your specific issue. > > Also, keep in mind that we don’t have paid support staff. Everyone here who helps does it solely because they want to and manages it between things like sleep and work. For that message, I could look offensive because I have a laptop that I have to open every time in live boot. So forgive me if it looks a little bit impolite and excessive. ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 5:46pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/11 "2025-01-27T17:46:49Z")
But please note that every time I send those like messages, you answer. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 5:50pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/12 "2025-01-27T17:50:56Z")
all harddrives are using msdos partition scheme not gpt so seems windows is installed in legacy mode using CSM settings in the Bios. `/dev/sda2 528297984 1282422783 754124800 359.6G 83 Linux` This is where you installed Linux ? Was there another distribution installed before already? ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 5:52pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/13 "2025-01-27T17:52:49Z")
> [@Parsa](#): > > But please note that every time I send those like messages, you answer. Moderators will answer in this case to … moderate and reminding you on the rules. People will most likely help more if you stay calm and friendly. ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 5:55pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/14 "2025-01-27T17:55:13Z")
> [@joekamprad](#): > > This is where you installed Linux ? Actually I haven’t installed any kind of linux in this machine. Every time I tried to install EOS, I failed. > [@joekamprad](#): > > Was there another distribution installed before already? No ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 5:56pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/15 "2025-01-27T17:56:49Z")
I could emphasized very much. Forgive me for that. ---
**Author:** ![thefrog](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/thefrog/32/114250_2.png) [@thefrog](https://forum.endeavouros.com/u/thefrog)\ **Post date:** [January 27, 2025, 5:59pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/16 "2025-01-27T17:59:10Z")
> [@joekamprad](#): > > all harddrives are using msdos partition scheme not gpt so seems windows is installed in legacy mode using CSM settings in the Bios. Please read what @joekamprad posted in his first response. > [@joekamprad](#): > > is all prepared properly? > > - secure boot = off > - fastboot on possible Windows install disabled > - Firmware/Bios set to EFI mode + disable CSM mode for drives and USB > - Any RAID is set to off and it uses AHCI mode > - installation Media properly created and fully synced to the USB ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 6:00pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/17 "2025-01-27T18:00:16Z")
![2025-01-27_18-56](https://forum.endeavouros.com/uploads/default/original/3X/b/3/b3309c9e8b358723815e30c5beb07ef24e39d1d5.png) it installed the OS but failed on bootloader setup… There is no BUG free software so it can happen something bails out in cases… but in general It is strongly recommended to install EndeavourOS in EFI mode if the system is supporting this. in Your case it could be the issue that the liveISO boots in EFI mode but the drive you want to use is in dos scheme not gpt. You can check the booted mode on live session by running `efibootmgr` in terminal it will show an error if its booted in legacy (BIOS) mode. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [January 27, 2025, 6:01pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/18 "2025-01-27T18:01:05Z")
> [@Parsa](#): > > Forgive me for that. no problem you are welcome. ---
**Author:** ![Parsa](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/p/e99b99/32.png) [@Parsa](https://forum.endeavouros.com/u/Parsa)\ **Post date:** [January 27, 2025, 6:04pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/19 "2025-01-27T18:04:45Z")
> [@joekamprad](#): > > it installed the OS but failed on bootloader setup… As far as I know it’s not installed because every time it raised an error. It just renames the partition. > [@joekamprad](#): > > You can check the booted mode on live session by running `efibootmgr` in terminal it will show an error if its booted in legacy (BIOS) mode. > $ efibootmgr > BootCurrent: 0000 > Timeout: 0 seconds > BootOrder: 2001,2002,2003 > Boot0000\* EFI USB Device (UFD 2.0 Silicon-Power8G) PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0x4a514722,0x536b20,0x51000)RC > Boot2001\* EFI USB Device RC > Boot2002\* EFI DVD/CDROM RC > Boot2003\* EFI Network RC ---
**Author:** ![svartsol](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/s/bb73d2/32.png) [@svartsol](https://forum.endeavouros.com/u/svartsol)\ **Post date:** [April 13, 2026, 12:26pm UTC](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840/20 "2026-04-13T12:26:47Z")
Hey, I just wanted to throw in my 50 cent. I had the same problem. I double checked fast boot, secure boot etc. It was all correct set. What helped me finish the task was to use Grub as a bootloader. The screen prior to manage the disc, you have three options. Systemd Grub Or non bootloader. There I picked the grub one and it worked. [Next page](https://forum.endeavouros.com/t/having-a-problem-with-calamares/66840.md?page=2)