# After installing eos pc doesn't boot **URL:** \ **Category:** Newbie\ **Created:** [January 12, 2025, 12:33pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069 "2025-01-12T12:33:15Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 12, 2025, 12:33pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/1 "2025-01-12T12:33:15Z")
after installing and rebooting, the pc remains stuck at “A job is running for …” line: ![IMG_20250112_114225](https://forum.endeavouros.com/uploads/default/original/3X/e/d/ede995288df6ab7edb91e5b3ea8e045f53527df1.jpeg) then I went to check (using chroot) if the uuids in the fstab file match : ![IMG_20250112_114949](https://forum.endeavouros.com/uploads/default/original/3X/e/e/ee73bbc2a08d785590fa46b153c832514d9f451e.jpeg) another person also had this problem (in [this](https://forum.endeavouros.com/t/stuck-on-a-start-job-is-running-for-dev-disk-by-uuid-while-booting-please-help/43048?page=2) post) and solved it by removing resume=… from the grub configuration, but I have no resume. ![IMG_20250112_114103](https://forum.endeavouros.com/uploads/default/original/3X/f/8/f8d1786da9e29c5805c178df9aaf848176d00db0.jpeg) ---
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 12, 2025, 12:39pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/2 "2025-01-12T12:39:42Z")
i will add that this is the third reinstallation done with a flash drive, i have used both balena etcher and the dd command (as it says in the eos site on how to do the install). it always gives the same problem ---
**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 12, 2025, 12:40pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/3 "2025-01-12T12:40:52Z")
Hi @icsp and welcome to the forum, so others can help more you should post some more information, here is a link to guide with that [https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/](https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/) BTW have you tried to boot with other kernels? ---
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 12, 2025, 12:52pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/4 "2025-01-12T12:52:18Z")
yes, i tried with linux-lts but it gives the same problem. using linux-lts (fallback initramfs) it stops one line before (the one where it says “reached target basic system.”) and after a while it appears: ![IMG_20250112_135608](https://forum.endeavouros.com/uploads/default/original/3X/5/7/57ce360a4a2544589032e5260cb81a9453072088.jpeg) To send the logs do i have to use chroot? because when i did journalctl it tells me they are not there. ---
**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 12, 2025, 12:54pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/5 "2025-01-12T12:54:53Z")
I am honestly not too sure but hopefully someone more knowledgeable will be able to help you with this. ---
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 12, 2025, 2:45pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/6 "2025-01-12T14:45:17Z")
I was able to boot. by doing: ```auto sudo mount /dev/nvme0n1p2 /mnt sudo mount /dev/nvme0n1p1 /mnt/boot/efi sudo cat /mnt/var/log/Calamares.log ``` would tell me that the packages were missing: 1. virtualbox-guest-utils 2. qemu-guest-agent 3. spice-vdagent 4. open-vm-tools 5. gtkmm3 6. xf86-input-vmmuose 7. xf86-video-vmware 8. mkinitcpio then I did: ```auto sudo mount -t proc /proc /mnt/proc sudo mount --rebind /sys /mnt/sys sudo mount --rebind /dev /mnt/dev sudo mount --rebind /run /mnt/run ``` I then saw if there was a dns configured with: `sudo cat /mnt/etc/resolv.conf` in my case there was then I did: ```auto sudo arch-chroot /mnt ping 8.8.8.8 ping google.com ``` since the network was working I did: `pacman -Syu` and installed the missing packages then exited chroot and did: `sudo umount -l /mnt` then I closed the terminal and nothing worked, everything I touched said I didn’t have permissions, so I did a forced shutdown of the computer and when it rebooted it went in. I tried it for a while and so far it’s not giving me any problems. ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [January 12, 2025, 4:49pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/7 "2025-01-12T16:49:18Z")
recheck all option in your UEFI motherboard for Endaevouros - secureboot off - csm off - fast boot off - all disks to ahci - no optane , off - no legacy ---
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 13, 2025, 7:16am UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/8 "2025-01-13T07:16:38Z")
Only the fast boot is active, and it was during installation as well. ---
**Author:** ![ricklinux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ricklinux/32/110798_2.png) [@ricklinux](https://forum.endeavouros.com/u/ricklinux)\ **Post date:** [January 13, 2025, 6:42pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/9 "2025-01-13T18:42:25Z")
How could one be missing these packages from installing EOS as per topic title. Most of those aren’t installed on an EOS install. Doesn’t make sense to me. ---
**Author:** ![Dinomonster](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dinomonster/32/137219_2.png) [@Dinomonster](https://forum.endeavouros.com/u/Dinomonster)\ **Post date:** [January 13, 2025, 8:30pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/10 "2025-01-13T20:30:46Z")
Came to my mind that maybe this was some sort of homebrew or something. 🤔 ---
**Author:** ![icsp](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/a183cd/32.png) [@icsp](https://forum.endeavouros.com/u/icsp)\ **Post date:** [January 14, 2025, 7:02pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/11 "2025-01-14T19:02:13Z")
I followed what the installer said. Maybe because I had installed it on an external ssd and then did the install on my pc’s ssd. It still seems strange to me though because to install it on my pc I did a fresh install. ---
**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 14, 2025, 7:09pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/12 "2025-01-14T19:09:33Z")
I’m also confused and trying to make sense of this, about the only thing that I can think is maybe tried to install during live session or tried after without updating mirrors. ---
**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\ **Post date:** [January 16, 2025, 7:09pm UTC](https://forum.endeavouros.com/t/after-installing-eos-pc-doesnt-boot/66069/13 "2025-01-16T19:09:40Z")
Closed on January 16, 2025, 7:09pm UTC This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.