# Not able to boot after fresh install

**URL:** <https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942>\
**Category:** General system\
**Created:** [January 3, 2021, 1:42pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942 "2021-01-03T13:42:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shreyanshkuls](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/s/35a633/32.png) [@shreyanshkuls](https://forum.endeavouros.com/u/shreyanshkuls)\
**Post date:** [January 3, 2021, 1:42pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942/1 "2021-01-03T13:42:13Z")

</div>

I recently bought a new Asus laptop which have both an HDD and an SSD. It had windows already installed on the SSD, so I created a new partition on the SSD and installed EndeavourOS on it. Now when I booted the system from the grub screen, it shows this error.  
 ![VheNcVC](https://forum.endeavouros.com/uploads/default/original/3X/0/4/0411711bf32b7da6493048166340072b7f0da1b1.jpeg)

I looked for the problem online and tried some suggested solutions. I have replaced the `UUID=<UUDI>` part with `/dev/nvme0n1p5` in the `/` mount point entry in `/etc/fstab`, but I still got the same error. I also tried chrooting into the installation and running `mkinitcpio -p linux` but same result.

However I did observe a peculiar thing (atleast according to me). So my current partition scheme looks like this in Windows  
 ![screenshot](https://forum.endeavouros.com/uploads/default/original/3X/6/8/6826763ca10c930e2ffe94d11f998b005b17a70b.png)  
But when I ran `fdisk -l` and `blkid` from the live usb, I only saw partitions on SSD (on `/dev/nvme0n1` disk) and the usb itself (`/dev/sda` disk). I am neither able to see the HDD disk nor its partitions.  
 ![HjzeEzC](https://forum.endeavouros.com/uploads/default/original/3X/a/0/a0864e7c3f946d762c66d49344de006a7a515b1f.jpeg)  
Also when it drops me to the emergency shell after boot fail, I tried running `blkid` from the rootfs prompt. But I only saw the usb drive. Both SSD and HDD were not visible. (Can be seen in the first picture).

I think there is some issue with these disks being not visible during the boot. Please help!

EDIT: My laptop is Asus Vivobook 15, Model Number X513EA-EJ532TS

---

<div class="post-metadata">

**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 3, 2021, 1:58pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942/2 "2021-01-03T13:58:03Z")

</div>

> [@shreyanshkuls](#):
>
> Also when it drops me to the emergency shell after boot fail, I tried running `blkid` from the rootfs prompt. But I only saw the usb drive. Both SSD and HDD were not visible. (Can be seen in the first picture).

I guess that means your initramfs is getting built without support for your disk controller.

Can you share the model number of your laptop? I would be curious to see that hardware specs on that.

---

<div class="post-metadata">

**Author:** ![shreyanshkuls](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/s/35a633/32.png) [@shreyanshkuls](https://forum.endeavouros.com/u/shreyanshkuls)\
**Post date:** [January 3, 2021, 2:36pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942/3 "2021-01-03T14:36:19Z")

</div>

Sure  
It is Asus Vivobook 15, Model Number X513EA-EJ532TS

---

<div class="post-metadata">

**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 3, 2021, 3:03pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942/4 "2021-01-03T15:03:44Z")

</div>

I have seen some other reports of having to add the vmd module to get tiger lake based laptops working. I am not sure if this is your issue or not but worth a shot.

Try booting off the live media and and use [arch-chroot](https://wiki.archlinux.org/index.php/Chroot#Using_arch-chroot) to access your installed system.

Then open up `/etc/mkinitcpio.conf` and add `vmd` to the `MODULES` line. Then run `mkinitcpio -P`.

---

<div class="post-metadata">

**Author:** ![shreyanshkuls](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/s/35a633/32.png) [@shreyanshkuls](https://forum.endeavouros.com/u/shreyanshkuls)\
**Post date:** [January 3, 2021, 4:10pm UTC](https://forum.endeavouros.com/t/not-able-to-boot-after-fresh-install/10942/5 "2021-01-03T16:10:26Z")

</div>

Thank you!!  
It totally worked!
