How are you clearing the SSD? It would be advisable to create a new GPT partition with gparted and then try running the installer.
This log looks better than before.
The Windows question is still open. And is
- secure boot disabled?
- fast boot disabled (from Windows)?
Edit: it is already late here, hopefully others can help you more today.
-Secure boot is disabled
-I don’t necessarily understand what you mean by fast boot. I have no Windows installed on my laptop.
You have Windows partitions on sda disk.
Not anymore
Edit: but how? I don’t see it
The log near the end shows nfts partitions on /dev/sda.
Well it’s because my SSD isn’t called /dev/sda it is called /dev/nvme0n1
I can’t boot the USB when legacy bios models are turned off.
= = = >Your installation log :
<class ‘OSError’>
[Errno 30] Read-only file system: ‘/tmp/calamares-root-fzqrj498/efi/a6f745e9362949aeac69e927f8d94f7c’
File “/usr/lib/calamares/modules/bootloader/main.py”, line 898, in run
prepare_bootloader(fw_type)
File “/usr/lib/calamares/modules/bootloader/main.py”, line 863, in prepare_bootloader
install_systemd_boot(efi_directory)
File “/usr/lib/calamares/modules/bootloader/main.py”, line 527, in install_systemd_boot
create_systemd_boot_conf(installation_root_path,
File “/usr/lib/calamares/modules/bootloader/main.py”, line 226, in create_systemd_boot_conf
os.makedirs(machine_dir, exist_ok=True)
File “/usr/lib/python3.10/os.py”, line 225, in makedirs
mkdir(name, mode)
Traceback:
File "/usr/lib/calamares/modules/bootloader/main.py", line 898, in run
prepare_bootloader(fw_type)
File "/usr/lib/calamares/modules/bootloader/main.py", line 863, in prepare_bootloader
install_systemd_boot(efi_directory)
File "/usr/lib/calamares/modules/bootloader/main.py", line 527, in install_systemd_boot
create_systemd_boot_conf(installation_root_path,
File "/usr/lib/calamares/modules/bootloader/main.py", line 226, in create_systemd_boot_conf
os.makedirs(machine_dir, exist_ok=True)
File "/usr/lib/python3.10/os.py", line 225, in makedirs
mkdir(name, mode)
2023-04-17 - 10:53:07 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
Calamares will quit when the dialog closes.
2023-04-17 - 10:53:07 [6]: QML Component (default slideshow) deactivated
2023-04-17 - 10:53:07 [6]: void Config::doNotify(bool, bool)
Notification not sent; completion: failed
= = = > Your installation failed.
I had met similar situations in Arch OS, Hefftor OS, and orthers fogotten.
This happened because the os’s configuration doesn’t allow one partition legacy bios boot, so installation failed.
I guess maybe your vfat partition was also damaged, though not sure for that.
Re-install maybe is not your prior choice, since i guess to rescue windows os should be your first priority which probably can only be done with another windows os.
Have you tried removing the Windows drive and then boot?
there could lay the issue…
is usb boot set to CSM or both drives and usb?
[PYTHON JOB]: "|-nvme0n1p1 vfat FAT32 159B-235D 998M 0% /efi 1000M\n"
[PYTHON JOB]: "`-nvme0n1p2 ext4 1.0 endeavouros 41426fb9-87b2-4ade-a281-ded623346d1a 426.5G 1% / 464.8G\n"
as it does install in EFI mode…
Didn’t work
Does the installer allow for this?
Booting up the usb in Legacy and installing in UEFI 
How can I check that?
in your Bios… search for CSM legacy boot or similar…
and on the booted ISO you can check mode in terminal by running efibootmgr
it will show efi boot entries if booted on efi or an error if not…
Your configuration log ::
.. Job 1 "hardwaredetect" +wt 1 tot.wt 1
.. Job 2 "Manage auto-mount settings" +wt 0.111111 tot.wt 1.11111
.. Job 3 "Clear all temporary mounts." +wt 0.111111 tot.wt 1.22222
.. Job 4 "Clear mounts for partitioning operations on /dev/nvme0n1" +wt 0.111111 tot.wt 1.33333
.. Job 5 "Create new gpt partition table on /dev/nvme0n1." +wt 0.111111 tot.wt 1.44444
.. Job 6 "Create new 1000MiB partition on /dev/nvme0n1 (TOSHIBA-RC500)." +wt 0.111111 tot.wt 1.55556
.. Job 7 "Set flags on 1000MiB fat32 partition." +wt 0.111111 tot.wt 1.66667
.. Job 8 "Create new 475935MiB partition on /dev/nvme0n1 (TOSHIBA-RC500) with entries endeavouros." +wt 0.111111 tot.wt 1.77778
Starting job "Create new gpt partition table on /dev/nvme0n1." ( 5 / 42 )
23:51:36 [6]: virtual Calamares::JobResult CreatePartitionTableJob::exec()
Creating new partition table of type “gpt” , uncommitted partitions:
… “unallocated”
… “New Partition”
… “New Partition”
… Running (“lsblk”)
… lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.7G 1 loop /run/archiso/airootfs
sda 8:0 0 931.5G 0 disk
-sda2 8:2 0 912.5G 0 part sdb 8:16 1 14.6G 0 disk -sdb1 8:17 1 14.6G 0 part /run/archiso/bootmnt
nvme0n1 259:0 0 465.8G 0 disk
… Running (“mount”)
… mount output:
.. Running ("pacman", "--noconfirm", "-Rcn", "mkinitcpio")
.. Target cmd: ("pacman", "--noconfirm", "-Rcn", "mkinitcpio") Exit code: 1 output:
error: target not found: mkinitcpio ============== >
[PYTHON JOB]: “Root partition uuid: "41426fb9-87b2-4ade-a281-ded623346d1a"”
… Running (“sh”, “-c”, “which dracut”) ============>
[PYTHON JOB]: “Configuring kernel version 6.2.11-arch1-1”
… Running (“kernel-install”, “add”, “6.2.11-arch1-1”, “/usr/lib/modules/6.2.11-arch1-1/vmlinuz”)
.. Running ("systemctl", "enable", "lightdm.service") =======>
Your configuration concluded ::
- Your windows os is gone (Create new gpt partition table on /dev/nvme0n1, if you want to have dual boot)
- dracut installs the bootloader
- lightdm.service is enabled (some os updates in 6.2.10 or 6.2.11 need to re-enable lightdm.service)
The only suggestion i may have is to check whether complete or not EFI in vfat and /boot/* and /boot/grub/* .
Boot the live ISO,
$ sudo mount /dev/sdX2 /mnt (sdX2 = system / partition)
$ sudo arch-chroot /mnt systemctl enable lightdm.service
$ reboot
Please show us exactly what you did, and provide the full details, including the command(s) you did, and all their output(s). You can use photos too.
Without exact details it is not possible to help you.
Just saying “XYZ did not work” doesn’t give us any info for more troubleshooting.
1 Like